New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SteamPipe] -sv_pure shouldn't be needed for sv_pure to work #216
Comments
"You CAN change sv_pure after boot, provided that you start with it on. The only thing you cannot do is turn it on, when it started off. The reason is that there is extra work involved in maintaining some hashes, and they need to start happening from the very beginning. By the time the server parses the config file, it is too late for many important files. So, for example, GSP’s would probably force this option on, and then allow server operators to lower the setting or turn it off if they wanted." |
I still think it would be better to force it on by default. I think it's going to be a real problem if every GSP need to add another option for this. |
nvm, just need add only that parameter without value |
I also still think it would be better to force it on by default |
Force it on by default. But first, fix the bugs for heavens sake! #583 |
lord, the humanity |
@fletcherdvalve You're assigned to this, what's your progress on it? |
The server now needs to have -sv_pure in the command line with the SteamPipe update, otherwise you can't use sv_pure. It's going to be a real problem for servers hosted by GSPs, the server admin won't be able to turn sv_pure on.
I can't see why this is now a requirement as it wasn't before. I think it should be removed.
The text was updated successfully, but these errors were encountered: