3. Connecting Platform API Nodes
What to do in this step: Wire your platform's chat/donation receiver nodes to a MARS Event Input node so that typing !Throw in real chat triggers the reaction.
Prerequisites
- Scene with the
Throwrule enabled (step 2 complete) - Your platform's integration plugin and login:
- Chzzk: CHZZK plugin from the Workshop
- SOOP: SOOP plugin from the Workshop
- Twitch: Warudo built-in (connect under Settings → Twitch)
Steps
- In the Blueprint tab, click + to create a new blueprint and name it
Platform → MARS. Keeping this blueprint separate from your reaction blueprints makes management easier. - Place the platform receiver node. For example, for Chzzk: CHZZK Chat Receiver.
- From the Moraecat category, place a MARS Event Input node.
- Set the Event Type in MARS Event Input. Use Chat for a chat node, Donation for a donation node. Changing the Event Type updates the port names below to match the event. (e.g. Donation → Amount · Message · Donation Type; Subscription → Months · Message · Tier)
- Wire the connections as shown in the table for your platform. Connect the flow output (▶ shape) to Run, and data outputs to the matching port. Unused ports can be left empty.
- Save the scene.
Place one MARS Event Input per event type. If you use both chat and donation, you need two Event Input nodes.
Chzzk (CHZZK Plugin)
| Receiver node | MARS Event Type | Receiver output → MARS Event Input |
|---|---|---|
| CHZZK Chat Receiver | Chat | Exit → Run · Nickname → Nickname · SenderChannelId → User ID · Content → Message |
| CHZZK Donation Receiver | Donation | Exit → Run · DonatorNickname → Nickname · DonatorChannelId → User ID · PayAmount → Amount · DonationText → Message · DonationType → Donation Type |
| CHZZK Subscription Receiver | Subscription | Exit → Run · SubscriberNickname → Nickname · SubscriberChannelId → User ID · Month → Months · TierName → Tier |
SOOP (SOOP Plugin)
| Receiver node | MARS Event Type | Receiver output → MARS Event Input |
|---|---|---|
| SOOP Chat Message | Chat | Exit → Run · UserNickname → Nickname · UserId → User ID · Message → Message |
| SOOP Star Balloon Gift | Donation | Exit → Run · UserNickname → Nickname · UserId → User ID · Count → Amount (star balloon count) |
| SOOP Consecutive Subscription | Subscription | Exit → Run · UserNickname → Nickname · UserId → User ID · SubscriptionMonths → Months |
| SOOP Subscription | Subscription | Exit → Run · UserNickname → Nickname · UserId → User ID |
SOOP's Count is the number of star balloons, not a currency amount. Enter the count in the amount condition as well. (e.g. 10 star balloons → Threshold Amount 10)
Twitch (Warudo built-in)
| Receiver node | MARS Event Type | Receiver output → MARS Event Input |
|---|---|---|
| On Twitch Channel Message | Chat | Exit → Run · UserDisplayName → Nickname · Username → User ID · Message → Message |
| On Twitch Bits Received | Donation | Exit → Run · UserDisplayName → Nickname · Username → User ID · BitsUsed → Amount · Message → Message |
| On Twitch Subscription Received | Subscription | Exit → Run · UserDisplayName → Nickname · Username → User ID · CumulativeMonths → Months · Message → Message |
| On Twitch Channel Points Received | Channel Points | Exit → Run · UserDisplayName → Nickname · Username → User ID · RewardCost → Points · UserInput → Viewer Input · RewardTitle → Reward Title |
| On Twitch Channel Follow Received | Follow | Exit → Run · UserDisplayName → Nickname · Username → User ID |
| On Twitch Raid Received | Raid | Exit → Run · RaiderDisplayName → Nickname · RaiderUsername → User ID · RaiderViewerCount → Viewer Count |
Twitch node documentation is also available at Warudo Node Reference.
The English names in the table are the internal port identifiers. Depending on Warudo's display language or the plugin version, they may appear in Korean on the node UI. The order from top to bottom is the same.
Testing without a live broadcast
You can test without real chat.
- Chzzk: Use the CHZZK Receive Test node's test button to send a fake chat or donation. Enter
!Throwand press it. - Any platform: Wire an On Key Press node to the Run input of MARS Event Input, set the Event Type to Chat, type
!Throwdirectly in the Message field of the node, and press the key.
The Success ▶ output of MARS Event Input means "the request was accepted" (not that the reaction has finished). If you see Rejected ▶, check Recent Errors on the node and Recent Errors in MARS Execution Status in the Hub.
Verification
- Sending
!Throwin live chat (or via test) makes the cat fly out. !throw(lowercase) or!Throw!does not trigger, because the rule uses Exact Match.- Running and Queued in MARS Execution Status increment and return to
0.
Next step: 4. Making Your Reaction MARS-Compatible