Community RaidersDEVELOPER FIELD GUIDEVisit Community Raiders

COMMUNITY RAIDERS / ENGINEERING

Build the next adventure

A practical map of the systems behind Community Raiders: what exists, who owns state, and where a contribution belongs.

Source-backed guide · 2026-10-26

Start with a boundary

Community Raiders is a Twitch-first community game with a normal website/dashboard, a native Twitch Panel Extension and a shared Raiderville campsite. FastAPI and persistent storage own identity, inventory and progression; Phaser renders accepted state.

This edition describes the verified source snapshot, not a promise that every integration is configured, Twitch-approved or currently live.

WEBSITEDashboardCreator & player controls
TWITCHNative panelLinked viewer + channel
PHASERRaidervilleAccepted room state
SERVER AUTHORITYCommunity Raiders APIIdentity · community scope · inventory · progression
Persistent SQLite storageShared appearance / community-owned gameplay records
Browsers request changes. The API validates identity and ownership; persistent state determines what renders.

What can you build on?

StateAvailable foundation
Implemented in sourceCreator/player sign-in; associated-community browser; shared appearance; owned-gear validation; native panel; code-bound campsite presence and movement.
Local-only / awaiting integrationGoblin battler, chat transport, new walk-cycle work and worn-knight armor proofs. They are not active current-main gameplay APIs.
PlannedLive automatic encounters and rewards, community PvP raids, controlled dungeons, campsite upgrades/editor and account-wide cosmetic entitlements.

Choose a small first feature

Read Architecture and Identity before adding a request. Then choose the guide for the system you will change. Keep the contribution isolated, test incorrect identities and communities as well as success, and document any contract change.

  • UI: extend existing accepted-state views without inventing owned items or statistics.
  • API: add validated community/account-scoped behavior with transactional ownership checks.
  • Art: use the registered neutral-body contracts and prove every advertised material/outfit combination.
  • Gameplay: agree the server-owned state and reward boundaries before connecting a renderer or chat command.

Get contributor / agent context

Get structured project context

A room is not a combat engine

Raiderville already provides a shared visual space. Its current movement is composed still art; joining or walking does not award XP or simulate battles.

Local Raiderville renderer proof: approved night woodland, male and female raiders, campfire and overhead labels.
Actual local renderer proof with synthetic players. This illustrates the scene, not live account or encounter activity.

CHECK THE IMPLEMENTATION

Read the source

Links are pinned to the edition above. Repository access is managed separately.