CB kicks out new config
•
10 May 2007, 15:11
•
News
ClanBase is proud to announce the release of a new set of configs today.Due to the recent discovery of several significant exploits against Enemy Territory servers, ClanBase has released a new config pack. It includes a LUA module provided by the ETPro team which will fix and secure your game server.
This new config also contains the map script hashes and some minor cvar tweaks and fixes.
We also want to add we are open to any suggestions you could do to improve it.
Important Note
This set of config are the official release from ClanBase Enemy Territory and must be used in all matches.
All servers to be used for any match at ClanBase must be updated with this configs.
All old configs are deprecated and must not be used anymore.
Any match not using this config after May 14th, 2007 will be cancelled.
How to install
Just copy the combinedfixes.lua to your server etpro folder and the config files to the etpro/configs.
Detailed list of changes
* fix several game server exploits by the ETPro lua module
* com_maxfps IN 40 125 (fix the spread bug exploit)
* r_depthbits IN 24 32 (fix some texture exploits)
* match_mutespecs removed (spectators can now be muted)
* g_noTeamSwitching 1 (players will not be allowed to switch teams accidentally during game)
* mines in battery removed
* added new maps and their timelimits
* map script hashes added for all maps
You can download the configs here: ClanBase Enemy Territory official config pack
najs
i wont get ownd by mztik´s spawnscript anymore :D
No more spreadlaming!!! Reya1p said he might be fixing the bugged spread so it still feels the same as the old spread, but makes it fps undependend. Once the spread is fixed the fps cvar could be unrestricted again.
bah naab
Add cl_maxpackets 100
For some1 who has a bad connection anyway maxpackets 60 are very usefull.
+
Posted by Angrykid on Thursday 10th May 2007, 17:11
=
DOES NOT COMPUTE
and nice changes
"Any person not already following this new law is stupid."
com_maxfps IN 40 125 (fix the spread bug exploit)
* mines in battery removed
nice!
FU!!
well done. cheers
://///////////////////////////////////////////////////////
i cant rly see any difference shooting to 100 or 40 maxpackets guys...
its just the easiest thing you all guys whine about when you cant hit a shit
texture exploits = ?
with some values of com_maxfps your spread is being reduced (q3 engine :P)
btw you could never have maxfps 1 on cb config :) it was > 41 if im correct
2) With depthbits 16 you could see through the walls at some points, if the opponent behind the wall was close enough to it, e.g near the upstairs window above the main entrance at supply crane. Didn't apply for older graphic cards tho, never had that problem with my old Gf3.
Yes there are no additional programs used, only abusing cfg.
http://www.warleagues.com/viewnews.asp?view=598
:)
this is ridiculous..
i also use 76 or 152fps .. to sync to my monitor / mpackets..
i think they don't know shit at all about this.
spreadbug .. wtf? .. WHAT SPREADBUG ??
i have the same fuck spread with 76fps AND 166fps ..
ridiculous cuntz not knowing shit about the engine
but yes limiting fps to under 200 would have been enough to get rid of the abuse
people use 152(166) fps because of syncronisations not because of some spreadbug..
atleast not me!
i double my sync and never thought about some stupid spreadbug.
i even played with 3 or 4 times more than my vsync fps.
but i got told the ETPRO team is workin on this "BUG" ..
weird just that you actually don't hit more or better or have a higher acrcy with a higher fps rate.. just ridiculous crap if you ask me ..
if it is so, then also with 125fps, or not?
125-175 should NOT be any difference, everything above migth lead to some faggot bugs, yeah.
with 300fps you here your footsteps like 1 every 3-5 steps :)
but saying that syncing is an advantage .. pls ;) ..
And just because you never noticed it, doesn't mean it doesn't exist. The bug can be easily verified.
If you use a polling rate of 125Hz any higher frame rates than 125fps will lead to a more or less significant spread reduction. Another example: 166fps should result in 1/2 of the normal spread.
I guess, there might even be a way around the 125fps limit.
EDIT: nice removing your comment :-)
not everybody got skilled MG-42 operators
mg42 is only good for a few stages on a few maps
same for airstrikes, you can use them on a few stages and then its possible to kill the whole team with only 1 spawnkill (goldrush)
so isnt it overpowered too?
rifle overpowered ?? medics overpowered when they heal themself?
but you can always see the mg42-soldier and kill him
Thats why sten overheats, assault rifle has insane spread, rifle has a constant spread etc.
you mean submachinegun? :P
Fallschirmjägergewehr 42 (aka. FG42)
Sturmgewehr 44 (aka. StG44)
There is no reason to force the average player to use a config aimed at the best of ET. Forcing israelis to play 60 maxpackets is bullshit, same as needing at least 60 fps when playing ESL config.
Besides, I'm sure that with a little experience any good team can take out the mg, just like it you rape mg's on grush or supply. Maybe the mg could be removed on bremen like it was on battery. I say we wait some more and give teams a chance to adapt to the mg, prolly counter it in the future.
ignorant spaintard
in most settings in ET, it's either 16 or 32 bits, but what *I* always thought, was that r_depthbits used 24 instead of 32; (16 lowest, 24 highest)
so what confuses me is that the new CB CVAR gives you the choice between 24 and 32 -- which I believe is the same.
please correct me if I'm wrong, but explain how as well. thx.
To this time you could use 16 OR 24 OR 32.
Now cfg limits this by allowing you to have either 24 OR 32 as long as it's not 16 (cause then we have less than 8 bits per color) and in some moment in the game something might not de displayed resulting in wallhack-like feature.
And yes, there's practically no difference between 24 and 32. You can see the difference at some point of projecting graphics. then alpha channels are used as transparency.
so the new CB config doesn't only give you the choice between 24 and 32 but mainly it permits you using 16.
never mind
should have been released before this season tho
config is fixing a lot of bugs, nothing you can complain about. I guess CB should have an open discussion with the scene after this season to see if mg or other stuff should be changed.
The only thing that I was really looking forward too.
so useless imo ;<
now u can't abuse fps s1l anymore :<
There goes 50 fps :(