TheManaDrain.com
November 21, 2025, 10:10:18 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Calendar Login Register  
Pages: [1]
  Print  
Author Topic: Aggress - new keyword ability  (Read 1203 times)
orgcandman
Full Members
Basic User
***
Posts: 552


Providence protects children and idiots

orgcandman
View Profile WWW
« on: August 13, 2007, 08:42:15 am »

------------------------------------------------
502.50
Aggress

502.50a
Aggress is a triggered ability that triggers during the Declare Attackers Step. (See rule 308, "Declare Attackers Step"). "Aggress" means "Whenever attackers are declared, this creature may be declared as an attacker."

502.50b
A creature declared as an attacker this way may be assigned blockers by the defending player during the "Declare Blockers Step"

502.50c
Aggress modifies combat rules...

------------------------------------------------

The premise: I can attack on my opponents turn, whenever he declares attackers. His attackers will be attacking me, and my attacker(s) will be attacking him. We declare blockers, etc..

I'm not quite sure how to correctly word this into the game so that it correctly modifies sections 308, 309, and 310. A better rules guru will have to help.

I see this as primarily a W and R ability.

The basic d00d with aggress:
-----------------------------------------
Block Me Plz        -        1WR
Creature - Warrior
Aggress
2/1
-----------------------------------------
Logged

Ball and Chain
Quote from: jdizzle
Congrats to the winners, but as we all know, everyone who went to this tournament was a winner
Quote from: iamfishman
Just to clarify...people name Aaron are amazing
Anusien
Adepts
Basic User
****
Posts: 3669


Anusien
View Profile
« Reply #1 on: August 13, 2007, 08:55:52 am »

I'm not even sure this would work, but I definitely wouldn't post a rules snippet as if it were from the CR, since those numbers can change at any date.

Can you talk a little bit more about why you want to do this, what benefits you think it has?  I mean, it messes with something pretty fundamental, and I'd like to hear your thoughts on why that's good.

Also, you realize that this guy can attack while tapped, Pacifismed, etc, right?  (I think, would have to double check).
Logged

Magic Level 3 Judge
Southern USA Regional Coordinator

Quote from: H.L. Mencken
The urge to save humanity is almost always a false front for the urge to rule.
Harlequin
Full Members
Basic User
***
Posts: 1860


View Profile
« Reply #2 on: August 13, 2007, 09:44:17 am »

I think better acknowledgement of what exactly this does is needed. 

1) It allows the creature to attack or block while tapped.
2) it allows the creature to bipass normal summoning sickeness requirements as well as Pascifism effects
3) It allows a creature to attack and block in the same round, so its vigilance-esque.

So its actually really really powerful.  To make this a more versitile keyword I would add a cost.  Keeping in mind that the cost on a spesific creature like the 2/1 you propose the cost could be {0} or some other non-mana cost (like discarding a card or paying life).

Now look at provoke.  Provoke untaps a target creature and forces it to block.  It could (in terms of rules) not have the creature untap, but for clearity and general sense-making it untaps the provoked creature. 

Forcing the creature into combat adds additional rule bagage, and questionable interactions Pascifism, Propaganda, Silent Arbitor, etc ... would all have to be address and evaluated.  Also say, if I attack with a single creature with pro-red and you Aggress a red creature ... can it block?

Proposal:

Aggress [cost]

At the begining of combat you may pay the Aggress Cost, if you do untap this creature, it gains Haste and must attack or block this turn if able. 
At the end of combat if the Aggress cost was paid this turn, tap this creature.

Ok so its got a few differances like for example, if you have something like Whipcorder (tap target creature) it would still work as a valid answer to Aggress.  Also ability that prevent creatures for attacking or blocking will still prevent Aggress.  Also it could have negative synergy with something like Vigilance... but I think the re-tapping is nessisary if not only for multiplayer (where vigilance is stronger than normal). 

It also adds the ability to use a {T} ability multiple times in a round.  You could theoretically, use the {T} in the first main, then {T} again durring pre-combat (meaning it wouldn't attack), and then AGAIN use the {T} durring your oppoent's turn after thier pre-combat.  So giving Aggress to a creature with a built in {T} ability is probably not smart.  However, allowing this to mini-combo with a card like Quicksilver Dagger or Fire Whip is probably fine.
« Last Edit: August 13, 2007, 09:46:56 am by Harlequin » Logged

Member of Team ~ R&D ~
Norm4eva
Full Members
Basic User
***
Posts: 1072

The87thBombfish
View Profile
« Reply #3 on: August 19, 2007, 09:58:33 am »

I'm pretty sure this changes SO many rules of combat that it's probably a bit nightmarish.
First of all, attackers/blockers have classically all been declared simultaneously during the proper step of the combat phase.  If both AP and IAP are declaring attackers and blockers, that pretty much adds another couple of steps to the combat phase which is already the most complex aspect of the game when it comes to correct priority passing, etc.
Then, since combat damage is assigned all at once, Aggress seems to lend itself to the occasional tie game.  Someone does the math wrong and alphas only to 'lose' to random aggress guy that gets Aether Vial'd in.  Kind of dumb.
I think this could make an interesting drawback for a creature, if worded slightly differently...

Impatient Ogre
G

Creature - Ogre

Aggress - Impatient Ogre must attack or block each turn if able.  If it does, untap it after combat.

"Bullocks 'n' fudge!  Where's the fight?!"
3/2

It's kind of huge.  But it also HAS to block that White Knight when it comes over, and will be swiftly taken down.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 1.207 seconds with 21 queries.