ESO_Nightingale wrote: »1 thing that surprised me was how few responses there were about combat changes directly
ESO_Nightingale wrote: »to add to why i was surprised, most of the discussion channels i look at on the forums are combat mechanics and the PTS. I just thought id see more people say things like they had grievances with stuff like gravelords sacrifice etc.
I only have 1 pain point:
PVP meta: For years its been about building tankiness via blocking or % dmg reduction and tons of healing while still being able to deal dmg through proccsets.
Look at the current fotm meta where you slot Relequen, Draugrkin and Jeralls while having 40k max hp.
katanagirl1 wrote: »katanagirl1 wrote: »valenwood_vegan wrote: »Thanks for starting this conversation, @LadyGP.
Just wanted to put a reminder that if folks share bugs and pain points here, that they also reflect that in the thread where we are collecting the list from players. LadyGP has it in the first post of this thread.
Hey Kevin, I posted in the thread but just wanted to add here that I wonder if this might also be some good material for a survey, like y'all did last year about guilds. Not that you won't get useful feedback here on the forum, but I feel like that's going to be very difficult to parse through. Especially with the answers varying so greatly depending on the areas of the game that people engage with. Just a thought about another potential avenue for gathering this feedback from players but in perhaps a more structured way.
It's really nice to see our feedback being sought after, whatever form that may take.
That is a good idea. The general point with the thread is to get a baseline for the communities most sought after bugs. We are reviewing this now and seeing what can get tackled and when. However, getting more feedback via a survey is not a bad idea and something we can work on for later in the year.
We do have a few surveys in the works on other issues, so we need to finish those and get them out before taking on any other survey projects.
I am curious how survey recipients are selected. Despite having many, many more hours in the game than most players and several stars next to my name here on the forums, I have never got one. I guess I have bad RNG everywhere, lol.
The last survey on Guilds was posted on the forum, discord and shared on social media. We will be posting surveys here on the forum, discord and on Reddit going forward. These are community team led surveys. However, sometimes our other teams send out surveys and they have their own data points they are trying to hit.
I don’t use Discord or social media but I’m on here several times a day. I don’t remember seeing anything. I wouldn’t know when or where to look to be honest.
Kevin created a thread asking players to submit their top five bugs and pain points that we would like addressed but asked to keep comments to a minimum.
This thread is for discussing the dev team’s request itself, what bugs and issues you think are the most important, and any expectations or thoughts on how they might address them.
So, about the request itself, my plan is to ignore it. My expectations are that it won't matter. My expectation is that they will be more attracted to player comments that align favorably with their current decisions and not as much for comments that are not.
I expect that they already have stuff in the works. Planned, booked, and confirmed. While ZOS needs to listen to players, I think that what we say now won't be in the game for over a year, assuming that it aligns well with what ZOS wants. 2026 or even 2027. By then, the player comments and opinions may be very much different than they are today. Many players that respond to this query today may not even be playing the game anymore.
The goal is to get feedback to that we can see what can be prioritized over the next few updates and then plan out from there. Part of Matt's end of year letter notes how the team is working to be more agile and tackle things at a faster rate. So the ask is helping to set up for that. Obviously, ultimately up to you on your level of participation in that. Just wanted to provide extra context for the ask.
Izanagi.Xiiib16_ESO wrote: »Kevin created a thread asking players to submit their top five bugs and pain points that we would like addressed but asked to keep comments to a minimum.
This thread is for discussing the dev team’s request itself, what bugs and issues you think are the most important, and any expectations or thoughts on how they might address them.
So, about the request itself, my plan is to ignore it. My expectations are that it won't matter. My expectation is that they will be more attracted to player comments that align favorably with their current decisions and not as much for comments that are not.
I expect that they already have stuff in the works. Planned, booked, and confirmed. While ZOS needs to listen to players, I think that what we say now won't be in the game for over a year, assuming that it aligns well with what ZOS wants. 2026 or even 2027. By then, the player comments and opinions may be very much different than they are today. Many players that respond to this query today may not even be playing the game anymore.
The goal is to get feedback to that we can see what can be prioritized over the next few updates and then plan out from there. Part of Matt's end of year letter notes how the team is working to be more agile and tackle things at a faster rate. So the ask is helping to set up for that. Obviously, ultimately up to you on your level of participation in that. Just wanted to provide extra context for the ask.
@ZOS_Kevin
It would be really interesting (for me at least and likely for some others) to see how all this feedback has been interpreted on your side once you have finished compiling the information.
For example, are you going to be ranking all our suggestions by gameplay area and then similarity / popularity of suggestion. Will there be difficulty of implementation taken into account etc?
I think that's what would help players understand whether their help has been valuable or not.
For example If I saw a pvp bugs/pain points list and the 'stuck in combat' bug was at the top because many players had mentioned it I would understand it, even though it's not top of my individual list. But equally that's been 'known' about for 10 years at this point and is unfixable by conventional means so far so it would be heartening to understand that if it is the feedback about the problem being not being able to mount / teleport to keeps when in combat being the main issue was actually received.
/raises handLike I might be the only person left from the large amount of people on these forums wanting a "class change token" (:< or alternate, class swapping through armory when?) left after all these years
Izanagi.Xiiib16_ESO wrote: »Kevin created a thread asking players to submit their top five bugs and pain points that we would like addressed but asked to keep comments to a minimum.
This thread is for discussing the dev team’s request itself, what bugs and issues you think are the most important, and any expectations or thoughts on how they might address them.
So, about the request itself, my plan is to ignore it. My expectations are that it won't matter. My expectation is that they will be more attracted to player comments that align favorably with their current decisions and not as much for comments that are not.
I expect that they already have stuff in the works. Planned, booked, and confirmed. While ZOS needs to listen to players, I think that what we say now won't be in the game for over a year, assuming that it aligns well with what ZOS wants. 2026 or even 2027. By then, the player comments and opinions may be very much different than they are today. Many players that respond to this query today may not even be playing the game anymore.
The goal is to get feedback to that we can see what can be prioritized over the next few updates and then plan out from there. Part of Matt's end of year letter notes how the team is working to be more agile and tackle things at a faster rate. So the ask is helping to set up for that. Obviously, ultimately up to you on your level of participation in that. Just wanted to provide extra context for the ask.
@ZOS_Kevin
It would be really interesting (for me at least and likely for some others) to see how all this feedback has been interpreted on your side once you have finished compiling the information.
For example, are you going to be ranking all our suggestions by gameplay area and then similarity / popularity of suggestion. Will there be difficulty of implementation taken into account etc?
I think that's what would help players understand whether their help has been valuable or not.
For example If I saw a pvp bugs/pain points list and the 'stuck in combat' bug was at the top because many players had mentioned it I would understand it, even though it's not top of my individual list. But equally that's been 'known' about for 10 years at this point and is unfixable by conventional means so far so it would be heartening to understand that if it is the feedback about the problem being not being able to mount / teleport to keeps when in combat being the main issue was actually received.
So we can't answer this with exact detail because we are in the beginning stages of addressing this. Also depending on the issue, it may take a different set of resources to resolve. But the general idea is compile what are the top items (this is why we asked for top 5) and figure out what a solution looks like and what it takes to implement said solution. We can then assess what we can do with the time and resources we have for each update (we work on a lot of stuff, so time is always our worst enemy). As Matt mentioned in his end of year letter, the change in update structure is to allow the team to address things faster and more often. This is the year of transition for that change and we are prepping for that with the bug/pain point list.
That doesn't mean that the least asked items will not get addressed. We will work on a way to prioritize them once we get some of the bigger asks out of the way. For any that can't be addressed at this time, we will figure out a way to message that out. Similar to what we said about items like class change tokens.
But just to reiterate, this is all in an effort to address some of the higher bug issues and pain points in the community as a starting point and then adapt from there.
ESO_Nightingale wrote: »to add to why i was surprised, most of the discussion channels i look at on the forums are combat mechanics and the PTS. I just thought id see more people say things like they had grievances with stuff like gravelords sacrifice etc.
It's quite possible that many people feel that the scope of "Combat is bad" is simply too much for this sort of thing.
Notably, the "Top 5" nature of it means really you'd list 5 individual things. Which might barely scratch the surface of things.
Take for example Necro. As a single class. Many threads have been made about the class, all of which touch on large numbers of issues. Vastly more than 5.
I suppose one could try and just list "Necro is bad" as a single point in the list... But does that accurately portray things? Will it highlight the aspects that are lacking? Or will it just be considered "My Necro isn't viable in endgame content" and then be dismissed because Necro's do see play in Trifectas/Vet Trials?
Personally, I could write an essay around all of my qualms with the combat system (And related systems like Overland and Dungeons). Which would likely hit 100+ different pain points.
But do I really expect there to be major overhauls in combat to be done anytime soon? Not in the slightest. Especially given the years that the massive Overland megathread has been active wherein only now (According to the live letter) is something this large being looked at.
If combat overhauls were seriously being looked at, I'd expect there to be more focused feedback requests related to specifics. Like, each class, skill line and even base combat mechanics (LA's, HA's, LA weaving, items like Oakensoul/Velothi etc)
So instead, focusing responses into smaller issues seems most appropriate. They're most likely to be considered and changed based off of limited feedback (I.e. Listing of the issue in question)
One thing I would caution against is that once the list gets compiled people are going to naturally assume the top 5 are going to be worked in that order and obviously this is not how development works.
343i (Halo Studios now) did a really good job when they went through something similar at communicating WHY say Top Issue #14 was solved before Top Issue #2. They would say something like... well we realized we couldn't solve #2 because #14 was directly responsible for a portion of said issue #2 so we had to solve that first before we can finish #2.
People are going to unfairly freak out when they see the lower hanging fruit get solved first so just knowing that is going to come and be prepared to explain the reason behind it might make it easier on y'all. In no way trying to tell you how to do your job so hopefully this doesn't read in a condescending manner (text sucks lol).
One thing I would caution against is that once the list gets compiled people are going to naturally assume the top 5 are going to be worked in that order and obviously this is not how development works.
343i (Halo Studios now) did a really good job when they went through something similar at communicating WHY say Top Issue #14 was solved before Top Issue #2. They would say something like... well we realized we couldn't solve #2 because #14 was directly responsible for a portion of said issue #2 so we had to solve that first before we can finish #2.
People are going to unfairly freak out when they see the lower hanging fruit get solved first so just knowing that is going to come and be prepared to explain the reason behind it might make it easier on y'all. In no way trying to tell you how to do your job so hopefully this doesn't read in a condescending manner (text sucks lol).
No you're fine. No worries! We will plan to be clear in Patch Notes for when fixes happen and follow up with some longer explanations on fixes. I'm sure we will need to adjust a bit on the communication front, but we'll do that based on your feedback.
Izanagi.Xiiib16_ESO wrote: »Kevin created a thread asking players to submit their top five bugs and pain points that we would like addressed but asked to keep comments to a minimum.
This thread is for discussing the dev team’s request itself, what bugs and issues you think are the most important, and any expectations or thoughts on how they might address them.
So, about the request itself, my plan is to ignore it. My expectations are that it won't matter. My expectation is that they will be more attracted to player comments that align favorably with their current decisions and not as much for comments that are not.
I expect that they already have stuff in the works. Planned, booked, and confirmed. While ZOS needs to listen to players, I think that what we say now won't be in the game for over a year, assuming that it aligns well with what ZOS wants. 2026 or even 2027. By then, the player comments and opinions may be very much different than they are today. Many players that respond to this query today may not even be playing the game anymore.
The goal is to get feedback to that we can see what can be prioritized over the next few updates and then plan out from there. Part of Matt's end of year letter notes how the team is working to be more agile and tackle things at a faster rate. So the ask is helping to set up for that. Obviously, ultimately up to you on your level of participation in that. Just wanted to provide extra context for the ask.
@ZOS_Kevin
It would be really interesting (for me at least and likely for some others) to see how all this feedback has been interpreted on your side once you have finished compiling the information.
For example, are you going to be ranking all our suggestions by gameplay area and then similarity / popularity of suggestion. Will there be difficulty of implementation taken into account etc?
I think that's what would help players understand whether their help has been valuable or not.
For example If I saw a pvp bugs/pain points list and the 'stuck in combat' bug was at the top because many players had mentioned it I would understand it, even though it's not top of my individual list. But equally that's been 'known' about for 10 years at this point and is unfixable by conventional means so far so it would be heartening to understand that if it is the feedback about the problem being not being able to mount / teleport to keeps when in combat being the main issue was actually received.
So we can't answer this with exact detail because we are in the beginning stages of addressing this. Also depending on the issue, it may take a different set of resources to resolve. But the general idea is compile what are the top items (this is why we asked for top 5) and figure out what a solution looks like and what it takes to implement said solution. We can then assess what we can do with the time and resources we have for each update (we work on a lot of stuff, so time is always our worst enemy). As Matt mentioned in his end of year letter, the change in update structure is to allow the team to address things faster and more often. This is the year of transition for that change and we are prepping for that with the bug/pain point list.
That doesn't mean that the least asked items will not get addressed. We will work on a way to prioritize them once we get some of the bigger asks out of the way. For any that can't be addressed at this time, we will figure out a way to message that out. Similar to what we said about items like class change tokens.
But just to reiterate, this is all in an effort to address some of the higher bug issues and pain points in the community as a starting point and then adapt from there.
One thing I would caution against is that once the list gets compiled people are going to naturally assume the top 5 are going to be worked in that order and obviously this is not how development works.
343i (Halo Studios now) did a really good job when they went through something similar at communicating WHY say Top Issue #14 was solved before Top Issue #2. They would say something like... well we realized we couldn't solve #2 because #14 was directly responsible for a portion of said issue #2 so we had to solve that first before we can finish #2.
People are going to unfairly freak out when they see the lower hanging fruit get solved first so just knowing that is going to come and be prepared to explain the reason behind it might make it easier on y'all. In no way trying to tell you how to do your job so hopefully this doesn't read in a condescending manner (text sucks lol).
No you're fine. No worries! We will plan to be clear in Patch Notes for when fixes happen and follow up with some longer explanations on fixes. I'm sure we will need to adjust a bit on the communication front, but we'll do that based on your feedback.
katanagirl1 wrote: »katanagirl1 wrote: »valenwood_vegan wrote: »Thanks for starting this conversation, @LadyGP.
Just wanted to put a reminder that if folks share bugs and pain points here, that they also reflect that in the thread where we are collecting the list from players. LadyGP has it in the first post of this thread.
Hey Kevin, I posted in the thread but just wanted to add here that I wonder if this might also be some good material for a survey, like y'all did last year about guilds. Not that you won't get useful feedback here on the forum, but I feel like that's going to be very difficult to parse through. Especially with the answers varying so greatly depending on the areas of the game that people engage with. Just a thought about another potential avenue for gathering this feedback from players but in perhaps a more structured way.
It's really nice to see our feedback being sought after, whatever form that may take.
That is a good idea. The general point with the thread is to get a baseline for the communities most sought after bugs. We are reviewing this now and seeing what can get tackled and when. However, getting more feedback via a survey is not a bad idea and something we can work on for later in the year.
We do have a few surveys in the works on other issues, so we need to finish those and get them out before taking on any other survey projects.
I am curious how survey recipients are selected. Despite having many, many more hours in the game than most players and several stars next to my name here on the forums, I have never got one. I guess I have bad RNG everywhere, lol.
The last survey on Guilds was posted on the forum, discord and shared on social media. We will be posting surveys here on the forum, discord and on Reddit going forward. These are community team led surveys. However, sometimes our other teams send out surveys and they have their own data points they are trying to hit.
I don’t use Discord or social media but I’m on here several times a day. I don’t remember seeing anything. I wouldn’t know when or where to look to be honest.
This is the link to the post we made for the survey. Best places to look in the future would be pinned to the recent discussions, General section and to check the Dev Tracker. We had it available on all three of those points here on the forum when the survey was available for feedback.
Izanagi.Xiiib16_ESO wrote: »Kevin created a thread asking players to submit their top five bugs and pain points that we would like addressed but asked to keep comments to a minimum.
This thread is for discussing the dev team’s request itself, what bugs and issues you think are the most important, and any expectations or thoughts on how they might address them.
So, about the request itself, my plan is to ignore it. My expectations are that it won't matter. My expectation is that they will be more attracted to player comments that align favorably with their current decisions and not as much for comments that are not.
I expect that they already have stuff in the works. Planned, booked, and confirmed. While ZOS needs to listen to players, I think that what we say now won't be in the game for over a year, assuming that it aligns well with what ZOS wants. 2026 or even 2027. By then, the player comments and opinions may be very much different than they are today. Many players that respond to this query today may not even be playing the game anymore.
The goal is to get feedback to that we can see what can be prioritized over the next few updates and then plan out from there. Part of Matt's end of year letter notes how the team is working to be more agile and tackle things at a faster rate. So the ask is helping to set up for that. Obviously, ultimately up to you on your level of participation in that. Just wanted to provide extra context for the ask.
@ZOS_Kevin
It would be really interesting (for me at least and likely for some others) to see how all this feedback has been interpreted on your side once you have finished compiling the information.
For example, are you going to be ranking all our suggestions by gameplay area and then similarity / popularity of suggestion. Will there be difficulty of implementation taken into account etc?
I think that's what would help players understand whether their help has been valuable or not.
For example If I saw a pvp bugs/pain points list and the 'stuck in combat' bug was at the top because many players had mentioned it I would understand it, even though it's not top of my individual list. But equally that's been 'known' about for 10 years at this point and is unfixable by conventional means so far so it would be heartening to understand that if it is the feedback about the problem being not being able to mount / teleport to keeps when in combat being the main issue was actually received.
So we can't answer this with exact detail because we are in the beginning stages of addressing this. Also depending on the issue, it may take a different set of resources to resolve. But the general idea is compile what are the top items (this is why we asked for top 5) and figure out what a solution looks like and what it takes to implement said solution. We can then assess what we can do with the time and resources we have for each update (we work on a lot of stuff, so time is always our worst enemy). As Matt mentioned in his end of year letter, the change in update structure is to allow the team to address things faster and more often. This is the year of transition for that change and we are prepping for that with the bug/pain point list.
That doesn't mean that the least asked items will not get addressed. We will work on a way to prioritize them once we get some of the bigger asks out of the way. For any that can't be addressed at this time, we will figure out a way to message that out. Similar to what we said about items like class change tokens.
But just to reiterate, this is all in an effort to address some of the higher bug issues and pain points in the community as a starting point and then adapt from there.
Because the game provides so little guidance to casual players, they end up *very* dependent on content creators and friends for guidance. A lot (but not all) of those content creators and friends are end game players with *detailed* knowledge of how the game works. And a lot of those players turn up less and less in my circles - almost every friend who taught me has left the game, and now I'm in the position of being the one teaching others even though I know infinitely less than the people who have left. I'm a very average player who still struggles to weave well, and suddenly I'm the local "expert" in some of my guild circles solely because the real experts are gone.to add to why i was surprised, most of the discussion channels i look at on the forums are combat mechanics and the PTS. I just thought id see more people say things like they had grievances with stuff like gravelords sacrifice etc.
allochthons wrote: »One of the things I think is lost in the original discussion is the differences between playing on PC (and thus access to add-ons) and console.
Pain points for console are much, much different. For instance, I can't begin to express how much damage the 2-week guild trader change hurt console traders. Engaging with the guild trader system is exponentially more difficult on console without addons than it is on PC with add-ons. It takes literally hours to check prices, if you check prices in more than your own location. I simply can't do that for high priced items more than maybe every few months, certainly not every 2 weeks. I've stopped selling things like Timbercrow for this very reason, and my engagement with the guild trader system is down by 75%.
And then I see people in the Dev Team request thread ask for more guild trader locations and I want to scream.
I didn't even bother listing guild traders under my (more than) 5 things, because it's hopeless. The feeling that ZoS won't bother with things that are fixed by plug-ins is strong.
And when they do (Armorer) their version is sub-standard (can't use in trials, IA etc? PC can change builds running through vet trials, using 1 build for adds, 1 for bosses. I heard a DEV comment how cool it was that players could change builds during vet trial runs during an official Bethesda Stream. WTH?)
I concentrated on things I know affect all platforms. The "consoles are the peasants of ESO" feeling we get from ZoS is very strong.
Having said that. I really appreciate that ZoS's communication seems to be improving drastically. I agree with LadyGP about this.
Thank you, ZOS.
I've sent several tickets in-game reporting this issue with the player's bank gamepad/console UI layout...DenverRalphy wrote: »Bank Stacking seems to be under represented under pain points.
The bank ui is in dire need of a Stack All option. Let alone a smarter algorithm knowing when to stack items upon deposit.
I didn't reflect enough on how much I see casual players frustrated by trying to make their own dungeon/trial builds then doing only 2-5% of group damage.