(BUG) Wishful Baton/Black Market Interaction

[XK920XK]

Client: 2.62.0.4268:#1861
Card: Black Market
Card Number: Team Up 134
Expected Action: when active dark pokemon with 3 or less dark energy with a wishful baton is KO the energies are suppose to be moved to a bench pokemon first and before any prizes are taken thus disabling the stadium effect.
Actual Action: Even if all dark energies are moved to bench pokemon from wishful baton the stadium still treats the active as if it has a dark energy attached and reduce prizes taken.
Steps to Reproduce: KO any dark pokemon with a wishful baton attached and move the dark energies attached off of it. 

Additional Notes: This was a ruling that just got clarified like 2-3 weeks ago, updates on this ruling can be found the compendium updated april 4 2019

[RobRatt]

So others don't have to look it up....

 

Black Market Stadium:  When a Darkness Pokémon (yours or your opponent's) that has any Darkness Energy attached to it is Knocked Out by damage from an opponent's attack, that player takes 1 fewer Prize card.

 

Q.  If Black Market {*} is in play, and an Active Darkness Pokemon with up to 3 Darkness energy and a Wishful Baton is Knocked Out by damage from an attack, can the player move all of the Darkness Energy from that Pokemon to another Pokemon and still get Black Market {*}'s effect?
A.  Sorry, but no. Taking prizes is the last step when a Pokemon is knocked out; so after all the Darkness Energy is moved, the opponent would not take one fewer Prize card. (Mar 28, 2019 TPCi Rules Team)

 

Edited April 20, 2019 by RobRatt

[RobRatt]

We should have looked at the Known Issues list.  Oops.  This is already there.

• Black Market Prism Star (TEU #134): The effect of this card does not consistently function if an effect such as Exp. Share removes all {D} Energy from a {D} Pokemon that has been Knocked Out by damage from an opponent's attack before that Pokemon leaves play.

[Mod_Alder]

Hello XK920XK, I'm sorry to hear you ran into a bug. Thank you Rob for updating us all that this bug is in the known bugs list, which means the development team will fix it as soon as they can.