Page 85 of 141

Re: Card Development Questions

PostPosted: 12 Jan 2012, 08:49
by moomarc
Dominating Licid | Open
Code: Select all
Name:Dominating Licid
ManaCost:1 U U
Types:Creature Licid
Text:no text
PT:1/1
A:AB$ SetState | Cost$ 1 U U | Defined$ Self | Mode$ Transform | SpellDescription$ CARDNAME loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature.
AlternateMode:DoubleFaced

#Shared
SVar:Rarity:Rare
SVar:Picture:http://www.wizards.com/global/images/magic/general/dominating_licid.jpg
SetInfo:EXO|Rare|http://magiccards.info/scans/en/ex/30.jpg
Oracle:{1}{U}{U}, {T}: Dominating Licid loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature. You may pay {U} to end this effect.\nYou control enchanted creature.

ALTERNATE

Name:Dominating Licid
ManaCost:no cost
Colors:blue
Types:Enchantment Aura
Text:You control enchanted creature.
K:Enchant creature
A:SP$ Attach | Cost$ 0 | ValidTgts$ Creature | AILogic$ GainControl
A:AB$ SetState | Cost$ U | Defined$ Self | Mode$ Transform | SpellDescription$ End this effect.

End
Is this what you had in mind?

Edit: Quick question. Will this transform if the licid becomes a Human somehow and then Moonmist is cast?

Re: Card Development Questions

PostPosted: 12 Jan 2012, 09:29
by Hellfish
That would be transformed if it gained the human subtype and moonmist was cast, yes,because it is marked as a doublefaced card. Here's a fixed version.
Code: Select all
Name:Dominating Licid
ManaCost:1 U U
Types:Creature Licid
Text:no text
PT:1/1
A:AB$ SetState | Cost$ 1 U U | Defined$ Self | NewState$ Alternate | SpellDescription$ CARDNAME loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature.
#If the value of AlternateMode isn't Flip or DoubleFaced, it will be the name of the state defined below, so you can switch to it with SetState+NewState$.The name of the first state defined is always "Original".
AlternateMode:Alternate

#Shared
SVar:Rarity:Rare
SVar:Picture:http://www.wizards.com/global/images/magic/general/dominating_licid.jpg
SetInfo:EXO|Rare|http://magiccards.info/scans/en/ex/30.jpg
Oracle:{1}{U}{U}, {T}: Dominating Licid loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature. You may pay {U} to end this effect.\nYou control enchanted creature.

ALTERNATE

Name:Dominating Licid
ManaCost:no cost
Colors:blue
Types:Enchantment Aura
Text:You control enchanted creature.
K:Enchant creature
A:SP$ Attach | Cost$ 0 | ValidTgts$ Creature | AILogic$ GainControl
A:AB$ SetState | Cost$ U | Defined$ Self | NewState$ Original | SpellDescription$ End this effect.

End
EDIT:There seems to be some more issues, though, such as when you pay to end the effect..

Re: Card Development Questions

PostPosted: 12 Jan 2012, 09:37
by moomarc
Hellfish wrote:That would be transformed if it gained the human subtype and moonmist was cast, yes,because it is marked as a doublefaced card. Here's a fixed version.
Code: Select all
Name:Dominating Licid
ManaCost:1 U U
Types:Creature Licid
Text:no text
PT:1/1
A:AB$ SetState | Cost$ 1 U U | Defined$ Self | NewState$ Alternate | SpellDescription$ CARDNAME loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature.
#If the value of AlternateMode isn't Flip or DoubleFaced, it will be the name of the state defined below, so you can switch to it with SetState+NewState$.The name of the first state defined is always "Original".
AlternateMode:Alternate

#Shared
SVar:Rarity:Rare
SVar:Picture:http://www.wizards.com/global/images/magic/general/dominating_licid.jpg
SetInfo:EXO|Rare|http://magiccards.info/scans/en/ex/30.jpg
Oracle:{1}{U}{U}, {T}: Dominating Licid loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature. You may pay {U} to end this effect.\nYou control enchanted creature.

ALTERNATE

