AquaGuard

AquaGuard

Server-side audit logging, investigation, and rollback for modded Minecraft servers.

AquaGuard records what happens on your server in SQLite or MySQL without running database writes on the server thread. Moderators can inspect a block, trace a player’s actions, preview a rollback, and restore damaged areas with in-game commands.

It is built for modded servers: block entities, container changes, NBT, automated actors, and actions reported by other mods share one audit trail with vanilla events.

One version, three loaders. Every release ships Fabric, NeoForge, and Forge builds for Minecraft 1.21.1, built from the same source with the same version number.

Features

• Audit trail: block breaks and placements, containers, signs, entity interactions, deaths, logins and logouts, explosions, and natural changes such as fire spread, leaf decay, and falling blocks.
• In-world inspection: toggle inspect mode and click a block to see its recent history with timestamps, players, states, and stored details.
• Rollback and restore: preview and reverse changes by player or area, then re-apply a rollback if needed. Rollbacks run in small batches on the server tick to avoid lag spikes.
• NBT-aware history: keeps container contents, sign text, furnace state, item components, and supported block-entity data.
• SQLite or MySQL/MariaDB: SQLite works with no setup. MySQL or MariaDB lets several servers share one database.
• Asynchronous pipeline: writes go through a bounded queue and a dedicated database thread in batches. Lookups run on separate worker threads.
• Operations tools: Discord grief alerts, automatic pruning, CSV exports for moderation evidence, and a database health check.
• Developer API: other mods can log their own attributed actions through AquaGuardAPI.

Chat, command, and item pickup/drop logging is planned.

Commands

All commands live under /ag and use vanilla operator levels.

| Command | Purpose |
|—|—|
| /ag inspect (/ag i) | Toggle block inspection mode |
| /ag area ... | Get the selection wand and set area corners |
| /ag lookup ... (/ag l) | Search by player, radius, position, action, or page |
| /ag rollback ... | Preview or reverse recorded changes |
| /ag restore ... | Re-apply changes from a previous rollback |
| /ag status | Show log count, database state, and active settings |
| /ag export ... | Export a player’s history to CSV |
| /ag prune <time> | Permanently delete history older than the given time |

Inspect, lookup, status, and area need permission level 2. Rollback, restore, prune, and export need level 3.

Full syntax and examples are in the command reference.

Installation

1. Download the file for your loader: aquaguard-fabric-<version>.jar, aquaguard-neoforge-<version>.jar, or aquaguard-forge-<version>.jar.
2. On Fabric, also install Fabric API. NeoForge and Forge need no other mods.
3. Put the jar in the server’s mods/ folder and start the server once.
4. Review config/aquaguard/aquaguard-common.toml and restart after changing it.

AquaGuard runs on the server only. Players do not need it on their clients. It also works in singleplayer and on LAN worlds.

| Loader | Minecraft | Minimum loader version |
|—|—|—|
| Fabric | 1.21.1 | Fabric Loader 0.16.9, Fabric API |
| NeoForge | 1.21.1 | NeoForge 21.1.93 |
| Forge | 1.21.1 | Forge 52.0.16 |

Configuration

Every logging category can be turned off on its own. Database, maintenance, alert, and telemetry settings each have their own section. Read the configuration guide before enabling MySQL or Discord alerts.

Telemetry is off by default. Nothing is sent unless a server owner enables it and sets an endpoint. It never includes player names, UUIDs, chat, or coordinates.

Links

• Source code and documentation
• Report a bug or request a feature
• Changelog
• Developer API
• Contact: Telegram

AquaGuard is released under the MIT License.