Sinka · 1.2.0 · Added

A chest can be set down on top of another chest (StackContainers, on). Vanilla refuses this outright and no snap point could ever have changed it, because two separate rules are in the way. Player.UpdatePlacementGhost marks the ghost invalid whenever the piece you are aiming at has WearNTear.m_supports off, which every chest does - the same reason a torch cannot go on a chest. And WearNTear.UpdateWear runs if (m_noSupportWear) { UpdateSupport(); if (!HaveSupport()) num = 100f; }, where 100 is the whole of the piece's health: a chest that ends up unsupported is destroyed with its contents. The field name reads backwards; it means "no support, wear".

Discussion

Nothing said yet.

Sign in or make an account to join in.