squeek502 opened issue fortressforever/fortressforever-scripts#17 ('Add a wiki article with instructions on translating FF')

View on Github

alaswell created fortressforever/fortressforever-scripts:features/id-round-timer at 274fbd (+1 new commit)

• 274fbd alaswell: 'Adds a very basic round timer system to base_id.lua. Updates ksour.lua and napoli.lua to utilize it'

View on Github

alaswell opened pull request fortressforever/fortressforever-scripts#18 ('Adds a very basic round timer system to base_id.lua')

View on Github

squeek502 commented on commit fortressforever/fortressforever-scripts@4edd5a:

@R00Ki3, seems like a good idea. You want to submit it as a pull request?

View on Github

squeek502 commented on issue fortressforever/fortressforever-scripts#18 ('Adds a very basic round timer system to base_id.lua'):

So something that wasn't addressed in fortressforever/fortressforever#60 but needs to be fixed in my opinion is that the scoring in ID feels (or is) really arbitrary, and it's unclear why a certain team is winning or wins in the end.

This might need to be addressed by giving the defending team...

View on Github

squeek502 created repository fortressforever/fortressforever-media

View on Github

R00Ki3 opened pull request fortressforever/fortressforever-scripts#19 ('Features/sniper-bullet nails')

View on Github

squeek502 pushed 1 commit to fortressforever/fortressforever-media:master

• 3c399e squeek502: 'Add FF logo svg files'

View on Github

squeek502 commented on issue fortressforever/fortressforever-scripts#19 ('Features/sniper-bullet nails'):

It'd be good if you could remove that merge commit. What git client are you using? Or, are you just using the Github web interface?

View on Github

R00Ki3 commented on issue fortressforever/fortressforever-scripts#19 ('Features/sniper-bullet nails'):

I'm using the web interface. i never pulled anything before LOL let me try again.

View on Github

R00Ki3 opened pull request fortressforever/fortressforever-scripts#20 ('Features/sniper nails-2 ')

View on Github

R00Ki3 closed without merging pull request fortressforever/fortressforever-scripts#19 ('Features/sniper-bullet nails')

View on Github

R00Ki3 commented on issue fortressforever/fortressforever-scripts#20 ('Features/sniper nails-2 '):

Here's the second try. Hope this works out.

View on Github

squeek502 commented on issue fortressforever/fortressforever-scripts#20 ('Features/sniper nails-2 '):

Looks good, thanks!

View on Github

squeek502 merged pull request fortressforever/fortressforever-scripts#20 ('Features/sniper nails-2 ') from R00Ki3 to master

View on Github

alaswell commented on issue fortressforever/fortressforever-scripts#18 ('Adds a very basic round timer system to base_id.lua'):

I totally agree, and I actually looked into all of this when I was considering giving the D points for a hold, but ultimately decided that it wasn't really fair to give them 2 points every 30 seconds and then give them a huge lump sum of points at the end of the round timer too, while O only gets...

View on Github

R00Ki3 opened issue fortressforever/fortressforever#118 ('Add lua callback when life or armor is gained')

View on Github

BullyFF commented on issue fortressforever/fortressforever#101 ('Add effect/sound while sharking'):

FFshark2 and FFsharkloop added

View on Github

squeek502 commented on issue fortressforever/fortressforever#101 ('Add effect/sound while sharking'):

I think those are too bubbly.

I was imagining something like this: http://www.soundsnap.com/boatwake

View on Github

BullyFF commented on issue fortressforever/fortressforever#101 ('Add effect/sound while sharking'):

FFsharkloop2 added

View on Github

BullyFF commented on issue fortressforever/fortressforever#115 ('Sound for scout movement weapon'):

FFjumpgun1 added

View on Github

squeek502 commented on issue fortressforever/fortressforever#101 ('Add effect/sound while sharking'):

Nice, I think that might sound pretty good. Will be able to give more feedback once I implement it. :+1:

