All reports
wizardsgrimoire_displayed reports
#112313: "Soul Pact draws cards for damage from Reckless Attack"
fixed: Bug has been fixed
1
What is this report about?
What happened ? Please select from below
Rules: a rule of the game has not been respected
Detailed description
• Which part of the rules was not respected by the BGA adaptation
Expected Result:
Soul Pact - in accordance with the spell description - only allows drawing of cards based on damage from instant attack spells.
Actual Result:
Soul Pact allows drawing of cards based on damage from Reckless Attack, which is a delayed attack spell.
Notes:
The card description states: If the previous spell you cast this turn was an instant attack spell, gain mana equal to the damage dealt by that spell.• Is the rules violation visible on game replay? If yes, at which move number?
Yes, move 37 to 39.• What is your browser?
Google Chrome v120
Report history
Lim-Dul • Bug has not been reproduced by delopers yet:
25. Jan 2024 10:36 • i.imgur.com/XXcsTBc.png
To be checked if this interaction was incorrect for other delayed activation spells like Doom Drop.
To be checked if this interaction was incorrect for other delayed activation spells like Doom Drop.
Lim-Dul • Bug has not been reproduced by delopers yet:
25. Jan 2024 10:39 • Steps to reproduce:
* Put any mana card (preferably a 4) on Reckless Attack, have Soul Pact in your repertoire
* Next turn, after the cooldown phase, immediately cast Soul Pact after the damage from Reckless Attack has been resolved.
* Put any mana card (preferably a 4) on Reckless Attack, have Soul Pact in your repertoire
* Next turn, after the cooldown phase, immediately cast Soul Pact after the damage from Reckless Attack has been resolved.
MGoulet • Bug has been confirmed by developers:
26. Jan 2024 17:14 •
26. Jan 2024 17:17 •
26. Jan 2024 19:51 • Confirmed
Forget to check the "instant" activation (only check if type = attack)
Forget to check the "instant" activation (only check if type = attack)
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.