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

Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, incorrectly use the power and toughness of the either one of the creatures tapped for conspire instead of the sacrificed creature #414

Open
silasary opened this issue Apr 10, 2018 · 1 comment

Comments

@silasary
Copy link
Member

@silasary silasary commented Apr 10, 2018

From Bug Blog.
Affects: [Life's Legacy], [Momentous Fall]

Bug Blog Text: Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, such as [Life's Legacy] and [Momentous Fall], incorrectly look at the power and toughness of the last creature clicked for conspire.

@vorpal-buildbot vorpal-buildbot changed the title Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, such as [Life's Legacy] and [Momentous Fall], incorrectly look at the power and toughness of the last creature clicked for conspire. Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, such as Life's Legacy and Momentous Fall, incorrectly look at the power and toughness of the last creature clicked for conspire. Apr 10, 2018
@stash86 stash86 added this to 3.4.114.4047 in Verification Jun 1, 2020
@stash86 stash86 changed the title Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, such as Life's Legacy and Momentous Fall, incorrectly look at the power and toughness of the last creature clicked for conspire. Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, incorrectly use the power and toughness of the last creature clicked for conspire instead of the sacrificed creature Jun 1, 2020
@stash86
Copy link
Collaborator

@stash86 stash86 commented Jun 1, 2020

So I just tested this bug. It's not always use the p/t of the last creature tapped for conspire. So some Combinations I found in my tests

Combinations where the system will use first creature's p/t

  • I tapped a 3/3 first, then a 2/4. The system will use 3/3
  • I tapped a 3/3 first, then a 2/1. The system will use 3/3
  • I tapped a 3/3 first, then a 0/2. The system will use 3/3
  • I tapped a 2/4 first, then a 1/2. The system will use 2/4

Combinations when the system will use later creature's p/t

  • I tapped a 3/3 first, then a 1/1. The system will use 1/1
  • I tapped a 1/1 first, then a 3/3. The system will use 3/3
  • I tapped a 2/4 first, then a 0/3. The system will use 0/3

They aren't random, but I can't find the pattern yet. But definitely not based on the order of the creatures being tapped to pay conspire cost

@stash86 stash86 changed the title Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, incorrectly use the power and toughness of the last creature clicked for conspire instead of the sacrificed creature Cards cast with conspire that require a player to sacrifice a creature as an additional cost to cast, incorrectly use the power and toughness of the either one of the creatures tapped for conspire instead of the sacrificed creature Jun 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Verification
  
3.4.114.4047
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants