Skip to main content

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).

NodeWhere to place itWhat it does
MARS LinkStart of a reaction blueprintEntry point when MARS runs a reaction; exposes event data
MARS CompleteEnd of a reaction blueprintSignals that the reaction is done so the next request can run
MARS Event InputPlatform-connection blueprintSends broadcast events to the Hub for rule-condition checking
MARS Manual TriggerAny blueprintRuns a specific reaction directly, bypassing rules

Overview​

CHZZK Donation ReceiverPlatform Plugin
MARS Event InputEvent Type: Donation
MARS LinkReaction picked by Hub
Reaction ActionsProp · Motion · Camera
MARS CompleteStart next request

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.

The entry point of a reaction blueprint. When MARS runs this reaction, the flow exits through Invoked.

MARS Link
Internal Reaction ID
Auto
Reaction Name
Throw
Allow Re-running the Same Reaction
NoYes
Allow Running with Other Reactions
NoYes
▶Invoked
Custom Parameter
Request ID
Source
Event Type
Nickname
User ID
Amount
Message
Type
JSON Data

▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.

InputDescription
Internal Reaction IDAuto-assigned ID. Do not change.
Reaction NameThe name shown in the Hub and .mars file
Allow Re-running the Same ReactionIf Yes, new requests for this reaction overlap even while it's running → Execution Policy
Allow Running with Other ReactionsIf Yes, this reaction can run alongside other reactions (the other reaction must also be Yes)
OutputDescription
Invoked ▶Reaction execution starts
Custom ParameterInteger set in the rule. Use it to vary behavior per rule with the same reaction → Custom Parameter
Request ID · Source · Event TypeInformation about the request that triggered this run
Nickname · User ID · Amount · Message · TypeEvent data. Type is donation type, subscription tier, channel points reward title, etc.
JSON DataRaw 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.

MARS Complete
▶Run
Extra Delay After Completion
0
Recent Errors
▶Success
▶Rejected

▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.

PortDescription
Run ▶Connect here after all effects and cleanup are done
Extra Delay After CompletionKeeps 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.
MARS LinkInvoked
Throw PropThrow Prop
WaitUntil the effect ends
MARS CompleteRun

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.

MARS Event Input
▶Run
Event Type
Select...▾
Nickname
User ID
Amount
0
Message
Type
Recent Errors
▶Success
▶Rejected

▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.

PortDescription
Run ▶Connect the flow output (Exit) of the platform receiver node here
Event TypeChat, Donation, Subscription, Channel Points, Raid, etc. Changing this updates the field labels below to match the type.
Nickname · User ID · Amount · Message · TypeConnect 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.
CHZZK Chat ReceiverCHZZK Plugin
MARS Event InputEvent Type: Chat

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.

MARS Manual Trigger
▶Run
Reaction
Select...▾
Source
Event Type
Nickname
User ID
Amount
0
Message
Type
JSON Data
Recent Errors
▶Success
▶Rejected

▶ Green = execution (flow) port · ● White = data port. Left side is inputs, right side is outputs.

PortDescription
ReactionThe 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