WTF Happened to "CC Immunity"?

CromulentForumID · July 2017

Nelson_Rebel wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

Trust me @ZOS_GinaBruno I would love nothing more than to have a calm and rational Discussion on here regarding bug fixes and other feature issues ingame.

If you can help bring it up to the staff so that some of these can actually start to be addressed it would go miles as far as getting the playerbase to be less agitated and angry lately what with all the server crashes and issues such as these going on.

Please, make me bite my previous words on current affairs regarding the staff. If they could do some sort of Live Cast to talk about some things, and what's actually going on to fix things currently I would stop with all negativity honestly. We just want to be an Informed playerbase

I don't believe that communication is the best, or even good, on a lot of these issues. But in order to be a little bit fair, what can they say to us that would have some meaning, but not be open to months and months of ridicule?

If they can't figure out how to fix it, they can't say that. "Six month status: We have examined the issues with CC immunity and have replicated them in our development environment. However, we cannot determine why they are happening or how to correct the issue. Frankly, we're at a loss."

This one would replace "You don't have to be here" as the favorite forum meme.

Is this, "We're aware of the issue and working on potential fixes," better than stating nothing at all? How many times can they do this before they are mocked for the repeats?

How about this one? "We are aware of the issue. However, we have several other issues of a much higher priority we are devoting our resources to. Our current plan is to address the issue in August 2018."

Again, I don't think the communication or the pace of fixes gets a high grade, or even a decent one, but they are kind of limited in what they can tell us.

NBrookus · July 2017

Lord-Otto wrote: »

Fossilize is also a big offender. Been flung in the air by Dizzying Swing as a stone statue way too many times. Or fossilized on horse back, no chance to break free.

If you are fossilized on your horse, hit H (or whatever your key is to dismount). It's not intuitive at all. But if you know this, it's not a helpless death sentence. It's about like getting up from a horse gank or or the animation of picking yourself up from a crystal frag proc or similar. Difference is a magDK probably can't burst you down in that time. XD

Nelson_Rebel · July 2017

CromulentForumID wrote: »

Nelson_Rebel wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

Trust me @ZOS_GinaBruno I would love nothing more than to have a calm and rational Discussion on here regarding bug fixes and other feature issues ingame.

If you can help bring it up to the staff so that some of these can actually start to be addressed it would go miles as far as getting the playerbase to be less agitated and angry lately what with all the server crashes and issues such as these going on.

Please, make me bite my previous words on current affairs regarding the staff. If they could do some sort of Live Cast to talk about some things, and what's actually going on to fix things currently I would stop with all negativity honestly. We just want to be an Informed playerbase

I don't believe that communication is the best, or even good, on a lot of these issues. But in order to be a little bit fair, what can they say to us that would have some meaning, but not be open to months and months of ridicule?

If they can't figure out how to fix it, they can't say that. "Six month status: We have examined the issues with CC immunity and have replicated them in our development environment. However, we cannot determine why they are happening or how to correct the issue. Frankly, we're at a loss."

This one would replace "You don't have to be here" as the favorite forum meme.

Is this, "We're aware of the issue and working on potential fixes," better than stating nothing at all? How many times can they do this before they are mocked for the repeats?

How about this one? "We are aware of the issue. However, we have several other issues of a much higher priority we are devoting our resources to. Our current plan is to address the issue in August 2018."

Again, I don't think the communication or the pace of fixes gets a high grade, or even a decent one, but they are kind of limited in what they can tell us.

Then they need to fire whoever doesn't know what the hell is going on, and post some hiring ads out for coders who are willing to actually work for their paycheck

Nelson_Rebel · July 2017

NBrookus wrote: »

Lord-Otto wrote: »

Fossilize is also a big offender. Been flung in the air by Dizzying Swing as a stone statue way too many times. Or fossilized on horse back, no chance to break free.

If you are fossilized on your horse, hit H (or whatever your key is to dismount). It's not intuitive at all. But if you know this, it's not a helpless death sentence. It's about like getting up from a horse gank or or the animation of picking yourself up from a crystal frag proc or similar. Difference is a magDK probably can't burst you down in that time. XD

Lol if i ever see that I'd laugh. Mag Dk and Burst are two words you'll rarely see in the same sentence xD

