Rules of protection. Protection in Magic: The Gathering – A Comprehensive Guide to MTG’s Evergreen Keyword Ability

What is protection in Magic: The Gathering. How does protection work in MTG. What are the rules for protection in Magic. When was protection introduced in MTG. How has protection evolved over time in Magic: The Gathering. What are the limitations of protection in MTG. How does protection affect gameplay in Magic: The Gathering.

Understanding Protection in Magic: The Gathering

Protection is an evergreen keyword ability in Magic: The Gathering that grants a permanent or player resistance against certain types of magic. This powerful mechanic has been a part of the game since its inception in Alpha and continues to shape gameplay strategies to this day.

How does protection work in MTG? Protection is defined by a set of rules often remembered by the acronym DEBT:

• D – Can’t be Damaged by sources with the specified quality
• E – Can’t be Enchanted, Equipped, or Fortified by permanents with the specified quality
• B – Can’t be Blocked by creatures with the specified quality
• T – Can’t be Targeted by spells or abilities from sources with the specified quality

This comprehensive set of defenses makes protection a formidable ability in the game, but it’s important to note that it doesn’t provide complete immunity.

The History and Evolution of Protection in MTG

When was protection introduced in MTG? Protection has been a part of Magic: The Gathering since the game’s first set, Alpha, released in 1993. However, its status and usage have fluctuated over the years.

How has protection evolved over time in Magic: The Gathering? Let’s explore its journey:

1. Alpha to Magic Origins: Frequent use as an evergreen keyword
2. Post-Magic Origins: Demoted to deciduous status
3. Modern Horizons and Core Set 2020: Return to probationary evergreen status
4. 2021 onwards: Officially reinstated as an evergreen keyword

This evolution reflects the ongoing balancing act between the ability’s power and its complexity for newer players.

The Mechanics of Protection: Rules and Applications

What are the rules for protection in Magic? Protection is typically written as “Protection from [quality],” where the quality can be a color, card type, or even a specific characteristic. The current reminder text, as of Core Set 2020, states: “This [object] can’t be blocked, targeted, dealt damage, enchanted, or equipped by anything [quality].”

Are there any exceptions to protection in MTG? Yes, there are some important limitations:

• Protection doesn’t prevent effects that don’t target or deal damage
• Global effects still affect creatures with protection
• Protection doesn’t remove auras or equipment already attached before it was gained

Protection and Color: A Special Relationship

Why is protection often associated with colors in MTG? Protection from specific colors is one of the most common forms of this ability. It represents a magical resistance to certain types of magic, often aligned with the game’s color pie philosophy.

How does protection from a color work in practice? For example, a creature with protection from blue:

• Cannot be blocked by blue creatures
• Takes no damage from blue sources
• Cannot be enchanted or equipped by blue permanents
• Cannot be targeted by blue spells or abilities

This color-based protection adds a layer of strategic depth to deck-building and gameplay.

Protection’s Impact on MTG Gameplay and Strategy

How does protection affect gameplay in Magic: The Gathering? Protection can significantly influence game dynamics:

• It can make certain creatures virtually unstoppable against specific deck types
• It forces opponents to find creative solutions to deal with protected permanents
• It can nullify entire strategies if used correctly

Why is understanding protection crucial for MTG players? Mastering the intricacies of protection can provide a significant competitive edge. It allows players to:

1. Build more resilient decks
2. Anticipate and counter opponent strategies
3. Create powerful combos and synergies

Protection in Different MTG Formats

How does the use of protection vary across different MTG formats? While protection is an evergreen mechanic, its prevalence and impact can differ:

• Standard: Protection appears regularly but is carefully balanced
• Modern and Legacy: Older cards with powerful protection effects can shape the meta
• Commander: Protection can be a potent tool in multiplayer politics
• Limited: Protection can be a game-changing ability in draft and sealed formats

This versatility across formats underscores protection’s enduring relevance in the game.

Notable Cards with Protection in MTG History

Which cards have made the most significant impact with their protection abilities? Several cards have left a lasting mark on the game:

• Mother of Runes: Grants protection at instant speed
• True-Name Nemesis: Has protection from a chosen player
• Progenitus: Has protection from everything
• Emrakul, the Promised End: Protection from instants
• Knight of Grace: Conditional protection from black

These cards demonstrate the diverse applications of protection and its potential to create uniquely powerful effects.

The Future of Protection in Magic: The Gathering

