Many people don't understand the purpose of a test server. I see this in a lot of games.
See I am a software developer. And developing software goes through a process of..:
1. Determine requirements - ie. what do we want to build/change
2. Do the design - ie. How are we going to achieve that - which programs/databases etc. need to change
3. Do the build - ie. changing the code
4. Unit testing - does the code change do as per the design states
5. Systems testing - do all the code changes fit together
6. User/Beta/QA testing - Does the whole thing work as determined by the Requirements (1.)
We are at stage 6. A long way down the development cycle. The aim of this test is to check if the requirements have been met. This means that if the requirement states that Constitution should return 60% less than it used to - is it now returning 60% less than it used to? If it isn't - its a bug. If it is - its working as intended
And that is the key word. Working As Intended - Intended is determined in black and white in the Requirements.
You guys are all asking for the requirements to change - Now don't get me wrong - ZoS probably are listening to the feedback - but changing requirements part way through a project creates a LOT of risk, a LOT of re-work and a LOT of retesting.
The way Requirement changes are generally done is by creating NEW requirements for the next project - which starts at step 1 again.
TLDR;
It will likely be a while till the feedback you are giving now gets to the PTS - and it will probably NOT be in this patch.
It does NOT mean this testing is pointless - AS LONG AS YOU REPORT ANY BUGS/EXPLOITS YOU FIND. Also the early feedback (as opposed to waiting till live) gives them a head start in the next patch wich probably will take some of the comments on-board.
Many people don't understand the purpose of a test server. I see this in a lot of games.
See I am a software developer. And developing software goes through a process of..:
1. Determine requirements - ie. what do we want to build/change
2. Do the design - ie. How are we going to achieve that - which programs/databases etc. need to change
3. Do the build - ie. changing the code
4. Unit testing - does the code change do as per the design states
5. Systems testing - do all the code changes fit together
6. User/Beta/QA testing - Does the whole thing work as determined by the Requirements (1.)
We are at stage 6. A long way down the development cycle. The aim of this test is to check if the requirements have been met. This means that if the requirement states that Constitution should return 60% less than it used to - is it now returning 60% less than it used to? If it isn't - its a bug. If it is - its working as intended
And that is the key word. Working As Intended - Intended is determined in black and white in the Requirements.
You guys are all asking for the requirements to change - Now don't get me wrong - ZoS probably are listening to the feedback - but changing requirements part way through a project creates a LOT of risk, a LOT of re-work and a LOT of retesting.
The way Requirement changes are generally done is by creating NEW requirements for the next project - which starts at step 1 again.
TLDR;
It will likely be a while till the feedback you are giving now gets to the PTS - and it will probably NOT be in this patch.
It does NOT mean this testing is pointless - AS LONG AS YOU REPORT ANY BUGS/EXPLOITS YOU FIND. Also the early feedback (as opposed to waiting till live) gives them a head start in the next patch wich probably will take some of the comments on-board.
This is the official feedback thread for class balance. Specific feedback that the team is looking for includes the following:
- In general, what are your thoughts on the class balance in this update?
- How long did it take you to run out of resources? What did you do in this case?
- Did you change your character/build in any way because of these changes? How so?
Carbonised wrote: »SpoilerMany people don't understand the purpose of a test server. I see this in a lot of games.
See I am a software developer. And developing software goes through a process of..:
1. Determine requirements - ie. what do we want to build/change
2. Do the design - ie. How are we going to achieve that - which programs/databases etc. need to change
3. Do the build - ie. changing the code
4. Unit testing - does the code change do as per the design states
5. Systems testing - do all the code changes fit together
6. User/Beta/QA testing - Does the whole thing work as determined by the Requirements (1.)
We are at stage 6. A long way down the development cycle. The aim of this test is to check if the requirements have been met. This means that if the requirement states that Constitution should return 60% less than it used to - is it now returning 60% less than it used to? If it isn't - its a bug. If it is - its working as intended
And that is the key word. Working As Intended - Intended is determined in black and white in the Requirements.
You guys are all asking for the requirements to change - Now don't get me wrong - ZoS probably are listening to the feedback - but changing requirements part way through a project creates a LOT of risk, a LOT of re-work and a LOT of retesting.
The way Requirement changes are generally done is by creating NEW requirements for the next project - which starts at step 1 again.
TLDR;
It will likely be a while till the feedback you are giving now gets to the PTS - and it will probably NOT be in this patch.
It does NOT mean this testing is pointless - AS LONG AS YOU REPORT ANY BUGS/EXPLOITS YOU FIND. Also the early feedback (as opposed to waiting till live) gives them a head start in the next patch wich probably will take some of the comments on-board.
Except you're flat out wrong.
Yes, glorified bugfixing is a part of the PTS (and pretty much the only part where we are actually heard, though not always).
However:
This isn't bugfixing, man, this is asking for feedback on the content. Go to the Morrowind Closed Beta, and there are even more official thread asking for feedback on content, experience, opinions etc. Not just asking for "Hey, did you guys run into any bugs while doing content XYZ?"
So yeah, considering that the devs do ask for feedback on specific content and balancing issues that go beyond glorified bugfixing, I don't really buy into your premise.
I mean, I'd be completely ok if devs just came out and said "hey sod you guys, we don't want any feedback regarding our content, just bugfixing, thanks". At least then I'd know where they stood, and I could just pass on wasting my time helping them bugfix for free.
The issue at hand here is that 90 % of the community agrees on a certain direction for the game (not to mention a lot of more specifics on the Morrowind Closed Beta forum that do not pertain to class balancing issues or the sustain issue), and that feedback is continually being ignored in the PTS cycles, just like it was in the past in all the other PTS cycles, which makes this whole process extremely frustrating and ungratifying.
InvitationNotFound wrote: »
Or the whole development life cycle is broken. Cut it to smaller pieces and verify if everything works out as expected. Do it more "agile" and not like we used to do it decades ago. Blindly following some requirements, which normally change during the development, is pretty stupid. And yet, it is what we see with every PTS, they get a huge amount of complaints with every PTS and the game is getting worse with every PTS, but yes, keep following the same stupid process over and over again.
Furthermore, I doubt that the feedback provided will influence the next patch. I even doubt that anyone has provided such *** up feedback that could have ended in this current patch.
Band Camp statements: To state "But this one time I saw X doing X... so that justifies X" Refers to the Band camp statement.
Coined by Maxwell
Yeah right. Would be a valid comment, if you hadn't decided to start the thread with "sorcs got (just) a 10% nerv, but DK got lots of sustain problems, and that get changed..." Sorcs suffer a lot of the previous changes as well. But nice try to shine unbiased...Carbonised wrote: »SpoilerMany people don't understand the purpose of a test server. I see this in a lot of games.
See I am a software developer. And developing software goes through a process of..:
1. Determine requirements - ie. what do we want to build/change
2. Do the design - ie. How are we going to achieve that - which programs/databases etc. need to change
3. Do the build - ie. changing the code
4. Unit testing - does the code change do as per the design states
5. Systems testing - do all the code changes fit together
6. User/Beta/QA testing - Does the whole thing work as determined by the Requirements (1.)
We are at stage 6. A long way down the development cycle. The aim of this test is to check if the requirements have been met. This means that if the requirement states that Constitution should return 60% less than it used to - is it now returning 60% less than it used to? If it isn't - its a bug. If it is - its working as intended
And that is the key word. Working As Intended - Intended is determined in black and white in the Requirements.
You guys are all asking for the requirements to change - Now don't get me wrong - ZoS probably are listening to the feedback - but changing requirements part way through a project creates a LOT of risk, a LOT of re-work and a LOT of retesting.
The way Requirement changes are generally done is by creating NEW requirements for the next project - which starts at step 1 again.
TLDR;
It will likely be a while till the feedback you are giving now gets to the PTS - and it will probably NOT be in this patch.
It does NOT mean this testing is pointless - AS LONG AS YOU REPORT ANY BUGS/EXPLOITS YOU FIND. Also the early feedback (as opposed to waiting till live) gives them a head start in the next patch wich probably will take some of the comments on-board.
Except you're flat out wrong.
Yes, glorified bugfixing is a part of the PTS (and pretty much the only part where we are actually heard, though not always).
However:
This isn't bugfixing, man, this is asking for feedback on the content. Go to the Morrowind Closed Beta, and there are even more official thread asking for feedback on content, experience, opinions etc. Not just asking for "Hey, did you guys run into any bugs while doing content XYZ?"
So yeah, considering that the devs do ask for feedback on specific content and balancing issues that go beyond glorified bugfixing, I don't really buy into your premise.
I mean, I'd be completely ok if devs just came out and said "hey sod you guys, we don't want any feedback regarding our content, just bugfixing, thanks". At least then I'd know where they stood, and I could just pass on wasting my time helping them bugfix for free.
Carbonised wrote: »The issue at hand here is that 90 % of the community agrees on a certain direction for the game (not to mention a lot of more specifics on the Morrowind Closed Beta forum that do not pertain to class balancing issues or the sustain issue), and that feedback is continually being ignored in the PTS cycles, just like it was in the past in all the other PTS cycles, which makes this whole process extremely frustrating and ungratifying.
Fair points, but the changes you're referencing are minor, cosmetic changes; and the community here, Facebook, Twitter, Reddit, game-magazine Forums, Streamers on Twitch and YouTube, etc., are all very unhappy and voicing their well-thought out and numbers-proven concerns over the blanket nerfs you're making to every area of Sustain and Cost Reduction in the game.ZOS_GinaBruno wrote: »To be fair, there have been changes in each PTS patch, but they aren't the changes you're looking for (sorry, had to get a #MayTheFourth joke in today somewhere). At the risk of regurgitating the same thing we've said before, we do care about your feedback, but keep in mind there's feedback coming from many different sources, some of which everyone here doesn't see (like in-game feedback, for example). Also, we need to take a look at what's best for the entire game and for its future. Your feedback isn't useless - we do read, and we do take everything into consideration.
ZOS_GinaBruno wrote: »To be fair, there have been changes in each PTS patch, but they aren't the changes you're looking for (sorry, had to get a #MayTheFourth joke in today somewhere). At the risk of regurgitating the same thing we've said before, we do care about your feedback, but keep in mind there's feedback coming from many different sources, some of which everyone here doesn't see (like in-game feedback, for example). Also, we need to take a look at what's best for the entire game and for its future. Your feedback isn't useless - we do read, and we do take everything into consideration.
ZOS_GinaBruno wrote: »Short answer is DKs likely won't be seeing a ton of changes before we go live; this class is still quite powerful (as it should be being a tank), even after some of the adjustments we've made to other classes and abilities.
ZOS_GinaBruno wrote: »To be fair, there have been changes in each PTS patch, but they aren't the changes you're looking for (sorry, had to get a #MayTheFourth joke in today somewhere). At the risk of regurgitating the same thing we've said before, we do care about your feedback, but keep in mind there's feedback coming from many different sources, some of which everyone here doesn't see (like in-game feedback, for example). Also, we need to take a look at what's best for the entire game and for its future. Your feedback isn't useless - we do read, and we do take everything into consideration.
They make changes, and state, that the goal is, to make sustain more difficult, so u cant run pure glasscannon anymore.
There is feedback, that u cant run pure glasscannon anymore, as u have to use heavyattacks and/or sustainset and/or drop dmgglyphs for sustain ones.
In my opinion, this is exactly the feedback they expected and wanted to hear.
tinbromide wrote: »Group Finder fixes?
Can you guys take a week off of nerfing my toons and fix the group finder?
@ZOS_GinaBruno There's been a lot of angst RE: the state of DK, specifically mDK. Last year, when there were similar concerns about the state of Stamina Sorcerer Wrobel did like a mini QA to provide the players with an idea of where he saw the class headed. Any chance we could get something similar on DK? I think some of our stress could be assuaged if we could at least see the direction Development has for this class.
@ZOS_GinaBruno There's been a lot of angst RE: the state of DK, specifically mDK. Last year, when there were similar concerns about the state of Stamina Sorcerer Wrobel did like a mini QA to provide the players with an idea of where he saw the class headed. Any chance we could get something similar on DK? I think some of our stress could be assuaged if we could at least see the direction Development has for this class.
Short answer is DKs likely won't be seeing a ton of changes before we go live; this class is still quite powerful (as it should be being a tank), even after some of the adjustments we've made to other classes and abilities.
@ZOS_GinaBruno There's been a lot of angst RE: the state of DK, specifically mDK. Last year, when there were similar concerns about the state of Stamina Sorcerer Wrobel did like a mini QA to provide the players with an idea of where he saw the class headed. Any chance we could get something similar on DK? I think some of our stress could be assuaged if we could at least see the direction Development has for this class.
We've made some fixes on the backend that should've made the Group Finder issues better on the PTS. Have you tried it out there versus what's currently on Live?tinbromide wrote: »Group Finder fixes?
Can you guys take a week off of nerfing my toons and fix the group finder?
ZOS_GinaBruno wrote: »Short answer is DKs likely won't be seeing a ton of changes before we go live; this class is still quite powerful (as it should be being a tank), even after some of the adjustments we've made to other classes and abilities.
ZOS_GinaBruno wrote: »We've made some fixes on the backend that should've made the Group Finder issues better on the PTS. Have you tried it out there versus what's currently on Live?
ZOS_GinaBruno wrote: »Short answer is DKs likely won't be seeing a ton of changes before we go live; this class is still quite powerful (as it should be being a tank), even after some of the adjustments we've made to other classes and abilities.
We've made some fixes on the backend that should've made the Group Finder issues better on the PTS. Have you tried it out there versus what's currently on Live?
ZOS_GinaBruno wrote: »Short answer is DKs likely won't be seeing a ton of changes before we go live; this class is still quite powerful (as it should be being a tank), even after some of the adjustments we've made to other classes and abilities.
PTS is not now, never was intended to be and never will be a vehicle for 11th hour drastic changes in the direction of the river. Those major course shifts were planned and decided way before pts. Anybody thinking the minute fraction of players participating in PTS (or the slightly not as minute fraction who follow the streamers, eso live, forums et al) are ever going to change the course of the river are just not being realistic.
That is not the same as saying your feedback isnt being heard.
ZOS_GinaBruno wrote: »Short answer is DKs likely won't be seeing a ton of changes before we go live; this class is still quite powerful (as it should be being a tank)