In pvp Dk's just are weak right now

CarefreeX · July 2017

+1 this keeps happening in cyrodiil

Moloch1514 · July 2017

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

LOL, most have decided the best bet to get a quick reaction from ZOS is to claim that we can't buy crowns or make crown store purchases. Post that in a thread with ZOS tagged and they come flocking.

Another simple way to fix it is to have internal testing (hire better QA if this already happens) on a much larger scale prior to rolling out updates. The QA process should not be outsourced to your customers, but that is the case with ZOS.

Ackwalan · July 2017

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

While you are talking internally about how this can be fixed, be sure to let those of us on the outside know about it. We don't need the full monty of details, just a peek.

StereoLiz · July 2017

This problem is not only about not breaking free before second hard CC.
I use immovable potions and get stuned right in next second very often. Sometimes I drink potion because I see crystal shard on my way and get stunned anyway.

Reverb wrote: »

Apokalypt wrote: »

I experience the complete opposite. Players in bgs that are permanently immune to cc...

Anyone in BG without almost 100% Immovable (via pots or the heavy armor skill) uptime is doing it wrong.

Btw you can't have 100% uptime with pots - 15,7 sec immovable buff, 45 sec cooldown

http://i.imgur.com/gte7UAf.png&key=a0e2a1c2d5b0a88058f15e389786721acddce51a067657367a8441fe5bf0d30e

Magdalina · July 2017

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

May I ask what issues exactly are these while you're on this? Buggy cc immunity on all accounts? Specifically cc immunity never kicking in until cc expires, allowing for infinite chain cc? Is cc immunity upon letting cc lapse being missing completely in PvE on that list too or is that one actually intended?

@ZOS_GinaBruno

Ch4mpTW · July 2017

Ackwalan wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

While you are talking internally about how this can be fixed, be sure to let those of us on the outside know about it. We don't need the full monty of details, just a peek.

Agreed. I've been saying for a long time that a small amount of transparency goes a long way. In fact, not just me. I think the vast majority of the posters here on the forums have said that. I can definitely vouch for: You, @Vaoh @Rohamad_Ali and @Sharee on that topic. As you all have always said to allow players to know just a tiny bit of what's going on behind the scenes, rather than leaving us in the dark about these types of highly important things.

Jamascus · July 2017

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

What's the current process for gameplay issues being relayed from the forums to the people that can fix it?

Curragraigue · July 2017

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

@ZOS_GinaBruno but this has been said a number of times. Your biggest problem has always been lack of communication. For the most part we find out about big changes a few weeks before they go live when we read about them in patch notes.

You must surely have a list that Matt, Richard, Wrobel and Brian look at every day/week that shows this is the overall plan. We just want that updated list on the forum. Divide it up into something like:

1) things being considered
2) things we are working on fixes for
3) things being tested/balanced
4) things coming in update x
5) things we are not going ahead with anymore

Doesn't need the detail in the list just bullet points. Give people time to get ready for the large changes and for people to provide suggestions or comments on your plans. Let people know what you are currently working on and what fixes are coming and bam you have the level of communication that people are looking for.

ecru · July 2017

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

If there's one thing I've learned in nearly 20 years of pvping in mmo's, it's that people absolutely hate losing control over their character. CC absolutely needs to respect some kind of immunity timer or diminishing returns, especially due to how low TTK can be in ESO.

The 70% snare from Tremorscale also needs to be looked at IMO.

vyndral13preub18_ESO · July 2017

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Just don't call anyone tiny and adorable. That can get you a 72 hour ban.

Nelson_Rebel · July 2017

vyndral13preub18_ESO wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Just don't call anyone tiny and adorable. That can get you a 72 hour ban.

I don't know wether you're jesting or not XD

ZOS_GinaBruno · July 2017

Jamascus wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

What's the current process for gameplay issues being relayed from the forums to the people that can fix it?

From the forums specifically? There's a number of avenues for how threads get to the dev team, including:

