79 lines
2.7 KiB
Markdown
79 lines
2.7 KiB
Markdown
# slaywithfriends rules delta (canon vs web)
|
|
|
|
This file records intentional and current differences between:
|
|
- Canon: `docs/rules-canon.md`
|
|
- Web implementation target: `docs/rules-web-mvp.md`
|
|
|
|
Use statuses:
|
|
- `implemented` - enforced in app
|
|
- `planned` - accepted but not yet built
|
|
- `deferred` - intentionally skipped for now
|
|
|
|
## Current deltas
|
|
|
|
1. Setup shuffle details for non-combat decks
|
|
status: planned
|
|
canon: Summons, Daze, and Status are not shuffled in setup.
|
|
web: MVP setup may simplify by treating some decks uniformly.
|
|
impact: low if card order is random anyway, but should be corrected for parity.
|
|
|
|
2. Act transition deck swapping granularity
|
|
status: planned
|
|
canon: only act-specific decks are replaced; relic/potion/boss-relic handling differs.
|
|
web: MVP may use a simplified deck replacement step.
|
|
impact: medium; affects progression balance and content pools.
|
|
|
|
3. Summons transition behavior between Acts
|
|
status: planned
|
|
canon: switch to next Act's Summons deck (not shuffled).
|
|
web: currently documented ambiguously in prior markdown.
|
|
impact: medium; can change encounter difficulty distribution.
|
|
|
|
4. Playing Copies edge-case constraints
|
|
status: planned
|
|
canon: X-cost copies use original X; only one multi-play effect can apply per card at a time.
|
|
web: MVP doc currently describes the basic copy model only.
|
|
impact: medium-high for combo correctness.
|
|
|
|
5. Cross-character Stance/Orb caveat (Prismatic Shard)
|
|
status: planned
|
|
canon: additional restrictions apply (including Watcher stance caveat).
|
|
web: simplified handling.
|
|
impact: low-medium; niche but rules-visible.
|
|
|
|
6. Status card mode specifics
|
|
status: planned
|
|
canon: Status card behavior depends on icon mode from source enemy.
|
|
web: MVP currently treats status at a higher level.
|
|
impact: medium for enemy fidelity.
|
|
|
|
7. Potion limit overflow options
|
|
status: planned
|
|
canon: when at potion cap, player must skip/pass/use-discard before gaining.
|
|
web: MVP requires explicit UI decision flow.
|
|
impact: medium UX and correctness.
|
|
|
|
8. Act IV key acquisition details
|
|
status: deferred
|
|
canon: includes Burning Elite token replacement, Sapphire reveal/discard flow, and key-specific setup effects.
|
|
web: not required for first playable Act loop.
|
|
impact: low for Act I MVP, high for Act IV parity.
|
|
|
|
9. Daily Climb and custom modifiers
|
|
status: deferred
|
|
canon: full positive/negative modifier system.
|
|
web: out of MVP scope.
|
|
impact: none for base mode.
|
|
|
|
10. Achievements and full FAQ interactions
|
|
status: deferred
|
|
canon: includes broad edge-case rulings and achievement list.
|
|
web: omitted in MVP.
|
|
impact: none on base gameplay if core engine is correct.
|
|
|
|
## Promotion criteria (move planned -> implemented)
|
|
|
|
A delta can be marked `implemented` when:
|
|
- it is represented in rules docs,
|
|
- enforced in engine logic,
|
|
- and covered by at least one deterministic test.
|