Installation and Updating

Clean installation

1. Run Paper 1.21.11 with Java 21.
2. Stop the server completely.
3. Place AeroOneBlock-1.0.0.jar in plugins/.
4. Install PlaceholderAPI if you need placeholders. Install Vault and an economy provider if any money cost is positive.
5. Start the server and inspect the console for the first AeroOneBlock error, if any.
6. Review the generated plugins/AeroOneBlock/ directory.
7. Restart safely after finishing the initial configuration.

On first startup, AeroOneBlock creates or loads three void worlds: aero_oneblock, aero_oneblock_nether, and aero_oneblock_end. World names can be configured, but changing them on a live installation does not move existing islands.

Optional dependency behavior

PlaceholderAPI and Vault are soft dependencies. Basic island gameplay can start without either plugin. However:

• %aerooneblock_*% values require PlaceholderAPI.
• Placeholder-based upgrade comparisons remain incomplete without PlaceholderAPI.
• Positive recreation or upgrade costs require Vault and an economy provider.
• A configured cost of 0 disables the related money requirement.

Generated layout

plugins/AeroOneBlock/
├─ config/   gameplay and system settings
├─ menus/    built-in inventory interfaces
├─ lang/     player-facing text and translations
└─ data/     live island and player records

Do not edit data/ while the server is running. It is plugin-owned state rather than a configuration template.

Safe update procedure

1. Stop the server.
2. Back up all three AeroOneBlock worlds and the complete plugin directory together.
3. Archive the previous JAR and place the new JAR.
4. Read release notes for configuration or data migrations.
5. Start the server and review the complete startup output.

Do not use Bukkit /reload or third-party hot-reload tools as a replacement for a restart. /aerooneblock reload is intended for supported configuration, menu, and language changes. JAR and dependency changes require a full restart.

Backup scope

islands.yml alone is not a complete backup. Physical builds are stored in world data while ownership and progress are stored under data/. Keep worlds, data, configuration, menus, and languages in one consistent backup snapshot.