client/graphics_interface.py, in function backendMessage, handles several types of messages in a big if-elif-else. Most of those messages come from the server, but RequestUnitAt originates in the client. Since we use the same error reporting for all of them, an invalid RequestUnitAt results in a warning that blames the server, when the client should be outright crashing.
The real solution is probably that all server-to-client messages should be handled in backend.networkMessage, rather than being forwarded on to other client components.
RequestUnitAt is now gone, so the bug is fixed. But the underlying issue remains: messages from the server should be handled in client.backend; they shouldn't be blindly forwarded on to other components.
client/graphics_interface.py, in function backendMessage, handles several types of messages in a big if-elif-else. Most of those messages come from the server, but RequestUnitAt originates in the client. Since we use the same error reporting for all of them, an invalid RequestUnitAt results in a warning that blames the server, when the client should be outright crashing.
The real solution is probably that all server-to-client messages should be handled in backend.networkMessage, rather than being forwarded on to other client components.