I'm very interested in how critical a bug must be to make a hot fix for it. Some bugs are not critical and will be fixed with scheduled updates. And other little things are not fixed sometimes for years in this game.
So I had a question. Characters below level 50 using a group tool and getting into groups passing veteran dungeons don't deserve a hot fix? This bug has just existed since the last major patch. It still hasn't been fixed. Hello, are the developers generally aware of this?
They are aware of this bug. However no fix yet.
So its not an trivial bug to fix as in some obvious error.
Its an reason why groupfinder is called bugfinder.
I'm very interested in how critical a bug must be to make a hot fix for it. Some bugs are not critical and will be fixed with scheduled updates. And other little things are not fixed sometimes for years in this game.
So I had a question. Characters below level 50 using a group tool and getting into groups passing veteran dungeons don't deserve a hot fix? This bug has just existed since the last major patch. It still hasn't been fixed. Hello, are the developers generally aware of this?
I feel like this falls under the annoying but not too serious category and therefore might be lower down the list of priorities than other things.
Plus I think they have a lot on their plates at the moment what the patch coming out and all the PVP tests done recently.
I wouldn't worry about it too much if I were you. By the time it's fixed your character will probably be CP level anyway and it won't affect you.
I'm very interested in how critical a bug must be to make a hot fix for it.
They are aware of this bug. However no fix yet.
So its not an trivial bug to fix as in some obvious error.
Its an reason why groupfinder is called bugfinder.
I almost get the feeling that whoever gets the Group Finder story assigned to them starts looking for a new job. That thing must be one hell of a poison chalice in their backlog.
We had a similar problem with a specific piece of business logic of a feature in an application we delivered; no one could fix it , not in 8 years. All we had were a handful of ideas and passable workarounds, and no time to rebuild the entire component from scratch. I feel for them on this in some ways, but honestly, we've got to the point where bug fixes and bandaids don't appear to work, and its quickly becoming a game of whack-a-mole. Maybe the GF just needs to be redesigned from the ground up?
I'm very interested in how critical a bug must be to make a hot fix for it.
Is it a bug for crown store? yes -> hotfix in a hour or two
Is it a bug making people unable to access some part of the game? -> fix in same or next day
Is it a bug breaking some major game functions? -> fix in a week or two (next maintenance)
Is it a bug impairing some functionality for many but not all player? -> possible fix in a month or two
Is it a bug affecting performance or non function breaking bug? -> possible acknowledgement in a month or two, fix maybe in a year or so
They are aware of this bug. However no fix yet.
So its not an trivial bug to fix as in some obvious error.
Its an reason why groupfinder is called bugfinder.
I almost get the feeling that whoever gets the Group Finder story assigned to them starts looking for a new job. That thing must be one hell of a poison chalice in their backlog.
We had a similar problem with a specific piece of business logic of a feature in an application we delivered; no one could fix it , not in 8 years. All we had were a handful of ideas and passable workarounds, and no time to rebuild the entire component from scratch. I feel for them on this in some ways, but honestly, we've got to the point where bug fixes and bandaids don't appear to work, and its quickly becoming a game of whack-a-mole. Maybe the GF just needs to be redesigned from the ground up?
They have redesigned it from the ground up. It used to work way worse - you may remember the "someone declined" times, and the cancelled Undaunted events, and all that stuff.
After that, they revamped the thing, and it worked decently for a while (and still does, generally speaking).
This bug with people getting into the wrong difficulty is a new one, introduced around the time when the Bugmoor dropped, so it may be buried somewhere in the dumpster fire that were the Greymoor launch issues.
This, now as I understand its two variations of it, says its vet and don't allow <50 in, then inside its normal. This also affect < cp 300 in normal dlc.Fixing bugs isn't just about whether they're critical or trivial. It's also about the team being able to recreate the bugs so they can diagnose them and work out a fix - which then has to be tested extensively so as not to break something else in the process. Moreover, it also depends on whether it is literally game-breaking or merely inconvenient, and how consistent it is as well as how many players it affects. Your best bet on any particular bug is to follow/contribute to the Bug Reports forum.
From Monday randoms also give 10 transmute crystals so this will be much more of an issue as all the 810 who don't do PvP will start running random normals.
They are aware of this bug. However no fix yet.
So its not an trivial bug to fix as in some obvious error.
Its an reason why groupfinder is called bugfinder.
I almost get the feeling that whoever gets the Group Finder story assigned to them starts looking for a new job. That thing must be one hell of a poison chalice in their backlog.
We had a similar problem with a specific piece of business logic of a feature in an application we delivered; no one could fix it , not in 8 years. All we had were a handful of ideas and passable workarounds, and no time to rebuild the entire component from scratch. I feel for them on this in some ways, but honestly, we've got to the point where bug fixes and bandaids don't appear to work, and its quickly becoming a game of whack-a-mole. Maybe the GF just needs to be redesigned from the ground up?
They have redesigned it from the ground up. It used to work way worse - you may remember the "someone declined" times, and the cancelled Undaunted events, and all that stuff.
After that, they revamped the thing, and it worked decently for a while (and still does, generally speaking).
This bug with people getting into the wrong difficulty is a new one, introduced around the time when the Bugmoor dropped, so it may be buried somewhere in the dumpster fire that were the Greymoor launch issues.
They didn't redesign it, they just changed the error message which was often wrong to begin with. Often it would state someone declined when really the issue was that a new instance couldn't be spawned. They didn't change the queue that much but tweaked how the instances connected to it. Its not a new queue system we have at all. And that's the point I'm making. They keep 'fixing' things around the queue, and fiddling with things in the queue and what we get as a result are a variety of behavioural kinks and quirks.
They are aware of this bug. However no fix yet.
So its not an trivial bug to fix as in some obvious error.
Its an reason why groupfinder is called bugfinder.
I almost get the feeling that whoever gets the Group Finder story assigned to them starts looking for a new job. That thing must be one hell of a poison chalice in their backlog.
We had a similar problem with a specific piece of business logic of a feature in an application we delivered; no one could fix it , not in 8 years. All we had were a handful of ideas and passable workarounds, and no time to rebuild the entire component from scratch. I feel for them on this in some ways, but honestly, we've got to the point where bug fixes and bandaids don't appear to work, and its quickly becoming a game of whack-a-mole. Maybe the GF just needs to be redesigned from the ground up?
They have redesigned it from the ground up. It used to work way worse - you may remember the "someone declined" times, and the cancelled Undaunted events, and all that stuff.
After that, they revamped the thing, and it worked decently for a while (and still does, generally speaking).
This bug with people getting into the wrong difficulty is a new one, introduced around the time when the Bugmoor dropped, so it may be buried somewhere in the dumpster fire that were the Greymoor launch issues.
They didn't redesign it, they just changed the error message which was often wrong to begin with. Often it would state someone declined when really the issue was that a new instance couldn't be spawned. They didn't change the queue that much but tweaked how the instances connected to it. Its not a new queue system we have at all. And that's the point I'm making. They keep 'fixing' things around the queue, and fiddling with things in the queue and what we get as a result are a variety of behavioural kinks and quirks.
They completely replaced the activity finder. https://forums.elderscrollsonline.com/en/discussion/503224/activity-finder-server-performance-update
Or that was a lie.