SmoothRestarter

Moved

Total Downloads: 5,594 - First Release: Apr 11, 2016 - Last Update: Dec 30, 2017

5/5, 22 likes
  1. Hi all, I found a bug
    If player kill and not respawn and is restarted using the sr.restart command
    Then after that the player can no longer go into the game, he has an endless connection to the server, until he is teleported to somewhere admin
     
  2. That for sure...but i'm absolute sure that one not inside this plugin :)
     
  3. Try also on the local server, I made 5 attempts, it is on this plugin that this problem occurs
    [DOUBLEPOST=1526132231][/DOUBLEPOST]You turn on the plugin then you need to die and do not press the "Respawn" button, you write sr.restart through the console. 1 You wait for restart, you throw it out and then you can not go any connect
     
  4. Wulf

    Wulf Community Admin

    Try with Rust's restart, functionality is the same thing. There's nothing happening to players from this plugin when restarting.
     
  5. Got it, very strange, maybe I could not stumble upon this without a plugin
     
  6. Wulf

    Wulf Community Admin

    Have you unloaded all other plugins and only tested with this plugin?
     
  7. Yep=).

    The thing is that after the plug-in is unloaded, the players no longer write to me about this issue
     
  8. Ever used the "server.quit" command? Thats inbuilt by FP to console, in case of it's a new one for you ;)

    And exactly that, and nothing else, is SmoothRestarter calling :p
    Players are almighty...they always do know the exact issue ^^ Trust them, plz not the coders!!
     
  9. I did not personally look at the plugin code, I just decided to check it myself, it means a coincidence. Because of what this problem then arose in the rust? Previously, there was no
     
  10. Hey all,

    seem to be having an issue and not sure what's up. The auto restart timer isn't doin anything..as in not restarting at the times specified. Manual restart command sr.restart 5 works just fine. And when I type "sr.simulatepatch" it says:

    "[SmoothRestart] Changed current Devblog and OxideBuild numbers to simulate successful checks" and does nothing... below is my config!
    Code:
    {
      "Checks": {
        "autoRebootCountDown": 3,
        "checkIntervalMinutes": 5,
        "currentDevblog": 0,
        "currentOxideBuild": 0,
        "enableAutoChecks": true,
        "enableAutoReboot": true,
        "notifyOnlineAdmins": true
      },
      "Settings": {
        "ShowMinutes": [
          60,
          45,
          30,
          15,
          10,
          5,
          4,
          3,
          2,
          1
        ],
        "ShowSeconds": [
          50,
          40,
          30,
          20,
          10,
          5,
          4,
          3,
          2,
          1
        ]
      },
      "SimpleUI": {
        "SimpleUI_Enable": true,
        "SimpleUI_FontSize": 30,
        "SimpleUI_HideTimer": 10,
        "SimpleUI_Left": 0.1,
        "SimpleUI_MaxHeight": 0.05,
        "SimpleUI_MaxWidth": 0.8,
        "SimpleUI_Top": 0.1
      },
      "Timers": {
        "RebootTimes": {
          "11:30:00": "30",
          "24:30:00": "30"
        },
        "useTimers": true
      }
    }
     
  11. same problem, timers not working for me either
    my cfg file:
    Code:
    {
      "Checks": {
        "autoRebootCountDown": 3,
        "checkIntervalMinutes": 5,
        "currentDevblog": 0,
        "currentOxideBuild": 0,
        "enableAutoChecks": true,
        "enableAutoReboot": false,
        "notifyOnlineAdmins": true
      },
      "Settings": {
        "ShowMinutes": [
          60,
          45,
          30,
          15,
          10,
          5,
          4,
          3,
          2,
          1
        ],
        "ShowSeconds": [
          50,
          40,
          30,
          20,
          10,
          5,
          4,
          3,
          2,
          1
        ]
      },
      "SimpleUI": {
        "SimpleUI_Enable": false,
        "SimpleUI_FontSize": 30,
        "SimpleUI_HideTimer": 10,
        "SimpleUI_Left": 0.1,
        "SimpleUI_MaxHeight": 0.05,
        "SimpleUI_MaxWidth": 0.8,
        "SimpleUI_Top": 0.1
      },
      "Timers": {
        "RebootTimes": {
          "05:00": "120",
          "13:00": "120",
          "21:00": "120"
        },
        "useTimers": true
      }
    }
    i just tried the simulate command, and it only displays this line as a reply:
    Code:
    (16:16:17) | [SmoothRestart] Changed current Devblog and OxideBuild numbers to simulate successful checks
    and that's all it replies
     
    Last edited by a moderator: Jun 6, 2018
  12. Yep, looks like the web-request calling functions are kinda bugged in the plugin.
    ...shown by the zero's inside the config...
     
  13. and is it possible to fix the restart timers? that's the only reason i installed it. the devlog/oxide thing is nice to have, but for me the key is the timers for restarts.
     
  14. Would be nice if this could have a multi day function, been looking at performance of a server we've had up for 44 hours and its steady, be cool to have it on a 3 day timer.
     
  15. Will this be fixed?
    I'd love to have it auto detect update releases and automatically restart the server.

    It seems the plugin Update Notice has a way of web-requesting if there's updates or not. Maybe something to look into?
     
  16. Wanted to set this up to restart my server every 24 hours, but looks like it needs fixing?
     
  17. Nope, function was taken out of order due to Facepunch does'nt deliver the DevBlog title anymore, and also no devblog number anymore.
    This way, the initial trigger for the update-check does'nt work anymore.
    [DOUBLEPOST=1532297478][/DOUBLEPOST]
    Nope, there's nothing to fix on the timers.
    [DOUBLEPOST=1532297499][/DOUBLEPOST]
    Nope...see above.
     
  18. Except, this person has figured out a way to do it, supposedly (which is why I pointed that out before).
    PLUGIN: https://oxidemod.org/plugins/update-notice.2837/
    DEV: https://oxidemod.org/members/psystec.230891/

    This is a newer plugin, so I'm assuming it works.
     
  19. I never said to use HIS/HER API for UpdateInfo, I was just pointing out that it is possible. That there are indeed version numbers for the updates somewhere accessible to the public, just not where you originally expected.

    His/her API has discovered the following information...
    Code:
    {"ServerVersion":2963146,"ClientVersion":2963120,"StagingVersion":2964512}
    So it's pulling these version numbers from SOMEWHERE.