Quoting M4rcin: "Fortunately for you guys, as someone wise once said, cry is free"
You're right, Marcin. Crying is free. A full forensic analysis of a client that feels fundamentally untrustworthy, however, is not. But we did one anyway.
People on this thread are talking about scams, fake streamers, and seasonal servers. It all starts to make sense when you look at the code. Let's talk about what's actually in your client, shall we?
* Undisclosed Tracking: You have a native function, g_app.getMachineFingerprint(), that creates a unique, persistent hardware ID for every single player. Your privacy policy doesn't mention this. You call it "legitimate interest," but the reality is that you're fingerprinting and tracking your players' machines without their informed consent.
* Covert Data Channel: You hide this hardware fingerprint by pre-encrypting it with RSA (rsaSetPrivateKey) and then piggybacking it onto the main XTEA game stream via Protocol.send(). This isn't "security," as you claim; it's a classic covert channel designed to exfiltrate data without being detected by firewalls. These are techniques used in malware, not reputable game clients.
* A Potential Backdoor: Your client contains a native function, g_platform.requestAccess, which has the capability to access files outside of the game's own directory. It's an undisclosed security risk, a backdoor waiting for a purpose.
You mock players and tell them "you still cheat and blame me". But the evidence shows you're the one using deceptive techniques. You build a client that doesn't respect its players' privacy or security, and then act surprised when the community feels scammed.
And don't bother checking my account age. The data doesn't lie, no matter who presents it.
Fortunately for you guys, filing a GDPR complaint is also free. And all the evidence is now ready.
Like sands through the hourglass, buddy.