Prowess: Difference between revisions
Jump to navigation
Jump to search
(no prowess since ixalan block) |
|||
| Line 14: | Line 14: | ||
Prowess was designed by [[Jonathon Loucks]] during the second [[Great Designer Search]]. <ref>{{TumblrRef|author=[[Mark Rosewater]]|URL=http://markrosewater.tumblr.com/post/148030670263/todays-my-birthday-so-may-i-ask-for-trivia-on-my|title=Trivia on my favorite mechanic, prowess?|tumblr-title=Blogatog|date=July 26, 2016}}</ref>. Creatures with the Prowess trigger get +1/+1 until end of turn when a non-creature spell is cast by their controller. | Prowess was designed by [[Jonathon Loucks]] during the second [[Great Designer Search]]. <ref>{{TumblrRef|author=[[Mark Rosewater]]|URL=http://markrosewater.tumblr.com/post/148030670263/todays-my-birthday-so-may-i-ask-for-trivia-on-my|title=Trivia on my favorite mechanic, prowess?|tumblr-title=Blogatog|date=July 26, 2016}}</ref>. Creatures with the Prowess trigger get +1/+1 until end of turn when a non-creature spell is cast by their controller. | ||
Prowess is secondary in [[red]] and tertiary in [[white]].<ref>{{NewRef|making-magic/evergreen-eggs-ham-2015-06-08|Evergreen Eggs & Ham|[[Mark Rosewater]]|June 8, 2015}}</ref><ref>{{NewRef|feature/magic-origins-mechanics-article-2015-06-22|''Magic Origins'' Mechanics Article|[[Matt Tabak]]|June 22, 2015}}</ref><ref name="Color Pie 2017">{{NewRef|making-magic/mechanical-color-pie-2017-2017-06-05|Mechanical Color Pie 2017|[[Mark Rosewater]]|June 5, 2017}}</ref> [[Mark Rosewater]] has admitted that Prowess has more design issues than the average evergreen mechanic.<ref>{{TumblrRef|author=[[Mark Rosewater]]|URL=http://markrosewater.tumblr.com/post/166084435723/mark-prowess-has-only-been-majorly-on-more-than|title=Is Prowess harder to develop than originally concepted?|tumblr-title=Blogatog|date=October 05, 2017}}</ref> Because of this, prowess has lost its evergreen status.<ref>{{TumblrRef|author=[[Mark Rosewater]]|URL=http://markrosewater.tumblr.com/post/174424076108/mark-we-havent-seen-prowess-in-ixalan|title=We haven't seen Prowess in ''Ixalan'', ''Dominaria'', or ''Battlebond''. Is Prowess not being used anymore?|tumblr-title=Blogatog|date=May 30, 2018}}</ref> | Prowess is secondary in [[red]] and tertiary in [[white]].<ref>{{NewRef|making-magic/evergreen-eggs-ham-2015-06-08|Evergreen Eggs & Ham|[[Mark Rosewater]]|June 8, 2015}}</ref><ref>{{NewRef|feature/magic-origins-mechanics-article-2015-06-22|''Magic Origins'' Mechanics Article|[[Matt Tabak]]|June 22, 2015}}</ref><ref name="Color Pie 2017">{{NewRef|making-magic/mechanical-color-pie-2017-2017-06-05|Mechanical Color Pie 2017|[[Mark Rosewater]]|June 5, 2017}}</ref> [[Mark Rosewater]] has admitted that Prowess has more design issues than the average evergreen mechanic.<ref>{{TumblrRef|author=[[Mark Rosewater]]|URL=http://markrosewater.tumblr.com/post/166084435723/mark-prowess-has-only-been-majorly-on-more-than|title=Is Prowess harder to develop than originally concepted?|tumblr-title=Blogatog|date=October 05, 2017}}</ref> Problems typically included the density of cast triggers (overlapping with Historic triggers in [[Dominaria]]), weakness in creature dense-sets (such as for the Merfolk tribal theme in [[Ixalan]]), and coverage of artifacts and enchantments being unfavorable (such as for the Izzet League in [[Guilds of Ravnica]] wanting instants and sorceries), leading to the keyword constantly being pulled off sets. Because of this, prowess has lost its evergreen status.<ref>{{TumblrRef|author=[[Mark Rosewater]]|URL=http://markrosewater.tumblr.com/post/174424076108/mark-we-havent-seen-prowess-in-ixalan|title=We haven't seen Prowess in ''Ixalan'', ''Dominaria'', or ''Battlebond''. Is Prowess not being used anymore?|tumblr-title=Blogatog|date=May 30, 2018}}</ref> | ||
==Rules== | ==Rules== | ||
Revision as of 02:54, 23 October 2018
| Prowess | |
|---|---|
| Keyword Ability | |
| Type | Triggered |
| Introduced | Khans of Tarkir |
| Last used | Hour of Devastation |
| Reminder Text | Prowess (Whenever you cast a noncreature spell, this creature gets +1/+1 until end of turn.) |
| Storm Scale | 1[1] |
| Statistics |
38 cards 52.6%  28.9%  13.2%  5.3% |
| Scryfall Search | |
| keyword:"Prowess" | |
Prowess is a keyword ability that was introduced as the clan-specific mechanic for the Jeskai Way in Khans of Tarkir [2][3] and Fate Reforged. [4] R&D's need for blue to get a combat-relevant keyword that wasn't about evasion caused Prowess to become evergreen in Magic Origins.
Description
Prowess was designed by Jonathon Loucks during the second Great Designer Search. [5]. Creatures with the Prowess trigger get +1/+1 until end of turn when a non-creature spell is cast by their controller.
Prowess is secondary in red and tertiary in white.[6][7][8] Mark Rosewater has admitted that Prowess has more design issues than the average evergreen mechanic.[9] Problems typically included the density of cast triggers (overlapping with Historic triggers in Dominaria), weakness in creature dense-sets (such as for the Merfolk tribal theme in Ixalan), and coverage of artifacts and enchantments being unfavorable (such as for the Izzet League in Guilds of Ravnica wanting instants and sorceries), leading to the keyword constantly being pulled off sets. Because of this, prowess has lost its evergreen status.[10]
Rules
Rulings
- Any spell you cast that doesn't have the type creature will cause prowess to trigger. If a spell has multiple types, and one of those types is creature (such as an artifact creature), casting it won't cause prowess to trigger. Playing a land also won't cause prowess to trigger.
- Prowess triggers only once for any spell, even if that spell has multiple types.
- Prowess goes on the stack on top of the spell that caused it to trigger. It will resolve before that spell.
- Once it triggers, prowess isn't connected to the spell that caused it to trigger. If that spell is countered, prowess will still resolve.
Examples
References
- ↑ Template:NewRef
- ↑ Template:NewRef
- ↑ Template:NewRef
- ↑ Template:NewRef
- ↑ Error on call to {{WebRef}}: Parameters url and title must be specifiedMark Rosewater (July 26, 2016). "". Tumblr.
- ↑ Template:NewRef
- ↑ Template:NewRef
- ↑ Template:NewRef
- ↑ Error on call to {{WebRef}}: Parameters url and title must be specifiedMark Rosewater (October 05, 2017). "". Tumblr.
- ↑ Error on call to {{WebRef}}: Parameters url and title must be specifiedMark Rosewater (May 30, 2018). "". Tumblr.
