stricter validation to avoid corruption via messed up state files; resetting complete state if one single state file fails (not resetting individually); better handling of repetitive loading of the API
tiny inconsequential reordering
documented and cleaned up lama-conf
added setting 'useMinecraftCoordinates' which, if enabled, makes the API use coordinates that conform with minecraft's native coordinate system. it defaults to false, to not break compatibility with existing scripts when upgrading, but it's recommended to set it to true when starting a new project. also, internally the API still uses it's own coordinate system, so the setting can be changed at any time without invalidating the state
passing additional arguments as parameters to command handlers in lama-conf
made loadAPI paths not explicitly absolute. this way it's possible to overwrite os.loadAPI to use shell.resolveProgram and have the api at an arbitrary location that's in the shell.path
generalized config program a bit more so that it's easier to copy-paste the common logic parts (everything except the actual table of commands)
adjusted for parameter shuffle in my startup API
updated readme for v1.2 and decided to make using mc coords the default, meaning it's a breaking change
updated minified version