Managing Progress

Everything here needs optimalmilestones.admin (default: op). The command is /milestonesadmin, with the aliases /msadmin and /milestoneadmin. Running it with no arguments shows the help panel.

Changing a counter

/milestonesadmin progress give <player> <category> <amount>
/milestonesadmin progress take <player> <category> <amount>
/milestonesadmin progress set <player> <category> <amount>

Action	Does
give	Adds <amount> to the player’s progress.
take	Removes <amount>. Progress never goes below 0.
set	Sets progress to exactly <amount>.

• <category> is the category id (the file name without .yml). Tab completion lists the enabled ones.
• <amount> must be a whole number, 0 or higher. Anything else answers INVALID-NUMBER.
• Only API categories can be changed. A PLACEHOLDER category answers CATEGORY-NOT-TRACKED, because its value belongs to another plugin.

Examples:

/milestonesadmin progress give Steve blocks 5000
/milestonesadmin progress set Steve blocks 0

Raising progress does not claim anything. If the new value passes one or more thresholds, the player gets the usual MILESTONE-UNLOCKED notification on the next unlock check and claims the milestones in /milestones as normal. Lowering progress does not take back milestones that were already claimed.

Resetting a player

/milestonesadmin reset <player>
/milestonesadmin reset <player> <category>

A reset sets progress to 0 and clears every claim, so the player can earn and claim those milestones again. Without a category it covers every category; with one it covers only that category. Reset works on PLACEHOLDER categories too, where it clears the claims (the progress itself still comes from the placeholder).

Online and offline players

Both commands work whether the player is online or not:

• Online - the change applies to the loaded profile right away and the menu shows it the next time it is drawn.
• Offline - the change is written to the database. The player must have joined the server before (be in the server’s user cache), otherwise the reply is INVALID-PLAYER.

The confirmation (PROGRESS-GIVEN, PROGRESS-TAKEN, PROGRESS-SET or MILESTONES-RESET) is sent once the change has actually been applied. All of them can be edited in messages.yml.

Reloading

/milestonesadmin reload

Reloads config.yml, messages.yml, guis/milestones-menu.yml and every file in milestones/, and restarts the save and unlock timers with the new intervals. The reply shows how long it took. If a file has an error, the reload fails and the console names the offending file or key.

Testing a new category

A quick way to check a category you just made:

1. /milestonesadmin reload
2. /milestonesadmin progress set <you> <category> <amount> with an amount past a few thresholds
3. Wait a few seconds for the unlock messages, then open /milestones <category> and claim
4. /milestonesadmin reset <you> <category> to put yourself back