Latest Github Events

[FF_Team]

muldy opened issue fortressforever/fortressforever#223 ('Team Balancing Public server [SERVER side setting]')

View on Github

[FF_Team]

muldy commented on issue fortressforever/fortressforever#216 ('Examine possibilities for a 3rd offense class in competitive play'):

Medic class on the offence... it's only because he has concussion grenades...
Give the HW guy concussion grenades and he goes on the offence...
We don't see them healing playmates..., only flying around the maps (literally), for that we have scouts.

Any class with "The mighty concussion...

View on Github

[FF_Team]

fpsmoto commented on issue fortressforever/fortressforever#222 ('Fix cl_spawnweapon_spy tranq'):

Is this also an issue for the class cfg files with the ffc_spawnslot cvar? I can't seem to get them to work for any class.

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever#222 ('Fix cl_spawnweapon_spy tranq'):

What is ffc_spawnslot? Searching 'spawnslot' in this repo turns up no results.

View on Github

[FF_Team]

fpsmoto commented on issue fortressforever/fortressforever#222 ('Fix cl_spawnweapon_spy tranq'):

I got it from the FF wiki page here:
http://www.fortress-forever.com/wiki/index.php?title=Category:Cvars

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever#222 ('Fix cl_spawnweapon_spy tranq'):

Yeah, almost all the info on that page is incorrect (if you check the history, it hasn't been meaningfully updated since July 2006). ffc_ cvars don't exist.

View on Github

[FF_Team]

alaswell created fortressforever/fortressforever-scripts:features/disabling-security-rewards at 827af8 (+1 new commit)

• 827af8 alaswell: 'gives a player fortress points and displays a HUD message whenever a player disables security'

View on Github

[FF_Team]

alaswell opened pull request fortressforever/fortressforever-scripts#47 ('gives a player fortress points and displays a HUD message whenever a …')

View on Github

[FF_Team]

alaswell commented on issue fortressforever/fortressforever#212 ('Add in-game on-screen keyboard functionality'):

looks great :+1:

View on Github

[FF_Team]

R00Ki3 commented on issue fortressforever/fortressforever#223 ('Team Balancing Public server [SERVER side setting]'):

I have something like this as a [lua plugin](http://forums.fortress-forever.com/showthread.php?t=24502) but it's not perfect. If we get lua cvars implemented I could work on it more and make it easy to use with a cvar.

View on Github

[FF_Team]

ddm999 commented on issue fortressforever/fortressforever-maps#4 ('2d model wireframe/model picker not working with standalone setup'):

Using the Source SDK 2013 Multiplayer version of the editor models copied to FF's HL2 directory works fine for me in both 3D and 2D viewports.


View on Github

[FF_Team]

ddm999 commented on issue fortressforever/fortressforever#219 ('Make sniper deck ladder in ff_aardvark team-only or remove it altogether'):

Perhaps with a team-only elevator replacing the ladder?
Did a quick 30 min mockup in Hammer here:

Alternative could be a vent with a team-only door on. (Like the middle...

View on Github

[FF_Team]

fpsmoto commented on issue fortressforever/fortressforever#219 ('Make sniper deck ladder in ff_aardvark team-only or remove it altogether'):

I like that, though how about making that wall from the plat to the floor span around the whole platform and have the lift where it is on the side, but as an indented part of the platform. Here's a quick mock up:
http://mildsclan.com/mockup.png

View on Github

[FF_Team]

ddm999 commented on issue fortressforever/fortressforever#219 ('Make sniper deck ladder in ff_aardvark team-only or remove it altogether'):

More like this, then:

Having it like this also means less of the cliffside on the right gets cut out, and that also means the little pathway to it is more concealed.

View on Github

[FF_Team]

fpsmoto commented on issue fortressforever/fortressforever#219 ('Make sniper deck ladder in ff_aardvark team-only or remove it altogether'):

Yeah that looks great.

View on Github

[FF_Team]

fpsmoto opened issue fortressforever/fortressforever#224 ('Pyro Rework ideas')

View on Github

[FF_Team]

Chickenprotector commented on issue fortressforever/fortressforever#224 ('Pyro Rework ideas'):

Speed DOES NOT need to be nerfed when using it, it defeats the purpose of how the pyro's supposed to play, on offense or on defense. The primary role of a pyro is DPS. Plain and simple. In other words, clearing out the enemy be it a boat load of scouts, medics, or such on offense or eliminating an...

View on Github

[FF_Team]

fpsmoto commented on issue fortressforever/fortressforever#224 ('Pyro Rework ideas'):

The problem is Pyro is as fast as 4 out of 5 FF classes, so when hit by a flamethrower, a lot of the time it's impossible to escape. With the speed decrease while using it, you'd still be able to alternate between bhopping and firing the flamethrower to maintain some of your speed. It's either that...

View on Github

[FF_Team]

ddm999 opened issue fortressforever/fortressforever#225 ('Cleanup spectator menu')

View on Github

[FF_Team]

FDA- commented on issue fortressforever/fortressforever#224 ('Pyro Rework ideas'):

Remove afterburn entirely. Cross post from https://github.com/fortressforever/fortressforever/issues/216

"I think after burn is a largely undeserved reward for a relatively easy application, and I don't really think DoT type mechanics really belong in an FPS. It's just not a fun interaction. I...

View on Github