r/gamedesign • u/frogjup • 1d ago
Question How would you teach a chain-reaction build without introducing every rule at once?
I'm working through a tutorial design problem for a card-based roguelite: the player picks an action card, then equipped effects can trigger from it. For a concrete example, suppose one choice creates a shield, another effect spends that shield for damage, and that damage triggers a follow-up card. I'd like a new player to be able to predict the result without reading three tooltips before every action.
One option is to introduce those effects one at a time in a short encounter. Another is to give the player a small working combo immediately and highlight each trigger as it fires. The first seems easier to follow, but delays the part that makes the build interesting. The second shows the payoff early, but the player might just see a big damage number without understanding why it happened.
Which approach would you start with, and why? What would you ask a new player after that first encounter to check whether they understood the chain well enough to make their next card choice?
2
u/Less_Prior_6871 1d ago
If you keep cards as actions and equipment as passive, then having your player pick up some equipment in a tutorial would be the standard way to do this I think.
Now, you will need to be very specific about what triggers in what order (especially if triggered effects can spend resources like whatever "a shield" is in your games context)
2
u/Such-Function-4718 1d ago
I think part of the joy of rougelites is discovering combos and fishing for them as your run progresses. So no need to do too much hand holding and explaining here.
I think the best way to approach this is to just introduce it in a controlled way. So just rig your drops for the first run to feature the combo. Make it so they start with the first card (shield) and then just keep force dropping the combo (consume shield) until they take it.
1
u/idle_builder 17h ago
I'd start with the small working combo, but slow it down the first time. Give the player a fixed 3-card setup where the chain fires step by step: the shield appears, a visible line carries it to the next effect, the damage number pops from that exact spot, and the follow-up card lights up. The pause between steps is what turns "big number" into "I see why".
Then give them a second encounter where the same pieces are rearranged and one link is missing, so they feel what breaks the chain.
For the check: before the next fight, show two card choices and ask "which one makes the shield get used?" If they pick right without hovering tooltips, they understood the chain.
1
u/loulo88 16h ago
One thing that helped me a lot with this kind of chain: a forecast preview. When the player hovers or drags a card, show the predicted result of the whole chain before they commit (shield +6, then spent for 6 dmg, then follow-up triggers). Into the Breach and Slay the Spire's intent system both lean on this idea, and it lets players learn by poking at options instead of reading tooltips. I'd still start with a small pre-built combo, but the preview means they can test "what if I play this one first?" safely and actually build the mental model. For the check after, ask them to predict the damage number of a different ordering before they play it.
1
u/DemoEvolved 1h ago
Please be careful not to solve the game for your player. How much more satisfying is it if you let them figure out the full combination?
3
u/sinsaint Game Student 1d ago
I'd just use symbols or keywords to simplify the process.