I do think there is quite an obvious solution that game developers dont yet realize.
The client is always compromised
Instead of relying on increasingly invasine client side anti cheat, with a zero trust mentality it doesn’t matter how many cheats the client has installed.
Ofcourse this is’t easy to do, but its the only thing that actually works, client side anti cheat will always be broken.
Seems like it’s specs are still unknown?
I’ve used a pinephone pro with arch and postmarket.
It works, but you really have to love linux to use it as a daily driver.
My banking app (bunq) worked using way droid.
But you can make this argument for anything that is used to make rich people richer. Even something as basic as pen and paper is used everyday to make rich people richer.
Why attack the technology if its the rich people you are against and not the technology itself.
No?
Anyone can run an AI even on the weakest hardware there are plenty of small open models for this.
Training an AI requires very strong hardware, however this is not an impossible hurdle as the models on hugging face show.
All the calculations could be done before hand and stored and then the only thing left in the delayed draw is to set the buffer.
I haven’t looked at the code yet so not sure how much if any it will save though.
Could also group pixels that are far away from eachother into a single call, while a compromise i think it will maintain the effect.
A random suggestion would be to draw to multiple canvases, and use a CSS animation for the delay.
Also not sure if you are already doing this but it might be more peformant to use the raw buffer instead of draw functions.
Alternatively you could look into webgpu, it is ment for these kind of things.
I don’t use mint so this might be blatantly incorrect but after a bit of searching on mint’s release schedule I would assume gimp 3.0 will arrive with the 22.2 or 22.3 version. With 22.2 expected at middle 2025 and 22.3 at start 2026.
I do think some of these limitations can be resolved. But it indeed poses a big challenge. You can go to big lenghts with server occlusion checking to prevent wall hacks but under zero trust any game with directional sound already has build in wallhacks.
I mostly speak from experience with my developing my own game which is not an FPS. Previously the client would send “i build on this position”. Which could very easily be abused. Which I then changed to “i build with this angle and this distance from the previous node” the client would then already show the newly constructed “ghost” node while the server would check if that construction is valid and then send the real position to all clients. The only thing a player would notice is that with high ping the constructed node would move slightly as it got the definitive position from the server. While being significantly more cheater proof.
I suppose im biased towards this kind of thinking since im not working on a FPS game, what for me might be a simple change is a massive undertaking for other genres.