What does the future hold for protection in MTG? With its return to evergreen status, protection is likely to remain a significant part of the game. However, designers continue to explore new ways to balance its power and complexity:

• Simplified versions like those on Sungold Sentinel and Skrelv, Defector Mite
• More specific and situational forms of protection
• Integration with new mechanics and card designs

As Magic: The Gathering evolves, protection will undoubtedly continue to adapt, challenging players and shaping the game’s strategic landscape.

Protection: A Double-Edged Sword

Is protection always beneficial in MTG? While protection is generally a powerful ability, it can sometimes be a drawback. For instance:

• Protection from a color can prevent beneficial effects of that color from affecting the creature
• In multiplayer formats, having protection from an ally’s color can hinder cooperative strategies
• Some cards, like Troll Ascetic, have protection from their controller’s spells, limiting interaction

This duality adds another layer of strategic consideration when using cards with protection.

Protection and the Color Pie

How does protection fit into MTG’s color pie? While protection can appear in any color, it’s primarily associated with white. Each color typically gets protection from its enemy colors or concepts:

• White: Protection from various colors or creature types
• Blue: Protection from red or creatures
• Black: Protection from white or nonblack
• Red: Protection from blue or white
• Green: Protection from artifacts or blue

This distribution aligns with each color’s strengths and weaknesses in the Magic color pie.

Protection in Multiplayer Formats

How does protection function in multiplayer games of MTG? In formats like Commander, protection can have interesting implications:

• Protection from a color can create temporary alliances
• Cards like True-Name Nemesis become more balanced
• Global protection effects can significantly alter the game state

Players must carefully consider the political ramifications of protection in these formats.

Countering Protection: Strategies and Techniques

How can players deal with protection in MTG? While protection is powerful, it’s not unbeatable. Some strategies include:

• Using colorless spells and abilities
• Employing global effects that don’t target
• Forcing sacrifices or -1/-1 counters
• Removing protection with cards like Bonds of Mortality

Understanding these counters is crucial for any player looking to compete at a high level.

Protection and Set Design

How do MTG designers approach protection when creating new sets? The inclusion of protection in a set requires careful consideration:

• Balancing its power level with the set’s overall theme
• Ensuring it doesn’t overly suppress certain strategies
• Creating interesting interactions with new mechanics

This design process helps maintain the health and diversity of the Magic metagame.

The Role of Protection in Limited Formats

Why is protection particularly impactful in limited formats like draft and sealed? In these environments:

• Color-based protection can be extremely powerful due to limited removal options
• Protection can create unbeatable threats in certain matchups
• It adds an additional layer of consideration during the drafting process

Understanding the value of protection can give players a significant edge in limited tournaments.

Protection and the Evolution of MTG Rules

How have the rules for protection changed over time? The definition and implementation of protection have seen several adjustments:

• Early versions were less clearly defined
• The introduction of the DEBT acronym helped clarify its effects
• Rules updates have fine-tuned interactions with newer mechanics

These changes reflect the ongoing effort to balance protection’s power with clarity and fairness.

The Psychology of Protection in MTG

How does protection affect player psychology in Magic: The Gathering? The presence of protection can significantly impact game dynamics:

• It can create a sense of security for the controlling player
• It may induce frustration or a feeling of helplessness in opponents
• It often forces players to think creatively about solutions

Understanding these psychological aspects can help players leverage protection more effectively in their strategies.

Protection in MTG’s Digital Platforms

How is protection implemented in digital versions of Magic: The Gathering? On platforms like Magic: The Gathering Arena and Magic Online:

• Clear visual indicators show when a permanent has protection
• The game automatically enforces protection rules
• Tooltips and hover effects explain protection’s effects

These digital implementations help reduce confusion and rules violations related to protection.

The Future of Protection Design in MTG

What new forms of protection might we see in future MTG sets? While speculative, some possibilities include:

• Protection from specific card types or subtypes
• Temporary or conditional protection effects
• Protection tied to new mechanics or themes

As Magic continues to evolve, so too will the design space for protection, keeping this classic mechanic fresh and exciting for players.

Protection – MTG Wiki

in:
Keywords/Static, Glossary

Edit this Page

Protection from [quality] is an evergreen keyword ability that grants several different effects to the permanent or player it is affecting. ^[2]

The definition of protection, and the rules backing it, have changed over the course of the game’s history.

Contents

• 1 Description
• 2 History
• 3 Rules
  • 3.1 Variants
