I'm waiting for a Community Manager to post the usual "We have a fix scheduled for next patch..." comment.
I'm waiting for a Community Manager to post the usual "We have a fix scheduled for next patch..." comment.
Dont forget "it would be in this patch but we didnt have time to properly test it". So they will test this awesome solutions for another week to deliver us another pill of dissapointment.
IF they respond at all, its been going for so many weeks might aswell go back to pretending that this topic and whole issue doesnt exist...
ZOS_GinaBruno wrote: »Hey guys, just letting you all know that we do see your replies about the ongoing queuing issues, and we're working on a larger, more detailed post explaining what our next steps are. Expect to see this in the next couple days.
ZOS_GinaBruno wrote: »Hey guys, just letting you all know that we do see your replies about the ongoing queuing issues, and we're working on a larger, more detailed post explaining what our next steps are. Expect to see this in the next couple days.
ZOS_GinaBruno wrote: »Hey guys, just letting you all know that we do see your replies about the ongoing queuing issues, and we're working on a larger, more detailed post explaining what our next steps are. Expect to see this in the next couple days.
ZOS_GinaBruno wrote: »Hey guys, just letting you all know that we do see your replies about the ongoing queuing issues, and we're working on a larger, more detailed post explaining what our next steps are. Expect to see this in the next couple days.
ZOS_GinaBruno wrote: »Hey guys, just letting you all know that we do see your replies about the ongoing queuing issues, and we're working on a larger, more detailed post explaining what our next steps are. Expect to see this in the next couple days.
They don't seem to understand that a ready-check queuing system cannot AND WILL NEVER work. They're wasting time.
The probability of getting 12 people to perpetually ready check doesn't make logical sense. Look:
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
(several hours later)
MATCH - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes
Now i want you to imaging that their background, all those "no's" are getting replaced with other people, and it keeps all the "yes's" together for that one ready-check iteration. (or worse, it just jumbles everyone back in some master pool or queued players)
Only here's the problem. Those are NOT individual no's. Those are no's that are segmented and partitioned into groups of 3 people, groups of 4 people. So now they need to throw out that entire chunk of yes' that go along with the single no.
Okay now for that one iteration, it needs to now find a replacement group for the exact amount of people. But its much easier to fill that void with three individual people, rather than a group of three.
So if you're in a group... its harder to fill those spaces. It's like a nightmare game of Tetris.
Every wonder why solo queuing goes so fast? Its because you're one individual replacing/filling the final holes in a pre-matched group that's looking for those final replacements to start the Battleground.
They don't seem to understand that a ready-check queuing system cannot AND WILL NEVER work. They're wasting time.
The probability of getting 12 people to perpetually ready check doesn't make logical sense. Look:
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
(several hours later)
MATCH - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes
Now i want you to imaging that their background, all those "no's" are getting replaced with other people, and it keeps all the "yes's" together for that one ready-check iteration. (or worse, it just jumbles everyone back in some master pool or queued players)
Only here's the problem. Those are NOT individual no's. Those are no's that are segmented and partitioned into groups of 3 people, groups of 4 people. So now they need to throw out that entire chunk of yes' that go along with the single no.
Okay now for that one iteration, it needs to now find a replacement group for the exact amount of people. But its much easier to fill that void with three individual people, rather than a group of three.
So if you're in a group... its harder to fill those spaces. It's like a nightmare game of Tetris.
Every wonder why solo queuing goes so fast? Its because you're one individual replacing/filling the final holes in a pre-matched group that's looking for those final replacements to start the Battleground.
- Update 23Ice Furnace: This item set now grants Spell Damage, rather than Weapon Damage for the 4 piece bonus
They don't seem to understand that a ready-check queuing system cannot AND WILL NEVER work. They're wasting time.
The probability of getting 12 people to perpetually ready check doesn't make logical sense. Look:
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
(several hours later)
MATCH - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes
Now i want you to imaging that their background, all those "no's" are getting replaced with other people, and it keeps all the "yes's" together for that one ready-check iteration. (or worse, it just jumbles everyone back in some master pool or queued players)
Only here's the problem. Those are NOT individual no's. Those are no's that are segmented and partitioned into groups of 3 people, groups of 4 people. So now they need to throw out that entire chunk of yes' that go along with the single no.
Okay now for that one iteration, it needs to now find a replacement group for the exact amount of people. But its much easier to fill that void with three individual people, rather than a group of three.
So if you're in a group... its harder to fill those spaces. It's like a nightmare game of Tetris.
Every wonder why solo queuing goes so fast? Its because you're one individual replacing/filling the final holes in a pre-matched group that's looking for those final replacements to start the Battleground.
Pls tell me they didn't program it that way.
@ZOS_GinaBruno @ZOS_JessicaFolsom
And i think they even when everyone presses ready it doesn't work right and says someone is not ready. (I don't think that so many ppl don't say they are ready)
Just deactivate the ready check to see if the grp tool works. Shouldn't be to hard just set player_ready=true or something like that.
@BigES that's a nice theory, except it goes: 12... 11... 8... 3... 2... 1... Forming Group... nope. And considering it does the same when you queue with 4 people for a dungeon where you know 100% no one declines - I'm pretty sure it's just incompetent coders, or "engineers", as Gina puts it. However, I agree there should be some kind of "decline penalty" of 5 - 10 min or so, just to avoid trolls and griefers.
They don't seem to understand that a ready-check queuing system cannot AND WILL NEVER work. They're wasting time.
The probability of getting 12 people to perpetually ready check doesn't make logical sense. Look:
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
FAILED - yes, yes, yes, no, yes, yes, yes, yes, yes, no, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, no
FAILED - yes, yes, no, yes, yes, no, no, yes, yes, yes, yes, yes
FAILED - yes, yes, yes, yes, yes, yes, yes, yes, no, yes, yes, yes
(several hours later)
MATCH - yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes, yes
Now i want you to imaging that their background, all those "no's" are getting replaced with other people, and it keeps all the "yes's" together for that one ready-check iteration. (or worse, it just jumbles everyone back in some master pool or queued players)
Only here's the problem. Those are NOT individual no's. Those are no's that are segmented and partitioned into groups of 3 people, groups of 4 people. So now they need to throw out that entire chunk of yes' that go along with the single no.
Okay now for that one iteration, it needs to now find a replacement group for the exact amount of people. But its much easier to fill that void with three individual people, rather than a group of three.
So if you're in a group... its harder to fill those spaces. It's like a nightmare game of Tetris.
Every wonder why solo queuing goes so fast? Its because you're one individual replacing/filling the final holes in a pre-matched group that's looking for those final replacements to start the Battleground.
Solo queues dont work either, I had 4 in 4 hours whilst livestreaming
SwaminoNowlino wrote: »This company doesn't care folks. There's no such thing as customers from their point of view. That's not the relationship they see themselves as having with us. And by us, I don't just mean the folks who care about Battlegrounds.
@ZOS_GinaBruno @ZOS_JessicaFolsom @ZOS_KaiSchober are community managers.
Look at the dev tracker. We went almost a full week without them replying to a single post. Look at the people who got screwed by the unannounced housing changes. People paid over $100 for limited edition housing. They decorated their house with stuff that cost them crowns, then ZOS without saying anything, put giant boulders and stuff blocking entire sections of the house off. Their stuff is stuck back there, ZOS doesn't respond for over a month to the thread, then replies and tells them to eat it, they aren't changing it back and everyone can bleep off.
What other gaming company behaves like this? Ubisoft will have unscheduled maintenance, then give everyone 3 days of reknown boost as an apology. Every time! They even admitted Rainbow Six was broken, and cancelled planned content to devote a quarter to major fixes. They even refunded the season pass money if you asked for it, even though the content in it was only delayed. When was the last time Blizzard charged $40 for ten hours of content that was critically broken, took 6+ weeks to attempt to fix it, then gave us a "post" about what they plan to do 4 weeks from now instead of working day and night to fix it? They all have community managers with 15+ posts a day on the forums and Reddit, answering questions, discussing issues, and giving daily status updates.
What other company would you accept treatment like this from? What other company would tell paying customers to bleep off, we don't care about you and we don't plan on compensating you, despite it being obviously justified. Heck! Most companies would provide compensation even if they got the fix out days later, let alone months!
As far as this company is concerned, this game is free to play, and their sole focus is on monetization. Crown store reskins, $40 mounts that will be put in crown crates for 100 gems, hidden mounts in crown crates. That's the only relationship this company has with any of us. Even when that stuff doesn't appear in game as advertised, once you buy it, they're done responding. They cut in game managers to save money! They had automated customer service responses that said "sorry, there are too many tickets right now, we won't be getting back to you."
I'm not even like an enraged customer yelling and being hysterical. Just basically resigned to the simple facts that are in front of us. Not mad, just disappointed. Sooner we accept our role in these transactions, the better for all of us.
Paulington wrote: »For future reference you can retrieve all items in a house via the housing UI regardless of whether you can see them or not.SwaminoNowlino wrote: »
Look at the dev tracker. We went almost a full week without them replying to a single post. Look at the people who got screwed by the unannounced housing changes. People paid over $100 for limited edition housing. They decorated their house with stuff that cost them crowns, then ZOS without saying anything, put giant boulders and stuff blocking entire sections of the house off. Their stuff is stuck back there, ZOS doesn't respond for over a month to the thread, then replies and tells them to eat it, they aren't changing it back and everyone can bleep off.
No items are lost..