Requirements
- A backed-up staging Paper 1.21.11 server.
- Java 21+. This release was tested with Java 25.
- The official PacketEvents 2.14.0 Spigot build.
- The protected ForgeGuard release JAR obtained through the official release channel. The BuiltByBit listing is still being prepared.
First start
- Stop the server normally and back up its worlds and plugin data.
- Put PacketEvents and the ForgeGuard JAR in
plugins/, keeping only one ForgeGuard installation. - Start fully. Check startup messages and
/forgeguard health. - Grant appropriate staff permissions and open
/fg menu. Read the staff guide before granting moderation or inventory-editing permissions. - Leave the shipped OBSERVE settings and disabled response ladder while reviewing normal play.
Configuration and moderation records live under plugins/ForgeGuard/. Back up that directory before replacing a JAR or changing settings. A successful menu opening on a different server version does not establish detection coverage.
Optional browser access
The website does not host your Minecraft server. Create your web account and pair your server, then approve the site in the Minecraft admin GUI. Each owner manages their own linked servers and staff roles. Hosting the included website package yourself is optional; check the included deployment guide and provider costs first.
Verify the workflow
Try a permitted inventory inspection, spectate and return, a temporary test freeze and release, then review an evidence case and recording where available. Use test players and a private staging server. Findings are observations, not verdicts.
Watch the feature guide · Exact supported scope · Discord support