Différences

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

--- en:yaml:evenements [2026/10/19 03:27] – Wiki 4.17 : exemples et tableaux manquants en anglais cyrilfiesta
+++ en:yaml:evenements [2026/11/04 21:35] (Version actuelle) – Documentation 4.17 : objets, evenements et mise en page verifies cyrilfiesta
@@ Ligne 3: / Ligne 3: @@
 ====== Events (YAML) ======
-Events are action blocks run automatically or called through an interaction, such as a button, shortcut or ''trigger_event:id''. An event bound to a shortcut or an explicit call is manual, even without a button.
+Events are action blocks run automatically or called through an interaction, such as a button, shortcut or ''trigger_event:id''. A button waits for a click. Without a button, ''manual: true'' or a shortcut makes the event manual. Merely referencing its ID in ''trigger_event:'' never makes it manual: otherwise it is still evaluated on entry and after commands.
 ===== Base Syntax =====
@@ Ligne 170: / Ligne 170: @@
 Local events can be controlled with ''event:id:ON'', ''event:id:OFF'' and ''event:id:SWITCH''.
+===== Manual event without a button =====
+^ Key ^ Effect ^
+| ''manual: true'' | Prevents automatic execution, without adding a button. |
+A choice can call this event explicitly. Its conditions, state and usage limits still apply.
+<code yaml>
+title: 'Wiki 4.17: manual'
+rooms:
+- id: depart
+  text: Start.
+  events:
+  - id: alerte
+    manual: true
+    text: Called only by the choice.
+  choices:
+  - command: appeler
+    button: Call
+    to: depart
+    effect: trigger_event:alerte
+</code>
+The alert text is absent on entry. The "Call" choice triggers it. Removing ''manual: true'' also makes it automatic; ''trigger_event:'' does not change that rule. French: ''manuel: true'' and ''declencher_event:alerte''.