[Epi]

I did a search but couldn't really find what I was looking for, so here goes:
I can disable a user's abillity to write configuration which stops them editing the command line, but it also stops them editing everything else.
So is it possible to completley disable a user's ability to edit the command line startup options for a game, without disabling the rest of their configuration abilities?
So for example they can still change the server name, rcon, start map etc, but not the command line.

ty

[adbot]

[Andrew]

Not at this time no.

Is there a specific reason?

[Epi]

well so that they can't change tickrate on css, or their port number in the command line...it would just be easier if I could disable it by having it as read only, ratehr than checking up on people to see they haven't changed it.

[Andrew]

They won't be able to change the port number unless they have Host Write access as well.

If they change it on the command line, the server will just crash anyway - GameCreate will be trying to query it on its port defined in GameCreate and just reboot it because it assumes its broken - not much use to them.

I think a solution to this (without adding more permissions, which would begin to make it too fine grained) would be to provide a webservice call to fetch information on each server (properties etc) which could be used to then decide if something has changed and stop the server if needed.