Différences

Ci-dessous, les différences entre deux révisions de la page.

--- en:yaml:modeles [2026/10/18 23:46] – Relecture 4.17 : clarifications, exemples et typographie cyrilfiesta
+++ en:yaml:modeles [2026/10/20 22:23] (Version actuelle) – Modèles sur_place, portée des encadrés et objets 4.17 cyrilfiesta
@@ Ligne 38: / Ligne 38: @@
     choices:
       - button: Finish
-        to: victory
+        to: conclusion
+  - id: conclusion
+    events:
+      - end: victory
 </code>
@@ Ligne 59: / Ligne 62: @@
 See [[en:yaml:listes-boucles|Lists and collections]], [[en:yaml:tags|Tags]] and [[en:yaml:evenements|Events]].
+===== Adding a model to the current room: inline =====
+Set ''inline: true'' in the model definition. The model must contain exactly one internal room. Its initialisations, objects, actions, events, choices, shortcuts and HUD panels are added to the calling room, without entering a virtual room. The calling room keeps its ID and text; the internal room's text is not added.
+<code yaml>
+title: A model in the workshop
+collections:
+  player: {}
+models:
+  inline_healing:
+    inline: true
+    collections:
+      hero: {health: 0}
+    defaults:
+      hero: {health: 100}
+    rooms:
+      - id: content
+        hud:
+          position: top-right
+          scope: room
+          text: 'Health: v_hero.health_v'
+        actions:
+          - verb: heal
+            target: all
+            button: Heal
+            do: hero.health + 1
+rooms:
+  - id: workshop
+    text: You are in the workshop.
+    models:
+      - model: inline_healing
+        collections: {hero: player}
+    choices:
+      - {command: leave, to: corridor}
+  - id: corridor
+    text: The corridor.
+    choices:
+      - {command: return, to: workshop}
+</code>
+Heal acts in the workshop and Leave remains available. Returning preserves ''player.health''. The model's ''init:'' entries run on each entry, just like the room's own initialisations, so they can explicitly reset values.
+''exits:'' and their instance bindings remain available. For an inline model, ''end_model'' refers to the calling room. Simple fields supplied by the model can replace room fields: check display settings in particular. Avoid competing commands and HUD positions; the linter reports a model panel replacing a room panel.
+''inline'' controls model integration. ''scope: room'' separately controls a panel's lifetime. **Without an explicit scope, panels remain persistent, including those from inline models.** See [[en:yaml:hud|HUD panels]]. French syntax: ''sur_place: true'' and ''portee: salle''.
+===== Collection defaults =====
+The example's ''defaults:'' block fills only missing properties in bound collections, before validation. Values already supplied by the scenario are preserved, including in nested collections. The target collection must exist: ''player: {}'' is sufficient here. Defaults apply to generic collections declared by the model; they do not replace room initialisations.
+The editor exposes inline insertion and defaults for each generic collection in the model definition. The French key is ''defauts:''.
+The supplied library includes ''grille_2d'', an inline model binding map and player collections. Its demos cover movement, collisions, furniture, doors and optional combat. It uses ordinary room objects and choices, with a panel explicitly scoped to the room. Copy the model and follow its definition comments to prepare the map and bindings.