As you may have gathered from my meandering introduction, today we will be talking about Legion Warboss<\/a>. For two generic mana and one red, this Borosian (Borosi? Borosite?) bruiser is a 2\/2 with Mentor who, at the beginning of combat on your turn, creates a 1\/1 Goblin token (with a free dose of haste until end of turn), which must attack that combat if able. Specifically, we\u2019re going to be looking hard at those last two words: \u201cIf able\u201d. When isn\u2019t the token forced to attack?<\/p>\n Some examples are obvious. If the token becomes tapped somehow- for example, if your opponent has a Kinjalli\u2019s Sunwing<\/a> out- then it\u2019s not able to attack. Tapped creatures can\u2019t attack. But what if your opponent somehow flashes out Luminous Bonds <\/a> onto your token? It both can\u2019t<\/strong> attack and must<\/strong> attack! As you\u2019ve probably guessed, Luminous Bonds \u201cwins\u201d and the token won\u2019t attack, but the reason is quite interesting. When deciding whether your declaration of attackers is legal, there are two things you need to keep in mind: “Restrictions” (basically, anything saying “this can\u2019t attack” and variants thereof, like “can’t attack alone”) and “Requirements” (“attacks each combat if able” and variants). When you\u2019re declaring your attackers, you have to fulfill as many REQUIREMENTS as you can, without violating any RESTRICTIONS. If there’s a setup that fulfills 3 out of 3 requirements but violates 1 restriction, and another that fulfills only 1 requirement but violates zero restrictions, only the latter is a legal attack. This is also true of declaring blockers (which is why your Relentless Raptor<\/a> doesn’t have to block your opponent’s fliers- it can’t<\/em>!), it just comes up much less often.<\/p>\n