Collectible Card Game Headquarters

hi
the value-change on "Turtleshell Changeling"
does not work

script_log:
"
[lua] [string "TURTLESHELL_CHANGELING_444145807_TITLE (CONTINUOUS_ACTION)~0x00000935"]:3: attempt to call method 'SwitchPowerToughness' (a nil value)
"

Ratava wrote:hi
the value-change on "Turtleshell Changeling"
does not work

script_log:
"
[lua] [string "TURTLESHELL_CHANGELING_444145807_TITLE (CONTINUOUS_ACTION)~0x00000935"]:3: attempt to call method 'SwitchPowerToughness' (a nil value)
"

yeah, I've just happen to see that too!!

I took thefiremind code which had a bug.

EffectSource():SwitchPowerToughnes() should be EffectSource():GetCurrentCharacteristics():SwitchPowerToughnes()

I will fix in next update.

HOLY CRAP THE PLANESWALKER WORKS!!!! I tip my hat to you good sir, hopefully soon it will be possible to use whichever walker you wish... I would like to know how it interacts with enchantment removal though, since the walker appears as an enchantment and all.

Drakno wrote:HOLY CRAP THE PLANESWALKER WORKS!!!! I tip my hat to you good sir, hopefully soon it will be possible to use whichever walker you wish... I would like to know how it interacts with enchantment removal though, since the walker appears as an enchantment and all.

I wouldn't say it works in capital letters , this is indeed prone to be disenchanted with any enchantment removal. and it also cause random results sometimes. I think someone did a Liliana of the Veil in another mod, but I don't know if it works. Personally, I think there are much better ways to program a Planeswalker, but I still have lot to learn about coding cards.

just curious about these mixed Interrogations, step, phases, or if we could use them in any way. especially WITHDRAW_FROM_ATTACKING. I wonder if its useable...

Those seem to be triggers that the game uses internally. They aren't coupled with a trigger constant here so it's very unlikely that we can access them from cards.

It's hard to say if those could be used or not, tests could be run to see if they ever work on a trigger, but if they don't trigger then it could mean we can't use them or it could mean they are never fired by the game (like BECAME_TAPPED_FOR_MANA, it has to be fired manually like in my manual mana functions). Trying to fire them manually would probably fail as we have no constants for them (trying to figure out the values would be quite time-consuming, assuming they even can be fired and caught).

There are certain values not defined in decompilable LOL files which could be listed on wiki page, like "replicate", "entwine", "flashback". my point is, if there's an internal function that is actually removing a creature from battle, there ought to be a way to trigger it, right? wish I could revert the exec into source code and hope that expansion cards will use every possibe things that this engine has to offer.. *cross fingers*

Surely this is the long and boring way but can't you give the walker protection from each card that destroys enchantments individually?

gorem2k wrote:There are certain values not defined in decompilable LOL files which could be listed on wiki page, like "replicate", "entwine", "flashback".

Those aren't triggers, and not everything needs to be paired with a constant, but triggers do.

This is my CANT_BE_BLOCKED_BY_MORE_THAN_1_CREATURE try.

Code: Select all

-- can't be blocked by more than 1 creature


  <TRIGGERED_ABILITY>
    <TRIGGER value="ATTACKING" simple_qualifier="self" />
    <TARGET tag="CARD_QUERY_CHOOSE_CREATURE_BLOCK" definition="0" compartment="0" count="1">
    MTG():SetTargetAnswerer( EffectSource():GetPlayerAttacked() )
    </TARGET>
    <MAY />
    <TARGET_DEFINITION id="0">
    local filter = ClearFilter()
    filter:Add( FE_TYPE, OP_IS, CARD_TYPE_CREATURE )
    </TARGET_DEFINITION>
    <CONTINUOUS_ACTION layer="8">
    local target = EffectDC():Get_Targets(0):Get_CardPtr(0)
    if EffectSource() ~= nil then
    local characteristics = EffectSource():GetCurrentCharacteristics()
     characteristics:CanOnlyBeBlockedBy_Clear()
     characteristics:CanOnlyBeBlockedBy_Set( target )
    end
    </CONTINUOUS_ACTION>
  -- duration
  </TRIGGERED_ABILITY>


CanOnlyBeBlockedBy_Clear() doesn't work for me, and I find it strange that CanOnlyBeBlockedBy_Set() isn't listed anywhere. no SCRIPT_LOG generated, so I may try again later when I'm less tired.

I wished it were so easy... CanOnlyBeBlockedBy_Set() only accepts "EVASION_INDEX_..." constants as parameters. It's used to code some blocking restrictions such as shadow (if DotP2014 still doesn't automatically include it in CHARACTERISTIC_SHADOW, I haven't tried yet). It feels a bit redundant given that we can use the EVASION_TEST trigger and get the same result (I think?), but it's shorter.

V3 out.

hey gorem any word if ya making anymore planeswalker cards and if so can it play with reg decks or other decks with another planeswalker besides doing a mirror match ?

What drleg3nd said