๐ŸŽฎ Sister Brawl โ€” Fun Audit v2

Date: 2026-06-04
Source: /home/usr/funday/docs/fun-ops/audits/2026-06-04-sisterbrawl-fun-audit-v2.md
Evidence basis: live browser playtest at /play/sisterbrawl plus code review.

Executive scorecard

FUN STACK     โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–‘โ–‘โ–‘ 3.4/5  (up from 2.8)
CORE LOOP     1 weak link: Reward; Learning improved from broken to weak
FUN TYPES     Hard: 3/5 | Social: 2/5 | System: 2/5 | Sensory: 3.5/5
PEAK MOMENT   Solo mode โ†’ bot fight โ†’ KO with screen shake + particles
DEAD MOMENT   Post-match: no progression, no XP, flat scoreboard

Evidence summary

SourceFinding
Live playtestGame loads, renders a 2D canvas, and solo mode auto-starts with a bot opponent
ConsoleNo JS errors observed in the referenced playtest; draw-loop logs confirmed rendering
Frontend codePrediction, interpolation, replay/spectator support, HUD, audio, particles, screen shake
Nakama server60Hz tick, physics/combat, bot AI, replay/spectating, progression hooks
ManifestallowSoloAutostart: true, integrationType: "svelte-component"

Top remaining fun killers

KillerSeverityFix direction
Character specials still feel too similar server-side๐ŸŸก gameplayDifferentiate each characterโ€™s special in authoritative match logic
Tutorial/onboarding is still thin๐Ÿ”ด clarityAdd first-run tutorial and explain win condition, block, specials, and rematch loop
Reward loop is weak๐ŸŸก retentionAdd XP/progression or character mastery surface after match end
Multiplayer social proof remains under-tested๐ŸŸก confidenceAdd two-context Playwright smoke for match create/join/play
Silent match-state failures๐ŸŸข polishReplace silent catches with visible retry/error state where player action is needed

Fix priority

  1. Onboarding: teach movement, attack, block, special, and win condition before the first real fight.
  2. Special differentiation: make the six characters mechanically distinct server-side, not just statistically distinct.
  3. Reward: show progression, mastery, match history, or another persistent reason to rematch.
  4. Multiplayer proof: verify 2-player create/join/sync/disconnect behavior with an E2E smoke.