WTF Happened to "CC Immunity"?

Sneaky-Snurr · July 2017

This is clearly a L2P issue.

Krayzie · July 2017

The thing is, if they never made absolutely everything cause CC, this wouldn't be a problem.

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.

You're actually worried about things coming to fruition?!?!

This game has implemented *FIXES* at every patch and there's been multiple reports EVERY PATCH of the fixes not even working as stated.

Pretty sure that's the least of your worries at a point long long ago.

RinaldoGandolphi · July 2017

CC Immunity is simply broken right now. Javelin, DK Chains and Meteor being the 3 biggest offenders. I has chained stunned 3 times in a row by Javelin's last night multiple times despite breaking free twice. just knocked right back down...after the 3rd knockdown I was chain pulled by a DK LOL...the whole thing is broken.

I am glad i got a few hundred more immovable pots and plenty of ingedients to make more..

lasertooth · July 2017

Cherryblossom wrote: »

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

Yes, I was/am too.

While in mist form, players are still able to gap close and pull me out of mist form, in a similar way an aoe pulls a nightblade out of cloak.

It's not every single time, and it tends to happen in large group fights (many players chasing me) so I think it's related to lag.

pema · July 2017

many things in PVP are broken, CC imunity; using macro's; block/break free being hard as mag users don't have any stam and stam users use it for skills... cheat engines are another big one, people who can't die wtf.
There is a lot wrong, also the que jumping. so please do a good repair on the pvp and move on to pve then next.

CromulentForumID · July 2017

Juli'St wrote: »

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!

Example 1 of why companies get hesitant to engage their online communities. Good Job. Everyone needs a "Don't" example to follow.

MasterSpatula · July 2017

I left for 10 months after the B2P transition, and I always just assumed they removed CC immunity during that 10 months. I literally thought this was a (terrible, terrible) choice they made.

I'm really glad to know it's a bug, but also really frustrated to know it's still around. The absolute worst thing about PVP for me is the non-stop CC. Fixing this would make me want to be in Cyrodiil a LOT more.

Magdalina · July 2017

dennissomb16_ESO wrote: »

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.

In my experience Immovable pots take 1-2 seconds to work. If I drink one right before getting cc'd, it's 100% guarantee of getting cc'd with white swirls all over me. It seems server is slow processing this, perhaps cc immunity should be given priority to cc/damage skills which are currently obviously going through before it.

Magdalina · July 2017

Edit: Phone double post. Delete please

Lokey0024 · July 2017

Got cced 5 seconds after poping a immovable pot bombing a breach into a keep. Good times.

Idinuse · 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.

Munavar · July 2017

For simplicity sake, I am of the opinion that CC is an inane concept.

CC should be reviewed in its entirety. I have never heard any player praising being out of control of their character.

The skills that grant CC should do nothing else. No damage, no buff, or other de-buff should also be attached to the attack.

The skills should be creating areas of denial. Not be movable (attached to the target).

With animation canceling now being a feature (yes, I get it that the combat would be clunky for some if the animation times were enforced), the CC times should be drastically reduced to reflect the 'new' cast time of attacks.

The Shield Breaker set was created as a to counter shield stacking. How about an 'Always in Control' set that has constant CC immunity? I am willing to wager that nearly every person that spends any significant amount of time in PvP would wear it to get off of the immovability potion addiction.

Smmokkee · July 2017

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.

Bruh

Ch4mpTW · July 2017

Smmokkee 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.

Bruh

Lol. +1 bruh.

Reverb · 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.

I almost reported this post as someone having hacked Gina's account. I actually had the 'Report' window up and was typing that someone was pretending to be a Community Manager and was acknowledging Zeni's response shortcomings.

LUC1D7 · July 2017

There is no CC immunity from DK talons either. I felt like a rag doll fighting one the other day and constantly being CCed

Magdalina · July 2017

LUC1D7 wrote: »

