Skip to content

SettingsKick

Jump to bottom
ekudram edited this page Aug 27, 2026 · 5 revisions

Kick Settings

Set up Kick.com so RICS can read your chat and reply to commands (!buy, !event, !balance, etc.).

Please post issues or feedback on Discord.

You do Part A on kick.com. RimWorld does not need to be open yet.

Part A — Kick.com (no RimWorld)

1. Log in

Go to https://kick.com and log in with the account you stream with.

2. Turn on 2FA (required)

Kick will not show Developer tools without Two-Factor Authentication.

  1. Click your channel picture (top-left) → Settings.
  2. Open the Security tab.
  3. Enable 2FA if it is not already on.

3. Open Developer

Still in Settings, open the Developer tab.

Create a new app, or Edit an app you already made for RICS.

Each streamer creates their own Kick app. Do not share Client Secret. Client ID is not a password, but it is still your app — do not treat someone else’s screenshot as “the RICS key.”

4. Fill the app

Use values like this:

Field What to enter
Application Name RICS
App Description Its a mod for the game Rimworld that allows viewers to interact with the game Rimworld directly using commands from chat
Redirect URL http://localhost:17890/kick/callback
Enable webhooks Off

Redirect URL must match exactly:

http://localhost:17890/kick/callback
  • http not https
  • no trailing /
  • not a GitHub URL (that causes invalid redirect uri)

5. Scopes

Check at least:

  • Write to Chat feed — required to send replies
  • Read user information (including email address) — required so RICS knows who authorized
  • Read channel information — required so RICS can resolve your channel for send

Other scopes are optional (future features). Extra checkboxes will not break RICS.

Skip “Create a BOT for this App.” RICS sends chat as the Kick user who clicks Authorize (your streamer name), not as a Kick bot page.

Save / create the app.

Kick Developer application: redirect URL and scopes

6. Copy your keys

On the app page you will see:

  • Client ID — copy this (safe to keep in a notes file)
  • Client Secret — copy this once and treat it like a password

Never stream, screenshot, or paste Client Secret into chat, Discord, or this wiki. If you leak it, click Regenerate on Kick and paste the new secret into RICS.

Part B — RimWorld (RICS Kick tab)

You need a current RICS build that includes Authorize Kick. Older builds can read Kick chat but cannot send.

7. Open the Kick tab

  1. RimWorld → Mods → [CAP] Rimworld Interactive Chat Service → Settings
  2. Click the Kick tab
  3. Enable Kick Integration

8. Channel + keys

  • Channel Slug = the part after kick.com/
    Example: https://kick.com/captolamia → type captolamia (no @, no URL)
  • Client ID = paste from Kick
  • Client Secret = copy on Kick, then click Paste Client Secret in RICS (the field stays masked)
  • Redirect URI = leave http://localhost:17890/kick/callback unless you registered a different URL on Kick

RICS Kick tab: channel slug, Client ID, secret, redirect URI

9. Authorize Kick (required to send)

Connecting without this step still reads chat. Replies will not appear until you authorize.

  1. Click Authorize Kick (required to send chat)
  2. Your browser opens Kick — log in and approve the app
  3. You should see RICS authorized / You can close this tab and return to RimWorld
  4. Back in RICS you should see green text: Chat send authorized as (your Kick name)

RICS Kick tab after authorize: Chat send authorized and Connected

10. Connect (you must be live)

Kick chatroom access needs an active Kick stream.

  1. Go live on Kick
  2. Click Connect to Kick
  3. Status should show Connected to Kick
  4. Optional: Auto-connect on startup (you still need to be live)

11. Test

From Kick chat (or the in-game live chat overlay), try a command such as !balance.

A reply should appear in Kick chat as the account you authorized.

Troubleshooting

invalid redirect uri on Kick
The Redirect URL on the Kick app does not match RICS. Set both to http://localhost:17890/kick/callback and Authorize again.

Authorize times out / cannot listen on the port
Close other programs using port 17890, then Authorize again. Keep the default redirect unless you know you need another port.

“Cannot Connect” is gray
Fill Channel Slug, Client ID, and Client Secret first.

Connected, but no replies in Kick
You connected for read only. Click Authorize Kick and wait for green Chat send authorized as …, then Connect again. You must be live.

“Oops something went wrong” on kick.com
Common with Brave. Turn off Brave Shields for Kick, or use Chrome/Edge.

Client Secret lost or leaked
Kick Developer → Regenerate → Paste Client Secret in RICS → Authorize again.

Still stuck?
Open a GitHub issue or ask on Discord.

Clone this wiki locally