New Version

I’m glad to announce that there is a new version of MTG Forge that has 90 new cards which brings the grand total number of cards up to 1691. New features include land stacking, equipment, persist, and flashback. Multiple lands are grouped together making the user interface less cluttered. Equipment cards include Loxodon Warhammer, Lightning Greaves and the insane Skullclamp which should spice up your favorite deck.

Other changes include "champion" creatures like Wren’s Run Packmaster. The changeling champion cards are also included: Changeling Hero, Changeling Berserker, and Changeling Titan which can fit into almost any white, red, or green deck. Blue mages can control the board with Capsize while green mages can hold their own with Survival of the Fittest. (I love blue versus green.)

And as a hint, in the deck editor you can put the new card first by selecting the menu option "Sort By" then "Newer cards first". This puts the cards that were recently added first in the lineup. This option doesn’t sort by the date the card was printed but by the location that the card is in according to the file cards.txt. New cards are added to the beginning of cards.txt. (I keep meaning to add a sort option that sorts cards by their set: Alara Reborn, Conflux, Shard of Alara, etc…)

All of the credit for this new version goes to Dennis and Rob from MTG Forge's forum. Thanks and keep up the good work.

MTG Forge 06-12
Readme (also included in the above file)

p.s.
You may also want to download the official card token artwork. It isn't necessary but most of them look pretty good.
Tokens (1.5 MB)

And if you can't download the card pictures, this file has most of them.
Card Pictures (41 MB)

Rules Changes - My Opinion

The biggest rules change is combat. (In case you missed the memo, Wizards has updated a few things.) Last night I read and re-read the combat section but I’m not sure that I fully understand it. While the old way of doing combat was more complicated, I had spent many hours fully understanding all of the intricacies. Much as if the rules of chess were changed and pawns could now move diagonally, I’m not sure how the new combat rules differ greatly from the old ones.

The new combat rules deal damage as the damage is assigned, so there is not a step between assigning and dealing damage. That seems simple enough but the rules about multiple blockers is still fuzzy in my mind. The new rules state that the attacking players puts the blocking creatures in order, assigning them 1,2,3 and so on and then deals damage to them in that order.

Personally I don’t see a difference between putting the blockers in order (1,2,3) and not putting them in order. You will still kill the creatures that you want to. Hopefully the nuances of this new combat scheme will be explained in further detail. I would love a computerized demo like the one that is packaged with the 10th Edition starter kit and hopefully Wizards will put out a new version when Magic 2010 comes out. You can download the Windows demo here (85 MB).

Magic 2010 Rules Changes

There have been rumors about rules changes for the upcoming Magic 2010 set and Wizards has finally put up an announcement. I’ll go over the high points.

1. Simultaneous Mulligans – because technically one player mulliganed and then the second player mulliganed.

2. Terminology Changes – "In Play" becomes "Battlefield", "Removed from the game" becomes "Exile"

"Cast" is being reinstated as the verb used when referring to the act of playing spells or types of spells. "Play" is being kept as the verb associated with lands (and with cards of unspecified types). Activated abilities are also no longer "played" but rather "activated.

3. Changing "end-of-turn step" to the "end step" – to help clarify the difference between "at end of turn" and "until end of turn" effects.

4. Mana Pools now empty at the end of every step and phases, instead of only at the end of every phase. And mana burn is no more which helps a few cards and hurts other cards like Spectral Searchlight.

5. Token Ownership was changed from "the controller of the effect that put it into play" to "the player under whose control the token entered the battlefield".

6. Combat Damage No Longer Uses the Stack - As soon as damage is assigned in the combat damage step, it is dealt. This is probably the biggest change.

7. Deathtouch and Lifelink are being changed from a triggered ability into a static ability.

Hopefully MTG Forge can implement all of these changes. The biggest difficulty will be changing how combat damage is assigned. What do you think of these rule changes?

Personally I don't have much to say about the rules changes. Some of them will help out new players. I don't think the rules changes will really improve the game but every little bump in the right direction (if this is the right direction) is a good thing. The weather changes, the winds blow, and Wizards changes a few rules, nothing more, nothing less.

What is a Card?