There is no CC immunity from DK talons either. I felt like a rag doll fighting one the other day and constantly being CCed

Roots do not give and are not affected by hard cc immunity. However dodging a root grants a short(3 seconds? Not sure) immunity to soft cc, aka subsequent roots. Roots can also be cleansed(which is more the templar only option).

NightbladeMechanics · July 2017

Haven't had a chance to watch the video.

But I've been double cced by all sorts of things this patch, and @FENGRUSH and @gibous have both complained recently about their immov pots failing to prevent ccs.

Something appears to be up.

Gan Xing · 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 @ZOS_GinaBruno for getting back in touch with us. This helps restore some confidence within ZOS, as it illuminates what happens behind the scenes a bit. As another pointed out, you are one of the few who puts time and effort into keeping in touch with the player base and being both professional, but also understanding about it. I feel like for a lot of problems/bugs/broken sets, knowing who to contact besides you or @Wrobel would help reduce the strain that we place on you, as you are the first person everyone connects their post in when they find a bug/problem/broken set/skill.

gibous · July 2017

As @KenaPKK mentioned I've had several immovable pots fail recently during reasonable latency. The noticeable condition is having multiple CCs hit simultaneously about 1-2 seconds after consuming the pot. Maybe it's a lag issue, or maybe it has to do with when the CC abilities are fired vs when they hit compared to when the pot is taken. It just looks insane when you hit that pot and then 1 second later get knocked down.

In OP's vid, you can see them take a javelin and then a meteor right behind it. Perhaps there is something happening with the meteor CC overwriting the javelin CC during the knockback phase resulting in immunity being canceled.

sirston · July 2017

@ZOS_GinaBruno
When I see any dev or PR person say "QA team" I just think it's a 12 year old boy that's pressing buttons randomly on a keyboard and telling them "all the buttons are working!" The amount of times Ive seen people tell @ZOS about bugs and the response is

https://www.youtube.com/watch?v=cOCD_Jzre3c

Frickin drives me up the wall. I've played this game about 3 years (On and Off) now and If this game didn't have "The Elder Scrolls" behind it. the game would be dead; or a Very negative score on gaming sites.

I don't understand how a company trying to make money by video games; has a difficulty communicating with its player base. when you as a company have; /server say, forums, reddit, facebook, twitter, feedback, Snail Mail, Email and in game communication.

Also I understand that you and jessica have to be a face of a company that gets a lot of backlash for doing dumb stuff. But it took me 3 seconds to go into your website and type "cc broken" and found a humongous amount of complaining about it.

https://forums.elderscrollsonline.com/en/search?Search=CC+broken

If you guys don't have the manpower/Womenpower to deal with the game issues Just freakin say it. I'm pretty sure about 90% community would understand. If you need resources shifted I would say just pull a runescape move and make player moderators I mean that took a huge load off of Jagex support team and made their life about 100% easier Im sure a lot of people including myself would be more then happy to help your game succed so everyone could have fun and make the game work, I don't want this game to continuously give me a bad taste in the mouth when I talk about it.

Wreuntzylla · July 2017

For PC, I use an addon that tells me when I am cc'd. When it's laggy, the addon will be a second or two ahead of the cc graphic. It was a complete solution for what people call unbreakable fear.

Of course, on console there is no relief.

MehrunesFlagon · July 2017

Honestly think that cc immunity should count for all cc types from a single break. Also increasing the immunity duration by approximately 3x would be a step in the right direction.

Also they probably should make executes not work if they aren't in execute range. Undodgeable attacks need to go too. There is no reason that if I can see it coming that I should have to take the damage like a moron.

Ch4mpTW · July 2017

MehrunesFlagon wrote: »

Honestly think that cc immunity should count for all cc types from a single break. Also increasing the immunity duration by approximately 3x would be a step in the right direction.

Also they probably should make executes not work if they aren't in execute range. Undodgeable attacks need to go too. There is no reason that if I can see it coming that I should have to take the damage like a moron.

