Implement Channel Points Twungeon MVP
This commit is contained in:
+12
-10
@@ -35,7 +35,7 @@ The MVP should demonstrate that multiple Twitch viewers can:
|
||||
- encounter and fight a basic enemy,
|
||||
- heal themselves,
|
||||
- die and remain inactive for the current floor,
|
||||
- resurrect through Bits,
|
||||
- resurrect through a configured Channel Points reward,
|
||||
- advance the entire party by reaching the exit,
|
||||
- revive dead players on floor advancement,
|
||||
- and reset the run when all participating players die.
|
||||
@@ -81,7 +81,7 @@ When a valid `!spawn` command is received:
|
||||
|
||||
Only one active character may exist per Twitch user.
|
||||
|
||||
A follower who has died on the current floor cannot use `!spawn` to bypass death. That player must wait for either a Bits resurrection or advancement to the next floor.
|
||||
A follower who has died on the current floor cannot use `!spawn` to bypass death. That player must wait for either a Channel Points resurrection or advancement to the next floor.
|
||||
|
||||
### 3.4 Twitch Identity Binding
|
||||
|
||||
@@ -153,7 +153,7 @@ It must provide clear confirmation of significant game actions and state changes
|
||||
- AutoGuard blocks,
|
||||
- self-heal use,
|
||||
- player death,
|
||||
- Bits resurrection,
|
||||
- Channel Points resurrection,
|
||||
- Goblin aggro or return behavior when useful,
|
||||
- floor advancement,
|
||||
- dormant-state changes,
|
||||
@@ -489,22 +489,24 @@ There is no timed automatic resurrection.
|
||||
|
||||
A dead player returns to play only through:
|
||||
|
||||
1. immediate Bits resurrection, or
|
||||
1. immediate Channel Points resurrection, or
|
||||
2. another living player reaching the next floor.
|
||||
|
||||
---
|
||||
|
||||
## 17. Bits Resurrection
|
||||
## 17. Channel Points Resurrection
|
||||
|
||||
A dead player may use the Twitch Bits mechanism to resurrect immediately during the current floor.
|
||||
A dead player may redeem the configured Twitch Channel Points custom reward to resurrect immediately during the current floor.
|
||||
|
||||
Upon successful Bits resurrection:
|
||||
Upon successful Channel Points redemption:
|
||||
|
||||
- the player's dead state is removed,
|
||||
- the player returns to active play on the current floor,
|
||||
- and the player may participate in subsequent Player Phases.
|
||||
|
||||
The exact Bits price is not required to be finalized before implementation of the core MVP.
|
||||
The broadcaster configures the reward cost in Twitch. Twungeon identifies the reward by its stable reward ID and does not duplicate or override its cost in domain code.
|
||||
|
||||
Bits and Cheers are outside the MVP and must not trigger game-state changes.
|
||||
|
||||
---
|
||||
|
||||
@@ -572,7 +574,7 @@ The setup documentation must cover at minimum:
|
||||
- follower eligibility verification,
|
||||
- receiving and processing `!spawn`,
|
||||
- chat-to-Extension Twitch identity binding,
|
||||
- Bits resurrection event setup,
|
||||
- Channel Points custom reward and redemption EventSub setup,
|
||||
- separation and protection of secrets,
|
||||
- local/development testing,
|
||||
- live-channel testing,
|
||||
@@ -671,7 +673,7 @@ The MVP is successful if it demonstrates that:
|
||||
22. A surviving player can reach the exit without necessarily killing the Goblin and advance the entire group.
|
||||
23. Dead players return when the floor advances.
|
||||
24. A player who died on the current floor cannot bypass death by using `!spawn`.
|
||||
25. Bits can resurrect the correct dead player during the current floor.
|
||||
25. The configured Channel Points reward can resurrect the correct dead player during the current floor.
|
||||
26. A total-party wipe resets the run to Floor 1.
|
||||
27. Zero active players is distinguished from a total-party wipe.
|
||||
28. An eligible follower who has not died on the current floor can `!spawn` into an otherwise empty current floor.
|
||||
|
||||
Reference in New Issue
Block a user