• 4 Examples
• 5 References
• 6 External links

Description[]

This ability represents a magical resistance to certain types of magic, often a specific color.^[3] It was introduced in Alpha and saw frequent use through Magic Origins. Protection was previously dropped from evergreen status to deciduous status but as of 2021 is officialy back to evergreen status. It’s an ability primary in white that can show up in other colors, usually with protection from something the color dislikes (an enemy color, artifacts for green, etc.).^[4]

Protection is commonly misunderstood as complete exemption from permanents, and effects created by cards, with the specified quality. However, protection is defined by a relatively narrow set of rules, which are often communicated using the mnemonic acronym DEBT. The permanent or player with protection cannot be:

• Damaged by sources with the specified quality. (All such damage is prevented.)
• Enchanted, equipped, or fortified by permanents with the specified quality.
• Blocked by creatures with the specified quality.
• Targeted by spells with the specified quality, or by abilities from sources of that quality.

The current (as of Core Set 2020) reminder text for protection largely reflects this, reading “This [object] can’t be blocked, targeted, dealt damage, enchanted, or equipped by anything [quality].”

History[]

Despite intuitive expectations for the keyword, protection was recognized as potentially complicated even prior to the game’s release. Early attempts to define protection led the Alpha designers to invent the fundamental concept of targeting.^[5] However, even the original rulebook described it informally, offering only examples of things that protection would prevent. ^[6]

A creature with protection from one or more colors of magic cannot be affected by any magic of those colors. For example, a creature with protection from blue cannot be blocked by blue creatures, dealt damage by blue creatures, or enchanted, damaged, or otherwise affected by blue cards. Damage done by such a creature cannot be prevented using blue cards. Note that the creature does not have this ability until it is successfully summoned. If, for example, you are summoning a creature with protection from blue magic, your rival can still cast a blue interrupt that affects the summoning spell.

Protection was excluded from core sets beginning with Sixth Edition and returned to them in Ninth Edition, reflecting concerns about its complexity for newer players. With the release of Magic Origins, protection was demoted from evergreen to deciduous, relegating it to only occasional use.^[7][8] In the three blocks following that decision, it was used only once: on Emrakul, the Promised End.

Later, it reappeared in Modern Horizons.^[9] It also returned in Core Set 2020, where it was back to evergreen on a probationary status.^[2][10][11] Although it doesn’t show up in every set, protection became officially evergreen again in 2021.^[12][13]

Two white cards have a condensed version of Protection: Sungold Sentinel and Skrelv, Defector Mite. Both have an activated ability that grants hexproof from a color and prevent blocking by creatures of that color, making up about half of protection’s text and most of its gameplay. As with many gameplay design choices, the “prevent damage” aspect is left out as to avoid the “infinite blocking” scenario.

Rules[]

From the glossary of the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

Protection

A keyword ability that provides a range of benefits against objects with a specific quality. See rule 702.16, “Protection.”

From the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

