Obsolete Keywords
Post MTG Forge Related Programming Questions Here
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
3 posts
• Page 1 of 1
Obsolete Keywords
by friarsol » 15 Sep 2010, 20:33
(This originally started off as a post regarding the Spike keyword, but really applies for any obsolete keywords.)
The Spike keyword is really a combination of two different keywords. etbCounter which exists and abPutCounter which probably will in the near future.
In most cases we're making code blocks into keywords, so those blocks just get removed from the code.
But some of the ones I've been thinking about doing are combining keywords that can now be a single entry due to Ability_Cost being able to handle the cost portion.
There's a bunch of different addMana abilities which can easily fit into a single keyword
"Remove three spore counters from CARDNAME: Put a 1/1 green Saproling creature token onto the battlefield." should be generalized into an abCreateToken
So how about we make a list of keywords that should be generalized, or some of the ones that need Ability_Cost added to them?
Once we have a decent list, it should be pretty easy to convert the old keywords into a unified one, or take an existing keyword and just add usage of Ability_Cost to it.
The Spike keyword is really a combination of two different keywords. etbCounter which exists and abPutCounter which probably will in the near future.
In most cases we're making code blocks into keywords, so those blocks just get removed from the code.
But some of the ones I've been thinking about doing are combining keywords that can now be a single entry due to Ability_Cost being able to handle the cost portion.
There's a bunch of different addMana abilities which can easily fit into a single keyword
- Code: Select all
{cost}, Sacrifice CARDNAME: Add {mana} to your mana pool.
{cost}, {tap}: add {mana}
paintap:{damage number}:{mana}
tap: add 1
tap: add B
tap: add G
tap: add R
tap: add U
tap: add W
"Remove three spore counters from CARDNAME: Put a 1/1 green Saproling creature token onto the battlefield." should be generalized into an abCreateToken
So how about we make a list of keywords that should be generalized, or some of the ones that need Ability_Cost added to them?
Once we have a decent list, it should be pretty easy to convert the old keywords into a unified one, or take an existing keyword and just add usage of Ability_Cost to it.
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Obsolete Keywords
by zerker2000 » 15 Sep 2010, 22:28
Just saying:friarisol wrote:There's a bunch of different addMana abilities which can easily fit into a single keyword
These should already be treated astap: add 1
tap: add B
tap: add G
tap: add R
tap: add U
tap: add W
- Code: Select all
{cost}, {tap}: add {mana}
O forest, hold thy wand'ring son
Though fears assail the door.
O foliage, cloak thy ravaged one
In vestments cut for war.
--Eladamri, the Seed of Freyalise
Though fears assail the door.
O foliage, cloak thy ravaged one
In vestments cut for war.
--Eladamri, the Seed of Freyalise
- zerker2000
- Programmer
- Posts: 569
- Joined: 09 May 2009, 21:40
- Location: South Pasadena, CA
- Has thanked: 0 time
- Been thanked: 0 time
Re: Obsolete Keywords
by Chris H. » 16 Sep 2010, 12:41
There are some other cases where we may want to at some point combine a number of keywords into a single keyword. The attacking/blocking keywords for example.
I suspect that tap: add {mana} may have been one of the first keywords to be written.
I suspect that tap: add {mana} may have been one of the first keywords to be written.
-
Chris H. - Forge Moderator
- Posts: 6320
- Joined: 04 Nov 2008, 12:11
- Location: Mac OS X Yosemite
- Has thanked: 644 times
- Been thanked: 643 times
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 46 guests