Table of Contents
Introduction
Setting a BentoBox world as the server default world allows to avoid the generation of the default vanilla worlds.
In this step-by-step example/tutorial, we're considering you're doing this for BSkyBlock
, yet the process remains identical for all available gamemodes.
Preparations
- The whole procedure needs to be executed while the server is switched off.
- Delete the vanilla worlds (
world
,world_nether
,world_the_end
) by deleting their folders.
Highlighted folders are those of the default world. They must be deleted.
server.properties
Open the server.properties
file.
Find the following line:
level-name=world
Replace world
with the name of the BentoBox world. It usually is [gamemode]_world
, where [gamemode]
is the lowercased gamemode's name (e.g. bskyblock
or caveblock
). However, it can be modified in the gamemode's config.yml
file, so make sure it is the correct one.
For the sake of simplicity, we will expect the world name to remain untouched and generic, and therefore being bskyblock_world
.
The line should now look like this:
level-name=bskyblock_world
bukkit.yml
Open the bukkit.yml
file: we need to tell Bukkit that the world we're willing to make the default one uses a custom generator, otherwise it will mess up the world generation.
The configuration section we're willing to edit being optional, it is extremely likely that it does not exist already in your bukkit.yml
file. See the official Bukkit Wiki for more details about the section.
Add the following section to your file (do appropriate revisions if you're not using the Nether or the End at all):
worlds:
bskyblock_world:
generator: BentoBox
bskyblock_world_nether:
generator: BentoBox
bskyblock_world_the_end:
generator: BentoBox
Getting started
- Install BentoBox
- Migration from ASkyBlock or other plugins
- Set a BentoBox world as the server default world
- Database transition