Prevent GUID overflow

[Dreez]

Not sure how many crashes are related to GUID overflows but considering the amount of players spawning gameobjects / NPCs and similar:


Implement a scheduled server restart if the GUID limit is about to be reached with an automatic announcement notifying the players about the reason:

"The server will be restarted shortly to prevent a crash."
Server restart in 10 minutes

Restarts are way better than crashes!

[mortimz]

nah i like crashes better

[Aunstic]

You're suggesting this, but don't know if this is even the cause for 100% of the crashes. I'm not sure what type the GUIDs are stored at, but if its a 32 bit int the max is 8^31 (2.14 billion and some change). I doubt there's enough players to actively generate over 2 billion bones.

[Natrist]

The way Blizzard worked around this problem is by recycling the GUID values like when a monster would die and be destroyed. On private servers GUID values are not only explicitly used by a single monster, but this also means that monsters are still receiving updates when dead and de-spawned, thus wasting countless resources and CPU cycles.

[Kuroyu]

Proper and competent programming would avoid this issue fairly easily.