Stop pushing fixes to live if they are rubberbanding
zvavi
✭✭✭✭✭
✭✭✭✭✭
✭✭✭✭✭
Small background story:
This poll is against rubberbanding, pushing "fixes" to live that do not fix the original issue, but only create new bugs (and performance issues), sometimes minor, sometimes major.
I see no point in pushing fixes like that to live, because people work on the same bug 5 times, instead of working 1 time 3 times as long. (heck, it wont even take 3 times as long, only identifying the real bug shouldn't take as much as a rubberband, especially in the case above because people reported exactly what the original bug was very accurately).
Edited by zvavi on November 23, 2020 10:38AM lets take the recent group finder bugs as a reference.
group finder had a bug. that it would auto change the role of yourself to normal (affecting essentially those that queue for vet), even when you are doing exclusively vet content. Instead of fixing it, they have changed group finder, to auto register any cp player into the vet role, no matter what dungeon he gets into, normal included. This created a new bug. The one we know of low level characters not being able to join a normal dungeon, in a normal instance, but since group leader when group was queued was forced into vet role, all the low level characters werent able to join a normal instance, blocked by "group" setting. now instead of fixing that, they have meddled with the group finder grouping itself. creating longer than expected queue times for all normal dungeons.
group finder had a bug. that it would auto change the role of yourself to normal (affecting essentially those that queue for vet), even when you are doing exclusively vet content. Instead of fixing it, they have changed group finder, to auto register any cp player into the vet role, no matter what dungeon he gets into, normal included. This created a new bug. The one we know of low level characters not being able to join a normal dungeon, in a normal instance, but since group leader when group was queued was forced into vet role, all the low level characters werent able to join a normal instance, blocked by "group" setting. now instead of fixing that, they have meddled with the group finder grouping itself. creating longer than expected queue times for all normal dungeons.
This poll is against rubberbanding, pushing "fixes" to live that do not fix the original issue, but only create new bugs (and performance issues), sometimes minor, sometimes major.
I see no point in pushing fixes like that to live, because people work on the same bug 5 times, instead of working 1 time 3 times as long. (heck, it wont even take 3 times as long, only identifying the real bug shouldn't take as much as a rubberband, especially in the case above because people reported exactly what the original bug was very accurately).
Stop pushing fixes to live if they are rubberbanding 28 votes
Yes, stop sending rubberbanding fixes to live.
60%
17 votes
No, rubberbanding fixes are fine as long as they fix major issues, without creating new major issues (minor issues and small performance hits are fine)
21%
6 votes
No, rubberbanding fixes usually fix it without creating new bugs.
0%
Other.
17%
5 votes
0
-
Jaraal✭✭✭✭✭
✭✭✭✭✭ZOS has their vision and spreadsheets. They will do whatever they are gonna do and how the players feel about it is irrelevant.
The ratio of unwelcome to welcome (by players) changes is running about 10 to 1. Don't look for that number to change any time soon.4 -
zvavi✭✭✭✭✭
✭✭✭✭✭ZOS has their vision and spreadsheets. They will do whatever they are gonna do and how the players feel about it is irrelevant.
The ratio of unwelcome to welcome (by players) changes is running about 10 to 1. Don't look for that number to change any time soon.
i mean, regardless of balance issues this post is about bugs... spreadsheets and vision has nothing to do with it
0 -
NEMESIS_97✭✭✭No, rubberbanding fixes are fine as long as they fix major issues, without creating new major issues (minor issues and small performance hits are fine)Like la fix..its welcome fix asap with possible broke other things is fine..ofc if that fix wont make critical major issues to other things0
-
magnusthorek✭✭✭✭✭
✭No, rubberbanding fixes are fine as long as they fix major issues, without creating new major issues (minor issues and small performance hits are fine)"50% of something is better than 100% of nothing" ;-)I am the very model of a scientist Salarian, I've studied species Turian, Asari, and Batarian.
I'm quite good at genetics (as a subset of biology) because I am an expert (which I know is a tautology).
My xenoscience studies range from urban to agrarian, I am the very model of a Scientist Salarian.0 -
zvavi✭✭✭✭✭
✭✭✭✭✭magnusthorek wrote: »"50% of something is better than 100% of nothing" ;-)
well, if u didn't read the background story, sometimes the original bugs are the minor ones
also #this patch0 -
twev✭✭✭✭✭
✭✭magnusthorek wrote: »"50% of something is better than 100% of nothing" ;-)
If is was only 50% of the stuff getting fixed and 50% adding no difference- you'd be correct.
But you left out the part about the other 50% being a combination of nothing and breaking more stuff.
Sometimes it's been more than 50% new broken stuff, which leaves you with more broken than fixed, and also begs the question about why the original patch adding content was released so broken to begin with.
Edited by twev on November 23, 2020 10:58PMThe problem with society these days is that no one drinks from the skulls of their enemies anymore.0 -
jircris11✭✭✭✭✭
✭Other.Small background story:lets take the recent group finder bugs as a reference.
group finder had a bug. that it would auto change the role of yourself to normal (affecting essentially those that queue for vet), even when you are doing exclusively vet content. Instead of fixing it, they have changed group finder, to auto register any cp player into the vet role, no matter what dungeon he gets into, normal included. This created a new bug. The one we know of low level characters not being able to join a normal dungeon, in a normal instance, but since group leader when group was queued was forced into vet role, all the low level characters werent able to join a normal instance, blocked by "group" setting. now instead of fixing that, they have meddled with the group finder grouping itself. creating longer than expected queue times for all normal dungeons.
This poll is against rubberbanding, pushing "fixes" to live that do not fix the original issue, but only create new bugs (and performance issues), sometimes minor, sometimes major.
I see no point in pushing fixes like that to live, because people work on the same bug 5 times, instead of working 1 time 3 times as long. (heck, it wont even take 3 times as long, only identifying the real bug shouldn't take as much as a rubberband, especially in the case above because people reported exactly what the original bug was very accurately).
Issue with pts us that it's no where near as populated as live. Thus there are millions of variables that can change how a patch acts and works.IGN: Ki'rah
Khajiit/Vampire
DC/AD faction/NA server.
RPer0 -
zvavi✭✭✭✭✭
✭✭✭✭✭Small background story:lets take the recent group finder bugs as a reference.
group finder had a bug. that it would auto change the role of yourself to normal (affecting essentially those that queue for vet), even when you are doing exclusively vet content. Instead of fixing it, they have changed group finder, to auto register any cp player into the vet role, no matter what dungeon he gets into, normal included. This created a new bug. The one we know of low level characters not being able to join a normal dungeon, in a normal instance, but since group leader when group was queued was forced into vet role, all the low level characters werent able to join a normal instance, blocked by "group" setting. now instead of fixing that, they have meddled with the group finder grouping itself. creating longer than expected queue times for all normal dungeons.
This poll is against rubberbanding, pushing "fixes" to live that do not fix the original issue, but only create new bugs (and performance issues), sometimes minor, sometimes major.
I see no point in pushing fixes like that to live, because people work on the same bug 5 times, instead of working 1 time 3 times as long. (heck, it wont even take 3 times as long, only identifying the real bug shouldn't take as much as a rubberband, especially in the case above because people reported exactly what the original bug was very accurately).
Issue with pts us that it's no where near as populated as live. Thus there are millions of variables that can change how a patch acts and works.
PTS reported crashes. PTS reported not working skills. PTS reported not working boss daily. PTS reported falling of the map. PTS reported teleporting to beginning of trial. PTS reported brittle is bugged. PTS reported light attacks gimping skill animations. PTS reported some skills locking your skillbars.
All the bugs reported on week 1 of pts, went live. All of them. PTS is not the issue.
You are right though. If stuff are crashing on pts, it will be different on live. More things will crash cause load is bigger and more variables.2