Connecting a quest to a challenge
Support lets a Disney Lorcana character contribute to two goals in one turn: quest for lore and strengthen another character. It is not a swap of statistics or permission to challenge immediately. The bonus is temporary Strength; each character retains its own action requirements. Ask both how much Strength you gain and which character should act first.
This guide covers that specific sequence. Review ready, exerted and drying states for normal quest requirements. Our examples use unnamed characters, not a claim that a catalogue product contains Support. The numbers simply make calculations and table announcements easy to check.
What changes and what stays the same
When a character with Support quests, the ability triggers. As it resolves, you may add that character’s Strength to another chosen character’s Strength this turn. The choice is optional and must be legal. Another excludes the source character. The recipient does not have to be ready or dry merely to receive the bonus.
The questing character keeps its Strength. The recipient gains an addition, not a replacement statistic. Support does not increase Willpower or lore value and does not remove marked damage. More Strength does not automatically mean greater durability. Name the statistic before moving a die so that a Strength reminder is not mistaken for healing or extra lore.
Finish the quest before continuing
First check that the character can legally quest. Perform the quest, update lore and handle triggered abilities using the bag rules. Support is not an extra action taken before questing. When its ability resolves, say whether you use it and name the recipient. Finish the relevant effects before declaring another action.
Use a clear routine: questing character, lore gained, Support announcement, chosen other character, final Strength and duration. If several abilities trigger, resolve them in their applicable order instead of treating them as one vague operation. Check restrictions and do not import Magic’s stack into Lorcana.
A two-character example
A has 2 Strength and Support; B has 3 Strength. A can quest legally. After that quest, choose B when Support resolves. With no other modification, B has 5 Strength for the rest of the turn. A keeps 2 Strength: nothing is swapped or physically transferred.
If B is ready, dry and has a legal challenge, it can then challenge with its current 5 Strength. A newly played B does not stop drying because of the bonus. An exerted B does not become ready. Choosing a recipient and checking whether it can act are separate decisions; a legal bonus may still fail to enable your intended action.
Planning consecutive Supports
Order matters with two Support characters. Assume A has 2 Strength, B 3 and C 4; A and B have Support and can quest, with no other modifications. A quests and adds 2 to B, making B 5. B then quests and adds its current 5 Strength to C, making C 9 this turn.
In the reverse order, B first adds 3 to C, making C 7. A then adds 2 to B, but the bonus already granted to C does not grow retroactively. Record each result rather than applying a single overall sum. Keep the final recipient available instead of exerting it too early.
One keyword is not two triggers
Giving Support to a character that already has Support does not create two instances of that keyword. Support does not stack like a keyword followed by +N. Two different characters can nevertheless generate separate Support effects, and their bonuses can increase the same recipient’s Strength this turn.
Separate the keyword from effects already created. A character receiving two bonuses need not have two Supports; its Strength is modified by two effects. Use a clear temporary note without covering the text or confusing it with damage counters.
Track the duration without inventing protection
The bonus lasts until the end of the current turn, not through the opponent’s turn. It is not a permanent counter. When it expires, use the Strength resulting from any other effects still applying. Expiration neither readies the character nor removes its damage.
Our lore and damage tracking method separates the information: lore belongs to a player, damage belongs to a card and a Strength reminder records a temporary effect. Distinct functions make the next turn easy to reconstruct.
Errors to catch in practice
Watch for choosing the quester itself, increasing Willpower, gaining lore from Strength, readying the recipient or keeping the bonus next turn. Another mistake is declaring a challenge before Support has resolved and later changing its Strength retroactively. Plan ahead, but execute actions individually.
Other effects can restrict choices or change statistics. This routine never replaces current card text. In an international game, identify Support by its official keyword, then check the authoritative rules and text instead of guessing from artwork or the product’s language.
Six-question Poke-Geek checklist
Does the quester have Support and permission to quest? Are the quest and lore handled? Is the recipient another legal character? What Strength is added when the ability resolves? What is the final Strength after all bonuses? When should the temporary reminder be removed?
Repeat the three-character example, then reverse the quest order and compare. Browse the Disney Lorcana collection for catalogue formats, checking language and contents separately. Do not assume a product guarantees a particular character.
Pick two characters from your deck and announce the quest, recipient and final Strength before your next action.