@JoseDouglas26 If the solid node check didn't work out thats okay, the positional checks for top and bottom were what was most important and it looks like you implemented them good. All that was…
No problem, but I actually remembered that torches have a way of checking for solid blocks here is the block of code responsible
- Check if placement at given node is allowed
local function…
I would try using a pre-existing group that fits the need well instead of inventing a new 'solid' group definition and retroactively applying it to all applicable nodes. The group building_block…
I tried placing the twisting vines on both warped and crimson nylium, dirt, and netherrack. Under them, on top of them, on the sides of them. Why does the twisting vines check for solid nodes? And…
Here is chunk of code responsible for village generation checks found in mcl_villages/init.lua starting ln 81
if mg_name ~= "singlenode" then
mcl_mapgen_core.register_generator("village…
before changes: weeping and twisting vines could be placed either on top or bottom with no checks (incorrect) testing: weeping vines can be placed at top of block but not bottom (correct) twist…
Note that a similar issue exist with mobs_debug. It may be worth adding that into settings in a later pr as well if we decide to push this setting through.
Was there any reason the old PR never went through? It looks like it was just about ready for merge.
@JoseDouglas26 The issue is that none of the new lush cave stuff has a limit on its maximum y level, or the humidity data to help minetest place lush caves in a more apropriate biome (the mc wiki…