The community team sees threads that require attention, and we send them to the devs to review.
Other devs see threads that require attention, and they send them to the appropriate team to review.
The gameplay team sees threads and review amongst themselves (this happens more than you might think).
The QA team also reviews many, many threads posted in the Bug Reports section and take whatever action is appropriate. This includes creating a new bug if one doesn't exist and sends it to the team, noting if something is already bugged but is getting more reports, something that sounds off but can't be reproduced easily, or something that's been reported but is actually working the way it was designed (sometimes this can lead to further discussions, such as why it's being viewed as broken if it isn't, but that's another discussion).
Customer Support finds a thread that's related to tickets that get sent in, and those get triaged/escalated as appropriate.

Those are just some examples. We've said this before, but we are reading many of the threads and posts from the forums!

Curragraigue wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

@ZOS_GinaBruno but this has been said a number of times. Your biggest problem has always been lack of communication. For the most part we find out about big changes a few weeks before they go live when we read about them in patch notes.

You must surely have a list that Matt, Richard, Wrobel and Brian look at every day/week that shows this is the overall plan. We just want that updated list on the forum. Divide it up into something like:

1) things being considered
2) things we are working on fixes for
3) things being tested/balanced
4) things coming in update x
5) things we are not going ahead with anymore

Doesn't need the detail in the list just bullet points. Give people time to get ready for the large changes and for people to provide suggestions or comments on your plans. Let people know what you are currently working on and what fixes are coming and bam you have the level of communication that people are looking for.

It's a nice idea on paper, but when you start thinking of the logistics, something like this just isn't possible to maintain and would get muddied pretty quickly. And yes, we have considered it. Let's break it down based on your list:

1) things being considered - The danger in listing something like this out is what happens if it never comes to fruition, or gets punted due to lack of time/resources, or reprioritized for a different patch? All it will do is disappoint people because they'll see something that we once considered, but then never did for XYZ reasons (which ultimately end up not mattering). Also consider when we're looking at new features specifically, for example, this kind of takes the wind out of Marketing and PR's sails if we just lay it all out on the table early.

2) things we are working on fixes for - This is something we've toyed around with doing frequently, but what ultimately goes in this list? We're working on many fixes at one time, some of which take a lot of time and effort, some of which are very minor. We can't list everything - it just isn't reasonable or even feasible. What we decided to do instead is reply to threads in the Bug Reports section, as we're able, to give a status on the bug reported. Can we do a better job and reply to more threads? Sure. But as we originally said when we opened that section, we reply as we can.

3) things being tested/balanced - Again, this is a moving target and the effort to maintain something like this would probably be a full time job in itself. Unfortunately, the reality of the situation is we (the Community team) have many tasks and responsibilities and simply don't have the bandwidth to maintain something like this on a regular cadence. We can try to give you more general updates more frequently, though, and this is something we can work to improve.

4) things coming in update x - We do this to some extent when we release preview articles, and you could even consider the PTS patch notes to be a preview of sorts. Again, remember we have other departments that need to hold onto content based on a release schedule and strategy. I know that's a little different from gameplay-specific things, which is probably what you're referencing, and we can try to do a better job to let you know the things we're working on for the future. Many times, we're just not ready to talk about our plans because - again - it's a moving target. We iterate and iterate, and tweak things until they're close to being just right. That's when we put things on the PTS for final tweaks and testing, and gather up your feedback for what we've implemented.

5) things we are not going ahead with anymore - This is fair, and we can certainly be more open about things that aren't really on the table, just so you don't feel like you're being strung along.

Sorry for the wall of text, it's late and I started rambling. TL;DR - we'll work on doing a better job to communicate the larger, more overarching changes and plans we have for future gameplay updates to keep everyone abreast of what we're doing.

Juli'St · July 2017

ZOS_GinaBruno wrote: »

Jamascus wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

What's the current process for gameplay issues being relayed from the forums to the people that can fix it?

From the forums specifically? There's a number of avenues for how threads get to the dev team, including:
The community team sees threads that require attention, and we send them to the devs to review.

Other devs see threads that require attention, and they send them to the appropriate team to review.

The gameplay team sees threads and review amongst themselves (this happens more than you might think).

The QA team also reviews many, many threads posted in the Bug Reports section and take whatever action is appropriate. This includes creating a new bug if one doesn't exist and sends it to the team, noting if something is already bugged but is getting more reports, something that sounds off but can't be reproduced easily, or something that's been reported but is actually working the way it was designed (sometimes this can lead to further discussions, such as why it's being viewed as broken if it isn't, but that's another discussion).

