Roadmap

• Look at game difficulty more (DifficultGame)
• takkaria's plans:
  • move to frontends using graphics surfaces instead of terminal emulators (NextUi)
  • All menus using the new menu API
  • Significantly better split between the core game code and the text UI (CoreUiSplit)
  • New curses

The inevitable bugfix release for 3.4.0

This milestone refers to the "v4" fork of the game, which contains many changes which may or may not end up in the mainline (3.x) releases. It has no scheduled release date, and is likely to remain in long-term development. These changes may or may not include:

• sort out the LOS/FOV/projection mess (#757, #768)
• monster flow/AI/detection (#78, #300, #574, #591, #963, #1113, #1433), including importing elements of 4GAI
• rework armour effects on attacks (#1205)
• other combat changes (#1279, #1436, #1437)
• detection changes (#298, #418, #509, #1015, #1161, #1408, #1450)
• reworked magic (#1421 and implications for classes/skills)
• more changes to dungeon generation (room types, traps, terrain)
• changes to stores (maybe dungeon stores)
• rebalancing/redistributing monsters (#443, #488, #595, #1492)
• ego monsters
• new cursed items with quest-like connotations
• changes to races and classes (#594, #1024, #1298)
• any other tickets appearing on the DifficultGame page

Intended changes by owner:

• magnate
  • continuous improvements to affixes (#1233, #1562, #1567, #1569, #1600, #1627)
  • tiered effects (#1041)
  • affix-based randarts (#1006, #1045, #1407, #1442, #1448)
  • further improve monster power (#869, #334) (happy if someone else wants this)
  • further improve obj-power.c (#1003)
  • further refactoring (#1403, #726, #1124, #1437)
• d_m
• fizzix
• noz
• GabeCunningham
• takkaria
• myshkin
  • Stats improvements (#776, #1476, ...)

This milestone is used for any tickets which are long-term aspirations not yet scheduled for a particular release. Any non-bug tickets without owners should be set to this milestone when they are triaged/confirmed.

This milestone is the default, and is used for all new tickets of all types. When triaged by a developer, the ticket is either confirmed and assigned a new milestone, or closed as an unreproducible bug or an undesired change.

Tickets which are eventually closed as "invalid", "duplicate", "wontfix" or "worksforme" should have their milestone re-set to Triage to avoid them contaminating reports of tickets actually fixed for a real milestone.