AutoStopper

Added

• Tested support lines for Velocity 3.5.1 build 615 on Java 21 and Velocity 4.1.0-SNAPSHOT build 16 on Java 25, using one Java 21 bytecode plugin JAR.
• Explicit, isolated server_name to container_name mappings with startup/reload preflight.
• Real readiness strategies: Minecraft status protocol, Docker health, or either signal, all with bounded per-server deadlines.
• Shared lifecycle coordination so simultaneous players use one startup/readiness operation and stop/start/reload races have legal, deterministic outcomes.
• Bounded off-thread Docker execution, bounded plugin shutdown, cancellation, and saturated-worker handling without blocking Velocity event or command workers.
• Capped exponential retry for failed automatic stops while preserving activity until a confirmed stop.
• Atomic configuration reload: an invalid candidate is rejected completely and the previous immutable snapshot remains active.
• Permission nodes autostopper.command.status and autostopper.command.reload, plus the explicit autostopper.admin umbrella.
• Typed operational state and sanitized /autostopper status diagnostics with operator actions; raw Docker stderr remains in operator logs.
• Pinned legacy/current Compose examples, packaged Velocity runtime tests, a real Docker/Compose/Minecraft release-candidate gate, reproducible Maven Wrapper builds, strict dependency/package checks, SpotBugs, JaCoCo, and deterministic CI gates.
• Installation, security, configuration, troubleshooting, Modrinth, and 1.1.2 migration documentation.

Changed

• Generated inactivity timeout and public documentation now agree on 300 seconds.
• New installations generate no monitored mappings instead of controlling example containers by default.
• Velocity's actual lowercase data path is documented as plugins/autostopper/config.yml.
• A running Docker container must pass configured readiness before waiting players are connected.
• Inactivity scans retain activity on Docker failures and stop only explicitly mapped, running, player-free servers.
• Managed containers are expected to exist in advance and use restart: "no"; unmonitored hubs remain outside AutoStopper's lifecycle.
• Docker socket/group access is explicitly documented as a privileged, host-root-equivalent trust boundary rather than ordinary non-root isolation.
• The canonical build is the checksummed Maven 3.9.16 Wrapper on JDK 21 through 25.

Removed

• The prototype's custom /server command/interceptor. Velocity owns /server and its permissions; AutoStopper now observes normal pre-connect events.
• Unbounded fixed-delay startup behavior, blocking Docker work on platform workers, and partial or silent configuration fallback.

Migration

Read the complete 1.1.2 to 2.0.0 migration guide before replacing the artifact. The runtime matrix, lowercase data path, permissions, readiness policy, explicit mappings, pinned examples, and Docker security boundary all require operator review.