• 702.16. Protection
  • 702.16a Protection is a static ability, written “Protection from [quality].” This quality is usually a color (as in “protection from black”) but can be any characteristic value or information. If the quality happens to be a card name, it is treated as such only if the protection ability specifies that the quality is a name. If the quality is a card type, subtype, or supertype, the ability applies to sources that are permanents with that card type, subtype, or supertype and to any sources not on the battlefield that are of that card type, subtype, or supertype. This is an exception to rule 109.2.
  • 702.16b A permanent or player with protection can’t be targeted by spells with the stated quality and can’t be targeted by abilities from a source with the stated quality.
  • 702.16c A permanent or player with protection can’t be enchanted by Auras that have the stated quality. Such Auras attached to the permanent or player with protection will be put into their owners’ graveyards as a state-based action. (See rule 704, “State-Based Actions.”)
  • 702.16d A permanent with protection can’t be equipped by Equipment that have the stated quality or fortified by Fortifications that have the stated quality. Such Equipment or Fortifications become unattached from that permanent as a state-based action, but remain on the battlefield. (See rule 704, “State-Based Actions.”)
  • 702.16e Any damage that would be dealt by sources that have the stated quality to a permanent or player with protection is prevented.
  • 702.16f Attacking creatures with protection can’t be blocked by creatures that have the stated quality.
  • 702.16g “Protection from [quality A] and from [quality B]” is shorthand for “protection from [quality A]” and “protection from [quality B]”; it behaves as two separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B].
  • 702.16h “Protection from all [characteristic]” is shorthand for “protection from [quality A],” “protection from [quality B],” and so on for each possible quality the listed characteristic could have; it behaves as multiple separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B], [quality C], and so on.
  • 702.16i “Protection from each [set of characteristics, qualities, or players]” is shorthand for “protection from [A],” “protection from [B],” and so on for each characteristic, quality, or player in the set. It behaves as multiple separate protection abilities.
  • 702.16j “Protection from everything” is a variant of the protection ability. A permanent or player with protection from everything has protection from each object regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities and can’t be enchanted by Auras. Such a permanent can’t be equipped by Equipment, fortified by Fortifications, or blocked by creatures. All damage that would be dealt to such a permanent or player is prevented.
  • 702.16k “Protection from [a player]” is a variant of the protection ability. A permanent or player with protection from a specific player has protection from each object that player controls and protection from each object that player owns not controlled by another player, regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities the specified player controls and can’t be enchanted by Auras that player controls. Such a permanent can’t be equipped by Equipment that player controls, fortified by Fortifications that player controls, or blocked by creatures that player controls. All damage that would be dealt to such a permanent or player by sources controlled by the specified player or owned by that player but not controlled by another player is prevented.
  • 702.16m Multiple instances of protection from the same quality on the same permanent or player are redundant.
  • 702.16n Some Auras both give the enchanted creature protection from a quality and say “this effect doesn’t remove” either that specific Aura or all Auras. This means that the specified Auras aren’t put into their owners’ graveyards as a state-based action. If the creature has other instances of protection from the same quality, those instances affect Auras as normal.
  • 702.16p One Aura (Benevolent Blessing) gives the enchanted creature protection from a quality and says the effect doesn’t remove certain permanents that are “already attached to” that creature. This means that, when the protection effect starts to apply, any objects with the stated quality that are already attached to that creature (including the Aura giving that creature protection) will not be put into their owners’ graveyards as a state-based action. Other permanents with the stated quality can’t become attached to the creature. If the creature has other instances of protection from the same quality, those instances affect attached permanents as normal.

Variants[]

Protection is written in the form “protection from…”, followed by one or more qualities or characteristics. The first examples of protection are from colors, but many other variants have been printed.

Last Updated for Core Set 2021

1. ↑ ^{a b} Tsabo Tavoc originally had “protection from Legends”, but this was errataed to “protection from legendary creatures” when “Legend” ceased to be a creature subtype.

Examples[]

Example

White Knight
Creature — Human Knight
2/2
First strike (This creature deals combat damage before creatures without first strike.)
Protection from black (This creature can’t be blocked, targeted, dealt damage, or enchanted by anything black.)

References[]

1. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.
2. ↑ ^{a b} Mark Rosewater (June 18, 2019). “Did R&D change their mind on protection being removed from evergreen?”. Blogatog. Tumblr.
3. ↑ Mark Rosewater (May 29, 2019). “If a creature has protection from a color will that protection prevent effects such as Infest?”. Blogatog. Tumblr.
4. ↑ Mark Rosewater (June 5, 2017). “Mechanical Color Pie 2017”. magicthegathering.com. Wizards of the Coast.
5. ↑ Brady Dommermuth (June 01, 2009). “Mechanically Inclined”. magicthegathering.com. Wizards of the Coast.
6. ↑ John Carter (December 25, 2004). “The Original Magic Rulebook”. magicthegathering.com. Wizards of the Coast.
7. ↑ Mark Rosewater (June 8, 2015). “Evergreen Eggs & Ham”. magicthegathering.com. Wizards of the Coast.
8. ↑ Mark Rosewater (August 06, 2017). “I noticed that there have been very few cards with “Protection” in recent sets.”. Blogatog. Tumblr.
9. ↑ Matt Tabak (May 31, 2019). “Modern Horizons Mechanics”. magicthegathering.com. Wizards of the Coast.
10. ↑ Mark Rosewater (June 18, 2019). “Protection is back? i mean, i love that, but how come?”. Blogatog. Tumblr.
11. ↑ Mark Rosewater (June 24, 2019). “Core Than Meets The Eye”. magicthegathering.com. Wizards of the Coast.
12. ↑ Mark Rosewater (October 18, 2021). “Mechanical Color Pie 2021 Changes”. magicthegathering.com. Wizards of the Coast.
13. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.

External links[]

