READ THESE WARNINGS.

Pre generating your world with EWG means you can't, under any circumstance, use the async-chunks feature Paper provides you with. This has an extremely high likeliness of crashing your server with the latest version of the plugin.

The same goes for the use of FAWE, or Fast Async World Generation. You cannot use the plugin to pre-generate your world since it is not always compatible with EWG and can completely nullify your progress, with no noticable gain in generation speed to make up for it

For 1.16.1 & EWG, do not use Chunkmaster. It has been throwing non-bypassable errors for this version. You can use both WorldBorder and Chunky, where only a tutorial for WorldBorder is provided here. The rest of this tutorial is made for 1.15.2, but works on 1.16.1 as well (other than Chunkmaster)

We advise you to make use of Chunkmaster for pre-generating your world over WorldBorder. This is because (after thorough testing) we found a 50% speed increase at the start, and no memory leak in the long term. You can use WorldBorder alonside Chunkmaster.

In order to be able to use this, make sure you already have EWG installed and the correct version of WorldEdit

EpicWorldGenerator comes with a setting that allows you to cut off the world at a certain square size. Check this under the world border header.

With both World Border and Chunkmaster, the plugin may very well throw errors where it either Tried to load a block entity for block or Tried to load a DUMMY block entity and failed. Do not worry, this will have no noticeable effect on the map.

It is better to use Spigot over Paper since there are notably less bugs and glitches with spigot during generation. After you are done pre-generating the world, you can always change.

Note that it is advisable to use 6 GB of RAM at a bare minimum in this process. 10 GB or more is preferred.

The <sizeX> parameter is replaced by the distance from <centerX>, <centerZ> to the border. <centerX> and <centerZ> are the (rounded) coordinates of the center of the world, usually 0 and 0.

Replace <world name> by the exact, higher- and lowercase sensitive, name of the world (usually world). Also, replace <padding> with the outcome of the following function: 32 * (renderdistance + 1). You can find the render distance in your */server.properties file on the fourth line: view-distance=8. Eg. (using 8 as the render distance in the "world" world): 32 * (8+1) = 288, so you would ultimately run /wb world fill 20 288 true.

Note that if, at any point in the process of the filling process, the server crashes (restarting doesn't matter), you must run /wb fill cancel as soon as the server restarts. After that, continue the process with the same command as before, but using false at the end. (To stick with the example: /wb world fill 20 288 false, once again followed by /wb fill confirm)

You can check on the progress of the generation task in the console.

Note that a pre-generation process can take a large amount of RAM. This plugin is more lightweight and generally better at managing RAM than WorldBorder, but keep in mind that 5 GB or more is still advisable for this to work at reasonable or better speeds.

For the highest speed of generation, use this plugin on Paper, rather than Spigot.

Note that Paper is less stable than Spigot in some cases. Use at your own risk.

For the 1.15 configuration, you can edit the following settings:

chunks-per-step:
max-pending-chunks:
max-loaded-chunks:

Where changing to a lower number (if your server is lagging) or a higher number (if your server has more calculating capacity or RAM leftover), you will increase or decrease generating speed, while maintaining server stability.

In all of these presets the dynmap:setting is on true. This allows you to render a Dynmap alongside generating the world, at the cost of about 10% performance. If you're not interested in a Dynmap, you are best off turning dynmap: to false.

Replace <world name> by the exact, higher- and lowercase sensitive, name of the world (usually "world"). Also, replace <distance> with the amount of blocks you want in all directions (makes a square). Example (using "world" and a 10,000 block radius): /chm generate world 10000 blockradius.

Right after running the command and leaving the server, you must check the console to see if it actually started. If it did not, use chm resume 1 in the console. The 1 increases by one every time you start a new task with Chunkmaster.

You can check up on the progress of the generation task in the console.

Please contact Coco if you are not getting more than an average of 20 chunks per seconds in the generation task, so we can both improve performance and improve this tutorial. (Please don't jump to conclusions, and wait for at least 15 minutes to get an accurate speed)