feat: add paired goat care
This commit is contained in:
@@ -811,15 +811,20 @@ Completed:
|
||||
exact mid-route state through schema-v11 restore and presentation
|
||||
unload/reload. The animal feature assets now live together under
|
||||
`world/animals/goat/`, while ignored docs no longer create import sidecars.
|
||||
42. `Jajce Goat Pair 09`: Zora now joins Dunja as a second named, stable animal
|
||||
with an authored private shelter and deterministic access to the shared
|
||||
pasture. Simultaneous hunger selects the nearest available loaded goat,
|
||||
preserves two exact reservations through save/restore, and feeds only the
|
||||
named target. Private shelter ownership remains loaded-world context; no
|
||||
herd system, animal index, or schema bump was introduced.
|
||||
|
||||
Next:
|
||||
|
||||
1. Add one second named goat with its own stable state, authored shelter
|
||||
context, and deterministic use of the shared pasture. Prove nearest
|
||||
feed-target selection and independent reservations when both animals are
|
||||
hungry.
|
||||
1. Playtest the named pair and record one concrete gameplay or scaling need
|
||||
before extending the animal model.
|
||||
2. Keep breeding, products, herd scheduling, animal spatial indexing, and
|
||||
active/abstract simulation LOD deferred until two real animals require them.
|
||||
active/abstract simulation LOD deferred unless that evidence requires one
|
||||
of them; otherwise return to the broader milestone sequence.
|
||||
|
||||
Do not start with GIS data, a full city, a large asset pack, or more NPC
|
||||
mechanics. The next proof is a beautiful stage for the systems that already
|
||||
|
||||
Reference in New Issue
Block a user