Rule evolution
Rule 702.26d
Previously numbered 702.23d, 702.24d, 702.25d.
Earliest archived Rules release: 2009-10-01 · 2 wording revisions · 3 renumberings
Earliest archived Rules release702.23dDetails
The phasing event doesn't actually cause a permanent to change zones or control, even though it's treated as though it's not on the battlefield and not under its controller's control while it's phased out. Zone-change triggers don't trigger when a permanent phases in or out. Counters remain on a permanent while it's phased out. Effects that check a phased-in permanent's history won't treat the phasing event as having caused the permanent to leave or enter the battlefield or its controller's control.
Renumbered
702.23d→ 702.24dDetailsPreviously
7. Additional Rules
702. Keyword AbilitiesThen
7. Additional Rules
702. Keyword AbilitiesThe phasing event doesn't actually cause a permanent to change zones or control, even though it's treated as though it's not on the battlefield and not under its controller's control while it's phased out. Zone-change triggers don't trigger when a permanent phases in or out. Counters remain on a permanent while it's phased out. Effects that check a phased-in permanent's history won't treat the phasing event as having caused the permanent to leave or enter the battlefield or its controller's control.
Renumbered
702.24d→ 702.25dDetailsPreviously
7. Additional Rules
702. Keyword AbilitiesThen
7. Additional Rules
702. Keyword AbilitiesThe phasing event doesn't actually cause a permanent to change zones or control, even though it's treated as though it's not on the battlefield and not under its controller's control while it's phased out. Zone-change triggers don't trigger when a permanent phases in or out. Counters remain on a permanent while it's phased out. Effects that check a phased-in permanent's history won't treat the phasing event as having caused the permanent to leave or enter the battlefield or its controller's control.
Wording changed702.25dDetails
The phasing event doesn't actually cause a permanent to change zones or control, even though it's treated as though it's not on the battlefield and not under its controller's control while it's phased out. Zone-change triggers don't trigger when a permanent phases in or out. Tokens continue to exist on the battlefield while phased out. Counters remain on a permanent while it's phased out. Effects that check a phased-in permanent's history won't treat the phasing event as having caused the permanent to leave or enter the battlefield or its controller's control.
Renumbered
702.25d→ 702.26dDetailsPreviously
7. Additional Rules
702. Keyword AbilitiesThen
7. Additional Rules
702. Keyword AbilitiesThe phasing event doesn’t actually cause a permanent to change zones or control, even though it’s treated as though it’s not on the battlefield and not under its controller’s control while it’s phased out. Zone-change triggers don’t trigger when a permanent phases in or out. Tokens continue to exist on the battlefield while phased out. Counters remain on a permanent while it’s phased out. Effects that check a phased-in permanent’s history won’t treat the phasing event as having caused the permanent to leave or enter the battlefield or its controller’s control.
Wording changed702.26dDetails
The phasing event doesn't actually cause a permanent to change zones or control, even though it's treated as though it's not on the battlefield and not under its controller's control while it's phased out. Zone-change triggers don't trigger when a permanent phases in or out. Tokens continue to exist on the battlefield while phased out. Counters and stickers remain on a permanent while it's phased out. Effects that check a phased-in permanent's history won't treat the phasing event as having caused the permanent to leave or enter the battlefield or its controller's control.