rpg-embate-forge

RPG Embate Forge — assemble a runnable non-combat challenge

What this skill is for

A desafio is the non-combat sibling of encontro: a Victory Points challenge (or a single dramatic check) resolved by skills, not swords. This skill realizes it in Foundry end-to-end — a challenge journal the GM runs from, an optional scene, the live skill-check rolls, the VP track as a clock, and a one-click runner macro that rolls the challenge for you — reusing the scene compiler but driven by the challenge's VP structure. Content comes from the desafio note body + relations; you format and run it, you don't invent the challenge.

Workflow

1. Journal. Write the challenge via create-quest-journal used generically (the only journal-create tool — see rpg-journal-forge/references/journal-mapping.md), folderName: "Challenges/<subsystem>" (e.g. Challenges/Influence — the nested path groups challenges by subsystem; foundry-mcp ≥ 0.12.0 creates the hierarchy). Prefer existing: search-journals/list-journals by title first; if it exists, update-quest-journal instead of duplicating. Build pages from the desafio body: Structure (subsystem · format · vp_target · thresholds · per-roll awards), DCs (the DC table), Degrees & fail-forward, and a player-facing Read-aloud page. Content is HTML, not Markdown (the MCP strips Markdown) — use the quest classes: <div class="readaloud"> for player text, <div class="gmnote"> for GM-only, <h2 class="spaced"> for sections. Record journalId.
2. Scene (conditional). If desafio.location resolves to a local, delegate to rpg-scene-forge (prefer existing by name, else generate-under-confirmation, then light for mood). Record sceneId. If there is no local — most social/research challenges — skip scenes; a council debate needs no battlemap.
3. VP clock. For a VP challenge, add a clock page to the journal mirroring a relogio (name, segments = vp_target, filled = current VP, status). Give the page a stable name and seed an initial vp flag (flags.foundry-mcp-bridge.vp = 0) so the runner macro (step 5) has a fixed pageId to advance — the macro keeps VP authoritative in that flag and mirrors it as a ▰▱ bar in the page text. Without the macro, the clock is a journal page the GM advances by hand as VP accrue (there is no dedicated clock MCP tool); state that. For scale: single-check, skip the clock entirely.
4. Live: request the rolls. For each beat, request-player-rolls. rollType = skill (or custom for a formula / a skill Foundry doesn't list by that name); rollTarget = the skill (e.g. diplomacy, acrobatics, intimidation); targetPlayer = the player/character; flavor = the beat + its DC; rollModifier for a circumstance bonus from preparation. Visibility is mandatory: request-player-rolls requires userConfirmedVisibility: true, so establish public vs. private (isPublic) before each call — ask if the GM hasn't said. Map the result's degree to the VP award and narrate the fail-forward consequence; advance the clock page. (This is the manual, one-roll-at-a-time path; step 5 packages the whole loop as a hotbar macro.)
5. Runner macro (offer it). Install a one-click GM macro that runs the whole challenge, via the create-macro MCP tool (foundry-mcp ≥ 0.10.0). Bake this desafio's data — vp_target, the award map, the beats (skill + DC), thresholds, and the clock journalId/pageId — into the template in references/embate-macro.md. The macro is hybrid: on run it asks who rolls — GM rolls for the selected party (rolls each token's chosen skill, reads the degree, awards VP) or send to the players (posts an @Check button, collects each player's own roll via a createChatMessage hook) — then maps every degree of success to VP via the award map and advances the VP clock page automatically, firing threshold/fail-forward notes as VP crosses them. Offer to pin it: a global hotbarSlot (every scene), or — when the desafio has a local whose scene was ensured in step 2 — bind it to that scene via sceneName (foundry-mcp ≥ 0.11.0) so it shows on the GM bar only while that challenge's map is open and clears on leave. Pass flags.foundry-mcp-bridge.challengeId. Record the returned macroId. For scale: single-check, the macro is a single roll with clock: null (no track). The macro and step 4 are two front-ends for the same rules — install the macro for re-triggerable, self-contained play; use bare request-player-rolls for an ad-hoc one-off.
6. Serialize + manifest. Serialize any scene writes (the universal parallel-write rule). Record { journalId, sceneId?, clockPage?, macroId?, status:"built" } in the manifest desafio row; a built challenge (with journalId) is skipped on re-run. Any skill that can't be mapped to a rollType goes to openDecisions.