The future of Consistency Checking (and Serverside Mods)
Security
Join Date: 2005-01-07 Member: 33133Members, Constellation, Squad Five Blue
<div class="IPBDescription">Will it be fixed? Serverside mods over Steam Workshop ONLY?</div>How come consistency checking is <b>still</b> using the actual server files to check against client files, effectively preventing serverside modding that way?
It should be fairly easy to use fixed checksums or include an extra folder with vanilla files, for consistency checking to validate with.
Will it be fixed to affect clients only, or is it actually planned to control serverside mods that way, by forcing the usage of Steam Workshop & Whitelists?
Individual changes to Steam Workshop mods by server operators are impossible.
If intended, that would be pretty restrictive for NS2 as self proclaimed <b>"most moddable game ever"</b>.
The usage of Steam Workshop should be an option, not a requirement. And Consistency Checking should <b>not</b> interfere with serverside modifications at all.
Also, why not make consistency checking more user friendly, like TF2's sv_pure? Forcing modified clients to load vanilla files, instead of kicking them.
Some clarification about intentions and future plans would be nice.
It should be fairly easy to use fixed checksums or include an extra folder with vanilla files, for consistency checking to validate with.
Will it be fixed to affect clients only, or is it actually planned to control serverside mods that way, by forcing the usage of Steam Workshop & Whitelists?
Individual changes to Steam Workshop mods by server operators are impossible.
If intended, that would be pretty restrictive for NS2 as self proclaimed <b>"most moddable game ever"</b>.
The usage of Steam Workshop should be an option, not a requirement. And Consistency Checking should <b>not</b> interfere with serverside modifications at all.
Also, why not make consistency checking more user friendly, like TF2's sv_pure? Forcing modified clients to load vanilla files, instead of kicking them.
Some clarification about intentions and future plans would be nice.
Comments
The current system of dealing with mods in general is not very welcoming. However, I believe that currently they are so focused on dealing with optimizations and critical engine work that they do not have time to work on this issue right now. Hopefully in the coming weeks they will have time to address the issues with modding and allow this game to be the mod friendly environment that it was intended to.
Look at how popular mod friendly games like CS:S are. Players are not stupid they can identify from a vanilla experience and a modded one. Perhaps this was logical at launch to protect the payers that have no idea what ns actually is but in the weeks going forward that should no longer be an issue.
There is Metamod: Source and Sourcemod for Source Engine games to implement mods, but this is a route, we shouldnt be forced to go to be able to implement usefull mods like DAK or NS2Stats without our servers being marked as modified.
I'm sure, that UWE will implement the Whitelist again and will approve one or another mod again to be on the Whitelist, so that you can install it on your server without being "Community Content" marked.
I can't say anything about the future, but this is how it stands right now.
This too, if the server does not want you to modify any model, you will have the official default models o NS2 even if you changed them.
One server variable to disable all mods on the client, a real sv_pure, would be really great though.