Owner page
Invite streamers, see how far each one got with setup, and check that the site is healthy.
Checking your access…
Channels
Loading channels…
Add a streamer in three steps
- Create an invite. Type their Twitch login (the name in their channel link) and click Create invite link.
- Send them the link in a Discord or Twitch message. It works once, for 7 days, and only for the account it names.
- Watch their row below. They sign in on the link, then follow Stream setup on their mod controls page. Setup reaches 3 of 3 when the overlay is open in OBS, the StreamElements Duel module is off and the duel commands answer in chat.
Setup progress by channel
| Channel | Status | Setup | Overlay in OBS | Chat | Last chat activity | Actions |
|---|
Overlay in OBS counts overlays open right now, so it reads "not open" whenever the streamer is offline. Chat shows how many of the StreamElements commands have reached PixFray. A channel that's off keeps its fighters and ranks; its overlay, commands and viewer page stop until it's turned back on. Up to 200 channels can be on. Export downloads one channel's fighters, ranks, settings and StreamElements command names as a JSON file; keys and tokens are never included.
Invites
| For | Status | Created | Actions |
|---|
Loading site health…
Request counts come from Cloudflare analytics for the whole account (the Free limit is per account and resets at 00:00 UTC). They lag by a few minutes.
Error log, newest first
| Time | Source | Message | Context |
|---|
The newest 100 of up to 200 stored rows per channel.
Developer tools: code editor, releases and raw settings
For fixing the site itself. The code editor and releases need GitHub access, and Worker versions need the Cloudflare API; Integrations at the bottom lists what is set up. Running channels don't need any of this.
Code editor: changes go to a branch, never straight to main
Loads from the branch if it exists, otherwise from main. Secrets, CI files and build output can't be opened here.
Release a fix: test first, then promote or roll back
Each step starts the GitHub Actions deploy workflow. Nothing changes on chat.miolaf.xyz until you promote or use a hotfix.
- Save to a branch in the code editor above. Branch names start with
live-fix/orhotfix/. - Deploy to test.
- Check it in OBS with the test overlay: test.chat.miolaf.xyz overlay.
- Promote to production. Squash-merges the pull request, then deploys the base branch.
- Roll back if something breaks.
Hotfix: deploys a hotfix/ branch straight to production, skipping the test site (unit tests still run), and opens a pull request so main keeps the change.
Recent deploy runs
| Started | Run | Branch | Result |
|---|---|---|---|
| Not loaded. | |||
Worker versions now serving
| Site | Version | Traffic (%) | Deployed | Note |
|---|---|---|---|---|
| Not loaded. | ||||
nesszerra game settings as JSON
The same versioned settings as the Rules tab in Mod controls, edited as raw JSON. Running duels keep their old rules.
Settings history
| Version | Saved | By | Note |
|---|
Integrations and what each one needs
| Integration | Status | Missing | Used for |
|---|
Set missing values as Worker secrets or vars; docs/LIVE_FIX.md lists each one and its minimum permissions.