Orkuncakilkaya
dd6a449921
A mechanic package depends on ludic.base and nothing else: ports (records of function values for now) for questions, queues for facts, verbs for changes, phases for order and its own versioned save section. The runner inits, resets, saves and loads systems in the order added and ticks them phase by phase; a missing save section is a reset. Tests for each piece and a worked route between two toy mechanics live under tests/. The old ludic.core (engine ECS components) is used by examples/library and stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5 lines
232 B
Text
5 lines
232 B
Text
# ludic.base - the vocabulary every mechanic package shares and the only thing one may use:
|
|
# Tick, phases, Queue<T>, rng streams, the save tree and the system runner. See README.md.
|
|
package "ludic.base"
|
|
version "0.1.0"
|
|
kind source
|