Customer Support finds a thread that's related to tickets that get sent in, and those get triaged/escalated as appropriate.

Those are just some examples. We've said this before, but we are reading many of the threads and posts from the forums!

Curragraigue wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

@ZOS_GinaBruno but this has been said a number of times. Your biggest problem has always been lack of communication. For the most part we find out about big changes a few weeks before they go live when we read about them in patch notes.

You must surely have a list that Matt, Richard, Wrobel and Brian look at every day/week that shows this is the overall plan. We just want that updated list on the forum. Divide it up into something like:

1) things being considered
2) things we are working on fixes for
3) things being tested/balanced
4) things coming in update x
5) things we are not going ahead with anymore

Doesn't need the detail in the list just bullet points. Give people time to get ready for the large changes and for people to provide suggestions or comments on your plans. Let people know what you are currently working on and what fixes are coming and bam you have the level of communication that people are looking for.

It's a nice idea on paper, but when you start thinking of the logistics, something like this just isn't possible to maintain and would get muddied pretty quickly. And yes, we have considered it. Let's break it down based on your list:

1) things being considered - The danger in listing something like this out is what happens if it never comes to fruition, or gets punted due to lack of time/resources, or reprioritized for a different patch? All it will do is disappoint people because they'll see something that we once considered, but then never did for XYZ reasons (which ultimately end up not mattering). Also consider when we're looking at new features specifically, for example, this kind of takes the wind out of Marketing and PR's sails if we just lay it all out on the table early.

2) things we are working on fixes for - This is something we've toyed around with doing frequently, but what ultimately goes in this list? We're working on many fixes at one time, some of which take a lot of time and effort, some of which are very minor. We can't list everything - it just isn't reasonable or even feasible. What we decided to do instead is reply to threads in the Bug Reports section, as we're able, to give a status on the bug reported. Can we do a better job and reply to more threads? Sure. But as we originally said when we opened that section, we reply as we can.

3) things being tested/balanced - Again, this is a moving target and the effort to maintain something like this would probably be a full time job in itself. Unfortunately, the reality of the situation is we (the Community team) have many tasks and responsibilities and simply don't have the bandwidth to maintain something like this on a regular cadence. We can try to give you more general updates more frequently, though, and this is something we can work to improve.

4) things coming in update x - We do this to some extent when we release preview articles, and you could even consider the PTS patch notes to be a preview of sorts. Again, remember we have other departments that need to hold onto content based on a release schedule and strategy. I know that's a little different from gameplay-specific things, which is probably what you're referencing, and we can try to do a better job to let you know the things we're working on for the future. Many times, we're just not ready to talk about our plans because - again - it's a moving target. We iterate and iterate, and tweak things until they're close to being just right. That's when we put things on the PTS for final tweaks and testing, and gather up your feedback for what we've implemented.

5) things we are not going ahead with anymore - This is fair, and we can certainly be more open about things that aren't really on the table, just so you don't feel like you're being strung along.

Sorry for the wall of text, it's late and I started rambling. TL;DR - we'll work on doing a better job to communicate the larger, more overarching changes and plans we have for future gameplay updates to keep everyone abreast of what we're doing.

Can ZOS fix your servers? Ty!

Rohamad_Ali · July 2017

Just put me on the community team and I'll fix the communications issue . I will talk them into a coma .

Curragraigue · July 2017

ZOS_GinaBruno wrote: »

Jamascus wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

What's the current process for gameplay issues being relayed from the forums to the people that can fix it?

From the forums specifically? There's a number of avenues for how threads get to the dev team, including:
The community team sees threads that require attention, and we send them to the devs to review.

Other devs see threads that require attention, and they send them to the appropriate team to review.

The gameplay team sees threads and review amongst themselves (this happens more than you might think).

The QA team also reviews many, many threads posted in the Bug Reports section and take whatever action is appropriate. This includes creating a new bug if one doesn't exist and sends it to the team, noting if something is already bugged but is getting more reports, something that sounds off but can't be reproduced easily, or something that's been reported but is actually working the way it was designed (sometimes this can lead to further discussions, such as why it's being viewed as broken if it isn't, but that's another discussion).

