Quote:
Odd. I would have thought that a PBEM TBS server-client game design would follow one oft-espoused rule: Never trust the client.
|
Absolutely. This is especially true for a turn-based game, where effectively all you are doing is using the client to fill out an orders sheet which is then processed by the server.
Quote:
I'm reminded of Netrek, which had an open client architecture with known protocols and open sources but a two-pronged approach to client security
|
Lol. I ran a netrek server when I was starting university (yes, I'm old
). The client in that case had to handle things like movement plotting and aiming, which allowed for some fairly major abuse of the client by C-savvy Users (e.g. phasers that didn't need to be aimed with the mouse).
However, I don't see any of these issues with Dom 2. The server should be controlling all amounts/locations/etc, and the client simply indicates how it wants to manipulate these resources. The server then checks the legality of each order issued by the client. Seems simple enough...