Version 25 (modified by noz, 9 years ago) (diff)


Who's where in the angband codebase

This page has been created as a guide to which active (or semi-active) developers have extensive knowledge of which sections of code and where they can most easily/quickly be contacted. For a list of tickets they're each working on, click here.

It's worth noting that takkaria, magnate and d_m are currently the only developers who can pull changes into Angband (although all devs can fork and make pull-requests).


Maintainer-of-sorts. Knows most things about the code, likes fiddling with everything. Originally took on the game to do refactoring and UI work more than anything else, though. Current priorities:

  1. finishing refactoring menu API and moving remaining menus to it
  2. rewrite of the input layer (InputRework)

Contactable on #angband-dev on IRC, or the angband-dev mailing list. Their list of assigned tickets is here.


Maintainer of the Debian package. Author of randart.c and obj-power.c, also usefully familiar with (in descending order):

  • multiple pval handling (#571)
  • object knowledge stuff (obj-info.c plus bits of cmd-know.c, obj-util.c etc.)
  • game init
  • combat (attack.c, monster/*)
  • identify.c / stores.c / effects.c / randname.c

Usually contactable on #angband-dev, or the angband-dev mailing list.


Wrote the original item list. Heavily involved in the curses (GCU) code, as well as colors/flickering. Introduced the quiver to V. Fixes bugs. Kind of random. Future directions of interest:

  • better distance/LOS/FOV
  • better dungeon generation/vaults/terrain
  • better monster/drop flags
  • more interesting consumables, more hunger, more pain and suffering
  • add unicode support to GCU
  • (maybe) try to fix the GTK port, or kill it
  • (maybe) try to fix tiles for linux
  • update help files/documentation/in-game help

Mostly idles on #angband-dev (as d_m), and reads oook pretty regularly (as d_m). Also has an email address


Author of the much improved monster recall, working on improving the monster and object lists. Sometimes available on #angband-dev, and checks the forum regularly. (as of December, 2010 we haven't seen MarbleDice for awhile...)


Working on object and monster stats generation. Usually watching or idling on #angband-dev, and reading the forum.


Resident crazy person. Enjoys refactoring and code cleanup far too much; has no aspirations towards gameplay changes. Responsible for refactoring, internal API redesigns, and testing. elly on freenode, or in #angband-dev. Todo:

  1. Finish merging all my changes into staging.
  2. Solidify the object and object_kind APIs; test them.
  3. Start using {sp,}lint regularly on the codebase and see what they turn up.
  4. Look at making the build system less... amazing.
  5. Valgrind all day, every day.
  6. Pointers instead of indices. The extra layer of indirection makes testing less fun.




General bug-fixing and debugging. Now know quite a bit about the UI abstraction, menus, stores, and ID. Co-wrote the fractional blows change, and most recently converted trunk to UTF-8 clean edit files and wide chars internally. Usually contactable on #angband-dev. Have won only the once!