Editing Trail

Jump to: navigation, search

Warning: You are not logged in.

Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 43: Line 43:
 
Trail can be a weak counter to some attacks, especially when you have a high density of it in your deck. It replaces itself in the case of a discard attack, but may leave you vulnerable to a discard attack. Its usefulness to this end is thus heavily dependent on the number of players: in a two-player game it is a decent counter to {{Card|Militia}} and other typical discard attacks, but in a 4-player game with multiple players playing these attacks, it becomes weak.
 
Trail can be a weak counter to some attacks, especially when you have a high density of it in your deck. It replaces itself in the case of a discard attack, but may leave you vulnerable to a discard attack. Its usefulness to this end is thus heavily dependent on the number of players: in a two-player game it is a decent counter to {{Card|Militia}} and other typical discard attacks, but in a 4-player game with multiple players playing these attacks, it becomes weak.
  
There are fewer cards that do not synergize with Trail, but there are some. Alt-treasure combines poorly with it, because it tends to trigger it after the action phase is completed, when its +Action provides little benefit. Pseudo-trashing or cards with a set-aside dynamic, such as {{Card|Cage}}, {{Card|Crypt}}, {{Card|Native Village}}, or {{Card|Archive}} trigger it neither on setting aside nor returning it to the hand. In general it does not synergize as well with other cards providing draw: Trail-based engines usually work best when the draw is triggered by Trail combining with some other cards. Terminal draw risks drawing Trail dead, and the act of drawing Trail into your hand turns it into just-any [[cantrip]], which weakens it. Although Trail is strong when combined with other cards, a {{Cost|4}}-cost cantrip that does nothing else is inefficient, so any time you are drawing a trail into your hand and not discarding or trashing it, is a time your play is inefficient.
+
There are fewer cards that do not synergize with Trail, but there are some. Alt-treasure combines poorly with it, because it tends to trigger it after the action phase is completed, when its +Action provides little benefit. Pseudo-trashing or cards with a set-aside dynamic, such as {{Card|Cage}}, {{Card|Crypt}}, {{Card|Native Village}}, or {{Card|Archive}} trigger it neither on setting aside nor returning it to the hand. In general it does not synergize as well with other cards providing draw: Trail-based engines usually work best when the draw is triggered by Trail combining with some other cards. Terminal draw risks drawing Trail dead, and the act of drawing Trail into your hand turns it into just-any [[cantrip]], which weakens it. Although Trail is strong when combined with other cards, a {{Cost|4}-cost cantrip that does nothing else is inefficient, so any time you are drawing a trail into your hand and not discarding or trashing it, is a time your play is inefficient.
  
 
Attacks that force players to return cards to the top of the deck also do not trigger it, so {{Card|Clerk}} can be an effective counter or attack against it. {{Card|Warlord}} can sometimes harm Trail-based engines by limiting the number of times it can be played from the hand, although this depends on the nature of the engine: Warlord cannot prevent Trail from being triggered if it is trashed or discarded, so if your engine contains a diverse mix of actions to trigger Trail in different ways, it can have some resilience to Warlord. Trail also does not always fare well against [[junker|junking]] attacks, although it can sometimes handle them in the presence of strong trashers.
 
Attacks that force players to return cards to the top of the deck also do not trigger it, so {{Card|Clerk}} can be an effective counter or attack against it. {{Card|Warlord}} can sometimes harm Trail-based engines by limiting the number of times it can be played from the hand, although this depends on the nature of the engine: Warlord cannot prevent Trail from being triggered if it is trashed or discarded, so if your engine contains a diverse mix of actions to trigger Trail in different ways, it can have some resilience to Warlord. Trail also does not always fare well against [[junker|junking]] attacks, although it can sometimes handle them in the presence of strong trashers.

Please note that all contributions to DominionStrategy Wiki are considered to be released under the Creative Commons Attribution Non-Commercial Share Alike (see DominionStrategy Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)
Personal tools
Namespaces

Variants
Views
Actions
Navigation
Toolbox