Cabal

this project has a couple of goals:

1. break lich into groups of files
2. prune deadcode
3. create a way forward for development
4. provide a bin gem
5. use more gems to do the heavy lifting instead of own-rolled code

My previous attempts at a complete rewrite have been seriously hampered by MapDB's absolute necessity to navigate the game world in a reasonable manner, and the fact than any Lich API can be called within it. Without a way to isolate and refactor we will never be able to improve.

backwards compatibility with all systems and features is not a design goal

Differences Between Cabal & Lich

1. the Script class is a true Thread object
2. Script.run returns a handle to the Script instance
3. scripts have exit_codes like processes in *nix environments
4. scripts use significantly fewer threads (has taken my average playing session from 30% memory usage to 18%)
5. scripts are currently not "pausable"
6. significantly fewer tight loops
7. wait_while accepts a timeout: keyword
8. wait_until accepts a timeout: keyword
9. ;autostart can optionally use YAML to spin up supervisor trees

Autostart

;autostart is brittle for a variety of advanced use cases (like a Supervisor tree), but still supported unless a autostart/ directory is added to your cabal (lich) folder.

When an autostart/ directory is present, it instead uses YAML.

my autostart/ dir for example:

autostart/
├── _global.yaml
├── ondreian.yaml
├── pixelia.yaml
└── szan.yaml

_global.yaml is a special file that runs before character specific files, it's service-friendly (like Redis).

Example _global.yaml:

gems:
  - Olib

scripts:
  - services/log
  - alias
  - infomon
  - env

Notice that you can also specify gems to require, which happens before any scripts are launched!