promotional bannermobile promotional banner

StatusServer

Experimental
A lightweight Purpur 1.21.11 plugin that asynchronously updates server status every 4 minutes—even with no players online—without affecting world data or other plugins.

AutoServer is a lightweight server-side plugin that automatically builds and sends an up-to-date Minecraft server status every 4 minutes — without stopping, restarting, or keeping players online. It does not modify the game world, does not interfere with gameplay, and is designed to run safely alongside other plugins.

What AutoServer does

Every 4 minutes, AutoServer creates a status snapshot of the server and sends it to an external destination configured in config.yml. By default, this can be an HTTP request with JSON or a Discord Webhook. If no external destination is configured, AutoServer simply writes the status to the server log with a clear [AutoServer] prefix.

The status payload can include:

  • online player count and max slots;

  • server TPS for 1, 5, and 15 minutes;

  • average tick time (MSPT);

  • RAM usage;

  • server uptime since startup;

  • server version and core — Purpur/Paper 1.21.11;

  • list of loaded worlds without modifying their data;

  • custom metadata from config, such as server name or node ID.

Works with zero players and without restarts

AutoServer uses a repeating Bukkit/Paper scheduler task tied to the server lifecycle, not to player join/leave events. Therefore, status updates continue to run even when 0 players are online. The server does not need to be stopped, restarted, or kept alive by a “keeper” player. After the server starts, AutoServer begins its update cycle automatically: the first snapshot after the configured initial delay (4 minutes by default), then every 4 minutes.

World and data safety

AutoServer is read-only with respect to the game world. It does not force world saves, does not edit chunks, region files, level.dat, entities, blocks, or player inventories. All plugin-owned data is stored only inside plugins/AutoServer/. Configuration lives in config.yml. If AutoServer needs to store service data, it uses its own files and unique NamespacedKey values so it does not collide with other plugins.

Compatibility with other plugins

AutoServer is written against the standard Paper/Bukkit API and avoids NMS, reflection, or direct access to Minecraft internals unless absolutely necessary. Its paper-plugin.yml declares api-version: 1.21. AutoServer does not block the main server thread: data collection that must run on the main thread is kept short and synchronous, while network operations run asynchronously. Any network error, timeout, or invalid API response is caught inside the task: AutoServer logs the error and continues with the next cycle in 4 minutes without cancelling the task or crashing the server.

Configuration

config.yml controls:

  • enabling/disabling the plugin;

  • update interval — 4 minutes by default;

  • initial delay;

  • destination URL or Discord Webhook;

  • HTTP method, headers, and timeout;

  • which fields are included in the payload;

  • logging level;

  • additional server metadata.

Summary

AutoServer provides continuous, background, and safe monitoring for a Purpur 1.21.11 server. It refreshes server status every 4 minutes even with no players online, requires no restarts, does not touch the world, and does not interfere with other plugins. Important limitation: on free Aternos, custom .jar uploads are not allowed — to install AutoServer you need a local server or a paid host with access to the plugins folder, such as Exaroton.

StatusServer Team

profile avatar
  • 1
    Projects
  • 23
    Downloads