🗺️ Integrations & Compatibility
AegisGuard v1.2.6.1 is built for the modern Minecraft server ecosystem and is designed to work across:
- Spigot
- Paper
- Purpur
- Folia
This release also tightens reload behavior, hook declarations, and cross-server scheduling so integrations behave more safely on live servers.
✅ Native and Recommended Integrations
These integrations are supported directly or are part of the normal recommended AegisGuard setup.
| Integration | Function | Notes |
|---|---|---|
| Vault | Economy bridge | Recommended for money-based claims, resizing, group treasury, upkeep, and ClaimBlocks exchange flow. |
| PlaceholderAPI | Placeholders | Native expansion included. Uses the %aegis_...% placeholder namespace. |
| Dynmap | Web map | Native map marker support with configurable layers and styles. |
| BlueMap | 3D web map | Native support for claim visualization. |
| Pl3xMap / Squaremap | Web map | Supported through the Pl3xMap-style hook path used by AegisGuard. |
| Discord Webhooks | Event logging | Built-in webhook support for claim and admin events. |
| SQLite | Database storage | Supported and useful for smaller or self-contained servers. |
| MySQL / MariaDB | Database storage | Recommended for larger or network-style servers. |
| YML | Flat-file storage | Supported for simpler setups. |
🔌 Built-In Features and Hook Systems
AegisGuard includes several built-in hook systems without needing separate addons.
🗺️ Map Hooks
AegisGuard can hook into:
- Dynmap
- BlueMap
- Pl3xMap
- Squaremap
These hooks are optional and can be enabled or disabled in config.yml.
💬 PlaceholderAPI
AegisGuard ships with a built-in PlaceholderAPI expansion using the %aegis_...% identifier.
Examples include:
%aegis_player_plot_count%%aegis_plot_owner%%aegis_plot_role%%aegis_plot_status%%aegis_plot_sale_price%%aegis_plot_flag_<flagname>%
📢 Discord Webhooks
Discord webhook support is built in and can be configured directly in config.yml.
Supported event categories include:
- claim creation
- claim deletion
- claim merges
- admin actions
💾 Storage Backends
AegisGuard 1.2.6.1 supports:
- YML
- SQLite
- MySQL
- MariaDB
This bugfix release also improves storage backend consistency and SQL startup reliability.
🛡️ Protection Plugin Coexistence
Unlike older versions and older documentation, AegisGuard 1.2.6.1 now includes a real protection compatibility layer.
When hooks.protection_compat.enabled is enabled, AegisGuard can yield to external protection in overlapping areas according to the configured overlap policy.
Current protection compatibility hooks exist for:
- WorldGuard
- GriefPrevention
- GriefDefender
- Towny
- Residence
The default overlap policy is:
EXTERNAL_WINS
That makes coexistence safer when another plugin already controls an area.
Important note
This does not mean every dual-protection setup is ideal. It means AegisGuard is better prepared for:
- staged migrations
- global-region coexistence
- mixed protection environments where another plugin should take priority in some spaces
If your goal is a clean server setup, it is still usually better to let one main land-claim system handle ordinary player claims wherever possible.
🚚 Migration Compatibility
AegisGuard includes built-in migration tooling for:
- GriefPrevention
- GriefDefender
- Lands
This is the recommended path if you are moving away from an older protection plugin and want to avoid long-term overlap.
🏪 Shop and Market Ecosystem
AegisGuard supports both built-in market systems and optional external market/shop bridges.
Built-in systems
- Local Market
- TradeStalls
- plot sale listings
- auction listings
- zone renting
External bridge support
The current config also supports optional external bridge entries for plugins like:
- QuickShop
- Shopkeepers
- ChestShop
- ExcellentShop
These are handled through the local market hub and configured commands rather than a hard API dependency model. That means AegisGuard checks whether the named plugin exists, then opens the configured bridge action for that plot.
This makes external market integration flexible, but it is also more configuration-driven than a deep native hook.
⚠️ Use With Care
WorldEdit / FAWE
WorldEdit is listed as an optional ecosystem dependency, but large editing tools should still be used carefully around protected areas.
For staff workflows, use proper admin permissions or runtime bypass where appropriate:
/agadmin bypass
If your staff uses WorldEdit or FAWE heavily, test your workflow first before using it on a public server.
Overlapping Claim Plugins
Even with protection compatibility enabled, it is still wise to avoid stacking multiple full player-claim plugins in the same normal gameplay flow unless you have a clear reason.
Coexistence is best used for:
- migration periods
- special server regions
- global-region precedence
- compatibility-focused mixed environments
Not every multi-protection setup is automatically a good long-term design.
❌ Not Recommended as Your Main Parallel Claim Stack
These plugins may be detected, migrated from, or partially coexisted with in some cases, but they are not ideal as permanent overlapping player-claim systems unless you intentionally design around that:
- GriefPrevention
- GriefDefender
- Towny
- Residence
- Lands
- PlotSquared
For most servers, the best practice is:
- choose AegisGuard as the main claim system
- use migration tools where needed
- keep overlap limited and intentional
🧭 Final Compatibility Notes
For 1.2.6.1, the safest summary is:
- AegisGuard is fully modern-server oriented
- it supports Folia, Paper, Purpur, and Spigot
- it includes native map, PlaceholderAPI, Discord, and storage hooks
- it now has a stronger external-protection compatibility layer
- it supports migration away from older protection plugins
- it works best when long-term overlap is planned carefully instead of improvised
If you are deploying AegisGuard on a public server, test your map hooks, economy hooks, and any protection/plugin coexistence rules before going live.