The Sugar Skull string lights not appearing in Odyssey cockpit has expired but issue still persists. This issue is easy to reproduce and can't be too difficult to resolve. Please investigate and resolve.
Sugar Skull String Lights Expired in Issue Tracker
- Thread starter Witcher 7
- Start date
Why - are you saying FDev is in denial (of issues) mode?
Deleted member 110222
D
Case in point:
webapp
issues.frontierstore.net
Do you really trust this community to vote for a bug that only serves to give players benefits?
The voting system was flawed from the start, and we as a community cannot be trusted to make wise decisions.
Top voted issues include "nothing to do on shuttle rides."
That is not even a bug. It is literally working as intended. It might be boring to some but it's not actually broken.
This community is focused on features before bugs, and when bugs happen to benefit them? Ha! No way do they vote on them.
Indeed. Voting for features and quality of life improvements, sure. Not a bad plan. Even limited votes in this regard isn't too bad.
Voting for bugs under the same conditions.. erm, No.
Bugs are bugs and should all be on some list somewhere, maintained internally, to be fixed at some point, based on Fdev's priorities.
Maybe they are, I mean.. sure, some things get changed / fixed without seemingly anybody mentioning and talking about it, but the way the issue tracker appears to work at the moment just doesn't make any sense at all for reporting things that are broken.
Voting for bugs under the same conditions.. erm, No.
Bugs are bugs and should all be on some list somewhere, maintained internally, to be fixed at some point, based on Fdev's priorities.
Maybe they are, I mean.. sure, some things get changed / fixed without seemingly anybody mentioning and talking about it, but the way the issue tracker appears to work at the moment just doesn't make any sense at all for reporting things that are broken.
Last edited:
The voting for bugs isn't really the problem - Frontier have rarely paid that much attention to the order. I've had several fixed that never got close to even two bars of votes ... while Megaship Piracy hung around at five bars for most of a year, and I still think the forum complaints were more use in getting it fixed quickly. As they're using votes now, as a way of picking bugs to tell us they're working on - that's probably a good use of it. (And even within the top 20, there's plenty lower down the list as "fixed in update 7" and some higher up they've said are "low priority")
The problem is the confirmation step [1]. You're not limited in the number of bugs you can confirm ... but each bug needing ten separate accounts to confirm it is a killer, especially for things which are definitely bugs, easy to reproduce in the right circumstances, but don't come up all that often. Even for "popular" bugs once duplicates are taken into account they probably need 30 people trying to report before a single copy gets to 10 confirmations, if there's no organised attempt to focus confirmations on a particular instance.
All of Frontier's other games require a much more reasonable 3 confirmations - still a bit annoying, but seriously, if 4 people (reporter+3) have said it's a bug, is requiring 10 actually doing anything but discouraging participation?
[1] That and the whole confirmations/votes/etc. thing just confusing everyone, since every single one of these threads has someone apologising that they can't confirm a bug in Confirming state because they've "run out of votes". Confirming doesn't cost votes, but clearly there's such a persistent and widespread misconception that it does that Frontier really need to communicate better in that area too.
The problem is the confirmation step [1]. You're not limited in the number of bugs you can confirm ... but each bug needing ten separate accounts to confirm it is a killer, especially for things which are definitely bugs, easy to reproduce in the right circumstances, but don't come up all that often. Even for "popular" bugs once duplicates are taken into account they probably need 30 people trying to report before a single copy gets to 10 confirmations, if there's no organised attempt to focus confirmations on a particular instance.
All of Frontier's other games require a much more reasonable 3 confirmations - still a bit annoying, but seriously, if 4 people (reporter+3) have said it's a bug, is requiring 10 actually doing anything but discouraging participation?
[1] That and the whole confirmations/votes/etc. thing just confusing everyone, since every single one of these threads has someone apologising that they can't confirm a bug in Confirming state because they've "run out of votes". Confirming doesn't cost votes, but clearly there's such a persistent and widespread misconception that it does that Frontier really need to communicate better in that area too.
I quit my volunteer bug hunting positions many Sun Earth orbits ago, so I wasn't even aware that "VOTING"?! was part of the bug removal process until I read this thread.
FD-
"These player-reported bugs are endless!"
"I've got an idea, lets put the onus of bug-triage on the players by having them vote on bugs, then we act on high voted bugs. We've already offloaded lots of BETA testing on them and got them to PAY us for that privilege!"
"If bugs get few or no votes, we can ignore those and the players can take the blame for their apathetic responses."
"Great idea, make it so, Number One, maximum warp on implementation!"
FD-
"These player-reported bugs are endless!"
"I've got an idea, lets put the onus of bug-triage on the players by having them vote on bugs, then we act on high voted bugs. We've already offloaded lots of BETA testing on them and got them to PAY us for that privilege!"
"If bugs get few or no votes, we can ignore those and the players can take the blame for their apathetic responses."
"Great idea, make it so, Number One, maximum warp on implementation!"
Last edited:
Key rulesI found this post:
I always thought voting and confirming would be the same. Can someone explain the differences to me and the different consequences of both?Elite Dangerous Issue Report - 10/08/2021
Thank you all very much for your continued work on EDO, and the open communication with the community. Problems With Lighting and Illumination Maybe it's just me and my VR headset but I wish we had a contrast adjustment. Sometimes it's difficult to read some of the ship panels due to high...forums.frontier.co.uk
Furthermore:
Can you vote without confirming?
Can you confirm without voting?
- Confirming is the most important thing to do to bugs. Much more important than voting, even more important than reporting.
- Duplicate bugs are the players' worst enemy.
- Voting is much less important and very rarely has any visible effect on fix prioritisation by Frontier.
- Bugs start in "Confirming" state. (circular icon)
- In this state, they need 10 "confirmations" to progress to the "Confirmed" state. A "confirmation" is a comment from a user on the bug which selects the "can reproduce" option. Comments which don't choose this option (it's not the default) don't count. Each confirmation must be from a separate account, and not the account of the original reporter.
- There is no limit to how many bugs you can add a comment to and set "can reproduce" on.
- Bugs in the confirming state cannot be voted on at all. So you can - and often must - confirm without voting, because confirmations are most necessary before voting is possible.
- Bugs which do not receive 10 confirmations in an unclear timescale (three months is documented, but not always observed) become "Expired" - and can no longer be confirmed. Bugs in this state which still apply must be re-reported and the process starts over again ... or you can create a forum thread like this one and hope a Community Manager sees it, which is probably more productive.
- Frontier staff can move a bug to "Confirmed" state regardless of its confirmation count, if they feel like it.
- If you're playing a game which is not Elite Dangerous, only three confirmations are needed to get to Confirmed. This is far more reasonable.
- Once in "Confirmed" state, the bug gets the little "triangle of votes" by it as its icon
- It can still receive further confirmations at this point, but there's no benefit to doing so except to add extra information to the bug.
- Usually a Frontier QA employee will set it to "Acknowledged" within a working day or so (green tick added to icon) - this means that it has been transferred from the bug tracker to the Internal Real Bug Tracker Of Bugs Frontier Actually Knows About.
- At this stage, the bug can be voted on. There is the infamous limit of six votes.
- You do not have to have previously confirmed the bug (or added any comment to it at all) to be able to vote on it. Most voters - because they'll only see the bug after it's confirmed - won't have confirmed it.
- The more votes a bug gets, the more lines are filled in on the triangles icon (it looks from the recent news post that 100 votes gets you 4/5 bars, and 150 votes gets you 5/5 bars). You can sort by "top voted" to get a finer ordering within each bar.
- The number of bars a bug has doesn't usually do anything - remember, this isn't the bug tracker that Frontier use internally, so the devs won't know how many votes a bug has unless they go and look, and because the Acknowledged state occurs so quickly, they're probably almost all at one bar at that point.
- But vote if it makes you feel happier anyway. The top 20 bugs do get a personalised progress update now, so that's something.
- Because of this, duplicate reports are really dangerous. If there are six duplicate reports of an issue, all attracting confirmations, the bug can have been reported well over ten times before any individual report gets ten confirmations.
- When adding confirmations, make sure you add to the report with the most existing ones.
- Add a "report as a duplicate of" to the other issues and paste the URL of the real one. Frontier QA staff will then put those into "Duplicate" status which stops them taking confirmations away from the strongest issue.
- Make sure you don't report a bug - no, no matter what that nice Community Manager says! - until you've searched the bug tracker on every keyword you can think of and are absolutely convinced it's not already there.
- Remember those Powerplayers who complain about casual supporters and module hunters doing the obvious action and trashing their own power because all obvious actions are harmful in Powerplay? Take that mindset into the bug tracker.
- Sometimes bugs are fixed.
- Some time after that, Frontier QA staff will remember that they should mark them as "Fixed" in this bug tracker as well as the Real Internal One, and their icon will turn green. At this point no further confirmations or votes are possible.
- If they mark a bug as fixed and it isn't actually fixed, your options are either to start the reporting process all over again, or try to flag down a passing Community Manager and ask them what's going on.
Deleted member 110222
D
It's certainly possible in a technical sense.
Personally, for intermittent bugs it can be very useful to know when they don't occur as well as when they do, so I'd definitely encourage you to confirm bugs which only happen to you intermittently.
So Issues Tracker is more like a suggestion box based on number of votes to appease the majority of what they want - disappointing to say the least.
This also the reason why some bugs reported during alpha or beta phase are not resolved whilst majority of votes for new features are developed and new issues introduced? Tis sad real and simple bugs with less than 7 or 10 votes don't even get looked at
This also the reason why some bugs reported during alpha or beta phase are not resolved whilst majority of votes for new features are developed and new issues introduced? Tis sad real and simple bugs with less than 7 or 10 votes don't even get looked at
Deleted member 110222
D
Basically.So Issues Tracker is more like a suggestion box based on number of votes to appease the majority of what they want - disappointing to say the least.
This also the reason why some bugs reported during alpha or beta phase are not resolved whilst majority of votes for new features are developed and new issues introduced? Tis sad real and simple bugs with less than 7 or 10 votes don't even get looked at
That is why it is such a stupid system.