The ones who must not be pinged
@blackyps Would any of these desync issues appear in a replay out did it only happen in live games? Can we build a CI-pipeline on old repos? @draiget does this for the reverse engineering development somehow.
We now have desync tracking in the lobby server, so this could be used as alarm tracking after patches. But that would basically require more releases / smaller changes per patch.
We had rented a global 3rd party TURN relay service. It got maliciously abused and we had to disable. The costs went from 100$ to 600$ per month.
Since you referenced my pull request: it was never done to be able to actually play with it. I just need it to run the client and test FAF things while I mostly use a macbook 
I 100% want to make this open source, no worries, I just want a bit more time, as I'm well aware that open sourcing it will open the floor gates. I would also be interested in how this can be transferred over to the faf team as well. I do believe this has real merit to replace the base engine. it already demonstrates a large amount of the game working, and absolutely has the nuts and bolts to go all the way.
You can transfer the repository to the FAForever project and still remain the repo admin. It could also be a private repository if you are worried about cheats etc.
I suggest you contact us in our https://faforever.zulipchat.com, so we can discuss options.
Well I ususally say pics or didn't happen. But in this case I'd rather say code or didn't happen
Does your engine run the lua code for the game patch?
For further explanation: the game doesn't have a concept of mod versions. This ever new version needs to have a different uid, otherwise it could not pick an old mod version for replays while keeping the new version for playing.
No. As long as we do not separate account names and display names this is not possible.
Rewrite = compatibility to all existing lua game code? And also map, mod, textures and model compatibility?
Also Repo url or didn't happen! 
2026.7.1 is not a test version of the client and no changes to connection logic were made compared to 2026.7.0.
2026.7.1 should be able to play with anyone. Most likely it was just antivirus or some other network issue.
