Mirage
Version 1.1.5
This version was build for minecraft 1.21.1
Requires ProtocolLib
Custom map loading system for minecraft servers. It's able to reset maps to their saved state on server startup and during runtime. The world tracking system also allows for runtime rollbacks without kicking players.
Besides world management, mirage also supports per player chunk rendering:
This image shows different worlds being rendered while we're not leaving our world at all. This gif is in real-time.
Commands
- /world create [world name] [persistent world] [(?) world to copy from]
- /world go [world name]
- /world remove [world name] [target world for players] [(?) show message?]
- /world reset [world name]
- /world save [world name]
- /world settings [world name]
World settings
Access world settings by using
/world settings <world> or by changing the configs directly, located in
server/mirage/saved-worlds/<world>/mirage-world.yml
World configs look like this:
Code (Text):
# Persistent worlds don't get saved/loaded besides this mirage-world yml
# In other words, persistent don't make use of mirage's reset functions.
persistent: false
# Saves the modified world to a .zip in mirage/back-ups/<world name>
# This back-up will ALWAYS happen when the world gets unloaded by Mirage...
# So be very careful, especially with large worlds.
save-changes-to-backup: false
# Loading on start will put the world in the main server directory when the server gets started.
load-on-start: true
# Keep in memory ensures that this world is always loaded in memory. This makes traveling to that world extremely fast.
# But having a lot of worlds always loaded requires a lot of RAM.
keep-in-memory: false
# Rollback allows you to roll back the world in real time.
# This will roughly double the RAM usage of your world.
use-rollback: true