Server config snapshot

At each heartbeat, the clan.me plugin sends a snapshot of key server configuration values. These are stored with a timestamp, building a history of your server's settings over time.

What gets captured

The config snapshot includes:

• Difficulty: peaceful, easy, normal, or hard
• PvP: enabled or disabled
• Default game mode: survival, creative, adventure, or spectator
• View distance: in chunks
• Simulation distance: in chunks
• Online mode: whether the server requires Mojang authentication
• Max players: the configured slot limit

These are the settings that most often change accidentally or without coordination across a team of admins.

When the snapshot updates

The snapshot is sent with every heartbeat, but clan.me only stores a new entry when one or more values change. If your server runs for a week with identical config, the dashboard shows one config entry for that period rather than thousands. When something does change, the exact heartbeat at which it changed is recorded.

Using config history

Config history is most useful in two situations:

• After an incident: if players report that the game mode changed or PvP is unexpectedly on, the config history shows exactly when it changed and what it was before
• Coordinating admin changes: on servers with multiple admins, the config timeline provides a shared record of what changed and when, reducing disputes

View distance and simulation distance changes are worth watching in the config history because they directly affect server performance. Increasing view distance by one step raises the number of loaded chunks by roughly 60%, with an immediate memory and CPU cost.