Garry's mod startup commands for 40+ players - Help

Hello, my current : cl_allowdownload 1 sv_cheats 0 cl_downloadfilter all download_debug 0 sv_allowcslua 0 sv_client_predic 0 r_flashlightdepthres r_projectedtexture_filter 0 sv_region 255 sv_lan 0 sv_logbans 1 sv_logecho 1 sv_logfile 1 sv_log_onefile 0 sv_noclipspeed 5 sv_noclipaccelerate 5 sv_minrate 2500 sv_maxrate 0 sv_minupdaterate 10 sv_maxupdaterate 66 //Sandbox Settings sbox_allownpcs 1 sbox_godmode 0 sbox_plpldamage 0 sbox_playergod 0 sbox_noclip 0 sbox_maxprops 90 sbox_maxragdolls 0 sbox_maxtextscreens 3 sbox_maxnpcs 10 sbox_maxballoons 0 sbox_maxeffects 0 sbox_maxdynamite 0 sbox_maxlamps 2 sbox_maxthrusters 2 sbox_maxwheels 0 sbox_maxhoverballs 0 sbox_maxvehicles 0 sbox_maxbuttons 0 sbox_maxsents 0 sbox_maxemitters 0 sbox_maxspawners 3 sbox_maxturrets 0 //Server Settings net_maxfilesize 30 decalfrequency 10 //Execute ban files exec banned_ip.cfg exec banned_user.cfg // important sv_tickrate 33 sv_minrate 30000 sv_maxrate 0 sv_minupdaterate 11 sv_maxupdaterate 66 sv_mincmdrate 11 sv_maxcmdrate 66

cl_* commands are client commands only, they won't do anything on the server. sv_tickrate isn't a thing I'm assuming you have your tickrate set at 33, seeing as that's the value you used for the nonexistent "sv_tickrate". If so, your cmdrate and updaterate commands are probably better off this way (to my knowledge): sv_minupdaterate 34 sv_maxupdaterate 34 sv_mincmdrate 34 sv_maxcmdrate 34

Ok, i will fix it. But maybe someone got another server.cfg? [editline]29th April 2017[/editline] Maybe someone know values to set minrate and maxrate?

[QUOTE=tgandrew2468;52162634]sv_minupdaterate 34 sv_maxupdaterate 34 sv_mincmdrate 34 sv_maxcmdrate 34[/QUOTE] Minor question, is there actually an advantage to locking the client cmd/update rates to one step above the actual tickrate? [editline]29th April 2017[/editline] Also not sure why you have r_flashlightdepthres and don't set a value for it. Not that it should matter for a server with no ingame graphics to render... [editline]29th April 2017[/editline] You're also setting sv_minrate and maxrate twice.

[QUOTE=lNloruzenchi;52166486]Minor question, is there actually an advantage to locking the client cmd/update rates to one step above the actual tickrate?[/QUOTE] I'm not entirely sure if it makes a difference or not, but my reasoning behind it (and I'm assuming everyone else's) is that the tickrate goes into decimals. Ex: 66 tick = 66.66... most of the time If I'm wrong and someone actually knows please post.

[QUOTE=tgandrew2468;52167143]I'm not entirely sure if it makes a difference or not, but my reasoning behind it (and I'm assuming everyone else's) is that the tickrate goes into decimals. Ex: 66 tick = 66.66... most of the time If I'm wrong and someone actually knows please post.[/QUOTE] Nein. If you set the tick to 50, it will be 50, not 50.50

[QUOTE=Lilyxfce;52167912]Nein. If you set the tick to 50, it will be 50, not 50.50[/QUOTE] Depends on the tickrate. Don't know why you'd be using 50 anyways.

Tickrate is literally the number of times Source simulates the game per second. Because it's 1/tickrate, it'll always be a decimal, even though it's just being done 33 or 66 whole times per second. But yeah, I see what you mean. Just superstitious it would cause weird shit to happen.