Repository navigation
The editor link: the script's events for the editor's timeline #1207
Description
The editor's debugger plans a timeline of the script (openreliant-editor#5): when each trigger fires, each part starts, each command runs, and when the script is held and let go. The link only tells an editor where the script stopped (tag 0x1A), so a timeline can't be drawn from it.
What's needed, as a message of OpenReliant's own beside State (The editor link): the script's events as they happen, each with the script's clock:
- a trigger firing: the trigger, its object and its condition;
- a part starting: the part, its thread, and the trigger or part that started it;
- a command running: the command and its thread;
- a hold, and its release with the step.
The editor asks for them, so that the game sends none to a client that doesn't want them.
Part of #1126.
Activity
feat: what the editor's debugger needs from the link and the compiler (…
vdmkenny commentedon Oct 14, 2026
Not planned: the link stays the original's protocol plus the messages that docs/engine/editor-link.md and #1126 document. A timeline of the script's events would need a message the original doesn't have.
vdmkenny commentedon Oct 15, 2026
Reopened: the timeline stays, with no new message.
Stategains the triggers fired and the commands run since the last state, each with its time on the script's clock (#1214).feat: the editor link's live scene, timeline and console, and --mods (O…
chore(main): release 0.16.0 (#1213)