Owner page
See which streamers signed up and how far each one got with setup, turn a channel off, and check that the site is healthy.
Checking your access…
Inside
- Every channel that signed up, newest first
- Setup progress for every channel, with an on/off switch
- Worker requests, errors and open pages for today
- Logs per channel, plus test deploys and rollbacks
Channels
Loading channels…
Streamers add themselves in three steps
- Send them the sign-up page in a Discord or Twitch message: /start/
- They sign in with their own Twitch account. PixFray turns on for that channel only; nobody can turn it on for someone else's. A Twitch account under 30 days old, or one that has never streamed (no saved past broadcast and not Affiliate or Partner), waits off in the table below until you approve it.
- Watch their row below. After signing in they 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. A channel you turn off here stays off until you turn it back on; its streamer can't. 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.
Restore a channel to an earlier time
Cloudflare keeps every change to a channel's fighters, ranks, dollars and settings for 30 days. Restoring puts one channel back the way it was at the time you pick, and drops everything it saved after that. Open overlays and pages reload on their own.
Loading the last restore…
Only the picked channel goes back; the channel list, sign-ins and other channels stay as they are. For a copy older than 30 days, use Export above.
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 rows. Each channel keeps the last 500 rows per source (200 for alarms, duels and chat delivery, which also stop storing after 300 a day). Every line also goes to Workers Logs in the Cloudflare dashboard for 3 days.
Room counters by day
For the channel picked in the log above, newest UTC day first. A jump in alarms or requests points to a loop; bot_failed or bot_held point to chat delivery.
| Counter |
|---|
Counts reach storage at least every 30 seconds while the room is busy, so the last few seconds before it goes idle can be missing. Days older than 14 are dropped.
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 changes and releases run from a local checkout with the gh and cf command-line tools: deploy to staging with bunx cf deploy --mode test, check it, then deploy to production. The code editor and release buttons appear here only when GitHub is set up as in docs/LIVE_FIX.md.
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. Build files (package.json, configs, scripts/) open read-only.
Release a fix: test first, then promote or roll back
Each step starts the GitHub Actions deploy workflow. Nothing changes on the production site until you promote or use a hotfix. Promote, hotfix and production rollback need you signed in with Twitch.
- 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 site 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.