• A Planeswalker’s Primer for Magic 2011: Protection (Video). Magic: The Gathering. YouTube.

Community content is available under CC BY-NC-SA 2.5 unless otherwise noted.

• Fantasy

Protection – MTG Wiki

in:
Keywords/Static, Glossary

Edit this Page

Protection from [quality] is an evergreen keyword ability that grants several different effects to the permanent or player it is affecting. ^[2]

The definition of protection, and the rules backing it, have changed over the course of the game’s history.

Contents

• 1 Description
• 2 History
• 3 Rules
  • 3.1 Variants
• 4 Examples
• 5 References
• 6 External links

Description[]

This ability represents a magical resistance to certain types of magic, often a specific color.^[3] It was introduced in Alpha and saw frequent use through Magic Origins. Protection was previously dropped from evergreen status to deciduous status but as of 2021 is officialy back to evergreen status. It’s an ability primary in white that can show up in other colors, usually with protection from something the color dislikes (an enemy color, artifacts for green, etc.).^[4]

Protection is commonly misunderstood as complete exemption from permanents, and effects created by cards, with the specified quality. However, protection is defined by a relatively narrow set of rules, which are often communicated using the mnemonic acronym DEBT. The permanent or player with protection cannot be:

• Damaged by sources with the specified quality. (All such damage is prevented.)
• Enchanted, equipped, or fortified by permanents with the specified quality.
• Blocked by creatures with the specified quality.
• Targeted by spells with the specified quality, or by abilities from sources of that quality.

The current (as of Core Set 2020) reminder text for protection largely reflects this, reading “This [object] can’t be blocked, targeted, dealt damage, enchanted, or equipped by anything [quality].”

History[]

Despite intuitive expectations for the keyword, protection was recognized as potentially complicated even prior to the game’s release. Early attempts to define protection led the Alpha designers to invent the fundamental concept of targeting.^[5] However, even the original rulebook described it informally, offering only examples of things that protection would prevent. ^[6]

A creature with protection from one or more colors of magic cannot be affected by any magic of those colors. For example, a creature with protection from blue cannot be blocked by blue creatures, dealt damage by blue creatures, or enchanted, damaged, or otherwise affected by blue cards. Damage done by such a creature cannot be prevented using blue cards. Note that the creature does not have this ability until it is successfully summoned. If, for example, you are summoning a creature with protection from blue magic, your rival can still cast a blue interrupt that affects the summoning spell.

Protection was excluded from core sets beginning with Sixth Edition and returned to them in Ninth Edition, reflecting concerns about its complexity for newer players. With the release of Magic Origins, protection was demoted from evergreen to deciduous, relegating it to only occasional use.^[7][8] In the three blocks following that decision, it was used only once: on Emrakul, the Promised End.

Later, it reappeared in Modern Horizons.^[9] It also returned in Core Set 2020, where it was back to evergreen on a probationary status.^[2][10][11] Although it doesn’t show up in every set, protection became officially evergreen again in 2021.^[12][13]

Two white cards have a condensed version of Protection: Sungold Sentinel and Skrelv, Defector Mite. Both have an activated ability that grants hexproof from a color and prevent blocking by creatures of that color, making up about half of protection’s text and most of its gameplay. As with many gameplay design choices, the “prevent damage” aspect is left out as to avoid the “infinite blocking” scenario.

Rules[]

From the glossary of the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

Protection

A keyword ability that provides a range of benefits against objects with a specific quality. See rule 702.16, “Protection.”

From the Comprehensive Rules (June 16, 2023—The Lord of the Rings: Tales of Middle-earth)

