Recently, WL released its own config. Having heard so many troubled tales about the Global Config, I decided to check out the three configs made by ESL, WL and CB. So what did this investigation turn up. An endless list of commands, the configs looked totally different and it took me over 5 minutes to find these big differences:
Quite an impossible list to overcome ...
[img]http://tbn0.google.com/images?q=tbn:3yDhtrHzX33TGM:http://www.sproe.com/images/screenshots/mg42-01-large.jpg[/img][img]http://tbn0.google.com/images?q=tbn:3yDhtrHzX33TGM:http://www.sproe.com/images/screenshots/mg42-01-large.jpg[/img][img]http://tbn0.google.com/images?q=tbn:3yDhtrHzX33TGM:http://www.sproe.com/images/screenshots/mg42-01-large.jpg[/img][img]http://tbn0.google.com/images?q=tbn:3yDhtrHzX33TGM:http://www.sproe.com/images/screenshots/mg42-01-large.jpg[/img]
In my personal opinion, the mg matter should be open to public debate, not three people battling it out on a personal level. I know this community whines a lot, but our voices should be heard even if 90% of them are total crap. People want a global config, just take the best of both worlds: the global configs mg removal and use CB's more tolerant netsettings.
It's a global config. If it is really such an issue allow for tolerant settings. Forcing higher packets wont solve packetloss. Forcing higher fps will only screw over ppl with a shit pc, it will not affect you. Rate is the information you download from the gameserver. It only affects the way how you see the ET gameworld, forcing it IN 20000 25000 like WL did seems pretty pointless. Cg_autoaction 7 means demos get recorded automaticly. Seeing all leagues demand you to record demos of officials this could be turned on, anyway its nothing that could stop a global config.
Aside from these settings, the only differences are some LUA fixes and a md5 list for checking cheats, which is another pointless feature as you have to update the config once every two months or so. There's also some streaming issues that have to do with the config, but these should get resolved in the near future.
I demand, in name of the community, that the respective config makers from ESL, WL and CB put aside their differences and give us a global config.
Shoutouts:
Dr3am for making the Scary Config pic
Frop and Donex for all the information.Download all current 6v6 configs
a medic has 140 hp, 3 headshots without helmetprotection would do 150 damage, 3 headshots with helmetprotection would do 140 damage, 2 headshots and 2 bodyshots without helmetprotection would do 136 damage, 2 headshots and 2 bodyshots with helmetprotection would do 126 damage.
So forcing the helmetprotection to 0 would be the best option imo. in short:
- no fast ROF so a lucky med regen time = you're screwed over for at least 18hp of your own
- it doesnt change anything if you shoot only 2hs, just for the 3hs you shoot
OVERDRIVE HAVE MY BABIEZPLOX
I guess you're actually gonna have to LOOK at your opponent to see if he's dead and not rely on the 3 clings... and since you're gonna be doing that anyway (as you are aiming at him) I don't really see a problem... Why should you be able to kill someone without getting shot back at?`It's good if you lose some hp too...
"2 headshots and 2 bodyshots without helmetprotection would do 136 damage, 2 headshots and 2 bodyshots with helmetprotection would do 126 damage."
And what's this supposed to mean? It doesn't make a difference.. you still need 2 hs and 3 bodies to kill a med and 2hs and 2 bodies for anyone else... with or without helmetprotection...
So no whine... helmetprotection is the win.
medpacks for win!
Unless of course distance falloff comes into play, in which case you'll need three dozen headshots. :P
A team with one medic gets +10 hp per non-medic class, so that would mean a team with 1 or 2 medics gets +10 or +20 hp extra, so a fieldops would only die from 2hs without helmetprotection if a team doesn't have a medic at all but i can't think of a situation where a team wouldn't use a medic :P
(O:
Frop and others tried their damndest to get a global config when this problem last arose, in the end he got ESL, CF and WL to agree to a config. Now its just CF and ESL on one side, CB on another, WL on another.
However its a case of Frop trying as much as humanly possible and last time DoneX not wanting to budge, CB's latest cfg seems to be a bit of a move next to ESL/CF but the MG42 still remains. WL I didnt know had released another
There should be a public debate before next season, personal issues should be set aside.
Wouldn't know why. It can only be a good thing to get your server streaming & it generates no lag afaik...
Would make it possible for the leagues next to WL to know that their bans will actually be working as they won't be able to connect to anny matchserver annymore unless they change pb-guid...
cl_maxpackets IN [40-100]
rate [16000 - 25000]
forcecvar cg_autoaction [7]
that should be in the global config, mg/helmetprotection i dont care that much
- no MG (lame weapon)
- 4 mines (spam reduction!!!)
- helmetprotection 1 (what would the meaning of helmet be then? not rly, more gling gling is better for fragmovies)
- maxfps 40-125 (whatever)
- rate 15000-25000 (no impact on game anyway)
- maxpackets 40-100 (the same ^^)
- panzer rechargetime 25 sec
- no nades for medics xD (spam reduction, tho they could have 1 nade after picking ammo pack)
such as prone was ='(
I personally hate mg42 to, but it's part of the game imo =(
And I don't agree on the mines.. mines aren't all that helpful except for maps like supply (removed from most mappools) and goldrush (where it's just a part of the map).
Agree with the panzer charge time tho. Panzer without cp -> 25 secs, with CP 20 secs :)
and the "fops giving out ammo insetad of spamming random artis" will get more attention maybe
lol pls leave it. its not broken. dont fix it.
xD
luckily he is a nice aimer with smg nowadays as well :)
J/K, it would be too good if they increased waiting time that much ;-)
I would give it a thought or two.
as far as i know there is no bug in ET like in RtCW o_O
who cares about these 5 peeps :]
But by all means, enjoy some cheese with your whine.
(Ofc I can't say what's the exact fps amount or anything but I can make difference between 125,200 and 333 with 60Hz)
btw u can have the cheese all by yourself and when eating try tracking with low mouse rate yourself and u understand it's no need to disable abusing that "bug"
but if someone likes, it should be allowed. And capping fps sucks, because I could imagine playing with higher than 125 and often try it as well (Not because of spread but to make it run smoother)
not necessary to fix this tbh
I tried it out when madscie released info about this like a year ago, and it really worked, BUT playing with such a low mouse rate gives u much disadvantage compared to players who play with let's say stable 500 Hz, so I decided not to go that way, although I easily could have made stable 250 or even more fps with my PC. And if someone is playing with ballmouse, he should get some credit for that and I would just consider it as tweaking, because u need some knowledge to put things go that way..
And it really didn't help so much that it should be disallowed, not by any means, because being able to track better is much more effective.
And there are ppl who just want ET to run smoother, so they want more fps. And don't say that u won't notice difference between 125 or more, because that's utter bs. Even with a low display refresh rate TFT can show the difference in fps.
and remember, I got 125 fps myself, so I'm standing on neutral ground in here...
and I still repeat myself, putting a low mouse rate disturbs your tracking abilities which makes aiming a lot harder
Because it's not usual to see new mice without the rateswitcher option in the drivers nowadays, and still i dont see any problem besides maybe 5 more mins if something goes wrong when changing it in lan.
abort and me fucked up 2 computers until we noticed the only way to change the rate was doing it with the raziel tool and disabling the "on air" switch, that was the only way to make it work without crashing, every tool else would have made the computers crash once again.
Of course i get your point, it's more work for the admins and more chances of having to fix computers, but doing a prelan testing would solve it in my opinion, and since you would be able to allow players to change it, everyone will be able to use the rate they want so we can let the etpro guys fix the spread bug without having to change more things around the problem itself.
Or you could just disallow it like just like all major LANS and ET:QW future lans :P
However does anyone care? On few lans, on which i have been, changing usbrate was prohibited and ofcorse everyone (at least all polish) was changing it anyway :P
And yes, you can do whatever you want in smaller lans, same here in spain where in the most of them, et players have no clue about what the hell mouserate is.
You did forget knockback in the equation. ESL uses a different knockback than the rest IIRC (800 vs 1000). So that's another point to agree on.
EDIT: just double checked and it's not ESL, who uses 800 then?
Lowering knockback would benefit the natural aimers, wouldn't it?
I would also like to see an ET without aimspread, but etpro will never implement such a feature.
rate 25000
I'm happy with those, spread should stay, if you played in the xonx-server with mad"theres no lag in et"scientists config, you noticed how incredibly easy it is. Damage knockbacks and such should stay. Dont care about fpscaps as ill never get over 140 anyways, but 40-125 sounds ok.
you're just one of those guys who can only do singlepanzers, thats why u want the "useless" stuff away. making chargetime longer would just make panzer useless.
rate 25000
com_maxfps 60-125
cl_maxpackets 60-100
no helmetprotection
rate 15000-25000
maxpackets 40-100
maxfps 41-125
autoaction 7 (I always forgot to record in offis)
simpleitems 1
b_helmetprotection 0 - 1 i dont care
rate 25000
com_maxfps 60-125 <---seems to be okey if you cant even get 60 fps stop gaming afaik.
cl_maxpackets 60-100 <---netlamers suck so 60 - 100 is okey.
And the thing on the MG...if you have a good rifle np?
b_helmetprotection [0]
com_maxfps IN [60-125]
cl_maxpackets IN [60-100]
rate [15000 - 25000]
forcecvar cg_autoaction [7]
b_simpleitems [0-1]
oh and regeneration of health is useless too. its just makes medics maybey a bit lucky as perfo already told
But if you want to make a good config, make one where all spam weapons are removed (no riflenades, heavy weaps, less mines, only one support/arty at a time, and half the nades for engys (max4, 2 when spawning)
Big changes for the better (OO:
rate -> 25000
maxpackets -> 76 - 100
maybe you can even force swapinterval to "1"
afaik it forces maxpackets + fps to the value of your HZ, right ?!
(greetz to low fps pc's)
PS: change et to 5on5
Something else,
SW_Goldrush_te should be changed at the tank depot and at the bank courtyard because it's sometimes impossible to get the objectives done with mines well placed. Maybe change the terrain on a few places so there can't be mines placed?
And I think autoaction should be only SS because that is also an evidence for results and that the auto demo's will be deleted because it's quite annoying if I play on a public server ( YES I DO ) and it will automaticly starts recording a demo.
Or am I retarded?
b_helmetprotection 1
com_maxfps IN 40-166
cl_maxpackets IN 30-100
rate 10000 - 25000
cg_autoaction 0
b_simpleitems 0
- 3 mines max
- no nades for medics after spawn
Let's start with this ever-popular maxpackets whine. Face it, practically the only situation where you can actually have maxpackets 100 is when you have maxfps 100 (and that is stable) and that doesn't make much sense if you can't also have displayrefresh at 100 so cl_maxpackets can stay IN 30-100 or 40-100, doesn't matter really.
I've been eagerly promoting the decrease of g_soldierchargetime before and will do it again. The simple fact is that it was raised from 20 to 30 only and ONLY because of mortar and where is it now? That's right, nowhere! The current 30 second charge is just pure crap.
On lots of situations it will result in random single kills because even with a CP built you really can't wait for the perfect shot too long if you're planning to get someone killed from the next spawn as well. Without CP the situation is even worse and often ends up in shooting the pf for every second spawn.
It is extremely funny when e.g. crumbs is comparing ET pf to RTCW and claiming that raising the chargetime would make the pf somehow a better weapon whereas in RTCW there's a 20 second chargetime plus you will have a full power bar every time when respawning, not to mention the fact that the RTCW pf itself is a perfect doomsday weapon.
Of course the smg only people (that is the majority of the scene?) are against every possible spam addition, but I see no particular reason for not lowering the chargetime for soldier back to 20 seconds. A lower chargetime just enables a possibility for the more intelligent use of pf BUT it won't make it such a doomsday weapon as it is in RTCW because the ET pf itself just sucks. :p
Disabling helmetprotection is a change to which I would certainly at least give a try. It would hopefully weaken the rambo medics a bit and make the gameplay a bit faster. But it would require some testing first, I admit.
Reducing or even disabling landmines, now that is a change unlikely to happen. But, what we've seen from battery so far, it certainly would make the gameplay faster without completely ruining the chances of the defending team. Instead, it would hopefully make teams concentrate more in crossfires, especially in open maps. Also, we wouldn't see that many fullholds at tank in gr anymore, dunno if it's a good thing or not. :p
A global config gogo! I don't really have an opinion about preserving mobile mg42, but I think, that it should be the same in every league.
Oh, and remove pronedelay! :-)