Saved Data and Backups
data.yml
Section titled “data.yml”plugins/Carousel/data.yml stores entries under carousels.<id>. Commands and editor actions save changes immediately. External integrations changing Java settings must save explicitly.
| Saved fields | Purpose |
|---|---|
location | Serialized world and center position. |
amount, ticks, degreeIncrease, radius, stepHeight, maxHeight | Horse count and animation. |
leash, leashHeight, leashOffset | Holder visibility and placement. |
small, inventoryEnabled, allowRiding, saddlesEnabled | Appearance and access. |
rainbowGlow, glowColor | Rainbow or fixed scoreboard glow. |
Stop the server before manual edits and back up first. Use commands/editor controls during normal operation so live and saved settings agree. The file does not store entity UUIDs or a persistent running/stopped flag.
Loading
Section titled “Loading”Valid entries start on enable and reload. Invalid or unavailable-world locations are skipped with a warning and remain saved. Load the missing world before reloading. Loading bounds amount/ticks and normalizes non-finite or negative movement bounds; an unknown glow color disables fixed glow.
destroy keeps saved data, so the ride returns on enable/reload. delete removes its entry. Incomplete manual entries do not necessarily inherit all new-ride defaults; preserve complete records.
Entity Recovery
Section titled “Entity Recovery”Startup and /carousel purge scan loaded-world entities for the exact internal custom-name marker. They do not force-load every chunk. Do not assign that marker to unrelated entities. Purge also removes active ride entities; reload saved rides to recreate them.
Back up world files and data.yml together before renaming worlds, migrating servers or testing new server versions.