Forum Discussion
I can comfirm this issue.
3 of my 5 servers are affected by this issue since last week...
It turned out that resetting the server GUID... And by this losing your whole player base would fix this issue. At the same time kill your server forever...
Anyways, it also turned out that new server GUIDs are affected by this after a few days.
However, the issue dissapears sometimes for a few hours/days and comes then back
I also would like to adress an additional issue:
1. It is known that servers use fake player counts to populate.
2. Together with this issue the following is happening since last week: The fake players do not show up for the affected servers anymore (in the in game menu). This is extremely unfair because at the moment most servers still have fake player counts and all other servers are basically done and dead now... This is not a fair competition..
3. This is extremly unfair.
The BF4 server market is extremely unfair atm... Please help us...
@H3diusTbh. This issue seems like smth at the Blaze is going on. Not sure tbh.
It does not affect all players. The majority is not able to join from Battlelog and gets this error. Looking at the communication between Origin and Battlelog reveals only an unknown error.
Joining over the in game menu still works though. I did several tests and it turned out that the issue is linked to the server GUID. Moving to other machines/hosts with a GUID will not make the error dissapear. However, resetting a GUID does... So smth with the Blaze or any backend system is screwed up.
----
Same for the fake player counts. All servers should be able to use them or none... Excluding a small portion is unfair....
We need a level playing field...
About Battlefield Franchise Discussion
Recent Discussions
- 26 minutes ago
- 10 hours ago
- 10 hours ago