Lifecycle
IgniteSky has a real enable/disable lifecycle, and most of the important state hangs off it.
Enable order
| Step | What happens |
|---|---|
| Configs | Configs load first. |
| Storage | The island repository warms its write-through cache from storage. |
| Worlds | Saved per-island worlds are loaded and claimed for their hosting pool. |
| Services | Managers, modifiers, missions, upgrades and integrations wire up. |
| Commands | Player and admin command trees register. |
| Hooks | PlaceholderAPI and other optional hooks register if present. |
Disable order
| Step | What happens |
|---|---|
| Save | The repository flushes island state back to storage. |
| Cleanup | Live island caches clear, pending sessions end and runtime state is dropped. |
Repository behavior
IslandRepository is a write-through cache. Reads hit memory, saves encode a snapshot and persist
asynchronously, and deletes remove the island from both cache and storage. It also stores pending
cross-server arrivals for proxy sharding.
Why this matters
This is the part that keeps the rest of IgniteSky stable. Without the lifecycle and cache model, the wiki would explain how islands work but not how they survive restarts, reloads and cross-server visits.