DESYNC is caused by cheating - memory injection

[WhskyTangoFxtrot]

De-synching will happen EVERY time a player modifies their game client. The easiest example is the use of CHEATENGINE or any similar memory injector. "It comes with a memory scanner to quickly scan for variables used within a game and allow you to change them".

Doing so will allow a player to modify their game by finding certain values. Values such as Dust for example. If a player has 30 dust, and they find the proper memory address they can change it infinitely to 5,000+ without the game recognizing they are cheating. The player can then buyout whatever they want in order to instantly finish queues, build advanced ships, etc.

This change is client side and everyone else's client doesn't recognize how that player was able to make 50 ships, take systems with those ships, or finish queues so those clients do their best to ignore the anomalies causing desynch . Saving and reloading will fix the issue, however if you use the cheater's save it will validate the cheater fleets for all clients. Gamebreaking indeed, now go fix it devs.

[gia]

is this server side only? because the game shouldnt let a client fix their dust client side and tell everyone he just built 50 ships out of the blue :/

having said that, the game does desynch, crash, enter infinite loops, corrupts memory, video crash, hang, and whatnot (yeah it can do all of those) without cheating required

[WhskyTangoFxtrot]

I know for sure, if client or host cheat in this manner, the game will desynch. Am I saying that this is the ONLY way a game desynchs, or is this the only issue? no. However, this definitely needs to be fixed.