Configuration
IgnisCore reads config.yml from the plugin data folder. Reload server config without reloading extensions:
/ignis reload server
Default config
resource-pack:
host: "localhost"
port: 8080
public-url: "http://localhost:8080/resourcepack.zip"
performance:
chunk-restore-blocks-per-tick: 16
visual-refresh-blocks-per-tick: 32
resource-pack-retain-count: 3
resource-pack
| Key | Purpose |
|---|---|
host | Bind address for the embedded HTTP server that serves the pack |
port | TCP port for the pack server |
public-url | URL sent to clients — must be reachable from player machines |
Set public-url to your server's public address (or a reverse proxy) so clients can download the pack. Use /ignis pack in-game to rebuild and apply after extension changes.
performance
| Key | Purpose |
|---|---|
chunk-restore-blocks-per-tick | Rate limit for restoring barrier blocks after explosions |
visual-refresh-blocks-per-tick | Rate limit for block visual updates |
resource-pack-retain-count | Number of historical pack builds to keep on disk |
Extension config
Block and item extensions ship their own config.yml inside each extension JAR. These are separate from the server config.yml — see Extensions and the Extension Cookbook.
Related
- Resource packs — how packs are built and applied
- Storage — placed-block persistence
- Example config — production-oriented sample