MTG Forge has a card object which represents a real-world, cardboard card. This sound simple but it gets a little bit complicated. Let's say that I want to destroy one of your Forest's but you want to bounce it, so you have to know which specific Forest card that I am targeting. In the real world you can just point to the specific Forest, while a computerized game of Magic has to show the user. Magic Online uses nicely drawn arrows while MTG Forge just tells you the targeting card name and its unique number.

At the beginning of the game MTG Forge gives each card a unique number much like the old Shandalar game. Whenever a card is copied, the card's unique number is copied also. In MTG Forge every time a card's attributes need to be reset, like when a creature is going to the graveyard, a new copy of the card is made that has the same unique number. In MTG Forge, every time a card changes zone a new copy is made. I think that making a new copy of a card is easier than saving all of the base attributes and then resetting them, Card.reset().

The card name is important but so is the unique number. Ideally the unique number would not be shown to the user and little arrows would be drawn to show targets.

p.s.
Nothing I write about it really rocket science just one guys opinion about programming Magic. Just finding the subject is the hard part, the rest is usually straightforward.

Zone Events - Part 2

Other common events include when a player gains or loses life. Although more complicated, damage and combat damage events would simplify the coding for cards like Hypnotic Specter. (MTG Forge implements this card through some clever hacking, thanks Dennis!!) Since Control Magic and other cards allow players to steal creatures, you have to carefully update the damage and combat damage events of the stolen creature.

In summary some basic Magic events include when a card is added or removed from a zone, when a player's life changes and damage/combat damage triggered abilities. Additional events include discard for Megrim and "how many card were played this turn" for storm.

To further complicate the situation, technically the stack is an oddball zone that only holds spells and abilities while all of the other zones hold cards. Internally I'm thinking about letting the stack hold card objects so I could use only one method to move a card, moveCard(Card, Zone to, Zone from).

Anytime a card is moved it would have to use this one method. This would also allow me add an event that would fire every time a card changed zones, addEvent_moveCard(Event). Megrim could use this event to see when a player discards a card. Cards that care about the storm count could also use this event to get the information that they need. This last event is very general and very powerful.

Zone Events - Part 1

I am slowly working on MTG Forge 2.0 and I'm trying to figure out what events should be generated. Granted that this is just a baseline and more events could be added later but my question is "What events do Magic cards care about?"

Many cards have some effect when another card is added or removed from a zone like Glorious Anthem. A card could even want to know when itself was put into play, like Venerable Monk. The triggered ability "when this card comes into play" is fairly common.

Several cards like Darksteel Colossus and Serra Angel have the replacement effect "If this card would be put into a graveyard from anywhere, reveal this card then shuffle it into its owner's library instead" and need to know if they are in a graveyard. (Technically the card would never be put in the graveyard since it is a replacement effect but let's forget that detail for now.) Remember that replacement effects start with the word "instead", see 419.1a "Effects that use the word 'instead' are replacement effects."

The reader should also note that these basic add and remove card events would not be enough to implement Megrim since it only concerned when an opponent discards a card. A card could be removed from a player's hand if he plays it or if he discards it. It would be best to add a discard event if we want to implement Megrim.

Stay tuned for part 2 on Monday. Same bat-time, same bat-channel :+)

21,000 Lines of Code

MTG Forge has at least 21,000 lines of code. (I say "at least" because that number doesn't include CardFactory which has a lot of redundant code. CardFactory another 16,000 lines itself which makes for a grand total of 37,875 lines.)

It is hard to picture 21,000 lines of code but if you wrote 100 lines of code a day it would take you at 210 days, so you can easily see why MTG Forge took about a year to get it up and running. This doesn't include specific bug fixes which tend to take up tons of time and only account for a tiny bit of code.

MTG Forge’s source code is roughly the size of Oliver Twist by Charles Dickens. When the source code is compressed the size is 350 kb which is the same Oliver Twist. Oliver Twist is about 400 pages long, although the exact number of pages will vary from book to book, and has around 161,000 words. And for what it is worth, the source code is 1.78 MB uncompressed and Oliver Twist is 914 KB, so MTG Forge’s source code is about twice the Oliver Twist.

Computer programming is like writing a novel or building with toothpicks. It can be done, but it takes a lot of time. MTG Forge is by far the longest program I have ever written.