= NetHack 4 Bug Tracker =

Welcome to the bug tracker for NetHack 4, a branch of the popular game NetHack.

= Filing Guidelines =

== Type ==

A ticket should be a '''pull request''' if it is a request to pull some feature/bugfix already implemented in some fork of NetHack.

== Priority ==

Generally, the following guidelines should be used:

 * '''blocker''': It would be impossible to release the game without resolving the ticket. An example includes a crash on startup, or something making ascension impossible.
 * '''critical''': The ticket should be fixed if at all possible since it will severely impact the enjoyability or balance of the game. Examples include crashes, or the save system not working well.
 * '''major''': The ticket impacts enjoyability or balance, but not so much as to damage playability. Examples include a section of the game that can be bypassed, or significant interface issues.
 * '''minor''': The ticket is something that would be nice to fix, but is not a serious burden on users. Examples include small interface quirks or an item being strictly better than another.
 * '''trivial''': This bug is purely cosmetic or otherwise does not make a significant differences. Examples include typos or requests for new YAFMs.

== Severity ==

This represents how much effort resolving the ticket would be:
 * '''unknown''': Unknown effort.
 * '''easy''': A straightforward change; a few minutes at most.
 * '''difficult''': A more complex change, possibly touching a few components.
 * '''refactor''': Requires a rewrite of a major subsystem.

== Confirming Tickets ==

A ticket should only be confirmed when a reproduction is available. Simply having many users report the bug is insufficient. A reproduction should be instructions to reproduce the bug, possibly with an attached save.