Tower Waystone

v1.0.8 - Tower placement and light beam fixes

Fixed

• New towers placed wrong / spawning underwater: the simply_waystone_tower/_ruins/_pillager structures had their floor directly at y=0, without the 5-block dirt basement the mod's own towers have (which use start_height.absolute = -6). Reusing that same offset buried the 3 new tower families about 6 blocks into the terrain. Fixed to start_height.absolute = 0 for all three.
• Removed minecraft:swamp and minecraft:mangrove_swamp from simply_waystone_tower_ruins's biome tag - those biomes have shallow surface water pools that still spawned the tower underwater even with the corrected offset.
• Light beam too short: the configurable beam added in 1.0.6 cut off just a few blocks above the waystone (height field, defaulting to 6). The beam's starting point is now anchored to the top of the waystone block (which is 2 blocks tall), and the default height is raised to 100 blocks - much more visible in practice. The field stays configurable in waystone_beacon.json; an invalid value (<= 0) falls back to the default.
• Light beam didn't appear/disappear when placing or breaking a waystone: waystone detection only refreshed on chunk load/unload, so placing or breaking a waystone in an already-loaded chunk (the normal case while playing) wasn't picked up - the beam only showed up after the chunk reloaded (e.g. a server restart), and breaking a waystone left a "ghost" beam behind indefinitely. Added a periodic rescan (once per second, via a client tick event) of the chunks within the client's render distance, on top of the existing chunk load/unload handling.

Notes

The light beam fixes are purely client-side and visual. None of the changes in this version affect world generation, saved data, or dedicated server behavior.

JAR: tower_waystone-26.2-neoforge-26.2.0.37-beta-1.0.8.jar

Tag: 26.2-neoforge-1.0.8