Storage & Persistence
Plugin data folder
After first boot, IgnisCore creates a data folder (typically plugins/IgnisCore/ on Bukkit, platform-specific on Sponge).
| Path | Purpose |
|---|---|
blocks/ | Drop-in block extension JARs |
items/ | Drop-in item extension JARs |
placed-blocks.json | Index of placed custom blocks in the world |
resourcepack/ | Generated resource pack builds |
config.yml | Server configuration — see Configuration |
Extension JARs
| Kind | Deploy path | Reload |
|---|---|---|
| Block | blocks/ | /ignis reload blocks or all |
| Item | items/ | /ignis reload items or all |
Bundled extensions ship inside the bootstrap JAR and extract on first boot. Drop-in JARs in these folders override or add types.
Placed blocks
Placed custom blocks are tracked in placed-blocks.json.
- Legacy
placed-blocks.ymlfiles are migrated automatically on first load - After migration, the YAML file is renamed to
placed-blocks.yml.migrated
Breaking or replacing a placed block removes its entry from the index.
Resource pack artifacts
Generated packs and build history live under resourcepack/. The number of retained builds is controlled by performance.resource-pack-retain-count in config.yml.
Related
- Extensions — manifest and config layout
- Block lifecycle — placed vs active phases
- Troubleshooting — common data-folder issues