1. When a countdown starts for any queue you are likely to NOT get an option to accept (which sometimes results in getting kicked from the queue for not accepting).
2. If you do get the option to accept and do so, you sometimes have to go through multiple countdowns accepting as, one suspects, someone else queueing gets the countdown but no option to accept and the queue thus doesn't start as not all queued accepted.
3. This is especially bad on the now running Crystalline Event that needs 10 players. One sometimes has to sit there through multiple countdowns, 10+ is no exception before being able to actually play it (while sometimes having to re-queue for getting kicked because of aforementioned problems).
Please
@engineerb4#4806 &
@chrian#9670 9670, this needs attention. This is a very important aspect of your game and it is hurting it. Thank you.
One really wonders why the overhaul of the queueing system that before worked just fine without any issues. It wasn't broken, it didn't need fixing. Don't even get me started on team/private queueing that was easy, effortless and working under the old system without having to perform a complicated workaround, just like under the new one, in order to be able to play a queue with a pre-made team.
Comments
I dunno about this game anymore
You get notified the correct number of players have been matched, receive the countdown, and if everyone accepts, all is well. If someone doesn't accept, the ones that did accept remain in the queue and the ones that didn't accept are ejected from the queue. That is good too; however, if the right number of players are matched again and there's another prompt to accept, there's no guarantee the menu option to accept will appear the second or third time. You also can't leave the queue if the countdown is in progress, so you're stuck waiting for the timer to reach 0:00 with no way to respond and no way to leave. The system then acts as if you were the one that failed to accept even though there was no way for you to accept it or exit.
There's only one known work-around for this that I'm aware of. If the timer is counting down but there's no menu option to accept, changing map instances (not necessarily changing to a different map, but just a new instance of the same map) will allow the menu option to appear and you can accept.
Hopefully knowing this work-around will help developers identify and correct this problem permanently.
Core gameplay mechanic, you'd have thought they'd get this on the list to fix it asap.
Instead they think its a good idea to run back to back events (breach will be coming on the back of CC) and have a lazily made battle zone reliant on it working because players sitting about doing precious little for 20-30 minutes pads the numbers to make the game busier that it actually is.
I build things. Things that make us go.
If this is by design maybe you should log on to PS4 and play a few PVE queues and then tell us it's working as attended.
I just had 5 minutes of saying “Ready”, the queue not popping and putting me back into the queue, and not having an option to accept once that timer started.
I’m glad I had 14 shards saved from a previous run, because this would be nearly impossible to do now. What’s a quick event on PC is absurdly rough on PS4; one toon could be done within 5 minutes from log-in to character switch while another takes 5-7 minutes just to get into the map.
EDIT: On two more characters, everything ran smoothly and quickly. On a 5th character, I’m now trying for at least the 6th time to queue in. On at least one of these, I had no option to say I was “ready,” and I couludn’t leave the queue to try again. I then got kicked from the queue list ad had to re-queue. I finally got in on my 6th attempt with that character. I’ve tried space and ground, applying quickly and relatively slowly. I’ve tried switching maps. Nothing helps.
I build things. Things that make us go.
> Thank you engineerb4 for reading and replying. Many of us really want to see this resolved.
Indeed, thank you @engineerb4#4806
for the que system its almost enough to make players want to avoid doing any further events in the future at all on any toon/"characters" especially since you have multiple characters which for me would be one step away from quitting not their yet but you guys keep pushing things in that direction though .
Because I have 11 toons trying to this. And limited time. And having the que system TRIBBLE out almost constantly is making it impossible for do it for all my toons.
That's how you you kill customer support of any software product.
> Sorry, when I said the Lead Engineer has made a fix. That fix probably hasn't made it to live yet. It should show up in the next update.
Are you going to keep the event on longer? You try doing it with 11. Toons it's a nightmare.
Also seeing how u have a fix and are just sitting on it. Like seriously what are you doing? Waiting for it to hacte
Because doing that is fun
I build things. Things that make us go.
> I had thought the fix would've gone out on the 16th. I'll ask to have this looked into again.
It really boggles my mind. It is included in "known issues" but not fixed - especially as you said it was fixed on your end a month ago. Lemme' guess - a bad executive decision?
I build things. Things that make us go.
I build things. Things that make us go.
> I just fixed a bug today for not getting the Match accept prompt, it should also be in the Nov Build.
>
> Do you have reproduction steps for " The team bug where the game doesn’t recognize your in a team still exists months later."?
> Video of the bug would be very helpful. Or the steps, ie, "Do x,y,z and see that Teams don't show"
When you invite people to a team. You see them listed on the left hand side of your screen however when you go to join a pve que they are not in your team. If you check under Create private. They are not listed there. I understand there is a work around to change instances and then the are listed under your team if you check create private. However this does not always work. Or will stop working. I think this is a barrier to play and will discourage newer players for sure. Newer players who are not invested enough to trying the Change Instance work around. Please fix this bug.
The other issue with teams, I believe, is due to the differences between teams and queue groups. Based on my experience, the queue group you're in determines who goes into the same PvE with you, not necessarily all the ones on your team. If a team of 5, for example, is also in the same 5 member queue group, you can launch a PvE with everyone in it; however, if the team of 5 has some teammates in one queue group and some in a different queue group, then it's possible for the team to be split apart into different instances of the same PvE or possibly have the team split apart with some being left behind.
If the queue group is what really determines how a group of players enters a PvE now, I think it would help everyone if joining a new team automatically removed that teammate from any previous queue groups he/she was in and place that teammate into the same queue group of the team just joined. Right now, we have to tell people to double check to be sure they're not in a queue group before joining a team or give them instructions on how to quit a previous queue group so they can be invited to the team's queue group.