Slightly Incompatibility with Silkspawners about dungeontweeks HOT 2 CLOSED

might actually need to sync it with silkspawners in some way difficult to fix since the tile entities are not my own. Since yeah you can place it nothing happens but, what happens when you setblock this issue might still occur? I don't know maybe there is no fix on silkspawners side and when people use setblock with dungeon tweaks they should use the nbt required else very slim chance it might freak out.

Well based on capabilities and since structures can override existing loaded chunks there is no set way in fixing it via setblock the best I can do is on block place and on block break set hasScanned to true. will solve this on what I can actually fix since dungeon tweaks is too dynamic. Anyways your scan radius would have to be really high anyways and would have to be intended in some way if it's setblock via command but, I will be fixing it up on the other two to sync fixes as best I can. If that behavior occurs it's because the user didn't put the required new nbt for hasScanned and it could even be intended so I will fix the other two but, have to leave the setblock alone

from dungeontweeks.

newer version of silkspawner patches this

from dungeontweeks.