-
Notifications
You must be signed in to change notification settings - Fork 6
Configuration
ActiveTime - Developed by Simon_Flash (mcsimonflash@gmail.com)
Current Version: 1.3.1
Status: Active -> New features and updates are in development
ActiveTimes configuration contains two primary files: activetime.core in the main directory, and milestones.conf in the configuration folder.
The core configuration file for ActiveTime containing the main settings.
The interval in seconds between playtime limit checks. This task is used to check if players have surpassed their playtime for the given day as set using the playtime option. For example, a limit of 1 hour (3600 seconds) can be set with LuckPerms with lp user <player> meta set playtime 3600. If you are not limiting time for any players, it is recommended to disable this task (set to -1).
The interval in seconds between milestone checks. This task is used to check milestones that exist in milestones.conf (see below). If you are not using any milestones, it is recommended to disable this task (set to -1).
The interval in seconds between saving the cache. This task is used to save cached times to the appropriate log files. It is also used for updating the leaderboard and may not be disabled.
The interval in seconds between updating the cache. This task is used to check all of the online players for activity and store data in a temporary cache. This information is not saved to a file until the save task runs, so server crashes may cause cached data to be lost. This task may not be disabled.
The default response size of leaderboard requests.
The maximum response size of leaderboard requests.
Holds milestones for player's activetime. The name of the milestone is the node key and is used as a unique identifier in error messages. If a milestone is added after a player has passed the required time, the milestone will be given to them when the next check is made.
The activetime (in seconds) a player must have for this milestone to be met.
The command to be executed by the server when this milestone is met. Use <player> for the name of the player. If multiple commands are needed, consider using a plugin that can link commands such as CmdControl.
This example shows a milestone that broadcasts a message requiring 5 minutes of activetime.
five-minutes { //The milestone name, used in error messaging
activetime=300 //5 minutes @ 60 seconds/min = 300 seconds
command="broadcast <player> has been on our server for 5 minutes!" //Where <player> is replaced with the player's name
}