Making yet another post about this because of lazy devs

[Packetdancer]

And then we bring in Dave and he finds something we missed.

This is an entire mood.

And it turns out this wasn't entirely a bug but inefficient server processing that caused a backlog, so a lot of the results weren't ready to be communicated in time for the end of the lottery. Rather than fixing a bug the solution might be improving how efficient it is.

The root cause isn't a bug, per se, but the fact that the process was not fault-tolerant is, at least in my opinion. It's an understandable one to make, given that data replication is often handled by some underlying database system and not by the game's own code directly. Still, the code surrounding it should probably have required an acknowledgment of data transferred successfully, and add things to a retry queue if it failed to get said acknowledgment, and I do think the lack there qualifies as a bug.