Name:Dominating Licid
ManaCost:1 U U
Colors:blue
Types:Enchantment Aura
Text:You control enchanted creature.
K:Enchant creature
A:SP$ Attach | Cost$ 0 | ValidTgts$ Creature | AILogic$ GainControl
A:AB$ SetState | Cost$ U | Defined$ Self | NewState$ Original | SpellDescription$ End this effect.

End
Thanks. First test done. Turns out that at the moment, if you transform it back to a creature, it doesn't fall off the enchanted creature, so you also don't lose control of it.

I'm off to a meeting so you have some time to think about it. One last small fix to the script. The mana cost for the transformed licid should also be 1 U U so that its affected by spells that are restricted by cmc.

Re: Card Development Questions

PostPosted: 12 Jan 2012, 11:00
by SoulStorm
Thanks for the data regarding Sudden Spoiling Sloth.

Re: Card Development Questions

PostPosted: 12 Jan 2012, 14:01
by ArsenalNut
moomarc wrote:
Hellfish wrote:That would be transformed if it gained the human subtype and moonmist was cast, yes,because it is marked as a doublefaced card. Here's a fixed version.
Code: Select all
Name:Dominating Licid
ManaCost:1 U U
Types:Creature Licid
Text:no text
PT:1/1
A:AB$ SetState | Cost$ 1 U U | Defined$ Self | NewState$ Alternate | SpellDescription$ CARDNAME loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature.
#If the value of AlternateMode isn't Flip or DoubleFaced, it will be the name of the state defined below, so you can switch to it with SetState+NewState$.The name of the first state defined is always "Original".
AlternateMode:Alternate

#Shared
SVar:Rarity:Rare
SVar:Picture:http://www.wizards.com/global/images/magic/general/dominating_licid.jpg
SetInfo:EXO|Rare|http://magiccards.info/scans/en/ex/30.jpg
Oracle:{1}{U}{U}, {T}: Dominating Licid loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature. You may pay {U} to end this effect.\nYou control enchanted creature.

ALTERNATE

Name:Dominating Licid
ManaCost:1 U U
Colors:blue
Types:Enchantment Aura
Text:You control enchanted creature.
K:Enchant creature
A:SP$ Attach | Cost$ 0 | ValidTgts$ Creature | AILogic$ GainControl
A:AB$ SetState | Cost$ U | Defined$ Self | NewState$ Original | SpellDescription$ End this effect.

End
Thanks. First test done. Turns out that at the moment, if you transform it back to a creature, it doesn't fall off the enchanted creature, so you also don't lose control of it.

I'm off to a meeting so you have some time to think about it. One last small fix to the script. The mana cost for the transformed licid should also be 1 U U so that its affected by spells that are restricted by cmc.
This will require some code to fix. The setState AF should check to see if the card just transformed is enchanting something and not an enchantment anymore. If so, run unEnchantEntity. I'll try to make the changes after work if Hellfish doesn't beat me to it.

Re: Card Development Questions

PostPosted: 12 Jan 2012, 14:23
by Hellfish
Rules-wise, that should actually be taken care of in checkStateEffects. It's a simple little if-clause. I believe the problem with when the aura is attached can be addressed further down the road.

Re: Card Development Questions

PostPosted: 13 Jan 2012, 07:34
by ArsenalNut
Hellfish wrote:Rules-wise, that should actually be taken care of in checkStateEffects. It's a simple little if-clause. I believe the problem with when the aura is attached can be addressed further down the road.
Thanks for fixing checkStateEffects. I got the Attach drawback working for the human player. I haven't tested it with the AI yet, but I checked in the code.

Here's the updated script
Dominating Licid | Open
Name:Dominating Licid
ManaCost:1 U U
Types:Creature Licid
Text:no text
PT:1/1
A:AB$ SetState | Cost$ 1 U U | Defined$ Self | NewState$ Alternate | SubAbility$ DBAttach | SpellDescription$ CARDNAME loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature.
SVar:DBAttach:DB$ Attach | Cost$ 0 | ValidTgts$ Creature | AILogic$ GainControl
#If the value of AlternateMode isn't Flip or DoubleFaced, it will be the name of the state defined below, so you can switch to it with SetState+NewState$.The name of the first state defined is always "Original".
AlternateMode:Alternate

