Language / Langue : FR | EN
The linter analyses your scenario as you work and reports errors and warnings.
Running it: the Linter button (🔍 icon) in the toolbar, or Ctrl+Shift+L.
Kinds of messages:
Errors detected, among others:
trigger_event: identifiers that do not existbutton: nor command:: no button appears and the player cannot type anythingid:, which the engine would ignore
The label of a choice is written button:. Written text:, the choice keeps its destination but shows no button: the room looks like a dead end. The linter reports it and names the expected key.
Platform warnings. With a Discord or Terminal profile, the report adds the incompatibilities of that platform, with their location: more than 25 options in a room, a label longer than 100 characters, or a media file Discord cannot reach publicly.
Clicking an error opens the matching room in the inspector. For an undeclared variable, the click leads to the place that uses it; when it is used in several places, a window lists them with their kind of usage.
The Test button starts a game right inside the editor, without going through Discord. A game window opens, running the full engine.
It lets you check conditions, the order of events, timers and the HUD, exactly as if you were playing in the browser.
YAML export generates a .yaml file the engine can read.
Standalone HTML5 export generates a ZIP ready to be hosted or uploaded to itch.io as an HTML5 game.
jdrbot-<slug> folder inside the ZIP)PDF gamebook export generates a PDF with numbered chapters, cross-references, a tracking sheet and editable fields, playable on paper like a choose-your-own-adventure book.
Both exports include every asset, sounds and images, referenced by URL in the scenario. A hosted video stays online instead: see Sounds, images and videos.