My server server.stability command keeps getting changed from True to False, what addon could be causing this? Cause i cant figure out if one of my admins is doing it or if a plugin is automatically doing it.
Solved Server Stability keeps turning off
Discussion in 'Rust Discussion' started by brentplays, Feb 28, 2015.
-
Wulf Community Admin
Were are you setting the command? It will revert to default if you aren't setting it in with your other startup parameters. Any Rust commands you use in your server console are only for that instance.
-
-
happened to me allso
-
It was happening cause of Copy/Paste Plugin turning it off , everytime i use it i have to manually turn stability back on
-
Wulf Community Admin
Attached Files:
-
-
Mine keeps turning off and I have to manually turn it back on whenever I login. I have no idea what's causing it (it's not Copy/Paste as I don't use that).
I'm not able to put it in the command line as I'm with Streamline and they only have very limited options for command line editing. -
I've had this too .. i just deleted Build (I dont think that it was this plugin) but worked 4 me xD
-
-
I think you can use my plugin http://oxidemod.org/plugins/timedexecute.919/ and set in config
Code:{ "Commands": [ { "command": "server.stability true", "interval": 120 } ] }
-
I logged off my server the other night and all was fine. Stability was off as it had been since I'd set up the server weeks ago. I logged on the next morning and stability was back on. The server had not been restarted in the interim, so how is it that it turns back on? -
Wulf Community Admin
-
Just an update, the reason my stability was turning off when i made this post was the Copy/Paste tool kept doing it. Since its been updated i no longer experience this problem.
-
-
Wulf Community Admin
-
Are you talking about the config file in the game server? If so, how do you write it?
-
-
Wulf Community Admin
-
Whahahah yeah bit i still have the same problem as the pll here, so thought maby it works.
-
bit late but, in my case was the autocommands.json was setting the value to False on server restart, I switched it to True and have had no issues since.