'Equipped creature' doesn't work.

Login or register to post comments
Sat, 2007-05-12 02:56
Mallys
Mallys's picture

Maybe there's an easy solution to this, but I can't seem to get the word 'Equipped' to work in MSE (newest version). The program always sets up the Equip ability, and it ends up coming out as "Equip<cost>ped". Didn't know if this ought to go under the new version's bug thread or not, as I can't recall whether or not the problem was present in the old versions.

Sat, 2007-05-12 03:18
Pichoro
Pichoro's picture

Looks like in the future, equip will have to be separated into two different keywords the way splice is. Can't believe I overlooked that.

Anyway, in the meantime, users can fix this inside of their set files. You'll have to make two new custom keywords to do so, though.

Here's the first one:

Keyword: Equip (Mana Costs)
Mode: Expert
Match: Equip <mana>
Reminder: {param1}: Attach to target creature you control. Equip only as a sorcery.

Here's the second one:

Keyword: Equip (Alternative Costs)
Mode: Expert
Match: Equip—<cost>.
Reminder: {param1}: Attach to target creature you control. Equip only as a sorcery.

Okay, so some advice. Don't forget the period on the end of the match line for the second one; that's part of the formatting for it. And when choosing a parameter (such as <mana> or <action>), you can't just type it in. You have to put your cursor where you want the parameter to be, and then click the "Insert Parameter" button and select the parameter you want. Other than the parameters, these are made so you can just copy and paste them into their correct fields in the custom keyword section.

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

So I guess for the benefit of those who might make custom keywords, I'll talk about why this problem happened and why I prescribed the correction that I did. It didn't happen in the past because the text that actually initialized the equip keyword was "Equip "; now the text is "Equip". Notice the difference. Without the separator to let the program tell the difference beween "Equip<cost>" and "Equipped", the keyword doesn't function properly. So that's why my introduced versions feature built in separators. There's a period on the end for proper keyword formatting. You see, with alternative costs, you customarily should type a period at the end of the description of the cost, such as "Equip--Sacrifice a creature." But the period removal was built into the scripts that go with the cost parameter now, and are part of equip's problem. So this way, by putting the period in the match text and leaving it out of the reminder text, we can achieve the proper effect still.


Custom file library for MSE2b: http://pifro.com/mtg/
My custom sets:
The Taint: http://magicseteditor.sourceforge.net/node/183
Mare Harenum: http://magicseteditor.sourceforge.net/node/303
Enigma: http://magicseteditor.sourceforge.net/node/719
Sat, 2007-05-12 16:24
Twan
Site and Project Owner
Twan's picture

A simler workaround is to find:

keyword parameter type:
	name: cost

in the data/magic.mse-game/game file and insert:
	optional: false

after it

Sun, 2007-05-13 02:17
Mallys
Mallys's picture

That did the trick.