[1.20] Request for Stickied Bug/Issue Reporting Log Thread

Brad/Derek - can you please throw up a stickied thread that tracks all the community reported items? It will help those of us who do take the time of reporting issues to know that they're heard and documented. I'd personally like to see:

  • Issue or bug
  • Working as designed Y/N
  • If N, it's in the queue and eta if possible

If we report something and feedback is it's working as designed, well we can stop reporting it as a bug and maybe have some dialogue around working as intended. If feedback is a bug, then we won't waste our time reporting it anymore (taking the time to save, zip, and throw the support up) because it's on the log.

4,073 views 13 replies
Reply #1 Top

Unfortunately, experience shows that people don't really tend to read such stickies.

Reply #2 Top

Quoting kryo, reply 1
Unfortunately, experience shows that people don't really tend to read such stickies.
End of kryo's quote

Fair enough. Fully admit I'm a noob to this process. However, I'm unsure if the sweet spot is to just throw a post up like "this is still happening in 1.20" vs. going through the process of providing detailed information.

[Edit] I guess confirmation would be nice. Just don't want to spend time documenting stuff that in the end is a waste of my time (or yours).

Reply #3 Top

I agree (and I would read it - but I guess it's not worth it to the devs if just 2 people read it) :grin:  

edit - I beta tested a civ iv mod that used that system and it was great. I liked knowing the status of the bugs I posted and checked it every day. Unfortunately, it didn't last long as they abandoned the mod shortly after - it was World of Civilization.

Reply #4 Top

But on the gripping hand, a proper sticky of known bugs helps us feel that issues aren't forgotten whey they dont get patched. 

Reply #5 Top

Quoting sjwt, reply 4
But on the gripping hand, a proper sticky of known bugs helps us feel that issues aren't forgotten whey they dont get patched. 
End of sjwt's quote

Yeah, that's where I was going with it. There are certain things I'd like to know are design issues vs. bugs (for example the city build tile issue). That could be a design intent (spawns of goodie huts) thus if I knew it was design, I could stop reporting it as a bug and report other things.

Reply #6 Top

I don't see why it should matter if most people don't read a sticky like that when it does help those who are really intersted in reporting and finding bugs. I mean, there should already be a list like this internally at Stardock and if not then it's high time they make one. And when such a list is done properly it's just a copy paste then to get it on the forums. (ofcourse I don't know how these things work in practice).

The people who don't read stickies most likely won't search the forum for posts reporting the same issue either so when there's a sticky you can just revere to that or more likely the regular forum posters can revere to it.

Reply #7 Top

I agree with Reinbad.  (Although I think he means "refer" rather than "revere". =)  Don't worry, easy mistake to make if English is not your first language. =))

Best regards,
Steven.

Reply #8 Top

Ah, good to catch that Steven, It does give the word quite a differrent meaning though

 

Reply #9 Top

I would also read any sticky or even in the devs area such a thread, as it would save ME some time posting and replying on threads with similar issues that I am having(simple concentration of information) and might even help the devs when checking for bugs as there would be an idea of the issues that they NEED to look at.

harpo

 

Reply #10 Top

Yes, I think the point of having a Stickied Bug/Issue Thread is to help the devs and the people who are providing useful feedback and logs/saves etc.  It will not magically make everyone look at the thread, but you could argue that the people who are going to the trouble of posting useful files and feedback and worth supporting.  So even if others don't look, they aren't reading most of the important threads and aren't helping the devs as much anyway.

Not many threads are read by everyone anyway, so to focus too much on the fact that a lot of people won't read it, is perhaps not the most beneficial for the Elemental devs, testers, modders and community as a whole. =)  Could the devs, on the basis of the reasoning of harpo99999's Reply #9, which sums up the case well, please consider a Stickied Bug/Issue Thread for each Elemental game?  I think it would be great in many ways. |-)

Best regards,
Steven.

Reply #11 Top

Just create the Great Demandabot Bugsquashing Thread.

Im sure AlLanMandragoran can keep this sufficiently high to make it easy to find just by posting his bug reports.

Reply #12 Top

Quoting RFHolloway, reply 11
Just create the Great Demandabot Bugsquashing Thread.

Im sure AlLanMandragoran can keep this sufficiently high to make it easy to find just by posting his bug reports.
End of RFHolloway's quote

ALM is a great demandabot threadkeeper but I want SD to own this thread so that we know our bugs, AI suggestions, etc., are being heard.  How many times have 4 or 5 of us reported the same bug for multiple releases?  Is SD not reading our threads?  Do they read them and not care?  Do they read them and can't recreate the bug so they just give up on it?  It would be nice if they tossed it into a known issues thread so that we at least know they're working on it.

Reply #13 Top
The way I see it is that maintaining the thread is work. If SD maintains it, they will need to divert effort from actual project work. I don't think they'll do it, and I'm not sure I'd want them to either. I suggest ALM create the thread.