WorldBlockChanger -----
Want to remove all ores from an existing world? Maybe just specific chunks? This is the plugin for yDo you want to create a limited world?
So players have to use your resource world?
Maybe you want to remove all ores to add custom ones, or maybe you want a limited economy.
This is the plugin for you.
Replaces all ores to stone.
Replaces all deepslate ores to deepslate.
Removes spawners, chests and minecart chests.
For example:
3 3 3 3 3 3 3
3 2 2 2 2 2 3
3 2 1 1 1 2 3
3 2 1 0 1 2 3
3 2 1 1 1 2 3
3 2 2 2 2 2 3
3 3 3 3 3 3 3
So if the system has done until ChunkID 2. Everything within circle two has been done. "Done" means, the system has replaced the ores, and removed spawners, chesta and chest minecarts.
In order to efficiently let Minecraft replace the chunks, there is a scheduler system, which makes sure there is only a specific number of chunks being replaced at the same time.
/wbc start <fromChunkId> <toChunkId> <offsetBlockX> <offsetBlockZ> [world]
/wbc stop
/wbc terminate
So players have to use your resource world?
Maybe you want to remove all ores to add custom ones, or maybe you want a limited economy.
This is the plugin for you.
Features:
Replaces all ores to stone.
Replaces all deepslate ores to deepslate.
Removes spawners, chests and minecart chests.
System Design:
Chunks are added starting from the middle, to the outside, this is done by adding it as circles. The number of the circle which is called the ChunkID.
For example:
3 3 3 3 3 3 3
3 2 2 2 2 2 3
3 2 1 1 1 2 3
3 2 1 0 1 2 3
3 2 1 1 1 2 3
3 2 2 2 2 2 3
3 3 3 3 3 3 3
So if the system has done until ChunkID 2. Everything within circle two has been done. "Done" means, the system has replaced the ores, and removed spawners, chesta and chest minecarts.
In order to efficiently let Minecraft replace the chunks, there is a scheduler system, which makes sure there is only a specific number of chunks being replaced at the same time.
Commands:
/wbc start <fromChunkId> <toChunkId> <offsetBlockX> <offsetBlockZ> [world]
- fromChunkId: From what circle should we start (maybe some inner circles are already done, this is useful when restarting)
- toChunkId: Until what circle should we generate. I calculated the value for you, for the world you made it should be: 250
- offsetBlockX, offsetBlockY: In order to set the circles at the right spot (because the spawn point is not at 0,0). The values for you should be: X = -592, Z = 352 (I mistakenly called it Y inside the code, this is incorrect, should be Z).
- [world]: For players it will use the current world by default. You can also specify a specific world.
- This command starts the scheduler, and therefore starts scheduling the chunks. Starting from the first circle to the end circle.
- toChunkId: Until what circle should we generate. I calculated the value for you, for the world you made it should be: 250
- offsetBlockX, offsetBlockY: In order to set the circles at the right spot (because the spawn point is not at 0,0). The values for you should be: X = -592, Z = 352 (I mistakenly called it Y inside the code, this is incorrect, should be Z).
- [world]: For players it will use the current world by default. You can also specify a specific world.
- This command starts the scheduler, and therefore starts scheduling the chunks. Starting from the first circle to the end circle.
/wbc stop
- This command stops the scheduling. Any scheduled chunks will **not** be removed, if you have the time, you can wait until the already scheduled circles are done. After being done, it will give a message to what circle it has fully done.
/wbc terminate
- This command stops the scheduling, this also removes all scheduled chunks. It will give a message, to tell you to what circle it has fully done. So this immediately terminates the whole process.
Resource Information
Author:
----------
Total Downloads:
47
First Release:
Jan 8, 2023
Last Update:
Jan 8, 2023
Category:
---------------
All-Time Rating:
0 ratings
Version
-----
Released:
--------------------
Downloads:
------
Version Rating:
----------------------
-- ratings