Help reproducing bugs

Breakable · Post by **Breakable** » Tue Apr 01, 2008 5:03 pm

Hello Everyone,
Please help clean up the bug tracker. I think its a good idea to do it before the release, and I hope this is the kind of initiative developers would appreciate (This could bring the release closer!). I am not able to do much myself, as I just don't have enough knowledge about vs and reading all posts beginning from 2003 would take too much time.

I see that there is some old open bugs in tracker, most of them seem like fixed to me, but i cant be sure, as there is no way described to reproduce them, and no way to know if this functionality was intended. For example:
http://sourceforge.net/tracker/index.ph ... tid=119507
Seems like intended functionality. Is it?

http://sourceforge.net/tracker/index.ph ... tid=119507
Seems really old, is it fixed. Any easy way to reproduce it?

So please help:
http://sourceforge.net/tracker/?group_i ... tid=119507

1)Try to reproduce, if not reproduced mark as closed (or just comment), if reproduced describe how to do it and add a save file if it helps.
2)Close it if the functionality was intended.If the functionality was not intended, comment on it.

bgaskey · Post by **bgaskey** » Tue Apr 01, 2008 9:23 pm

first one is intended afaik. second not so much, but it may be fixed. I'll help out if I have any free time

Post by **jackS** » Fri Apr 04, 2008 12:01 am

Just wanted to preemptively thank everyone who helps out trying to reproduce these bugs -- it's really helpful for the devs to have detailed accounts of which bugs are actually reproducible. Heisenbugs may be real, but they're rarely worth the time to hunt down. Reproducible (Bohr) bugs, however, are much better prey, if the mechanism for reproducing them is well documented.

Re: two above bugs in particular -- the Basic repair functionality is not as intended, but may be very difficult to fix without a number of invasive changes to other parts of the codebase.

The turret bug is likewise still present. It took us a long time to come across a savegame that actually displayed the bug in question, and we were able to locate the cause of the problem, but do not have a solution we're particularly happy with, and have thus not implemented a fix yet.