Posts by Pauperprince

Nitrado now has an official Discord server to bring communities, friends and other gamers together!
Join the Nitrado Community Discord now and share your experiences and knowledge with others!

Click here to go to the Discord Server!

    When your server is stuck in a restart loop :
    First, wait patiently and when prompted, Force Stop your server; never Force Start. Then, wait no less than 5 minutes, and then Starrt your server.
    If the Looping continues, Save your messages.xml and then delete it from the Server. Then delete all of your Automated Tasks for Restarts. Once you have completed those two tasks. Either your Server will Start Up in two Minutes, or you will need to follow thru with the First Step again.
    If you have carefully completed Those steps and the Server is still Looping, notify Nitrado Tech Support.

    I dont mean to sound like a broken record already, but this symptoms of Desync. I will copy paste my response to a related post. It was likely that your server connection was poor at the time. If this is consistent, ask Nitrado to switch hardware. After you see that your server has a new IP address, reassess the issue.
    Ofcourse, consider that it may be your own connection to the internet. This sort of issue you need to play the inspector and investigate possibilities.

    Assuming that you had this issue prior to changing lifetimes to an ignored value. My experience with this leads me to think it is simply the core file with a persistence rule corrupted. I have had several members of discord run into this. The going solution has been..... wait for it.... a re installation. I know, it is every ones solution at times. But, I know it to have solved the issue. Save you XMLs that you have access to, and then reinstall. Save them to a PC first, as we know there to be a bump in the process that sometimes overwrites your XMLs without having selected the option.

    While no one is on the server the Central Economy is on pause. Though we have settings for this, the settings are as of now being ignored by the engine. If you think there is enough traffic on your server to keep the CE running. Then Your alternative could be to try changing the following values, to further assist the process :
    <var name="CleanupAvoidance" type="0" value="0"/>
    <var name="CleanupLifetimeRuined" type="0" value="120"/>
    Without any more information, I cannot help you past this information and advice.

    The two experiences are unrelated. The first issue with unresponsiveness sounds like desync. It is truly as simple as that. It was likely that your server connection was poor at the time. If this is consistent, ask Nitrado to switch hardware. After you see that your server has a new IP address, reassess the issue.