AegisGuard is designed to play nicely with the modern Minecraft ecosystem. However, like any powerful shield, it cannot be wielded alongside another shield.

These plugins are natively supported or highly recommended.

Plugin	Function	Compatibility Notes
Vault	Economy API	Recommended. Allows players to use server currency.
EssentialsX	Economy / Chat	Works perfectly. No conflicts.
ChestShop	Player Shops	Supported. Players can create shops inside their claims.
QuickShop	Player Shops	Supported. Chest interactions are protected but shop creation is allowed for members.
ShopGUI+	Server Shop	Fully compatible for menu-based economies.
Dynmap	Web Map	Automatically renders plot borders (Green = Player, Red = Server).
BlueMap	Web Map	Supported via standard marker API (3D visualization).
Pl3xMap	Web Map	Natively supported fast 2D renderer.
PlaceholderAPI	Chat formatting	Use %aegis_owner%, %aegis_plot%, or %aegis_role% in chat/tab.
LuckPerms	Permissions	The recommended permission manager.
WorldGuard	Global Flags	You can use WG for global regions (like Spawn) alongside AegisGuard.
Multiverse	World Management	Fully compatible.
DecentHolograms	Visuals	Compatible. AegisGuard uses packets, so it won’t break DH.

AegisGuard includes powerful integrations directly in the core jar, no extra plugins required.

Connect your server events directly to a Discord channel via Webhooks.

Features: Log land claims, deletions, merges, and admin actions.

Setup: Paste your Webhook URL into config.yml.

For large networks or performance-critical servers, AegisGuard supports enterprise storage.

MySQL / MariaDB: Recommended for production servers.

SQLite: Default local file storage (no setup required).

Do NOT install these alongside AegisGuard.
Running two land-protection plugins simultaneously causes “Event Conflicts” (the plugins fight over who handles the block break).

⛔ GriefPrevention: Uses a similar “Golden Shovel” mechanic. Will conflict immediately.

⛔ Lands: Similar chunk-based system. Incompatible.

⛔ Towny / Factions: These modify chat and land events heavily. Not recommended.

⛔ Residence: Conflicting selection tool logic.

⛔ RedProtect: Conflicting region logic.

⛔ PlotSquared: Do not use on the same world (conflicting generator logic).

Rule of Thumb: If the plugin allows players to claim land via a tool or command, it is NOT compatible.

WorldEdit / FAWE: AegisGuard prevents WorldEdit operations inside claims by default to stop griefing.

• Admins: Must use /agadmin bypass to WorldEdit inside player claims.
• Players: Generally cannot use WorldEdit inside their own claims unless you explicitly grant bypass permissions (not recommended).

Custom Chat Plugins: If you use a plugin that aggressively formats chat (like VentureChat or ChatControl), it might override the AegisGuard “Channel” feature. You may need to tweak listener priorities in their configs.

Heavy Hologram Plugins: AegisGuard sends packet-based titles/holograms for visuals. While generally compatible, running heavy hologram plugins alongside might cause visual clutter in spawn areas.