Voyage is a work-in-progress world management solution designed to be simple to use but powerful but needed.
Must also install (dependency):
Not required, but enables extra feature:
- Placeholder API (Placeholder Support)
World Creation
Generate a new world folder based on passed arguments.
Command: /world create
Permission: voyage.admin
--environment:
- NORMAL
- NETHER
- THE_END
--type:
- DEFAULT
- FLAT
- LARGEBIOMES
- AMPLIFIED
/world info <world name> - View information about world
/world options <world name> <option> <value> - Configure world options
Options and values:
time <freeze/unfreeze>- Changes daylight cyclefire <on/off>- Changes fire spread
/entity select - Select an entity
/entity tphere - Teleport entity to your location.
/entity mount - Mount onto entity
/entity remove - Delete entity
/chunk info - View information about the current chunk you're standing in
Voyage comes with multiple basic built-in generators.
In bukkit.yml, add a worlds configuration section.
Then add a subsection with the world name and generator.
worlds:
world:
generator: Voyage:void NOTE: The block generation height of the superflat world can be customized by adding :<height as int> to the end of the generator configuration section.
worlds:
world:
generator: Voyage:superflat:-60 worlds:
world:
generator: Voyage:moon %voyage_version% - Returns version of Voyage plugin
%voyage_world_name% - Returns player world name
%voyage_world_seed% - Returns player world seed
%voyage_world_border_size% - Returns world border size
%voyage_world_all_amount% - Returns amount of world folders
%voyage_world_loaded_amount% - Returns amount of loaded worlds
%voyage_chunk_is_slime_chunk% - Returns player chunk slime chunk status
%voyage_chunk_x - Returns player chunk X coordinate
%voyage_chunk_z - Returns player chunk Z coordinate
In vanilla Minecraft, datapacks are put into the desired world's datapacks folder. However, on Bukkit/Spigot/Paper/etc., they must be placed in the main world's folder.
Contributions are highly appreciated!
When working with Voyage in your local environment, please compile VexelCore and change Voyage's build.gradle VexelCore dependency to be the locally compiled file path.
This solution is temporary while the API gets worked on.
Voyage is awesome, but there are other great open-source plugins to try. Here are a few: