The current pre-release of the client ("pioneer" in the version) is only compatible to itself. So you can only play with other testers. Please be aware!
I think you're right, this is what my parser in C# does:
https://github.com/Garanas/cs-fa-replay-library/blob/main/FAForever.Replay/ReplayLoader.cs#L45
@c0rtex I have a work in progress thread with more graphs based on data from 2025, but life events have thrown a spanner in the work. I might release a half-finished version.
Edit: Released the thread:
https://forum.faforever.com/topic/9918/faf-statistics-megathread-3-the-stats-are-at-it-again
That question was answered in my first response, and as you keep using this thread to report players despite specific instruction not to do so I'll be locking it.
We use websockets to communicate from the client to the server. So if the proxy doesn't support long lived websocket connections then that could be the issue
It is unfortunate that you are experiencing technical issues. However, presenting the situation in such a theatrical-esque manner is not helpful.
I would recommend heading over to the FAF support section, providing the relevant logs and describing the issue. People will be more willing to help when you make an effort to share useful information.
I don't have the time to look at your games right now as I'm about to kick off my training session with nine trainees in a minute. I suppose, you're maybe making some mistakes slowing your own eco down. If you want someone to take a look, feel free to join us over at the FAF Dojo. We offer free voice-based coaching.
https://forum.faforever.com/topic/9594/the-faf-dojo-voice-based-coaching
I mean, multipliers had to be worked out and same goes for a floor level, may it be 60%, 70% of the rating when last logged in or whatever. But it's a good idea in general, I think.