Player State

Player State bundles the verbs that act on a player rather than the world: healing and feeding, flight, game mode, walk and fly speed, personal time and weather, experience, inventory inspection, and a stack of read-only info commands. Most verbs take an optional player argument, gated by their own others node.

Module playerstate · enabled by default · modules/playerstate/config.conf

Commands

Permissions

Settings

Placeholders

Playtime

The playerstate module keeps its own record of how long each player plays. Every sample-seconds (60 out of the box) it credits each online player that interval as active or AFK time, one row per player and day, in the plugin's database. /playtime shows the record for today, the last 7 and 30 days and all time.

The record starts on the day the plugin was installed. Time played before that lives only in the server's vanilla statistic, which the record does not read. Two tools close that gap: an import from the vanilla statistic, and a correction by hand.

Playtime commands

<time> is written like 30m, 2d5h or 1w (units s, m, h, d, w); set also takes 0. Naming a player other than yourself also needs uxmessentials.playtime.others, as every playerstate command does. Each subcommand sits under /playtime, so it needs uxmessentials.playtime.use too.

Corrections

set, add, take and an import do not rewrite the daily rows. They store one correction per player, which is added to the all-time totals. The today, week and month figures stay what the sampler counted. A correction counts as active time, so it also counts toward the playtime-active rank requirement.

Importing

An import compares the tracked all-time total with the vanilla statistic and adds the difference when the vanilla figure is higher. It never lowers a total, so running it twice changes nothing. import all reads the players one after the other and reports how many got time added when it is done.

With playtime.import-on-join = true in modules/playerstate/config.conf, each player is imported once, the first time they join with the setting on. The playerstate module does not reload live, so the setting takes a restart. A player imported before, by the command or on join, is skipped, so a player whose playtime was reset (for example by a prestige action) does not get the old time back on the next join.

Rank requirements

The ranks module reads this record:

To make players earn their playtime again after a prestige, reset it in the prestige actions:

actions = [
  "console playtime reset {player}"
]

The playtime board

%uxmessentials_top_playtime_<period>_<n>_name% and its siblings rank active time, AFK left out. The all-time board reads this record, corrections included, so it covers every day since the install; the monthly, weekly and daily boards count from the version that added them. Placeholders lists every board key.

Notes

• /ptime and /pweather are client-side. They change what one player sees and never touch the world for anyone else.
• /invsee opens read-only by default. Editing another player's inventory is a separate node, so watching and changing are different grants.
• /world reports, /worlds manages. This module owns the read-only one.
• /glow takes a colour. /glow on its own toggles the plain outline; /glow red turns it on in one of the sixteen vanilla colours, and /glow red Steve does it to somebody else. Turning the outline off drops the colour with it, so the next bare /glow starts plain again. The colour is carried by a scoreboard team, which is also how a hidden nametag works, so a player whose name this plugin hides can still glow in a colour.
• A command renamed in commands.conf keeps its permission node, because nodes are keyed to the command id rather than to the name you give it.
• Flight granted here and flight granted by staff mode are different things. Leaving staff mode restores the player's real flight allowance rather than whatever the mode gave them.

Related: Items & World, Teleport, Presence