Skip to content

feat(system-builder): call a rest from the GAME tab (4f5) - #229

Merged
over2take merged 1 commit into
feature/system-builderfrom
sb/4f5-game-tab-rests
Oct 10, 2026
Merged

over2take merged 1 commit into
feature/system-builderfrom
sb/4f5-game-tab-rests

Conversation

@over2take

Copy link
Copy Markdown
Owner

Approved mockup docs/mockups/builder-rests.html (2026-10-09), stage 3. Under a custom game, TTRPG_SYSTEM gains a RESTS panel for the GM and granted editors (a built-in game's rests stay its own buttons, and its panel never asks).

  • components/GameRestsPanel.tsx: one of the game's rests; who rests (every player character, the NPCs on the map being viewed too, or ticked by hand, starting with the players); what each will get (dice still to roll shown as such, conditions wearing off); CALL, with a count, then previewed again. Everyone the panel could choose is previewed once, so ticking asks the server nothing more. An answer that isn't a list of rests shows no panel rather than crashing.
  • sheets/restCalls.ts: the requests, the NPC tokens on the map being viewed (a battle map's floor shown, or the city, as the map's own controls decide), who is chosen, what the server is asked for, and how a change reads.
  • AdminPanel passes each panel's map NPCs into TTRPG_SYSTEM.

Summary

Test plan

  • Tested locally
  • Tests pass

Pre-merge checklist

Code quality:

  • Code follows project style
  • No breaking changes (or clearly documented)
  • No console errors or warnings

Version & Release:

  • Version bumped? If releasing to users, update:
    • frontend/package.json version
    • docker-compose.yml APP_VERSION
    • CHANGELOG.md with release notes
  • GitHub Actions will auto-tag Docker images with the new version

Before merging to main:

  • All tests passing
  • PR reviewed and approved
  • Branch is up to date with main
  • No merge conflicts

Related issues

Approved mockup docs/mockups/builder-rests.html (2026-10-09), stage 3.
Under a custom game, TTRPG_SYSTEM gains a RESTS panel for the GM and
granted editors (a built-in game's rests stay its own buttons, and its
panel never asks).

- components/GameRestsPanel.tsx: one of the game's rests; who rests
  (every player character, the NPCs on the map being viewed too, or
  ticked by hand, starting with the players); what each will get (dice
  still to roll shown as such, conditions wearing off); CALL, with a
  count, then previewed again. Everyone the panel could choose is
  previewed once, so ticking asks the server nothing more. An answer
  that isn't a list of rests shows no panel rather than crashing.
- sheets/restCalls.ts: the requests, the NPC tokens on the map being
  viewed (a battle map's floor shown, or the city, as the map's own
  controls decide), who is chosen, what the server is asked for, and
  how a change reads.
- AdminPanel passes each panel's map NPCs into TTRPG_SYSTEM.
@over2take
over2take merged commit a877894 into feature/system-builder Oct 10, 2026
4 checks passed
@over2take
over2take deleted the sb/4f5-game-tab-rests branch October 10, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant