Quickmatch Confusion

[shownder]

Okay I'm confused.

My clan only consists of 5 people, and when we play on our server we don't want to have to wait for random people to start playing.

I understand that there is a strict ruleset to be eligible for the quickmatch... But here is the confusion:

Yesterday I set the Round start to 2 people, and 4 of us joined to play against each other. Within 15 minutes we had 20 random people playing with us, to our shock. And no, we are not popular enough for people to manually join our server.

Later that day, 5 of us got on again (It was empty again) and we played for an hour with not even ONE random person joining.

So now, we are sitting in the server with the settings back to Quickmatch comparability (8 people needed) and still no random people.

Is there any specific information about what is needed to be eligible for quickmatch?

[kraze]

We do not have a lot of information on this as EA is keep it very quiet, but this is what we got so far;

http://www.nfoservers.com/forums/viewto ... =70&t=5942

[Edge100x]

It seems as though the QM requirements are being ignored right now, and QM is going more based on the size of the server (32-slot servers being preferred) and some random element (liking servers with certain GUIDs for no apparent reason). It's a bit of a mess. DICE is being tight-lipped on how QM works.

[globel]

Just try restarting it and seeding it again. And set your ping site.

[Sorry]

Its that origen browser. If you lucky enough to be in that 100 servers in that persons search set you will be seen. The player has to go to bottom of the list and it will show 100 more, go to the bottom of that list to see a hundred more. Bc2 would show all the servers and you could search by ping. Hopefully battlelog does away with this wierd 100 server filter system.

[Edge100x]

Yes, and the problem is that those top servers are the same for all clients.

I don't even think that Quickmatch is the one filling up a lot of servers. It could easily be that large chunks of clients join through the browser and the same servers fill up because whatever lousy pseudo-random system Battlelog is using results in the same servers always showing at the top.

[.Strafe]

... lousy pseudo-random system ... Battlelog

perfectly stated

[.Strafe]

this is a quote from JRipley on the Battleblog forums, he is the guy taking credit for writing the matchmaking component of Battleblog ...

if a server "re-install" wipes the unique identifier of your server it's not much Battlelog can now do keep your server in favorites. Since it's the unique identifier that we use to track favorites. The unique identifier is the random string in the server URL, ex. http://battlelog.battlefield.com/bf3/se ... mpfgruppe/ [battlelog.battlefield.com] == 53fe19bc-b462-46e1-93f1-9810f9954cbd.

As it is now, the default for Quick Match is to only pick Team DM, Rush and Conquest servers, if the user don't explicitly select Conquest Large in their server filter. Otherwise we can't set a reasonable "desired player count", to put the player in a decently populated server, since that would vary to much between the 32 player game modes and Conquest Large.

Also, we're looking into better solutions to randomize the server browser list.

here is the link if you wish to follow ...

http://battlelog.battlefield.com/bf3/fo ... 7715516807