I think this would fix the queue problem entirely. People log in to play 2 hours in a day, but afk the other 8 hours because they don’t want to wait in queue the second time.
Guess not, lotsa smart ppl that just sit in lobby doing nothing so they dont have to wait for que. Doesnt even kick them either so the que just is frozen lol.
I’m part of the problem, i do this too. Not 8 hours, but i have had times when i left it on over 30 minutes while i went to eat or something along those lines, because i had a near hour wait to get in already and wasn’t going to sit through that all over again. Was surprised they don’t kick, not even from being in a game (which explains why i see some games that have been open for 8+ hours with one person, because they clearly just parked there. You could clear all worthwhile content in much less time than that, so they aren’t actively doing anything. maybe checking their AFK status would stress their already stressed servers or something, but if they added an auto-kick after like half an hour of inactivity it would probably reduce the queue time, maybe enough to make it not necessary to park your characters lol
I bet most people that stay logged in play only a fraction of the time they stay logged in for. I am 100% sure that if they implemented a kick system for afk players, queue wouldn’t even exist…
Should definitely be an update. I accidently left mine on for 1 hour last night and was surprised to come back to it still logged in.
Until they do this, which I am EXTREMELY in favor of, I’m honestly only willing to get through the hours-long queue once/day. You can bet your derriere I’ll be AFK today for significant periods of time because of queue aversion.
1 Like
Activision: Nope. We need botters and spammers keep buying our games, period. Real players? Who need them nowadays?
No because when people will just run a freeware auto-clicker and defeat your stupid timer.
3 Likes
they had afk kicks implemented on launch, the crashes sometimes kick you out of the game if youre gone too long.
Because a simple ahk script wouldn’t be easily recognizable… Genius.
Also, not everyone will run an ahk script. Even more so if they decide to ban them, because they’re technically botting.
They won’t. Been running mouse auto click apps in games to anti-idle for 25 years. No one gives a bleep. Everyone around here is always so pissy and thinks someone is going to get banned over this trivial stuff.
“See, no body cares” - meme
Some people. Most wouldn’t because most of the people who are afk are unintentionally so.
Also that’s literally what anti-cheat software is already designed to detect so, while again it wont stop everyone it will stop enough to improve things.
“People have been doing it for years elsewhere”
Elsewhere isn’t here and they don’t generally have a community that’s pissed off about the problem that is caused by not doing anything about it. Most other games are sitting there in perpetual queues.
I AFK unintentionally all the time. The queue is like an hour long so I go to login, then leave my computer then get busy doing other stuff. One thing leads to another and hours later when I’m done whatever else I got up to I’ll finally come back to (maybe) play. At this point I think at least 50% of my official account play time was just spent in queue or sitting at the character select cause it takes way too long to login.
Since there’s no ETA on the queue I don’t know how long it takes and I have a life that isn’t best spent watching a queue.
30+ minutes away from keyboard should be enough time for someone to realize they need to logout. If you stay just to avoid the queue, that is the entire reason we need this feature implemented.
Player A. Who is waiting to play in queue. Should not be waiting because players B, C, D, E, and F decided they wanted Lunch and went AFK for 2 hours. If Player G burns a souffle and goes AFK for an hour. Player A is still waiting. Meanwhile Players H through Z are sitting in Queue behind Player A. Lets add the Chat bots and lobby sitters. Anyone in lobby for over an hour without any activity should be timed out.
It is a domino effect that needs to rectified with a time-out for idle players. At no point should someone be able to leave their game logged in over-night with zero activity.
This all assumes the queue works like a nightclub at capacity (eg, someone leaves another can go in) and isn’t just some heavily metered authentication server that is decoupled from the number of active players. IMO the only blue post on this topic was very light on the details.
I assume they wouldn’t want people with Engineering backgrounds to pick apart whatever they state. So they tried to be as general and non-direct as possible with the response.
But it is true. I believe it is set to a refresh interval and that’s why the gui updates in chunks when you are waiting in queue.
There are two different servers the servers with the que is the authentication server not the game servers once you’re in you get assigned a region it has nothing to do with the que to get in.
1 Like
The queue is to reduce load on the log in authentication server.
It is not indicative of a maximum capacity for concurrent logged in players.
There’s plenty of room in the park for everyone who wants to get it, you’re just in line with a single ticket taker.
Wrong. Completely wrong.
From their explanation:
"This will keep the population at the safe level we have at the time, so we can monitor where the system is straining and address it before it brings the game down completely. Each time we fix a strain, we’ll be able to increase the population caps. "
It is clearly stated under “Login Queue Creation”
Context is everything.
To diagnose and address them swiftly, we need to make sure the “herding”–large numbers of players logging in simultaneously–stops. To address this, we have people working on a login queue, much like you may have experienced in World of Warcraft. This will keep the population at the safe level we have at the time, so we can monitor where the system is straining and address it before it brings the game down completely.
Logging in simultaneously.
Not logged in simultaneously.