• 1/7/22 9:15 am
- 4.4k views • 0 today
- save_alt 181 downloads
- Compatibility
- Minecraft 1.18
- Changes include
- Functions
0
This Datapack makes stone slowly turn into deepslate when placed under a gold block in a vanilla-like way.
Let's say it is thanks to the pressure applied by the heaviest block in the game.
This can be used in a vanilla skyblock for example because it makes a deepslate generator possible by editing a stone generator.
You can edit the speed of change by changing the "schedule function deepslate_gen:tick 300t" in deepslate_gen/functions/tick.mcfunction file
You can also edit the range (that is currently fixed at 32 blocks around players) by deleting the deepslate_gen/functions/scan.mcfunctions et the files inside the deepslate_gen/functions/layers folder, then running the python script in readme with a different value for d (currently d=32)
Let's say it is thanks to the pressure applied by the heaviest block in the game.
This can be used in a vanilla skyblock for example because it makes a deepslate generator possible by editing a stone generator.
You can edit the speed of change by changing the "schedule function deepslate_gen:tick 300t" in deepslate_gen/functions/tick.mcfunction file
You can also edit the range (that is currently fixed at 32 blocks around players) by deleting the deepslate_gen/functions/scan.mcfunctions et the files inside the deepslate_gen/functions/layers folder, then running the python script in readme with a different value for d (currently d=32)
More like this
5437411
119




Have something to say?
One way to reduce the lag is indeed to reduce the range, or to lower people online.
One other way would be to build the datapack differently, and put for example an itemframe on the gold block with a deepslate block inside. Then instead of checking all around player for stone block bellow gold block, you would look for deepslate entity inside item frame, that is put on a gold block and with a stone block bellow. So you have way less things to check (instead of the 65x65 cube = 4225 blocks), inducing less functions calls so less lags. The problem with that is that it feels less vanilla.
I am currently working on a plugin that will include this deeplsate generator mechanics among other things. Plugins are less laggy than datapacks usually because you have to constantly run functions in datapacks to make things works.