Game Optimization

Fortress-Forever has been out for 2 years now and the mod still has quite a bit of choke/lag in a full 22 slot server.

Myself and a few others have spent some hours so far watching the network traffic as certain things happened in the game.

Here is a list I started of some of the bigger traffic hogs along with possible solutions on how they might be fixed.

If while reading this you are thinking, how in the hell could that cause problems, just go into the game, turn on net_graph 2, and test for yourself.

-----------------------------------------

Tossing medpacks:
+ Add a ~0.2 delay.

All grenades/pipes:
+ Don't play a bounce sound within ~0.2 seconds of each other.

Emp explosions:
+ a) Only allow a max of 3 dropped bags have an explosion temp ent.
+ b) Make bags explode 1 after another (short delay after each explode).

Blood:
+ Check if blood decal can be drawn in origin.
+ Only allow 1 decal per trace (shotguns are a huge problem right now).

Client Spawn/Death (really seems the sounds have too much data here?):
+ Delay sounds so they are sent on a different packet than the initial spawn/death.

Sentry Guns:
+ Reduce muzzleflash and tracer temp ents (same method that was used for reducing hwguy tracers).

Mirv Greade (the initial explosion seriously needs changed, packet is to big):
- This grenade needs a bit reworked to get optimized.
- Since it's in dire need of being optimized, bear with me while I explain how the new mirv works.
1) Throw the mirv.
2) Instead of the mirv exploding once and releasing 4 mirvlets it will:
+ The mirv will explode 4 times with a very short delay between explosions, each explosion releasing a mirvlet.
+ Each explosion will only be 1/4 the damage of the current mirv (so it equals the same damage).
3) When all the mirvlets are released it will continue as it currently works.

Napalm Grenade (these are a nightmare, just look at net_graph 2):
- Not even going to try and think of a way to optimize these, they need reworked imo.