Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The tokens created by Hunted Dragon display Banding in addition to first strike #548

Open
silasary opened this issue Jul 10, 2018 · 6 comments
Open

Comments

@silasary
Copy link
Member

@silasary silasary commented Jul 10, 2018

Reported in by Auron-Barlock in #Support channel.

What is the expected behaviour of the card?

  • When Hunted Dragon enters the battlefield, target opponent creates three 2/2 white Knight creature tokens with first strike.

What is the actual behaviour of the card?

  • That opponent creates three 2/2 white Knight creature tokens with first strike and banding.

Screenshot
image
image

Please provide a list of affected cards
Affects: [Hunted Dragon]

Card Images

@BackAlleyG
Copy link
Collaborator

@BackAlleyG BackAlleyG commented Jul 12, 2018

This is simply just a graphical bug. Updating the post along with adding screenshots

@PennyDreadfulBot
Copy link
Collaborator

@PennyDreadfulBot PennyDreadfulBot commented Sep 10, 2019

Still bugged according to wizzerinus in match 221354772.

@PennyDreadfulBot PennyDreadfulBot moved this from 3.4.104.2027 to 3.4.111.4007 in Verification Sep 10, 2019
@stash86
Copy link
Collaborator

@stash86 stash86 commented Nov 30, 2019

Still bugged

@silasary silasary changed the title The tokens created by Hunted Dragon have Banding in addition to first strike The tokens created by Hunted Dragon display Banding in addition to first strike Dec 1, 2019
@silasary silasary moved this from 3.4.111.4007 to 3.4.112.4019 in Verification Dec 1, 2019
@stash86 stash86 moved this from 3.4.112.4019 to 3.4.114.4048 in Verification Jun 6, 2020
@PennyDreadfulBot
Copy link
Collaborator

@PennyDreadfulBot PennyDreadfulBot commented Jul 20, 2020

Still bugged according to Vainfire in match 231505783.

@PennyDreadfulBot PennyDreadfulBot moved this from 3.4.114.4048 to 3.4.115.4054 in Verification Jul 20, 2020
@PennyDreadfulBot
Copy link
Collaborator

@PennyDreadfulBot PennyDreadfulBot commented Aug 2, 2020

Still bugged according to PureOhms in match 231905784.

@PennyDreadfulBot PennyDreadfulBot moved this from 3.4.115.4054 to 3.4.116.4059 in Verification Aug 2, 2020
@PennyDreadfulBot
Copy link
Collaborator

@PennyDreadfulBot PennyDreadfulBot commented Aug 31, 2020

Still bugged according to Rydyell in match 232727167.

@PennyDreadfulBot PennyDreadfulBot moved this from 3.4.116.4059 to 3.4.116.4065 in Verification Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Verification
  
3.4.116.4065
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants