Longhouse 2.0.8
11 September 2026. After 2.0.7.
Repins Vaettir to 1.5.3.
Fixed
- The stowing post could not see the chests in a real base. Its search used a fixed 256-collider buffer with no layer mask, and a buffer that fills is a truncation that reports nothing - every wall, beam, floor and terrain collider competed for those slots. Measured in a real base: over 1,024 colliders within 12m of one post, and all 24 of its chests invisible. It failed exactly where the mod is used and passed exactly where it is tested.
What moved · 1
Vaettir 1.5.2 → 1.5.3
1.5.3
The bug the previous three releases were chasing. None of them was it.
Fixed
The post could not see the chests in a real base.
CollectChestssearched with a fixedCollider[256]and a singlePhysics.OverlapSphereNonAlloccall, with no layer mask. That is a silent truncation: the method fills the buffer you hand it, returns how many it wrote, and never reports that there were more. Every wall, beam, floor, roof tile and terrain collider within range competed for those 256 slots.In a test world that is a handful of objects and the chests are always found. Measured in a real base: over 1,024 colliders within 12m of one post, and all 24 of its chests invisible. The post reported "0 usable chest(s)" with a configured chest two metres away.
It fails exactly where the mod is used and passes exactly where it is tested, which is why it survived three releases and four reports from the same player. The buffer doubles until the result fits now, so nothing can be missed, and it says so when it grows.
Not fixed with a layer mask, though that would be faster: a mask hardcodes an assumption about which layers a container may sit on - chests, ships, carts, anything another mod adds - and a wrong mask fails the same silent way this did.
discuss
Discussion
Nothing said yet.
Sign in or make an account to join in.