Describe the bug:
im currently pregenerating my world. spelunkery throws hundreds of setblock errors about the large emerald vein. the server ends up hanging and eventually killed by watchdog. fixed when spelunkery is removed.

Versions: (BEFORE SUBMITTING A BUG REPORT, make sure you have the most up-to-date versions of Spelunkery, Moonlight Lib and Supplementaries)
Minecraft version: 1.20.1
Spelunkery version: 0.3.6
Moonlight Lib version: 2.12.9 (slightly downgraded because of version compatibility)
Fabric API / QSL / Forge version: 47.2.17

Other mods:
crashlog: https://pastebin.com/M3SZRBVK

Logs:

https://mclo.gs/yD6O84u
https://mclo.gs/WFciC1N

To Reproduce:

1. run my spelunkery and my other addons
2. pregenerate chunks
3. watch as the server starts to lag and freeze then hang

Expected behavior:
that the server doesnt hang

Screenshots:
n/a

Additional info:
I am aware theres another person with the same problem, I am reposting because it was said their problem would be fixed in 0.3.5, and i'm on 0.3.6 and it's still present.

The Detected setBlock in a far chunk call shouldn't cause any actual slowdowns
Features have a certain radius in which they're allowed to set blocks

Large emerald veins may go beyond said limit but it's not problematic

Reason being: the check for this set block happens for every setblock (see WorldGenRegion) call and if this error occurs it returns false and no block gets placed (and therefor no chunk retrieval etc. meaning you could say it's faster than actually setting the block)

Spelunkery in general adds worldgen features which do slow down chunk generation (as any feature does)
Your modpack just seems to be hitting the limit on what your CPU can handle, there is no actual "fix" for this

The only thing you can do is to make sure you have all the relevant performance mods and / or tune down world generation mods / datapacks

(To get more information on what you could do you'd need the thread dumps which modernfix usually generates (might have to enable a config to force it to do so) and use Spark to see what's the biggest performance impact)