Customer Support finds a thread that's related to tickets that get sent in, and those get triaged/escalated as appropriate.

Those are just some examples. We've said this before, but we are reading many of the threads and posts from the forums!

Curragraigue wrote: »

ZOS_GinaBruno wrote: »

Nelson_Rebel wrote: »

Ch4mpTW wrote: »

ZOS_GinaBruno wrote: »

Thanks @Ch4mpTW, these issues are on our radar and is something we want to fix. We have some improvements coming in the next couple updates that should help with this.

@ZOS_GinaBruno Thank goodness. And thank you very much for responding to the thread. You guys at ZOS HQ be having me worried sometimes. And honestly? I don't know if you were just told to post that, in order to quiet a lot of us who are angry and frustrated. Or if it is genuine, and things will get fixed. All I know is that I appreciate you taking the time to post this, and that I'm going to hold you all at ZOS to your word on this.

Jesus they actually responded?

I've gotten some Moderator warnings in a couple posts by now, But honestly I don't care anymore.

It seems the only way to get things fixed is to scream at them now before anything gets noticed anymore

So frustrating

Honestly, it shouldn't have to be that way. We're talking internally about how we can fix this.

@ZOS_GinaBruno but this has been said a number of times. Your biggest problem has always been lack of communication. For the most part we find out about big changes a few weeks before they go live when we read about them in patch notes.

You must surely have a list that Matt, Richard, Wrobel and Brian look at every day/week that shows this is the overall plan. We just want that updated list on the forum. Divide it up into something like:

1) things being considered
2) things we are working on fixes for
3) things being tested/balanced
4) things coming in update x
5) things we are not going ahead with anymore

Doesn't need the detail in the list just bullet points. Give people time to get ready for the large changes and for people to provide suggestions or comments on your plans. Let people know what you are currently working on and what fixes are coming and bam you have the level of communication that people are looking for.

It's a nice idea on paper, but when you start thinking of the logistics, something like this just isn't possible to maintain and would get muddied pretty quickly. And yes, we have considered it. Let's break it down based on your list:

1) things being considered - The danger in listing something like this out is what happens if it never comes to fruition, or gets punted due to lack of time/resources, or reprioritized for a different patch? All it will do is disappoint people because they'll see something that we once considered, but then never did for XYZ reasons (which ultimately end up not mattering). Also consider when we're looking at new features specifically, for example, this kind of takes the wind out of Marketing and PR's sails if we just lay it all out on the table early.

2) things we are working on fixes for - This is something we've toyed around with doing frequently, but what ultimately goes in this list? We're working on many fixes at one time, some of which take a lot of time and effort, some of which are very minor. We can't list everything - it just isn't reasonable or even feasible. What we decided to do instead is reply to threads in the Bug Reports section, as we're able, to give a status on the bug reported. Can we do a better job and reply to more threads? Sure. But as we originally said when we opened that section, we reply as we can.

3) things being tested/balanced - Again, this is a moving target and the effort to maintain something like this would probably be a full time job in itself. Unfortunately, the reality of the situation is we (the Community team) have many tasks and responsibilities and simply don't have the bandwidth to maintain something like this on a regular cadence. We can try to give you more general updates more frequently, though, and this is something we can work to improve.

4) things coming in update x - We do this to some extent when we release preview articles, and you could even consider the PTS patch notes to be a preview of sorts. Again, remember we have other departments that need to hold onto content based on a release schedule and strategy. I know that's a little different from gameplay-specific things, which is probably what you're referencing, and we can try to do a better job to let you know the things we're working on for the future. Many times, we're just not ready to talk about our plans because - again - it's a moving target. We iterate and iterate, and tweak things until they're close to being just right. That's when we put things on the PTS for final tweaks and testing, and gather up your feedback for what we've implemented.

5) things we are not going ahead with anymore - This is fair, and we can certainly be more open about things that aren't really on the table, just so you don't feel like you're being strung along.

Sorry for the wall of text, it's late and I started rambling. TL;DR - we'll work on doing a better job to communicate the larger, more overarching changes and plans we have for future gameplay updates to keep everyone abreast of what we're doing.

Thank you for the response Gina it is appreciated. Fair point re 1 that Marketing and PR want to hold on to that.

