#Known Bugs Thread

1 messages · Page 1 of 1 (latest)

uneven kestrel
#

It would be great to have a "known bugs" channel where all the reported and recorded bugs are listed.

When I find a bug or glitch, especially now in the later stages of playtesting a patch, it feels like reporting it would not benefit much, since it has most likely been reported already.

I think a channel to list all the "reported bugs / known bugs that need to be reproduced or need more samples" would help people a lot who want to actively playtest to find stuff that has not been found and reproduced yet.

This could lower the "spam" for the reports in order to maximize efficiency in this department.

#

Known Bugs Thread

tight oracle
#

good quality of life improvement for many teammembers, mods and people can check and maybe use "fun" bugs while possible
I like the idea

floral dove
#

@restive wadi @stone rampart can we do a channel like this one?

unique gull
#

Simple and helpful idea.

abstract yarrow
#

Some counterpoints:

Reporting frequency is an important metric for tracking the occurrence rates and root causes of bugs. Knowing that a bug is known may reduce report rates, lowering the accuracy of data.

There may be situations where it's not desirable to communicate publicly about bugs as well.

For bugs that are:

  1. Not extremely detrimental to the player base,
    and
  2. Are well understood in terms of cause and frequency

I don't see any reason to not make it public that they are known and that fixes are planned.

viral vortex
#

I’m open to the idea. I would like the team to weigh in and let us know under which situations receiving multiple bug reports is helpful. The efficiency question is a good one and I expect the team can judge that for us (I.e. better to spend time making this process fully public vs the extra time to see multiple reports of the same bug).

frozen willow
small wyvern
abstract yarrow
frail hawk
# uneven kestrel It would be great to have a "known bugs" channel where all the reported and reco...

I agree with this for the most part however we don't want to deter people from repeat reporting bugs. Like blickter said we'd have to defer to the team but it's my understanding that repeat reports are extremely helpful. They help you eliminate possibilities as your dataset grows. Things like specific gpus or hardware setups. Mac vs pc and so on. The more instances you have and ways people replicate it and bug report logs are sent the easier it is to get out the bug spray so to speak.

However a list of known bugs is very beneficial to the community. I think this should be to the teams discretion tho. Eg if Johnny said 'we 100% know how to fix this bug' and then he can post it in the report to help prevent repeat posts and give the community clarity and peace of mind

small wyvern
unkempt canopy
#

I'm also afraid this would make people report bugs less frequent

restive wadi
#

Yeah, the system we have now, which we are trying to push more people directly to support because once a ticket is created we can track how many people are experiencing these bugs. That is then directly seen by QA/Dev team and they can determine priority and how bad a bug is thus pushing it up the list if its affecting a large group of people. So its honestly best for people to keep reporting these through our direct support on ZenDesk. @stone rampart setup this amazing system to help all the teams involved so its best we push people to use it as well.