View on Github

squeek502 commented on issue fortressforever/fortressforever#115 ('Sound for scout movement weapon'):

Nice work, I like that a lot. Note that it might end up having to be shortened, though, but I'm not sure about that yet.

Adding a direct link to it for quick reference in the future: https://soundcloud.com/tudberry/ffjumpgun1?in=tudberry/sets/ffsoundstuff

View on Github

alaswell created fortressforever/fortressforever-scripts:features/ctf-security-timer at ee2e31 (+1 new commit)

• ee2e31 alaswell: 'adds a timer on the HUD that reflects how long security is down for'

View on Github

alaswell opened pull request fortressforever/fortressforever-scripts#21 ('adds a timer on the HUD that reflects how long security is down for')

View on Github

squeek502 commented on issue fortressforever/fortressforever-scripts#21 ('adds a timer on the HUD that reflects how long security is down for'):

Good idea. A few questions:

* Why is it added with SECURITY_LENGTH + 1?
* Mushy's security maps have this as well, but it gets added inside of the security icon. I forget if there are any issues with it being drawn below the icon.

View on Github

alaswell commented on issue fortressforever/fortressforever-scripts#21 ('adds a timer on the HUD that reflects how long security is down for'):

It seems to take about a second for it to show up on the HUD, so adding 1 get's it to sync properly with the 10 second announcement schedule and end right as the enabled icon gets drawn...although that could just be me/my computer so testing that would be good.

I thought I had seen it somewhere...

View on Github

squeek502 opened issue fortressforever/fortressforever#119 ('Add player_onuse callback')

View on Github

squeek502 opened issue fortressforever/fortressforever#120 ('Add Lua function to get all triggers a player is touching/inside')

View on Github

squeek502 created repository fortressforever/fortressforever-maps

View on Github

squeek502 pushed 1 commit to fortressforever/fortressforever-maps:master

• 211a80 squeek502: 'Latest map source files (some *might* be out of date)'

View on Github

squeek502 opened issue fortressforever/fortressforever-maps#1 ('Need a verified, up-to-date Hammer setup guide in the README')

View on Github

R00Ki3 commented on issue fortressforever/fortressforever-maps#1 ('Need a verified, up-to-date Hammer setup guide in the README'):

I could try to set this up. You want it set up to use the current ff steam beta? you want me to use the online wiki with pictures? or an independent html file? or what?

View on Github

squeek502 commented on issue fortressforever/fortressforever-maps#1 ('Need a verified, up-to-date Hammer setup guide in the README'):

Not sure. Anywhere is good for now, and then we can have it mirrored (or linked) where ever its relevant.

It should be from the perspective of a brand new Steam install with zero other games installed. Also, it should be for the Steam version of the game rather than the /sourcemods/...

View on Github

R00Ki3 commented on issue fortressforever/fortressforever-maps#1 ('Need a verified, up-to-date Hammer setup guide in the README'):

Sounds like a good idea with the VM. I'll do the same.

View on Github

squeek502 closed issue fortressforever/fortressforever-maps#1 ('Need a verified, up-to-date Hammer setup guide in the README')

View on Github

squeek502 pushed 1 commit to fortressforever/fortressforever-maps:master

• f25604 squeek502: 'Add instructions to setting up Hammer for Steam FF. * Closes #1'

View on Github

squeek502 pushed 1 commit to fortressforever/fortressforever-maps:master

• 043417 squeek502: 'Small clarification'

View on Github

squeek502 pushed 1 commit to fortressforever/fortressforever-maps:master

• b12a45 squeek502: 'Fix "GameExeDir"'

View on Github

squeek502 created fortressforever/fortressforever-scripts:fixes/hammer-gameinfo at 31e295 (+1 new commit)

• 31e295 squeek502: 'Update gameinfo.txt SearchPaths to work with the new Hammer setup. * See also...'

View on Github