What exists now #
Streamer settings persist an enabled join command, default !join, and a validated custom command. This does not activate chat dispatch.
Current main has default-off bot/channel authorization setup and safe verification receipts. It does not retain exchanged chat tokens, create EventSub subscriptions, activate transport or post messages. The setup flag and actual user permissions are operator-managed.
The selected bot account is community_raiders; no additional app is required by the current setup design. Never reuse an Extension shared secret as creator/bot credentials.
Separate account and channel consent #
The intended bot permission flow and the streamer's channel permission flow are distinct. A creator login alone does not mean the bot can receive/send chat. Actual persistent grants, credential provisioning and live posts require their own approved setup actions.
Do not put credentials or live authorization URLs in a pull request, screenshot, issue, docs example or client bundle. The public site documents contracts; it is not a grant console.
Local-only battler and transport #
The goblin battler and chat transport live in isolated local work, not current-main active endpoints. Do not invent public chat ingestion, encounter-start or XP-award routes. The current OBS state is still a waiting battleground.
| Planned integration boundary | Rule |
|---|---|
| Chat ingestion | Verified viewer/broadcaster IDs, deduplicated events and the community's saved command |
| Encounter admission | Local design caps an encounter at ten unique battlers; duplicates do not consume slots |
| Scaling | Enemy budget derives from the closed admitted roster; exact balance remains provisional |
| Rewards | Server-authoritative and idempotent; never an award from the panel or a chat string alone |
Later systems #
Automatic encounters, PvP community raids, controlled dungeons, Raiderville upgrades/editor and account-wide cosmetic entitlements are planned. A public opt-in comparable-community raid directory and moderator-approved invitations are far-future work, not the hackathon build.