about cl_timenudge

[wardew Profile]

the timenudge cvar can be used for fix a wrong game prediction..
please don't lock it

[lis Profile Website]

as i said, if you're going to forcevar netsettings, i'd start with rate and maxpackets first, cause those have a bigger impact than those couple of timenudgers. i mean, 80% of players seem to be playing with the 30 maxpacket default... and if they get 2 minute pb kicks then they'll need instructions about how to correct it (via forum) or, what is more likely, new players will just connect elsewhere... therefore my pessimism.

And what about using a "server side" autoexec.cfg ?
When you connect to ps#1 (I guess other servers do same), you d/l a .pk3 with an autoexec.cfg, which look like :

Code: Select all

\com_hunkmegs 128
exec autoexec2.cfg

Just add some default settings for cl_timnudge/maxpackets/snaps and others... (yeah you will still be able to change this in game or througth autoexec2 perso settings, but the new player will have good settings when he connect. If PB restricted -> no kick). Or maybe I'm wrong ?

sounds pretty smart

only problem i see is:

rate and maxpackets should be allowed in a range... like rate from 15k to 25k and packets from 60 to 100, point is to avoid the defaults 5000 rate or 30 maxpackets. but i guess forcing a 0 nudge can't hurt^^

maybe some skilled server owner/engineer has an opinion on this?

[Sebbel]

maybe some skilled server owner/engineer has an opinion on this?

thats why i dont answer anymore in this topic^^

lets wait for one

[lis Profile Website]

maybe some skilled server owner/engineer has an opinion on this?

thats why i dont answer anymore in this topic^^

lets wait for one

pff!

i was actually referring to one of OUR server owners!



EDIT: "OUR server owners" as in ... someone like you seb (just to avoid a misunderstanding) ^^