|
Notes |
|
|
|
once upon a time i also fell victim to this cvar and was relieved to finally learn about it and keep it disabled forever so that i may have full control of server settings without some being forced by default (i dare go offtopic and mention alwaysapplydmflags annoyed me for a short period of time before i found about it as well)
of course, over time, theres been others who also had to find out about it one way or another, either by asking on irc (new hosters using best-ever) or by making a tracker ticket because they thought they found a bug (tickets 163, 252, and 1294)
now, i dont know if there are any maps, mods, scripts, lumps, or what have you that might break or exhibit weird behavior if this cvar gets removed, or maybe theres nothing to worry about, but if it is considered, perhaps simply changing the cvar to default to false instead would be a safer route, just in case? |
|
|
|
|
|
I agree, changing the default value to false should be the safest solution. |
|
|
|
|
> perhaps simply changing the cvar to default to false instead would be a safer route, just in case?
What could conceivably break by removal of the cvar, other than there maybe being a warning in a startup script? |
|
|
|
|
i was just speaking pessimistic in general because i dont actually know wut would break or not since i severely lack experience with modding/scripting/etc
dont get me wrong, i have 0 love for that cvar and personally wouldnt mind to see it gone as i will never use it, but a safer alternative (defaulting to false) would be just the same to me and might save something from breaking in the future, but if its just gonna be some warning printed to the console then that doesnt sound too bad, either way is fine with me |
|
|
|
|
|
I don't see an advantage in completely removing the CVAR. It is a shortcut to a reasonable set of settings. I certainly wouldn't add it, if it wasn't there already, but what do we gain by removing it? If the default is changed to false, it shouldn't cause problems for anybody. |
|
|
|
(0015153)
|
|
StrikerMan780
|
2016-06-29 21:41
(edited on: 2016-06-29 21:43) |
|
I'd make it a command rather than a cvar. That way you just call it once to set the DMFlags to default, and won't affect the flags on map change if the DMFlags are changed later.
|
|
|
|
|
|
Have alwaysapplydmflags default to 1 too. It's in the same boat as this hideous carncvar. |
|
|
|
(0015526)
|
|
Dusk
|
|
2016-08-26 08:07
|
|
|
alwaysapplydmflags, unlike this cvar, is totally pointless though. It doesn't even control the behavior of all dmflags. I think it should just be removed. |
|
|
|
|
|
I changed the default value of sv_defaultdmflags to false. |
|
|
|
|
|
Fired up r170513 on a local server and it was indeed defaulted to 0. |
|