#Shared
SVar:RemAIDeck:True
SVar:Rarity:Rare
SVar:Picture:http://www.wizards.com/global/images/magic/general/dominating_licid.jpg
SetInfo:EXO|Rare|http://magiccards.info/scans/en/ex/30.jpg
Oracle:{1}{U}{U}, {T}: Dominating Licid loses this ability and becomes an Aura enchantment with enchant creature. Attach it to target creature. You may pay {U} to end this effect.\nYou control enchanted creature.

ALTERNATE

Name:Dominating Licid
ManaCost:1 U U
Colors:blue
Types:Enchantment Aura
Text:You control enchanted creature.
K:Enchant creature
A:SP$ Attach | Cost$ 0 | ValidTgts$ Creature | AILogic$ GainControl
A:AB$ SetState | Cost$ U | Defined$ Self | NewState$ Original | SpellDescription$ End this effect.

End

I tested it by disenchanting with
1) ending the effect
2) Oblivion Ring
3) Naturalize

The controlled creature returned to its owner in all cases. I wanted to wait till I looked at how the AI used the Attach DB before I checked in the card script.

Re: Card Development Questions

PostPosted: 15 Jan 2012, 18:55
by SoulStorm
So what's the deal with Planechase cards such as Maelstrom Wanderer? Is it ok to add them? Also, regarding the double cascade of Maelstrom Wanderer, can you just list the keyword twice, or would some other coding magic need to be performed?

Re: Card Development Questions

PostPosted: 15 Jan 2012, 19:16
by friarsol
As far as future sets go, we should probably create a new branch for it until June when it will be released. (Similar to what we're doing with Dark Ascension)

Not sure about double Cascade.

Re: Card Development Questions

PostPosted: 15 Jan 2012, 19:19
by SoulStorm
friarsol wrote:As far as future sets go, we should probably create a new branch for it until June when it will be released. (Similar to what we're doing with Dark Ascension)

Not sure about double Cascade.
Ok, thanks for the info!

Re: Card Development Questions

PostPosted: 15 Jan 2012, 21:03
by SoulStorm
Just tried scripting Maelstrom Wanderer, and keywording Cascade twice doesn't work.

Re: Card Development Questions

PostPosted: 15 Jan 2012, 21:17
by moomarc
SoulStorm wrote:Just tried scripting Maelstrom Wanderer, and keywording Cascade twice doesn't work.
I know. I tried it a month or so ago and the closest I got was using a static effect to pump a second cascade. It then listed on the card properly, but never triggered twice. The temporary script has been sitting in the half implemented card thread for a while after someone requested it.

Re: Card Development Questions

PostPosted: 15 Jan 2012, 21:38
by Sloth
SoulStorm wrote:Just tried scripting Maelstrom Wanderer, and keywording Cascade twice doesn't work.
I've just uploaded a fix for this. Please test.

Re: Card Development Questions

PostPosted: 15 Jan 2012, 23:16
by SoulStorm
Sloth wrote:
SoulStorm wrote:Just tried scripting Maelstrom Wanderer, and keywording Cascade twice doesn't work.
I've just uploaded a fix for this. Please test.
Works perfectly, thanks Sloth!

Here's the script for when Planechase cards are ready to be added:

Code: Select all
Name:Maelstrom Wanderer
ManaCost:5 U R G
Types:Legendary Creature Elemental
Text:no text
PT:7/5
K:Cascade
K:Cascade
S:Mode$ Continuous | Affected$ Creature.YouCtrl | AddKeyword$ Haste | Description$ Creatures you control have haste.
SVar:Rarity:Mythic Rare
SVar:Picture:http://www.wizards.com/global/images/magic/general/maelstrom_wanderer.jpg
End

Re: Card Development Questions

PostPosted: 15 Jan 2012, 23:32
by wilsonbiggs
I tried to add a card but the game crashed at startup... any help? My post is at viewtopic.php?f=26&t=6173