|
Notes |
|
|
|
|
Yeah, I do think this is actually very important, especially for demo playback, because it helps with the verifiability of a kosher game (to help make sure that someone really used the settings they've said they used). |
|
|
|
|
|
The sv_* variables the clients don't need to know of are not synced with the clients. sv_coop_damagefactor is one of those. |
|
|
|
|
IMHO, it'd be nice if everything was synchronized with the clients, even if not truly needed. It can be confusing in some cases when you see one variable set, but another one is in effect. That's the main reason to why I reported it; confusion.
But then again, if it's too tedious to implement this, it's alright, as it's not a necessity. |
|
|
|
|
|
I'd need to take a completely different synchronization approach if we want all sv_* values to be synced in a feasible way. It would be nice to have this in the long run, thus I'll transform this bug report into a feature request so that it's not forgotten. |
|
|
|
|
|
IMHO, this is important. Not all sv_* values are important like this one. The main reason is verifiability. If we cannot have this value sync'd with clients, then I fully COMPLETELY disagree with it being in the Skulltag executable at all, and I think it should be taken out. |
|
|
|
|
There are various other CVARs that are as important as this one, like sv_killallmonsters_percentage and sv_suddendeath for instance. Nobody ever complained that the values are not synced with the clients.
In general I agree that the sv_* CVARs should be synced, but IMHO it doesn't make any sense to do this just for sv_coop_damagefactor now and ignore the other CVARs that are equally important. |
|
|
|
|
Well, here's the concern:
Say some guy says he put the sv_coop_damagefactor up to 3, and he's like, "yeah I recorded a demo of it, I'm the best Doom player ever haw haw haw!" ... you get the demo, and there's no way of telling, without really good judgment and really good knowledge of the game, if he really used that setting. And also, you never know, someone could just conveniently set it lower through rcon at just the right times, and no one would ever know by watching the demo. |
|
|
|
(0000345)
|
|
TIHan
|
|
2010-10-12 01:52
|
|
Before, I had sv_coop_damagefactor as a CVAR_LATCH which was taken out. If it was a CVAR_LATCH, it would require the server to restart the map in order to make changes. So, no one could "convenietly set it lower through rcon at just the right times". So, I would suggest making sv_coop_damagefactor a CVAR_LATCH to get rid of this issue.
I wouldn't be too concerned over this as it's not a huge deal at the moment. We are still in the beta builds. |
|
|
|
|
|