no on second thought let's not try multiprocessing just yet
include proper data files with ELiDE
parameterization
the beginnings of a new test, natural selection on sickle cell anemia
initializing rules with lists of callables caused trouble, add them all with decorators now

also clean up some SQL nonsense
JSON for everything.
Get rid of the special classes for fake Thing/Place/Portal, use just CharacterImage and dictionaries for that kind of thing
make sure to set the time back where it was before leaving the rule
uh, make sure to initialize the character with stuff
better networkx integration, I think
don't freak out when creating an empty FunList
first go at letting pathfinding happen ahead of time
style
handle mirrored portals properly
docstrings
Two types of function store. Right now I'm using the one backed by a database but it might come in handy to have one backed by a module instead.
docstrings
Allow Listeners lists to use function names and not just functions. Also clean up their SQL.
GlobalVarMapping->EternalVarMapping
not using these