• 702.16. Protection
  • 702.16a Protection is a static ability, written “Protection from [quality].” This quality is usually a color (as in “protection from black”) but can be any characteristic value or information. If the quality happens to be a card name, it is treated as such only if the protection ability specifies that the quality is a name. If the quality is a card type, subtype, or supertype, the ability applies to sources that are permanents with that card type, subtype, or supertype and to any sources not on the battlefield that are of that card type, subtype, or supertype. This is an exception to rule 109.2.
  • 702.16b A permanent or player with protection can’t be targeted by spells with the stated quality and can’t be targeted by abilities from a source with the stated quality.
  • 702.16c A permanent or player with protection can’t be enchanted by Auras that have the stated quality. Such Auras attached to the permanent or player with protection will be put into their owners’ graveyards as a state-based action. (See rule 704, “State-Based Actions.”)
  • 702.16d A permanent with protection can’t be equipped by Equipment that have the stated quality or fortified by Fortifications that have the stated quality. Such Equipment or Fortifications become unattached from that permanent as a state-based action, but remain on the battlefield. (See rule 704, “State-Based Actions.”)
  • 702.16e Any damage that would be dealt by sources that have the stated quality to a permanent or player with protection is prevented.
  • 702.16f Attacking creatures with protection can’t be blocked by creatures that have the stated quality.
  • 702.16g “Protection from [quality A] and from [quality B]” is shorthand for “protection from [quality A]” and “protection from [quality B]”; it behaves as two separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B].
  • 702.16h “Protection from all [characteristic]” is shorthand for “protection from [quality A],” “protection from [quality B],” and so on for each possible quality the listed characteristic could have; it behaves as multiple separate protection abilities. If an effect causes an object with such an ability to lose protection from [quality A], for example, that object would still have protection from [quality B], [quality C], and so on.
  • 702.16i “Protection from each [set of characteristics, qualities, or players]” is shorthand for “protection from [A],” “protection from [B],” and so on for each characteristic, quality, or player in the set. It behaves as multiple separate protection abilities.
  • 702.16j “Protection from everything” is a variant of the protection ability. A permanent or player with protection from everything has protection from each object regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities and can’t be enchanted by Auras. Such a permanent can’t be equipped by Equipment, fortified by Fortifications, or blocked by creatures. All damage that would be dealt to such a permanent or player is prevented.
  • 702.16k “Protection from [a player]” is a variant of the protection ability. A permanent or player with protection from a specific player has protection from each object that player controls and protection from each object that player owns not controlled by another player, regardless of that object’s characteristic values. Such a permanent or player can’t be targeted by spells or abilities the specified player controls and can’t be enchanted by Auras that player controls. Such a permanent can’t be equipped by Equipment that player controls, fortified by Fortifications that player controls, or blocked by creatures that player controls. All damage that would be dealt to such a permanent or player by sources controlled by the specified player or owned by that player but not controlled by another player is prevented.
  • 702.16m Multiple instances of protection from the same quality on the same permanent or player are redundant.
  • 702.16n Some Auras both give the enchanted creature protection from a quality and say “this effect doesn’t remove” either that specific Aura or all Auras. This means that the specified Auras aren’t put into their owners’ graveyards as a state-based action. If the creature has other instances of protection from the same quality, those instances affect Auras as normal.
  • 702.16p One Aura (Benevolent Blessing) gives the enchanted creature protection from a quality and says the effect doesn’t remove certain permanents that are “already attached to” that creature. This means that, when the protection effect starts to apply, any objects with the stated quality that are already attached to that creature (including the Aura giving that creature protection) will not be put into their owners’ graveyards as a state-based action. Other permanents with the stated quality can’t become attached to the creature. If the creature has other instances of protection from the same quality, those instances affect attached permanents as normal.

Variants[]

Protection is written in the form “protection from…”, followed by one or more qualities or characteristics. The first examples of protection are from colors, but many other variants have been printed.

Last Updated for Core Set 2021

1. ↑ ^{a b} Tsabo Tavoc originally had “protection from Legends”, but this was errataed to “protection from legendary creatures” when “Legend” ceased to be a creature subtype.

Examples[]

Example

White Knight
Creature — Human Knight
2/2
First strike (This creature deals combat damage before creatures without first strike.)
Protection from black (This creature can’t be blocked, targeted, dealt damage, or enchanted by anything black.)

References[]

1. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.
2. ↑ ^{a b} Mark Rosewater (June 18, 2019). “Did R&D change their mind on protection being removed from evergreen?”. Blogatog. Tumblr.
3. ↑ Mark Rosewater (May 29, 2019). “If a creature has protection from a color will that protection prevent effects such as Infest?”. Blogatog. Tumblr.
4. ↑ Mark Rosewater (June 5, 2017). “Mechanical Color Pie 2017”. magicthegathering.com. Wizards of the Coast.
5. ↑ Brady Dommermuth (June 01, 2009). “Mechanically Inclined”. magicthegathering.com. Wizards of the Coast.
6. ↑ John Carter (December 25, 2004). “The Original Magic Rulebook”. magicthegathering.com. Wizards of the Coast.
7. ↑ Mark Rosewater (June 8, 2015). “Evergreen Eggs & Ham”. magicthegathering.com. Wizards of the Coast.
8. ↑ Mark Rosewater (August 06, 2017). “I noticed that there have been very few cards with “Protection” in recent sets.”. Blogatog. Tumblr.
9. ↑ Matt Tabak (May 31, 2019). “Modern Horizons Mechanics”. magicthegathering.com. Wizards of the Coast.
10. ↑ Mark Rosewater (June 18, 2019). “Protection is back? i mean, i love that, but how come?”. Blogatog. Tumblr.
11. ↑ Mark Rosewater (June 24, 2019). “Core Than Meets The Eye”. magicthegathering.com. Wizards of the Coast.
12. ↑ Mark Rosewater (October 18, 2021). “Mechanical Color Pie 2021 Changes”. magicthegathering.com. Wizards of the Coast.
13. ↑ Mark Rosewater (March 28, 2022). “Deciduous”. magicthegathering.com. Wizards of the Coast.

External links[]

• A Planeswalker’s Primer for Magic 2011: Protection (Video). Magic: The Gathering. YouTube.

Community content is available under CC BY-NC-SA 2.5 unless otherwise noted.

• Fantasy

Three rules for data protection | Evernote

Privacy Center – PrivacyRegional Information – California – EU General Data Protection Regulation (GDPR) – Brazil – More InformationThree Data Protection RulesPrivacy Notice for Job SeekersMore Privacy Information – Cookie Information – Disclosure Report – Suppliers Services – Privacy Center Updates – Legal Help Home – Terms

• Privacy Center

• Information for specific regions

• Three Data Protection Rules

• Job Seeker Privacy Notice

• Additional privacy information

3 DATA PROTECTION RULES EVERNOTE

• Your information belongs only to you

• Your data is protected

  All information you post to Evernote is private by default. We do not specialize in “big data” and do not try to make money from your information. Our systems automatically analyze your data to enable Evernote features, such as finding and showing related notes, and to bring you information about important features and products that we think can make your Evernote experience better. We never share or sell your data to third parties for advertising purposes.

  Our business model is old fashioned: we only make money if you choose to pay for our great product. This means that trust is our main asset, and maintaining the confidentiality of your data is a fundamental principle of our work.

  Evernote allows you to post and share notes with other people. These are additional features and only you decide whether to use them or not. If you choose to link your Evernote account to one of our partner services, the partner may have access to all or part of your data. When you connect, we’ll let you know what the partner app is accessing in your account, and you can disable it at any time.

  In addition, we have put in place measures to prevent accidental data loss or theft. Everything you put into Evernote is synced and stored in a secure data center with multiple redundant servers, drives, and backup systems physically located elsewhere. Data between Evernote users and servers (and various data centers) is encrypted. Proven technologies such as two-factor authentication are available to all users, and we are constantly looking for ways to improve data protection. We take great care to protect your password, and no one on the Evernote team will ever ask you for it.

  We support the industry’s efforts to promote full transparency regarding data requests from government agencies, and have established a comprehensive legal process for such requests. For more information, see our Transparency Report.

• Your data is portable

Managing branch protection rule – GitHub Documentation

You can create a branch protection rule to enforce certain workflows on one or more branches, such as requesting a review for approval or passing status checks on all pull requests that are merged into a protected branch.

Protected branches are available in public repositories when using GitHub Free and GitHub Free for organizations, and in public and private repositories when using GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub Products.

For a specific branch, all branches, or any branch that matches the name pattern specified using the fnmatch syntax, you can create a branch protection rule in the repository. For example, to protect all branches that contain the word release , you could create a branch rule for *release* .

You can create a rule for all current and future branches in a repository using the wildcard syntax * . Since GitHub uses File::FNM_PATHNAME syntax flag File.fnmatch , * wildcard does not match directory separators ( / ). For example, will match all branches qa/* starting with qa/ and containing a single slash, but will not match qa/foo/bar . You can include any number of slashes after qa with qa/**/* which will match, for example . qa/foo/bar/foobar/hello-world You can also extend the qa string with qa**/**/* using to make the rule more inclusive.

See the fnmatch documentation for more information on syntax options.

If a repository has multiple branch protection rules that refer to the same branches, the rules that specify a specific branch name have the highest priority. If a particular branch name is specified in multiple branch protection rules, the rule created first will have the highest priority.

Branch protection rules that use a special character, such as * , ? or ] are applied in the order they were created, so older rules with those characters take precedence.