I just think if you don't already having someone employed as a project manager whose sole job was to gather and convey the information in points 2 and 3 between devs and the community that this would be a really good idea. I appreciate it is asking too much of you, Jessica and Kai to be on top of that in addition to your own work and I agree that would be a full time job in itself but it really would short circuit alot of the complaints on the forums if there was more communication even if it was just on those two issues.

If you had all the information together in a section of the forum it would save you having to scroll through the 100s of threads a day to respond to these issues as people would have a port of call that would answer most of the threads.

Ch4mpTW · July 2017

Rohamad_Ali wrote: »

Just put me on the community team and I'll fix the communications issue . I will talk them into a coma .

@Rohamad_Ali No, Roh'... We don't need to know about you having yarn fights with @SantieClaws and doing whatever you cat folks do. Let alone how rough it is as a Khajiit, in living about Tamriel. We need people (lol elves actually) to talk to us about what is getting fixed, and the bug removals to come.

rhapsodious · July 2017

Juli'St wrote: »

Can ZOS fix your servers? Ty!

Really? Gina went out of her way to write that post and you feel the need to bring that up? ~_~ Not the time or the place.

And Gina, thanks for the post by the way. I don't work in your job, but I do work in software development and I know all too well the risks of saying "yeah, we'd love to do that" and it turns out, for one reason or another, that you can't do it. And it sucks. Especially when people heard it as "we're doing it!" and you have to backtrack. It's a rough path between wanting to be transparent with your base and not digging yourself into a hole.

I think building off of what you've been doing in ESO Lives, where you highlight the upcoming patch notes, would be best going forward. Piggybacking off Curragraigue's idea, maybe a "Week In Review" post where you guys list, in layman's terms, progress on various issues? Maybe total bugs fixed, the plan going forward, and our favorite - developer comments? I appreciate the work you and the other CMs do, though! I don't envy you at all, though. No offense.

Rohamad_Ali · July 2017

Ch4mpTW wrote: »

Rohamad_Ali wrote: »

Just put me on the community team and I'll fix the communications issue . I will talk them into a coma .

@Rohamad_Ali No, Roh'... We don't need to know about you having yarn fights with @SantieClaws and doing whatever you cat folks do. Let alone how rough it is as a Khajiit, in living about Tamriel. We need people (lol elves actually) to talk to us about what is getting fixed, and the bug removals to come.

True but I have a unique skill . I once bored a customer out of a refund for 3 hours . He almost paid this one again to just shut up .

Ch4mpTW · July 2017

Rohamad_Ali wrote: »

Ch4mpTW wrote: »

Rohamad_Ali wrote: »

Just put me on the community team and I'll fix the communications issue . I will talk them into a coma .

@Rohamad_Ali No, Roh'... We don't need to know about you having yarn fights with @SantieClaws and doing whatever you cat folks do. Let alone how rough it is as a Khajiit, in living about Tamriel. We need people (lol elves actually) to talk to us about what is getting fixed, and the bug removals to come.

True but I have a unique skill . I once bored a customer out of a refund for 3 hours . He almost paid this one again to just shut up .

Lololol. +1

On some real though, I would love if somebody at ZOS would just casually post-up about current goals of getting things fixed evey here and there. Just to provide a tiny bit of transparency, you know? Just to provide us with a little bit of a whiff of what it is that they are cooking, so that we can be satisfied off of the fumes alone. And honestly, it would go incredibly far. Whether it be: You, Santie, Alcast, Gina, Wrobel, etc. The person doesn't matter. What matters is that connection is made to the player base, and that we aren't left out in the dark about what's going on. And that they are aware of the things occurring, and what they have planned to addressed them. I think something like that will stretch miles.

vyndral13preub18_ESO · July 2017

ZOS_GinaBruno wrote: »

5) things we are not going ahead with anymore - This is fair, and we can certainly be more open about things that aren't really on the table, just so you don't feel like you're being strung along.

So how is spell crafting coming?

The_Saint · July 2017

Rohamad_Ali wrote: »

Just put me on the community team and I'll fix the communications issue . I will talk them into a coma .

@Rohamad_Ali

https://jobs.zenimax.com/requisitions/view/1401

Rohamad_Ali · July 2017

