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>
10 lines
346 B
Text
10 lines
346 B
Text
# ludic.base - what a mechanic may use and nothing else: the frame it is handed, the phases
|
|
# that order it, queues for the facts it reports, its own dice, its save section, its system
|
|
module ludic_base
|
|
numbers float
|
|
import "tick.ludic"
|
|
import "queue.ludic"
|
|
import "rng.ludic"
|
|
import "save.ludic"
|
|
import "save_fields.ludic"
|
|
import "system.ludic"
|