When the config is used to set the minimum or maximum Y value for a Big Stone Cluster to a negative number, the minimum and maximum Y seem to be ignored completely; the clusters apear to go back to generating in the usual y 20-80 range.

Steps to reproduce:

• Create a new Minecraft 1.19.2 instance with Forge, Quark and AutoRegLib.
• First, to verify that changing the clusters' min and max y to positive values works, go into Quark's config and set the big Jasper cluster's maximum y to 16, and minimum y to 8.
• Create a new single biome world in Creative mode with the biome set to Desert, so we can see the jasper easily.
• To facilitate easy spotting of jasper clusters, enter spectator mode, and run /effect give @p night_vision 99999.
• Clip into the ground. Observe that all of the jasper clusters are close to the deepslate layer, and that, thus, they generate where the config says they should.
• Go into Quark's config menu and set Jasper's minimum y to -8. Also, add minecraft:deepslate to the list of blocks big stone clusters can replace, so that, if the clusters generate in negative y coordinates like we want, we'll be able to see them.
• Run /tp @p ~5000 ~ ~ to get to a freshly generated area.
• Observe how the jasper clusters now reach much higher, some reaching up into the y 40-50 range, when they aren't supposed to generate above y 16. This seems to imply that they aren't respecting the config anymore now that a negative number was introduced.

Minecraft: 1.19.2
Forge: 43.1.2
AutoRegLib: 1.8-54
Quark: 3.3-369

Github is being frustrating and not letting me edit the issue to add the latest.log I forgot. Here's latest.log:

https://hatebin.com/jczykahkyr