JDR-Bot - en:txt

actions

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:48:03+00:00

Language / Langue : FR | EN TXT — Custom Actions Legacy custom actions are supported, but YAML actions: is clearer: actions: - verb: inspect target: chest if: ~ text_ok: "An old chest."

alias

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:48:00+00:00

Language / Langue : FR | EN TXT — Aliases and Reactions Legacy aliases map typed commands or reactions to rooms and actions. In YAML, use choices:, button:, global_aliases: and action alias:.

conditions

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:47:59+00:00

Language / Langue : FR | EN TXT — Conditions Legacy conditions are used in events and exits. YAML offers a clearer condition syntax, but legacy scenarios remain supported. Common checks: * object name: object owned * -object: object missing *

evenements

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:48:00+00:00

Language / Langue : FR | EN TXT — Events (997) Legacy 997 entries execute conditional effects, redirections, timers or text. YAML equivalent: use events: with if:, do:, to:, timer: and text:.

objets

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:47:58+00:00

Language / Langue : FR | EN TXT — Objects and States Legacy TXT objects are defined on the variable/object line. The YAML format is recommended for new object-heavy scenarios because it separates furniture, object descriptions, pickup text and reactions more clearly.

options

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:48:03+00:00

Language / Langue : FR | EN TXT — Title Options Legacy title options are still parsed for old scenarios. For new scenarios, use YAML options: and the scenario header keys.

reactions

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:48:01+00:00

Language / Langue : FR | EN TXT — Discord Reactions Legacy reaction syntax is still supported for old scenarios. In YAML, reaction-like buttons are declared with button: on choices, events and actions.

sons-images

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:47:58+00:00

Language / Langue : FR | EN TXT — Sounds and Images Use [[url]] for images and <> for sounds. [[https://example.com/image.png]] <> Use <> to stop sounds.

syntaxe-base

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:47:54+00:00

Language / Langue : FR | EN TXT Syntax — Base The .txt format is the legacy JDR-Bot syntax. It is still supported, but new scenarios should use YAML. A room is made of several lines: number, title/text, variables/objects, then exits and events. Use the existing examples and the linter when maintaining legacy scenarios.

texte

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:47:58+00:00

Language / Langue : FR | EN TXT — Text and Formatting Legacy TXT scenarios support plain text, inline variables, media markup and some Markdown rendering depending on the selected scenario mode. * v_name_v displays numeric variables. * t_name_t

variables

Anonymous (anonymous@undisclosed.example.com) — 2026-05-03T16:47:59+00:00

Language / Langue : FR | EN TXT — Variables Legacy numeric variables use the v_name_v display syntax. Text variables use t_name_t. Online variables end with _o. Prefer YAML vars:, text_vars: and online_vars: for new scenarios.