Not sure if related, but when searching a bit, seems like more have issues, even if it is with BF4, guess it could be similar code base handling the server browser in the back end. Even if they reach different conclusion, issue seems to be same as what we are seeing: https://forums.battlefield.com/en-us/discussion/125247/battlelog-shows-me-wrong-amount-of-players-on-servers
I have been in contact with and EA advisor now, where only "solution" was to completely reload the server, thus wiping all the favorite markings you have, and the advisor had no idea if this actually would fix it, it is just there standard go-to solution. I am very sure this is a bug, so reloading server prob does not work, and we do not want to lose all players who have marked our server as favorite.
Here is another person with same issue on BF1, meaning more and more are noticing the issue now and reporting it: https://forums.battlefield.com/en-us/discussion/129756/server-keeps-say-64-64-while-its-not
EA StaffHey @Mandatoryswe,
unfortunately that's the only thing I can offer at this time - I had someone on the German forums with the same issue who states that restarting the server fixed his issue.
Restarting the server might be temporary fix. Again, this problem occurs not all the time, but every now and then, meaning u might think it is solved, only for it to re-appear 2 weeks later... We have the issue AGAIN right now. As stated on the BF1 forums, turns out more and more are reporting this now as an issue. I am sure there are a lot more with the issue that are not reporting it.
I understand that you cannot do more here, what I want is the bug recognized so devs can fix it. I thought this was the place to report bugs? Is there somewhere else I should report bugs so that they can reach the dev teams?
EA StaffHey @Mandatoryswe,
that's exactly the right place to post this feedback - the short term solution would be a restart. Recurring issues and issues that get reported frequently are looked into and passed on. So for now you can of course contact an Advisor to kick the server again, but rest assured it's also been reported.
