Several triggered abilities do not respect range of influence.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
>> 801.7. A triggered ability doesn’t trigger unless its trigger event happens entirely within the range of influence of its source’s controller.
Example: In a game in which all players have range of influence 1, Alex is seated to the left of Rob. Rob controls two Auras attached to Alex’s Runeclaw Bear: One with the trigger condition “Whenever enchanted creature becomes blocked,” and one with the trigger condition **“Whenever enchanted creature becomes blocked by a creature.”** Alex’s Runeclaw Bear attacks the player to Alex’s left and becomes blocked. The ability of Rob’s first Aura triggers because the entire event (Runeclaw Bear becomes blocked) happens within Rob’s range of influence. **The ability of Rob’s second Aura doesn’t trigger, however, because that event includes the blocking creature, which is out of Rob’s range.**
> I think this means that combat calligrapher should not trigger since only the blocker is within Combat Calligrapher's owner's range of influence, the attacker is not.
_Originally posted by @Alex-Vasile in https://github.com/magefree/mage/issues/8580#issuecomment-1183553707_
Other cards like Jolene, the Plunder Queen will create tokens for the attacking player even if they are outside the range of influence of Jolene's controller as long as the defender is within it.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the triggered-ability implementations for Combat Calligrapher and Jolene, the Plunder Queen, then compare their behavior with rule 801.7 and the range-of-influence handling. Done means affected abilities consistently respect the source controller’s range, including cases where attackers, blockers, or created-token recipients are outside that range.
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
- 35/100