Grim Games Live Grim Games Live

GRiMbot documentation

First stream checklist

This is the hosted copy of the GRiMbot technical manual. Use the table of contents to open any page in the manual.

GRiMbot product page Manual home

First stream checklist

Purpose and scope

Use this operational checklist for the first live stream after completing Setup for a Twitch stream. It verifies the running services and stream-facing output without changing the established configuration.

Prerequisites

  • SETUP BOT Progress says Setup is complete.
  • Bot Timezone and the non-default GRiMbOS password have been verified separately.
  • A Chat Message test has already succeeded.
  • OBS Browser Sources have been added and tested.
  • Required plugins have been configured.
  • The PC Agent has been installed only when Use streaming PC agent or OBS Agent mode is enabled.

Ordered procedure

1. Start services

  1. Start GRiMbot if it is not managed as an active service.
  2. Open GRiMbOS and confirm that /admin loads.
  3. Start OBS.
  4. Start the PC Agent when Use streaming PC agent or OBS Agent mode is enabled.
  5. Start the optional applications required by the configured plugins.

2. Verify connections

  1. Open System → Connection Status.
  2. Confirm that the broadcaster account is authorized.
  3. Confirm that the expected Chat Message identity is authorized and joined to chat.
  4. Confirm the PC Agent connection when used.
  5. Confirm each required plugin connection.
  6. Use Fix… for any failed row before going live.
  7. Open SETUP BOT Progress and confirm that Twitch events arrive over shows websocket.

3. Verify OBS output

  1. Open every OBS scene used during the stream.
  2. Confirm that each GRiMbot Browser Source loads.
  3. Confirm that its dimensions match the corresponding overlay canvas.
  4. Confirm that Control audio via OBS is enabled on sources that play clips or sounds.
  5. Run an Event Alert Preview.
  6. Run one controlled media test and monitor the OBS audio mixer.

4. Verify stream settings

  1. Open Stream Setup if you changed the Twitch title, category, tags, or schedule.
  2. Click SAVE.
  3. Confirm the changes on Twitch.
  4. Enable Opening Chat only when the first three qualifying people should receive the configured Rewards for this Stream Session.

5. Verify optional integrations

Integration Required check
Spotify The account is Premium, the Spotify app is open, an active device is playing, and a Song Requests playlist is selected.
Streamer.bot direct mode Streamer.bot is running on the same PC as GRiMbot, and Use streaming PC agent is cleared.
Streamer.bot Agent mode Streamer.bot and the PC Agent are running, and Use streaming PC agent is selected.
Voice Recognition Complete the checks listed in Voice Recognition settings.
OBS Integration OBS WebSocket is enabled and the configured Direct or Agent mode reports connected.
ATS or MSFS The applicable telemetry or local web service is running before the simulator session begins.

6. Go live and confirm

  1. Start the stream in OBS.
  2. Wait for Twitch to report the channel live.
  3. Open Live Dashboard on a secondary display if available.
  4. Send !ping once from a permitted second account or ask a moderator to send it.
  5. Confirm that the reply uses the expected Chat Message identity.
  6. Observe the first real EventSub event and verify its configured output.

7. End the Stream Session

  1. Stop the stream in OBS.
  2. Wait for Twitch to report the channel offline.
  3. Confirm that the Stream Session closes in GRiMbOS.
  4. Close the PC Agent if no enabled integration needs it between streams.
  5. Close optional local tools if they should not run between streams.
  6. Leave GRiMbot running only if the machine policy permits it.

Settings and choices

Opening Chat assigns places to the first three qualifying people who send a Chat Message. It does not award the first three messages. The broadcaster and known bot accounts are skipped.

Spotify and Twitch authorizations normally remain valid between streams. Re-authorize only when Connection Status or the integration reports an expired or revoked authorization.

Expected result

The channel goes live with GRiMbot joined to chat, overlays visible and audible in OBS, required integrations connected, and the intended Opening Chat behavior enabled.

Verification checklist

  • [ ] GRiMbot and GRiMbOS are reachable.
  • [ ] OBS and required local applications are running.
  • [ ] The PC Agent reports connected when required.
  • [ ] Twitch account rows are working in Connection Status.
  • [ ] Required plugin rows are working.
  • [ ] OBS Browser Sources load in every live scene.
  • [ ] Browser Source audio control is enabled where required.
  • [ ] Event Alert Preview appears in OBS.
  • [ ] A media test appears and sounds correct.
  • [ ] Stream Setup changes have been saved and confirmed on Twitch.
  • [ ] !ping receives one reply after going live.

Failure handling

If Twitch rows fail, open System Status and re-authorize the affected account. Packaged local installations restart WebSocket EventSub automatically. Use Re-subscribe EventSub only for a webhook deployment.

If Event Alerts remain silent, use Preview first. Confirm that the overlay layout contains Event Alerts and that the Browser Source has Control audio via OBS enabled.

If Spotify commands fail, start playback manually on the intended active device before testing again.

If the PC Agent fails, verify its GRiMbot URL and token. Download a fresh package after either value changes.

[!IMPORTANT] Do not use Event Emulator as an overlay-only test during a live stream. It runs normal event processing and can affect configured outputs.

Security and data notes

Do not show GRiMbOS credential fields, tokens, callback URLs, integration settings, or generated PC Agent configuration on stream. Keep the admin browser and service terminals out of captured scenes.

Related pages