The Pain of Trying to Join a Full Server

[Ca6e]

pro snipe, wlcome to the club! my finger is already twice a size used to be, and its so fast that when i`ll go to shooting range, i will probably shoot my self in the leg

[KillJoy[Fr]]

Auto-deploy is slow.. and it's more like a loto, maybe we can make the queue system as BF3 ?

[Heavy Death]

pro snipe, wlcome to the club! my finger is already twice a size used to be, and its so fast that when i`ll go to shooting range, i will probably shoot my self in the leg

Thats why I've been using something else. And its also twice the size by then!

[ghostfool84]

Devs stated somewhere that a Queue BF3 style is not so easy to manage because the Autodeplay script works quite simple and only looks for a free slot on the server (and doesnt know if others try to connect). But a automatic reconnect on failure would be enough.

[Heskey]

Personally, I've found Auto-Deploy to be broken at the moment.

On a 98/100 (2) server, you set the max players to 98, and after 5 seconds it will try to deploy anyway, tell you it's full, and not try again.

[Bringerof_D]

No, this only seems to be an issue with certain servers. For the past couple of weeks autodeploy has been working great for me, with a few exceptions.

3 days ago or so I tried to join the full HOG server using auto-deploy. While it was trying to connect me I noticed that in the server browser (which is still visible in the background) two HOG Mixed Maps servers showed up. After a couple of minutes I got deployed to the wrong (empty) server for some reason, and I have no idea why it would suddenly connect me to a different server.

yeah thats happened to me one too, only it was a few months ago when CIA had two servers running. after a couple minutes it connected me into the empty server.