The_Saint wrote: »

Rohamad_Ali wrote: »

Just put me on the community team and I'll fix the communications issue . I will talk them into a coma .

@Rohamad_Ali

https://jobs.zenimax.com/requisitions/view/1401

No need . The forums are my resume . 10 Stars . I can start immediately .

On a serious note , it is nice to have communication more often from Gina and Jessica . I have noticed them being more active with Us recently . Is good .

NBrookus · July 2017

ZOS_GinaBruno wrote: »

lots of good stuff

Serious suggestion: Start a council of players. A small group, similar to the community ambassadors, that has shown over time that they care about the game, have taken the time to contribute to the community as a whole, have perspective on multiple classes and playstyles and can communicate well. Put them under NDA. Maybe they can't even say they are on the council and everyone else only knows there IS one. Ask them to serve and give them shiny things for their time spent.

These folks are probably going to be able to give you the feedback on what issues seem most critical to day to day to your player base. What fixes will be most likely work from a play standpoint. Which things are going to be exploited.

I was a developer for decades. I understand the tug of war between making money, what's feasible and what's cool. When the devs are pushing technical fixes and the execs are pushing EBIDOC, it would be helpful in your decision making process to have thoughtful advocates from the player base.

Qbiken · July 2017

SwaminoNowlino wrote: »

GreenhaloX wrote: »

Aisle9 wrote: »

GreenhaloX wrote: »

Ch4mpTW wrote: »

https://youtu.be/I1wsTHhjb2M

Seriously. What happened to it? Whether it is PvE or PvP. I'm so damn tired of getting double CC'd from hard-CC's that I'm ready to scream. I can't avoid it in PvE, and I can't avoid it in PvP. NPC's and players alike just completely rendering CC immunity null and void. And I've damn near had it. I made a post about this a month or so ago, and not a single damn dev or combat team member made a comment about what they are doing to look into it. Nor have mentioned an ETA on a proper fix.

I'm sick of it, bruh. I'm tired of having point out crap, and nothing gets done. Just like how early I made a thread about how I could still gap-close into keeps, and sent out messages to the staff of ZOS. And not 1 of them has gotten back to me about it, or how they'll look into it. People have been exploiting the queue system, and still no ETA on when that will be fixed. Keep doors not letting you in or out have been broken for YEARS, and still no damn ETA on a fix. But you ZOS mods can come into a thread, and make a comment about how you removed a post this and that. You can sure comment on that. But, you can't comment and engage on what you're ACTIVELY doing to make your game better.

And yes, before some white knight joins this thread and says how I'm not entitled to a functioning game. Save it. I already know about how we signed the damn TOS that states how ZOS don't have to fix anything, and that they are free to do whatever they want and how we want. So save it. I don't want to hear that noise. Call this another complaint and whine thread. Call me the ESO Alex Jones. Idgaf at this point, bruh. I really don't.

Damn.. another language of ESO I don't understand. What is CC? I don't know.. looking at your clip, it just looks like a single dude in PvP land getting his arse handed to him by a group, which happens to every dudes or dudettes in Cyrodiil that decide to solo. That's why only being in a zerg or group in Cyrodiil pays..

Crowd Control

Oh.. thanks for the clarification. Not slamming or bashing on the Ch4mpTW dude in any way, but what is actually the problem again with CC that Ch4mpTW dude is beeaattcching about? Maybe it just me.. and no, no white knight (black sheep here more than anything) here. All I see is a dude getting his arse handed to him by a group, which happens to me too while I tried to solo in Cyrodiil.

He gets knocked down by a javelin. Gets back up. And is immediately knocked down again. There is supposed to an immunity to cc in there somewhere. It doesn't ever actually work that way.

As far as I know: Unless you break free you won´t get any CC-immunity. Some skills are acting wierd sometimes and are more difficult to CC-break from (looking at you Fear and Shield-charge)

Cherryblossom · July 2017

Still getting stunned and CC'd in Mist form so there is no hope in them fixing this.

dennissomb16_ESO · July 2017

I think the issue is going beyond broken CC immunity. Today in a keep fight I drank an immovability potion (15.7 second immunity to knockdowns) and within 2 seconds not only was I knocked down, but used my break free and was knocked down again immediately.