-
Notifications
You must be signed in to change notification settings - Fork 5
Server Settings
You can access any server's settings by opening the server's control panel and typing settings
This is the amount of RAM that the server will initially allocate. specified by the java argument -Xms
leaving this as null will simply omit the argument which is perfectly acceptable if you don't care.
Examples of acceptable arguments:
- 83886080 (When specifying bytes they have to be a multiple of 1024)
- 81920K (When specifying kilobytes they have to be a multiple of 1024)
- 80M (for megabytes)
- 2G (for gigabytes)
This is the amount of RAM that the server cannot exceed. specified by the java argument -Xmx
It is always recommended to have a cap on the amount of RAM that the server can use. However, leaving this as null is also acceptable.
Acceptable arguments are the same as (1) but keep in mind max RAM must always be greater than start RAM or your server won't start.
This is a powerful option that lets the manager start any crashed servers while making sure your server stays online. This however is overridden by the stop command from the server control panel. So if you have this option set to true and you stop or kill the server using the manager the server will stay offline.
Unresponsive states are determined when a linked plugin stops receiving info about the server from the monitoring plugin or when a starting server fails to be online within the Max starting duration. When this is true, the server restarts immediately when its deemed NOTRESPONDING.
This is the maximum duration a starting server to become online. Meaning if a server fails to become online after the start command has been executed by this duration, the server is deemed NOTRESPONDING and will restart if option (4) is set to true. Always set this to be 1.5 times your average server start times at least to avoid deeming perfectly fine starting servers as NOTRESPONDING.
This is the maximum duration for a stopping server to become offline. if a server fails to be stopped within this duration its process will be killed forcefully. Always set this to be 1.5 times your average server start times at least to avoid killing perfectly fine stopping servers as it can cause loss of data.
This the command string that is sent to the server's console. For example spigot servers should have it as "stop" while bungeecord server's should have it as "end"