Vaettir · 1.5.2 · Fixed

The post would not dispatch a single trip, and said nothing. 1.5.1 stopped trusting Container.IsInUse() for destination chests, because the raw m_inUse field is only ever written by the peer that owns the ZNetView and strands the moment ownership moves. CarryRun.Available was still asking that same question about the post itself, so the chests became reachable and the post never set off - the fix could not reach the person it was written for.

It is worse on a post than on a chest, because you have to open a post to put anything in it. That is the act that sets the flag, so losing ownership before the window closes strands it permanently - and building a new post does not help, because using it recreates the state. Both callers go through one helper now.

Discussion

Nothing said yet.

Sign in or make an account to join in.