MARS Node Reference
These are the four MARS nodes in the Moraecat category of the Blueprint editor. Field names on screen follow MARS's language setting (shown below in English).
| Node | Where to place it | What it does |
|---|---|---|
| MARS Link | Start of a reaction blueprint | Entry point when MARS runs a reaction; exposes event data |
| MARS Complete | End of a reaction blueprint | Signals that the reaction is done so the next request can run |
| MARS Event Input | Platform-connection blueprint | Sends broadcast events to the Hub for rule-condition checking |
| MARS Manual Trigger | Any blueprint | Runs a specific reaction directly, bypassing rules |
Overview
There is no direct connection between Event Input and Link. The Hub picks a reaction based on Execution Rules and calls that reaction's Link.
MARS Link
The entry point of a reaction blueprint. When MARS runs this reaction, the flow exits through Invoked.
▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.
| Input | Description |
|---|---|
| Internal Reaction ID | Auto-assigned ID. Do not change. |
| Reaction Name | The name shown in the Hub and .mars file |
| Allow Re-running the Same Reaction | If Yes, new requests for this reaction overlap even while it's running → Execution Policy |
| Allow Running with Other Reactions | If Yes, this reaction can run alongside other reactions (the other reaction must also be Yes) |
| Output | Description |
|---|---|
| Invoked ▶ | Reaction execution starts |
| Custom Parameter | Integer set in the rule. Use it to vary behavior per rule with the same reaction → Custom Parameter |
| Request ID · Source · Event Type | Information about the request that triggered this run |
| Nickname · User ID · Amount · Message · Type | Event data. Type is donation type, subscription tier, channel points reward title, etc. |
| JSON Data | Raw data sent by the platform (when available) |
- Place exactly one Link per blueprint.
- The flow must always reach MARS Complete.
MARS Complete
Notifies MARS that the reaction has finished. The next waiting request runs only after this signal.
▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.
| Port | Description |
|---|---|
| Run ▶ | Connect here after all effects and cleanup are done |
| Extra Delay After Completion | Keeps this reaction marked "Running" for this many extra seconds after completing. Use it to add spacing between reactions. |
| Success ▶ / Rejected ▶ | Result of the completion. If Rejected, the reason is in Recent Errors. |
If you call Complete immediately at the start, MARS treats the reaction as finished and starts the next request right away. Connect it after Wait or end-of-effect outputs.
MARS Event Input
Sends events from platform receiver nodes to the MARS Hub. The Hub checks rule conditions and runs the matching reaction.
▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.
| Port | Description |
|---|---|
| Run ▶ | Connect the flow output (Exit) of the platform receiver node here |
| Event Type | Chat, Donation, Subscription, Channel Points, Raid, etc. Changing this updates the field labels below to match the type. |
| Nickname · User ID · Amount · Message · Type | Connect the matching outputs from the receiver node. Leave unused ones empty. |
| Success ▶ | Means the request was accepted (not that the reaction has finished) |
| Rejected ▶ | Request not accepted. Reason is in Recent Errors and the Hub's recent notifications. |
Place one Event Input per event type. For per-platform wiring tables, see Platform Connection.
MARS Manual Trigger
Runs a chosen reaction directly, bypassing rules. Use it to call a reaction from another blueprint.
▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.
| Port | Description |
|---|---|
| Reaction | The reaction to run (you pick a reaction, not a rule) |
| Source · Event Type · Nickname · … | Values passed through to the reaction's MARS Link outputs |
| Success ▶ / Rejected ▶ | Whether the request was accepted |
- Custom Parameter runs as 0.
- Execution policy and queue apply normally. → Test Run and Recovery