You are most wlecome.  your other answers, right from the new FAQ:

1)  If an item with a bound spell is stolen (such as with the Steal Equipment spell) the bound spell is stolen along with the item.  If it was a face down spell (not revealed yet because it had just been bound) the new controller may look at the spell. The new controller may cast that spell, as long as it is not restricted for their Mage school or class. For example, the Priestess cannot cast a Drain Life spell bound to a Mage wand. If later the bound spell is changed, it is returned to its owner’s spellbook.

2) You cannot take control of creatures which your Mage is restricted from.  For example, the Forcemaster cannot cast Mind Control on Huginn, Raven Familiar, which has the Arcane Mage Only trait.
If you take control of a familiar you are legally allowed to control, you take control of any spell which was planned for it to cast (unless that spell is restricted from your Mage class or school, in which case it is immediately returned to the owner’s spellbook instead). You can use the familiar to cast that spell, and you will have control of that spell after it is cast.  Alternately, you can change out the spell on a future planning phase, at which time it is returned to its owner’s spellbook.

3) Steal Enchantment cannot be used to take control of an enchantment you are restricted from. For example, the Wizard cannot take control of a Forcemaster’s Forcefield.
When you cast Steal Enchantment, you can re-target the same target the enchantment is currently attached to. For example, you may want to take control of a Charm spell, and put it back on the current target creature. You must pay the casting cost for Charm to be placed on that same target again (as described on the Steal Enchantment spell).

No problem. I had to admit we had some internal debate on those Mage Restrictions. It truthfully was not clear in the rules!

Here is the latest excerpt from our FAQ which should be downloadable tonight:

Restricted Spells
If a spell is restricted to a particular Mage or school of training, it refers to two things:
1)   Placing that spell in that Mage’s spellbook when building their spellbook before the game begins.
2)   Controlling or using that spell during the course of the game.

Examples:
•   If the Forcemaster casts Steal Equipment, she can target a Warlock’s Lash of Hellfire, which has the Warlock Only trait. However, since she cannot use this spell, it is destroyed instead.
•   Steal Enchantment cannot be used to take control of an enchantment you might otherwise be restricted from. For example, the Wizard cannot take control of a Forcemaster’s Forcefield.
•   If the Priestess steals a Mage Wand with a Drain Life spell bound to it, she cannot use cast that spell. She can steal the wand, but the wand would be of no use to her unless she chooses to bind a new spell to it.
•   The Forcemaster cannot cast Mind Control a Huginn, Raven Familiar because it is Wizard Only.

Ha! This is a good debate I stumbled across!  

The Goblin Builder's ability is not considered healing. This was intentional by design.

This is the first time we have a damage removal ability which is not healing.  In every other case it is considered healing (and clearly states it as such on the card or in the Codex).

Thematically, he is repairing a building or structure, and not actually healing flesh and blood. We felt it s was fine to allow this exception and not use the word "healing" in his text, in order to maintain flavor and realism.

Yes, we could have/should have also said "Nonliving", to maintain theme, but we were trying to cut back on the number of traits and keywords used.

Good call gos_Jim, and yes we did it primarily for balance.  However, there is a little "flavor/theme" to the decision:  

The Scimitar is almost like a ranged attack, in that it is floating off by itself, making an attack on its own, and that is why it does not trigger a damage barrier or counterstrike.

Ranged attacks do not remove a guard marker because they lack creature presence and engagement. When a creature makes a melee attack, its body interposes the other creature's direction of movement, and the size/presence and active continuous engagement is what will remove a guard.

It is the creature presence, more so than the attack itself, that takes guards out.  A crossbow bolt hurts, but won't deter a guard (unless it stuns him or kills him).  But a big Orc standing in front of the guard ties him up while the other Orcs go around.

Yes, you could say the Scimitar has some presence to it of course, but its not quite the same as a creature.  We looked at as the Sword flies out to strike and then comes back again, and there is no active engagement.

Mage Wars has been challenging to design in that we try to have a realistic simulation while also maintaining balance.

Ha!  Sorry guys!  That would be really good!  A STUN which then becomes a Daze!

It's actually priced in our formulas fairly inexpensively because it has limited, specialized use.

It was designed to just be a simple knock down to the ground, and then the creature stands back up again (when it goes to act next round).  However, during that brief time it is knocked down, it loses Flying, Defenses, and Guarding (because it is incapacitated).

I'm sorry for the confusion,  This is in our FAQ now.  Thanks for the report.

Really?!  So how were they playing it?

Were they playing it as a super-powerful Stun which incapacitates them for a full round + Dazes them on the next round?  

What about the part that says "Remove Slam when this creature is activated."?!

I will add this to the FAQ upon your recommendation.  Please tell me more about what was missed.  Thanks!