Nick McConnell - Things I've Learnt from Maintaining Angband

Overview

Nick McConnell, longtime Angband maintainer, gave a short talk about the history, community, design evolution, and practical lessons from maintaining Angband — a free open-source roguelike descended from UMoria.

History & context

• Angband is a descendant of UMoria. Development began around 1990–1993 and has been continuously developed since.
• During the 1990s the game grew through many ports and spawned a large ecosystem of variants. Maintainers often absorbed successful ideas from variants back into the main game.
• The project’s long history has produced diverse and sometimes conflicting expectations from players about what “the game should be.”

Gameplay highlights and player culture

• Angband is a deep permadeath roguelike featuring roughly a 100-level dungeon. Dying risks losing very long playtime.
• Traditional play style: ultraconservative, slow progress to avoid losing long-term characters.
• Emerging play style (since the mid-2000s): aggressive “diving” or speedier play — statistically more successful overall because players can run many short attempts instead of investing in one long, cautious game.
• Competitive play and speedrunning have long existed in the community; some competitions are judged by turn count (i.e., speedrun-style play).

Design changes and examples

• Long-lived mechanics can “degrade” or stop being interesting. Example: trap detection became so easy early in play that traps were effectively irrelevant.
• The trap system was completely reworked to make traps meaningful and interesting again.
• Variants and forks are common; the community is generally receptive to experimentation even when variants have bugs.

Practical lessons & strategies for maintainers and designers

• Expect and respect legacy baggage, but remember you can escape it by forking or introducing focused changes.
• Engage the community: discussion and playtesting drastically improve ideas.
• Release early and often: early playtesting produces useful feedback sooner rather than later.
• Avoid rabbit holes: prioritize shipping features and iterating instead of over‑polishing a single complex aspect.
• Be prepared for diverse player reactions — a long history creates many differing views about what is “right.”
• Use the community to test and refine controversial or large changes.

Release early and often; use community playtesting to iterate on design.

Other notes

• The Angband community and the broader roguelike community are strong, helpful, and enthusiastic.
• Interest in speedrunning has existed for a long time in Angband and hasn’t dramatically changed recent development.

Questions addressed

• What to change in a decade-old game? Update or rework mechanics that no longer function as intended (example: traps).
• Has Angband changed because of speedrunners? Not dramatically; competitive/turn-count play has long been part of the scene.

Gamers / sources featured

• Nick McConnell (speaker, Angband maintainer)
• EMCEE (conference host)
• Evan (questioner)
• UMoria (Angband ancestor)
• Angband team / Angband community
• Roguelike Celebration / roguelike community