Likewise, I was merely telling you why this happens, though I did misremember so I double-checked quickly.
On load, it’s actually backwards, it’s the treasure loading before the coffer that’s the issue, since the treasures try to self-register once they loaded. That’s what they will attempt a second time after 4 seconds in hopes that the coffer finally loaded :slight_smile:

As for the scenarios I described, sure, those are usually situations where this would almost definitely happen, but that does not mean it’s exclusive to those situations, especially with more and more stuff being added to the game and not being optimized, we’re already noticing a bit of a slowdown on load.
Personally I never had this issue, but I do have a pretty decent computer and a fast drive, which is not the norm, though it might only be a matter of time.

In this case I think the easiest solution that would fix this in most cases and not require extra development would be to just give it a generous 20 seconds or so instead of 4 for that second attempt… Nobody is going to jump in the game and launch a purge in the first 20 seconds - especially since most of that will be spent on the loading screen - so there’s plenty of extra time and it would only run anyway if the treasure failed registering the first time :man_shrugging:

Replacing the coffer itself should still pick up all treasure in the radius, like I said before.

1 Like