Features To Do List

Bingehack4 has moved, for sanity's sake, as we often very selectively push changes to an upstream project (Nethack4), to using a GitHub-style workflow, where programmers fork ComputerScienceHouse/bingehack4 to themselves and make a pull request for integrating their changes.

Features To-Do List

Easy Difficulty

• Look at how achievements are implemented in bingehack and start adding hooks for them in BingeHack4.
• Better bedeck 'The Potter Level'; trees, different statues (removing the statues completely would make the game harder for wizarding folk), perhaps faux-elbereth'd landmines under dented pots in reference to explosive pot flying that occurs regularly at Potter parties? Or maybe ice-y water sections (similar Potter-party references).

Medium Difficulty

• Re-implement a live 'bingeboard' of the status of current games being played. We were considering doing this via adding additional PGSql logging during game turns, but other ideas can be entertained.
• Re-implement achievements database magic from bingehack in BingeHack4.
• Re-implement logging deaths to a database
  • Add hooks for bingehack twitter
• Look for open bugs in the issues tracker.
• When you see it, fix terrible source code formatting that NetHack 4 introduced with its tools. These should be targeted for our 'upstream' branch.

Advanced Difficulty