The Interval is a time in the 24h time format. But run the restart command with a delay of 5 minutes, meaning the server will restart exactly at 12. This however is not a bad thing, if you bundle world cleanups together with a restart, since this would not have happened on a crash.Ĭommonly a server restart of every 4 hours is used, but for the sake of simplicity the example below uses 12 hours.Īs you can see here, you add 2 commands, which are scheduled for execution at 11:55am and pm respectively. ![]() However, if your server happens to crash at 11pm, and your next scheduled restart is at midnight, the server will just run an hour before restarting again. Such as only doing a cleanup at midnight. This allows players to predict restart times, even if they are not ingame, and you can add additional commands only on specific restarts. With that you can make sure that your server always starts at the exact same time, or at fixed intervals. After saving the config with essentials they will be added back again.Ī more widespread solution for restarting the server is scheduled at fixed times. The CommandTrigger tells you it interval based. So you can easily increase or decrease them as needed. The time behind the !restart is in seconds. It's enough time for players to stop whatever they are doing, and secure their grids. This will begin the countdown to a restart 5 minutes before it actually happens, automatically saves the world and restarts the server. However it also makes sure that if a server just restarted after crash, it will not do so again within the next 4 hours. Additionally, if your server crashes in between, or you perform a manual restart after some config changes the 4h interval is completely out of the window. The next restart will therefore be at 2:10am. This means if the restart triggers at exactly 10pm, it takes about 5 minutes to save and go down, 5 more minutes to boot up again and starts counting down at 10:10pm. The server starts counting from the moment the session is loaded. However the restart times are unpredictable, and players usually love it, if they are able to predict when a restart will happen.Ĭonsidering you want to run a restart every 4 hours. There are two major ways of setting up a restart which are described below.Ī dynamic or interval based server restart is easier to set up, and it only really requires one command. Some of them require server restarts afterwards. Restarts also allow for an opportunity to perform some server maintenance such as cleanups that can be done fully automatic. Generally it is recommended to restart your torch server every now and then to fix bugged out grids, free up stuck memory and overall improve the performance, as over time things can get a bit annoying to deal with. Website based management tools, may no longer be able to control the server after such restart.Ĭheck first if the hosting solution you have chosen is compatible. : Item Merge Radius: 2.Some hosting providers are incompatible with Essentials !restart commands, as it will create a new torch process with new process id. : Nerfing mobs spawned from spawners: false : Zombie Aggressive Towards Villager: true : Arrow Despawn Rate: 1200 Trident Respawn Rate:1200 : Allow Zombie Pigmen to spawn from portal blocks: true : Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64 ![]() : Tile Max Tick Time: 50ms Entity max Tick Time: 50ms : Hopper Transfer: 8 Hopper Check: 1 Hopper Amount: 1 : Entity Activation Range: An 32 / Mo 32 / Ra 48 / Mi 16 / Tiv true : To change this, set "online-mode" to "true" in the server.properties file. ![]() : Whilst this makes it possible to use BungeeCord, unless access to your server is properly restricted, it also opens up the ability for hackers to connect with any username they choose. : The server will make no attempt to authenticate usernames. : **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE! : Server permissions file permissions.yml is empty, ignoring it : This server is running Paper version git-Paper-"ae892dc" (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT) : Starting minecraft server version 1.16.5 ![]() : Reloading ResourceManager: Default, bukkit : Environment: authHost='', accountsHost='', sessionHost='', servicesHost='', name='PROD' These are the logs I was shown after my server kicked me out and shutdown after like 2 minutes:
0 Comments
Leave a Reply. |