magefree / magefree/mage

Animate Dead / Necromany do not work properly with Astral Dragon

Open
#10,060 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2.4k
Forks
940
Avg merge
2d 12h
Merged PRs (30d)
160

Description

Tokens created by Astral Dragon that copy Animate Dead / Necromancy doesn't work as intended:

What's currently happening with the creature copies of Animate Dead on XMage:
- The Animate Dead creature tokens enter the battlefield.

What SHOULD happen with the creature copies of Animate Dead:
- The tokens should never get created due to rule 111.5.

> 111.5 If a spell or ability would create a token, but a rule or effect states that a permanent with one or more of that token’s characteristics can’t enter the battlefield, the token is not created. Similarly, if an effect would create a token that is a copy of an instant or sorcery card, no token is created.

What's currently happening with the creature copies of Necromany on XMage:
- The tokens enter the battlefield and reanimate their respective targets, all of them remain on the battlefield.

What SHOULD happen with the creature copies of Necromancy:
- That Creature Necromancy token would enter the Battlefield, Trigger, Target a Card in a Graveyard.
- Put said Card onto the Battlefield.
- The Creature Necromancy becomes an Aura.
- The Creature Necromancy Aura fails to attach to the Creature.
- The Creature Necromancy Aura is put into the Graveyard.
- The Creature Card that was put onto the Battlefield is sacrificed to the Necromancy Delayed Trigger.

Rules explaining the above interaction:

Rules

- 303.4d. An Aura can't enchant itself. If this occurs somehow, the Aura is put into its owner's graveyard. An Aura that's also a creature can't enchant anything. If this occurs somehow, the Aura becomes unattached, then is put into its owner's graveyard. (These are state-based actions. See rule 704.) An Aura can't enchant more than one object or player. If a spell or ability would cause an Aura to become attached to more than one object or player, the Aura's controller chooses which object or player it becomes attached to.

- 303.4f. If an Aura is entering the battlefield under a player's control by any means other than by resolving as an Aura spell, and the effect putting it onto the battlefield doesn't specify the object or player the Aura will enchant, that player chooses what it will enchant as the Aura enters the battlefield. The player must choose a legal object or player according to the Aura's enchant ability and any other applicable effects.

- 111.5. If a spell or ability would create a token, but a rule or effect states that a permanent with one or more of that token's characteristics can't enter the battlefield, the token is not created. Similarly, if an effect would create a token that is a copy of an instant or sorcery card, no token is created.

- 704.5m. If an Aura is attached to an illegal object or player, or is not attached to an object or player, that Aura is put into its owner's graveyard.

Screen Shot 2023-02-23 at 12 04 59 AM

Screen Shot 2023-02-23 at 12 06 26 AM

Contributor guide

No contributing guide indexed for this repository

Research direction

No source files, tests, or entry points are named. Start by reproducing the Astral Dragon copies of Animate Dead and Necromancy described in the issue, then trace token creation, Aura state-based actions, and delayed sacrifice handling; done means the interactions follow rules 111.5, 303.4d, 303.4f, and 704.5m.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.