@hackage LambdaHack0.9.3.1

A game engine library for tactical squad ASCII roguelike dungeon crawlers

  • Installation

  • Tested Compilers

  • Dependencies (36)

  • Dependents (3)

    @hackage/SpacePrivateers, @hackage/acme-everything, @hackage/Allure
  • Package Flags

      vty
       (off by default)

      switch to the vty frontend (screen reader friendly)

      curses
       (off by default)

      switch to the curses frontend (not fully supported)

      gtk
       (off by default)

      switch to the GTK frontend (not fully supported)

      sdl
       (off by default)

      switch to the SDL2 frontend

      jsaddle
       (off by default)

      switch to the JSaddle frontend (may be bit-rotted)

      with_expensive_assertions
       (off by default)

      turn on expensive assertions of well-tested code

      release
       (on by default)

      prepare for a release (expose internal functions and types, etc.)

      supportnodejs
       (on by default)

      compile so that the JS blob works in terminal with NodeJS

LambdaHack is a Haskell game engine library for ASCII roguelike games of arbitrary theme, size and complexity, with optional tactical squad combat. It's packaged together with a sample dungeon crawler in fantasy setting that can be tried out in the browser at http://lambdahack.github.io. (It runs fastest on Chrome. Keyboard commands and savefiles are supported only on recent enough versions of browsers. Mouse should work everywhere.)

Please see the changelog file for recent improvements and the issue tracker for short-term plans. Long term goals include multiplayer tactical squad combat, in-game content creation, auto-balancing and persistent content modification based on player behaviour. Contributions are welcome.

Games known to use the LambdaHack library:

Note: All modules in this library are kept visible, to let games override and reuse them. OTOH, to reflect that some modules are implementation details relative to others, the source code adheres to the following convention. If a module has the same name as a directory, the module is the exclusive interface to the directory. No references to the modules in the directory are allowed except from the interface module. This policy is only binding when developing the library --- library users are free to access any modules, since the library authors are in no position to guess their particular needs.

This is a workaround .cabal file, flattened to eliminated internal libraries until generating haddocks for them is fixed. The original .cabal file is stored in the github repo.