Release Healer Man 0.1.32
This commit is contained in:
1 parent
d3d6aaebdb
commit
6dcb1034e5
102 files changed
+10772
-788
No files matched your search
@@ -71,6 +71,21 @@ Optional template fields:
|
||||
- `reason`: why an object is deferred;
|
||||
- `source`: forensic image/model/classification evidence.
|
||||
|
||||
`source.scriptRoots` may list reviewed Lua entry functions for dynamically
|
||||
created bosses that have no static SQL row. The boss-mechanics importer follows
|
||||
those roots and their callbacks exactly as it does for static boss rows.
|
||||
|
||||
Optional top-level scripted placement fields:
|
||||
|
||||
- `scriptedSpawns`: reviewed creatures created by Lua rather than stored as
|
||||
active zone rows. Each entry has a stable `id`, a combat/boss `templateId`, a
|
||||
`sourceAnchorSpawnId`, source evidence, and optional source-unit offset,
|
||||
controller row, direction, or `objective: false` for a boss companion.
|
||||
- `scriptedFormations`: source `LuaFunc_Matrix_Maker` formations flattened to
|
||||
their initial positions. Each formation specifies its controller/anchor row,
|
||||
source direction and spacing, Lua root/evidence, and member template IDs with
|
||||
one-based rows and signed columns.
|
||||
|
||||
`expected*` values may be `null` only in a fresh scaffold. The explicit
|
||||
forensic refresh with `--update-recipe` pins them. A recipe should not be treated
|
||||
as production-ready until all classifications/models and counts are reviewed.
|
||||
Reference in new issue
Block a user