382956a941
The reset stamp is only meaningful while it is ahead of LastMoved. Clearing it from the LastMoved setter covers every path that records a real move (SetLastMoved, MoveToWorld, direct writes) and lets VerifyCompactInfo free the CompactInfo instead of holding it forever for any item that was ever unfrozen. Deserialization applies the same guard, since minute rounding can land the stamp on LastMoved. The setter deliberately does not touch scheduler registration: MoveToWorld assigns LastMoved while parent/map are mid-transition and defers registration until its state is final. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| BaseMulti.cs | ||
| Container.cs | ||
| Containers.cs | ||
| DecayScheduler.cs | ||
| Item.cs | ||
| Item.Enumerable.cs | ||
| Item.Messages.cs | ||
| ItemBounds.cs | ||
| Layer.cs | ||
| LightType.cs | ||
| OutgoingVirtualHairPackets.cs | ||
| SecureTradeContainer.cs | ||
| VirtualCheck.cs | ||