Skip to content

Integrations & compatibility

AtlasRealms has no hard dependency on anything. Every integration below is optional, detected at runtime, and degrades gracefully when it is missing.

Plugin What it is used for When it is absent
PolarPaper The polar world storage backend, and a requirement for the grid layout. Needs PolarPaper 2.1.0 or newer and Java 25. AtlasRealms logs the reason and falls back to folder storage. grid falls back to world (or the plugin refuses to enable, on Folia).
Vault The economy behind /realm create’s cost, the realm bank, and both upgrade ladders. Read fresh from Vault on every use, never cached. Every price is off, not free. The bank button is not drawn, and /realm bank answers that the bank is unavailable. Size permission nodes fall back to setting the border and member limit outright.
PlaceholderAPI Placeholders are resolved inside menu titles, item names and lore. AtlasRealms also registers its own atlasrealms expansion (twelve placeholders, added in 2.5.0). Placeholder text passes through unchanged, with a log line saying so. The atlasrealms placeholders are not registered.
Nexo, Oraxen, ItemsAdder A menu item’s material: may name a custom item — nexo:id, oraxen:id, itemsadder:pack:id (or ia:…). Resolved when the menu opens. The icon warns and falls back to a barrier block. The menu still opens.
Folia / CanvasMC AtlasRealms detects a region-threaded server itself and adjusts scheduling. On Folia, only realm.layout: grid works, and world-building admin commands are refused. CanvasMC needs nothing extra — both layouts and both storage backends work.

There is no WorldGuard, WorldEdit, or Multiverse integration. Realm protection — who may build, open a container, or fight where — is entirely built into AtlasRealms itself, through access levels, rights and flags. See How realms work.