What...?

MehrunesFlagon · July 2017

Ch4mpTW wrote: »

MehrunesFlagon wrote: »

Honestly think that cc immunity should count for all cc types from a single break. Also increasing the immunity duration by approximately 3x would be a step in the right direction.

Also they probably should make executes not work if they aren't in execute range. Undodgeable attacks need to go too. There is no reason that if I can see it coming that I should have to take the damage like a moron.

What...?

Not quite sure what you don't understand,but was really getting at doing that in addition to fixing what's broken.

Crimsonwolf666 · July 2017

I see glitches in CC all the time too. I put immunities up a few seconds before a CC hits and about 50% of the time it doesn't defend me. Either using potions, Immovable skill or whatnot it is extremely glitchy at best.

Ch4mpTW · July 2017

MehrunesFlagon wrote: »

Ch4mpTW wrote: »

MehrunesFlagon wrote: »

Honestly think that cc immunity should count for all cc types from a single break. Also increasing the immunity duration by approximately 3x would be a step in the right direction.

Also they probably should make executes not work if they aren't in execute range. Undodgeable attacks need to go too. There is no reason that if I can see it coming that I should have to take the damage like a moron.

What...?

Not quite sure what you don't understand,but was really getting at doing that in addition to fixing what's broken.

Oh. Ok. Lol.

xeNNNNN · July 2017

Aisle9 wrote: »

Sharee wrote: »

Aisle9 wrote: »

Ch4mpTW wrote: »

Aisle9 wrote: »

You don't break free, therefore no CC immunity

L2BF

How could I...? I was lagging horribly. Damn, I swear you ZOS fanboys will defend anything. No matter how blatantly obvious something is broken.

I'm not defending anything, just explaining how it works.

Is your argument that if you're lagging you should be immune to the game core mechanics ? Everyone is lagging, and everyone is having the same problems.

In your video you don't break free, but ask to be CC immune. It doesn't work like that, and you can be double CCed if you don't break free from the first one.

Would be cause to grief if you did break free, but did not get the CC immunity, like it happened to many people (myself included). I would never, nor I ever did, defend that.

Have a good day.

No, his argument is that he should be given CC immunity after a hard CC on him expires, regardless of whether he breaks free or not, and he is right, that is how it is supposed to work.

The hard CC didn't expire, therefore, no CC immunity.

I'm not sure where you play, but down here you can chain hard CCs in rapid succession as long as you do before the previous one expire.

I'm not saying it should work like that, and I do agree it's BS, but it's how it works, and it's been like this for a while now.

Becuase nobody can be bothered to complain. Because most pvpers feel like nothing gets done lol.

Nerf sorc? nah will be the go to class until 2020. I complain a lot about sorc, others do too nothing gets done.

Encase spam? Sureeee lets keep a spammable root that apparently has no built in immunity measure. Because morphs

look you get my point. This really needs to be dealt with, I am sick to death of being chained constantly. Infact I some how managed too get spammed twice by a jaevalin into a meteor.. I didnt even question it after I apparently flew from one side of chalman lumber too the others because "eso".

eso_lags · July 2017

@ZOS_GinaBruno I think its amazing and awesome that you acutally took the time to respond like that. We need that more around here. So im a solo player and that cc bug really messes me up a lot. But something that hurts much more is the lag. This leads me to my question for you that i have asked many many times in tickets and on here.

Is there any word about the ongoing lag that has been plaguing cyrodil, on console, for so many months getting fixed? Is it something that gets solved with next gen console like the xbox one x? I feel like its been ignored and i would really like to know if you guys have any word on it or are looking into it. Ive compared the large scale fights on xbox and pc many times over and the difference is huge.. Like its crazy how bad it gets. Lag spikes, fps drop, whatever its called it is bad and everyone is experiencing it.

TheHsN · 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.

PLS no offence...Look how you broke it in first place