Junky summary of me running #lambdaMOO myself on a 64 bit system.

Simple details such that you can do exactly what I have done. Debugging mood, not a high-quality-writing mood.

https://lispy-gopher-show.itch.io/lispmoo2/devlog/1484719/lambdamooing-at-all-me-working-around-classic-32-bit-modern-64-bit-core-database-problem

#gamedev #devlog #mud .

The 32/64 database problem I think is that the change in integer width broke some listutils, which trivially stops @create and @dig working (important ones!) because the map_args over the aliases errors.

tl;dr
@edit #21:set_names
del #14
ins "return {name, {}};"

LambdaMOOing at all + me working around classic 32 bit -> modern 64 bit core database problem - lispmoo2 by screwtape

Primer on running lambdamoo on your lonesome : hacking the old 32 bit core databases work to some extent on 64 bit. https://github.com/wrog/lambdamoo?tab=readme-ov-file#user-content-legacy-database-su...

itch.io
@mdhughes When you have time do you mind checking if you have the exact same experience building lambdamoo 1.9.0alpha for legacy database compatibility i.e. with @create and @dig foo to bar erroring on map_arg*s inside #21:set_names ?