SomeTroglodyte
commented
1 month ago Low effort/benefit ratio. Extremely so.
Unciv is open source, and as such someone will always be able to cheat. Even if you implement strong cryptography in the exchange protocols, invent a transactional change protocol including checkpoint verification - someone has to hold the keys, and that someone can cheat. Even then, someone without the keys could cheat by running from modified source code, or via debugger, meaning the change protocol would have to contain plausibility checks against the ruleset - meaning the change protocol would need to not simply log diffs, but step-by-step moves so a verificator could be made to work without a million lines of code... And we're already talking about thousands of lines of code.
My take, as always, ist to disable multiplayer altogether 😈 - I'm still miffed a default unciv sends packets to a third party at startup without my consent or a way to turn it off.
... just don't play with strangers. Trust total strangers with your fun and enjoyment - and you'll get infected sooner or later. It's bad enough that you have no alternative but to trust some of them with your life on the roads...
AutumnPizazz
Before creating
Problem Description
I found that certain individuals were circulating the rules for saving writing, enabling a group of players to exploit this knowledge and alter the online save, thus undermining fairness. I sincerely hope that we can take measures to counter such conduct.
Related Issue Links
No response
Desired Solution
To address this issue, I suggest adding a time stamp and implementing a code check for the online save. If a player modifies the save and another player starts their turn, a pop-up window should appear, indicating that the save file is abnormal.
Alternative Approaches
Nothing.
Additional Context
No response