User:Bulwersator/UnNetHackPlus bug tracking

From NetHackWiki
< User:Bulwersator
Revision as of 22:08, 21 March 2013 by Bulwersator (talk | contribs) (reset)
Jump to navigation Jump to search

Like other NetHack variants, UnNetHackPlus has bugs. This page tracks the status of the Bugs in NetHack 3.4.3 in UnNetHackPlus, (new bugs introduced in NetHack 4 are tracked at https://github.com/Bulwersator/UnNetHackPlus/issues and UnNetHack bugs at http://sourceforge.net/apps/trac/unnethack/report/1).

Special thanks to everyone who helped to compile this list.

UnNetHackPlus's developer would appreciate feedback on these bugs, especially the ones marked as "Unclear" (if anyone knows what these bug reports mean, please let us know!), and the ones marked as "Unknown" (where typically nobody knows what to do to reproduce the bug).

Key:

  • Fixed: The bug existed in UnNetHack or UnNetHackPlus and was fixed.
  • Incidentally Fix available: The bug was Fix available due to unrelated changes made in UnNetHackPlus.
  • Fix available: The bug has a fix available for it in some other variant, but that fix has not yet been merged into UnNetHackPlus.
  • Confirmed: The bug has been reproduced in UnNetHackPlus (typically with a save file recorded for it).
  • Moot: The bug's context no longer exists in UnNetHackPlus.
  • Info available: The cause of the bug has been explained for NetHack 3.4.3 on this wiki, and thus further investigation was not worthwhile.
  • Debatable: There is some doubt as to whether this is a bug, or about whether it would be reasonable to fix it.
  • Not a bug: Not a bug, but may be considered as one.
  • Unclear: It is not clear what the bug description refers to.
  • Unknown: The bug has not been reproduced in UnNetHackPlus, but may well still exist.
  • Untested: An explanation has been proposed (typically, as a result of looking at the source), but the bug has not actually been reproduced in UnNetHackPlus.