Save Point: Profiles, Levels and Unlocks Kit
README.md
store
Where saves live. Each player's saves sit in their own runtime_data.player(id) store under saveKit/<namespace>/..., which survives leaving and rejoining. Any machine can read any player's store; the engine refuses a write to a store that is not the writer's own, so one player cannot change another's profile.
- Local player:
localId,localName,mine,get,set,delete,onChange. - Other players:
of,read,onAnyChange,users(everyone connected). key(ns, name)builds a save's path;writeOtherattempts a write to another player's store and returns the engine's refusal (used by tests and the showcase's tamper check).use(fn, others)swaps the live store for a stand-in in tests;use(nil)restores it.
Internal: saveKit.save does all reading and writing through this module. Read and write calls never raise; they return nil or ok, error.