I don´t think they have the resources anymore to react that fast. If we are lucky, the feedback will be considered for the next patch cycle
So the team does look at feedback and play the game. We also make sure to send things that are hot button issues to the teams. So they are aware and reading. Sometimes feedback is able to be reacted upon quickly, other times, we may need more info on top of what PTS provided. But that feedback does not go to waste. We keep that feedback and reference when we see how more players react and can make better calls on how we can better adjust.
And sometimes the changes asked take longer to implement than the PTS cycle. Feedback and reaction to it varies, but we are always looking at it and discussing changes.
As for the callout of Azureblight and Pyrebrand, we are escalating those again as we see that feedback. I read two other threads on Azureblight before coming into this thread.
So the team does look at feedback and play the game. We also make sure to send things that are hot button issues to the teams. So they are aware and reading. Sometimes feedback is able to be reacted upon quickly, other times, we may need more info on top of what PTS provided. But that feedback does not go to waste. We keep that feedback and reference when we see how more players react and can make better calls on how we can better adjust.
And sometimes the changes asked take longer to implement than the PTS cycle. Feedback and reaction to it varies, but we are always looking at it and discussing changes.
As for the callout of Azureblight and Pyrebrand, we are escalating those again as we see that feedback. I read two other threads on Azureblight before coming into this thread.
So the team does look at feedback and play the game. We also make sure to send things that are hot button issues to the teams. So they are aware and reading. Sometimes feedback is able to be reacted upon quickly, other times, we may need more info on top of what PTS provided. But that feedback does not go to waste. We keep that feedback and reference when we see how more players react and can make better calls on how we can better adjust.
And sometimes the changes asked take longer to implement than the PTS cycle. Feedback and reaction to it varies, but we are always looking at it and discussing changes.
As for the callout of Azureblight and Pyrebrand, we are escalating those again as we see that feedback. I read two other threads on Azureblight before coming into this thread.
So the team does look at feedback and play the game. We also make sure to send things that are hot button issues to the teams. So they are aware and reading. Sometimes feedback is able to be reacted upon quickly, other times, we may need more info on top of what PTS provided. But that feedback does not go to waste. We keep that feedback and reference when we see how more players react and can make better calls on how we can better adjust.
So the team does look at feedback and play the game.
So the team does look at feedback and play the game. We also make sure to send things that are hot button issues to the teams. So they are aware and reading. Sometimes feedback is able to be reacted upon quickly, other times, we may need more info on top of what PTS provided. But that feedback does not go to waste. We keep that feedback and reference when we see how more players react and can make better calls on how we can better adjust.
And sometimes the changes asked take longer to implement than the PTS cycle. Feedback and reaction to it varies, but we are always looking at it and discussing changes.
As for the callout of Azureblight and Pyrebrand, we are escalating those again as we see that feedback. I read two other threads on Azureblight before coming into this thread.
So the team does look at feedback and play the game. We also make sure to send things that are hot button issues to the teams. So they are aware and reading. Sometimes feedback is able to be reacted upon quickly, other times, we may need more info on top of what PTS provided. But that feedback does not go to waste. We keep that feedback and reference when we see how more players react and can make better calls on how we can better adjust.
And sometimes the changes asked take longer to implement than the PTS cycle. Feedback and reaction to it varies, but we are always looking at it and discussing changes.
As for the callout of Azureblight and Pyrebrand, we are escalating those again as we see that feedback. I read two other threads on Azureblight before coming into this thread.
kyle.wilson wrote: »Does the current PVP lead play in Cyrodiil at all? We've had stuck in combat bugs for years.
u/decairn wrote:When will the always in combat bug be fixed? Please, and the entire game population thanks you.
u/ZOS_RichLambert wrote:We actually just had a game jam session and one of the teams devoted their entire project to tackling this long standing bug...
kyle.wilson wrote: »Does the current PVP lead play in Cyrodiil at all? We've had stuck in combat bugs for years.
From what I understand they've been actively working on fixing that bug, it seems like it's surprisingly difficult to fix. From an Ask us Anyting on Reddit from a few months ago:u/decairn wrote:When will the always in combat bug be fixed? Please, and the entire game population thanks you.u/ZOS_RichLambert wrote:We actually just had a game jam session and one of the teams devoted their entire project to tackling this long standing bug...