It is currently 27 Apr 2024, 09:10
   
Text Size

Shandalar - Program Bugs

Prompt bar cardname doesn't follow stack-based triggers priority between Durable Handicraft and Era of Innovation (not a bug)

 

Don't know if this is an issue known from the stack-based triggers feature or from the individual cards themselves Durable Handicraft and Era of Innovation so here is the situation :

- Durable Handicraft and Era of Innovation are in the bf with 2 City of Brass and 1 Ornithopter in hand with 6 Energy Counters

Image

- Ornithopter is cast from hand, both enchantments trigger

Image

- Caster want to activate Durable Handicraft 1st but not Era of Innovation so Durable Handicraft purple trigger is selected

Image

Durable Handicraft effect is put on the stack but Era of Innovation effect resolve 1st and game ask for it before Durable Handicraft one

Comments

Posted by Korath » 12 Dec 2016, 19:04

So to summarize:Correct?

If so, then this is working as designed. You can't put just some triggers on the stack and have them resolve; if a player is getting priority, all triggers that are waiting to get put on the stack get put on the stack, without a chance to do anything in between. Steps #4 and #5, which happen immediately after #3 without you having to do anything, areOnly then does Durable Handicraft's trigger resolve.

When you click on a purple trigger card displayed on the bf, you're selecting it to be put on the stack, so the first one you click on is the last to resolve. Manalink (and previous Shandalar) have trained you to do triggers backwards. Hence the extra paragraph about trigger ordering in the release post.

Alternately, if you're expecting the costs to be paid at announcement, this is still working as designed - unlike spells or abilities, these costs and similar choices are (almost) always paid at announcementresolution. The exceptions are choosing targets and declaring how effects like Bogardan Hellkite's or Verdurous Gearhulk's get divided.

(It doesn't particularly matter for this pair of cards, though: you can still decline to pay the cost of the first trigger to resolve, by clicking Cancel, and then pay the cost of the second. This should work even if you have the mana already floating in your pool.)
Last edited by Korath on 13 Dec 2016, 11:23, edited 1 time in total.
Reason: announcement->resolution

Posted by stassy » 13 Dec 2016, 05:41

Ok, so that is intended for priority, just need to pay attention to prompt then

Ticket details

  • Ticket ID: 1297
  • Project: Shandalar
  • Status: Not a bug
  • Component: Duel Engine
  • Project version: Gemcutter's Guild 1
  • Priority: Normal
  • Severity: Normal
  • Assigned to: stassy
  • Reported by: stassy
  • Reporter's tickets: List all tickets
  • Reported on: 12 Dec 2016, 17:48
  • Last visited by Korath » 06 Sep 2017, 21:17.
 

Login Form