global config
•
29 Jan 2011, 19:38
•
Journals
Could the person that's in charge of the global config please finally fix the bugs in it.
It's kinda annoying that u get random fullspawns if u die of ur own explosive, especially in 5v5 where u can't miss anyone.
explanation for the one that don't know about it;
if u go kamikaze with a nade before ur spawn - u can't tap fast enough and get fullspawn.
thx :)
It's kinda annoying that u get random fullspawns if u die of ur own explosive, especially in 5v5 where u can't miss anyone.
explanation for the one that don't know about it;
if u go kamikaze with a nade before ur spawn - u can't tap fast enough and get fullspawn.
thx :)
You just do not make any sense.
Because without this fucking command, you can block some truck/tank, and many other thing i'will not share.
But agree, that suck.
Download that, extract to your server's /etpro/ and replace all files it asks to (it just replaces the winter configs).
With this, the configs now use the combinedfixes.lua from the last 'Global' configs from 2010 spring or so, which don't have the forcetapout bugfix bug. It's also certified so nobody will notice anything - I also doubt anyone will miss the fixes in the first place.
2010 global configs were the last good ones ;__;
some years ago chaplja published a certify tool with that u can do it by ur own.
izi -,-
every new cfg = shit :\