No clue how to fix this exception.

It does loke like the same!

Although, that was framed like a very multiplayer specific thing, but here Diego has basically said it is Construct's object destruction logic not dismissing a request to destroy something that has already been destroyed.

So maybe this can manifest without multiplayer in other scenarios too, depending on how things are implemented.

So maybe this can manifest without multiplayer in other scenarios too, depending on how things are implemented.

Technically yes.

But the main point was to give an example where the crash can be reproduced consistently, so it can be debugged and fixed.

The proposed solution was obviously tailored towards multiplayer improvements, as it originated from the old feature request platform. So that can be technically ignored. It would have worked as a workaround to prevent this multiplayer edge case from happening in the first place, not fixing the actual crash.