To create an exception to an existing branch protection rule, you can create a new rule with a higher priority, such as a rule for a specific branch name.

For more information about each of the available branch protection options, see About Protected Branches.

Note: Only one branch protection rule can be applied at a time. This means that it can be difficult to know which rule will apply if multiple versions of a rule target the same branch. For an alternative to branch protection rules, see About Rule Sets.

When you create a branch protection rule, it is not necessary that the specified branch already exists in the repository.

1. On GitHub.com, go to the main page of the repository.

2. Under the repository name, click Options . If the Options tab is not visible, select the drop-down menu and click the Options button.

3. In the Code and Automation section of the sidebar, click Branches .

4. Next to Branch Protection Rules, click Add Rule.

5. In the Branch Name Template section, enter the name of the branch or template that you want to protect.

6. Optionally enable required pull requests.

   Note: If you select Close old pull request approvals when pushing new commits and (or ) Require approval of the latest checked push option, manually creating a pull request merge commit and pushing it directly to the protected branch will fail, if the content of the merge does not exactly match the merge generated by GitHub for the pull request.

   In addition, when using these options, the review approval will be rejected as stale if the merge base makes new changes after the review is submitted. A merge base is a commit that is the last common ancestor between a topic branch and the base branch. If the merge base changes, the pull request cannot be merged until someone approves the work again.

   • Under “Protect relevant branches”, select Require a pull request before merging .

   • Optionally, to require approval before merging the pull request, select Require approval .

     Select the Required number of approvals before merge drop-down menu, and then select the number of approval checks you want to require on the branch.

   • Optionally, to skip pull request approval when pushing a code change commit to a branch, select option Ignore obsolete pull request assertions when submitting new commits .

   • If you want to require code owner review if the pull request affects code with an assigned owner, select option Require code owner review . For more information, see About code owners.

   • Optionally, to allow certain actors to push code to a branch without creating pull requests when required, select Allow certain subjects to skip creating pull requests . Then, find and select the actors you want to be allowed to skip creating a pull request.

   • If the repository is part of an organization, optionally select the option Restrict ability to skip pull request checks . Then, in the search box, find and select the actors that are allowed to deny pull request checks. For more information, see Rejecting Pull Request Validation.

   • Optionally, to require anyone other than the last one to submit to a branch to approve a pull request before merging, select Require last checked submission approval. For more information, see About Protected Branches.

7. Enable mandatory status checks if necessary. For more information, see About status checks.

   • Select option Require status checks before merging .
   • To ensure that pull requests are tested with the latest code in the protected branch, select the option Require branches up to date before merging .
   • In the search box, search for status checks by selecting the checks you need.

8. If necessary, select option Require contention before merging .

9. If necessary, select the option Require signing of commits .

10. If necessary, select parameter Require linear history .

11. If you want to merge pull requests using a merge queue, select the option Require use of merge queue . For more information about merge queues, see Managing the Merge Queue.

    Tip: The pull request merge queue feature is currently in public beta and is subject to change.

12. If you want to select the environments to which changes must be successfully deployed before merging, select the Require successful deployment before merging option, and then select the environments.

13. Make the branch read-only if necessary.

    • Select Lock branch .
    • If necessary, select Enable fork synchronization to enable fork synchronization.

14. If necessary, select Do not allow bypassing the above parameters .

15. Optionally enable branch restrictions on public repositories owned by a GitHub Free organization and all repositories owned by an organization using GitHub Team or GitHub Enterprise Cloud.

    • Select the option Restrict users who can push to the respective branches .
    • Optionally, to also restrict the creation of corresponding branches, select Restrict submissions that create corresponding branches .
    • In the search box, search for and select the people, teams, or applications that will have permission to push a protected branch or create a corresponding branch.

16. Optionally, in the “Rules that apply to everyone, including administrators” section, select the option Allow push .

    Then choose who can push to the branch.

    • Select All to allow anyone with at least write permissions to the repository, including administrators, to push to the branch.

    • Select Specify who can push to allow only certain principals to push to the branch. Then find and select those subjects.

      For more information about pushing, see About Protected Branches.

17. If necessary, select parameter Allow deletion .

18. Click the button Create .

1. On GitHub.com, go to the main page of the repository.

2. Under the repository name, click Options . If the Options tab is not visible, select the drop-down menu and click the Options button.

3. In the Code and Automation section of the sidebar, click Branches .