🐛 Treasure Caskets fail to despawn

[TeoTwawki]

I affirm:

• [x] I understand that if I do not agree to the following points by completing the checkboxes my issue will be ignored.
• [x] I have read and understood the Contributing Guide and the Code of Conduct.
• [x] I have searched existing issues to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated.

OS / platform the server is running (if known)

Windows Server 2019

Branch affected by issue

base

Steps to reproduce

Spawn a casket. Fail to open it and run out of chances. Casket doesn't despawn. Waited for way longer than it shoudl be staying up, just never depopped. Unsire if this had anything to do with my failed attemtp to open it.

See https://github.com/LandSandBoat/server/discussions/3331

This appears to be cosmetic (rezone and its gone) so I suspect a packet is failing to be sent to tell the client.

Expected behavior

Caskets eventually time out, and if you run out of attempt sthey depop right away,

[TeoTwawki]

may be an additional bug with interacting with caskets after the 1st, not sure I could not repro myself:

[8:46 AM]mr_seatbelt: Teo I had about half a dozen chests from some quick kills. I clicked a blue chest and saw the temp items inside. From then on I can’t do anything with any other chests. [8:46 AM]mr_seatbelt: I can take the temp items from the first chest but all other blue and brown chests are unresponsive after clicking the first. [9:49 AM]mr_seatbelt: An hour later I still get no response from any chest. [9:49 AM]mr_seatbelt: Haven’t logged or anything, but the issue doesn’t seem to time out. [9:56 AM]mr_seatbelt: Okay I take that back. I can interact with new chests. [9:56 AM]mr_seatbelt: At least a couple right now. [9:56 AM]mr_seatbelt: I’m confused.

He might just be confused about which caskets are "real" and which are the ghost ones the client didn't despawn.

[CatsEyeXI]

this was also reported on catseye