Talk about new cards here

[sweetLu]

Yes the only way to get a card like this to work is if the player uses Riiaks activated ability approximation for manual mana. There is no way for the game to distinguish a land that auto taps for mana vs a land tapped by something like a Pestermite.

[cenarius]

Yes the only way to get a card like this to work is if the player uses Riiaks activated ability approximation for manual mana. There is no way for the game to distinguish a land that auto taps for mana vs a land tapped by something like a Pestermite.

Damn, what a shame. It would have been fun

Thaks for the reply

[migookman]

I'm trying to make Gemini Engine but am having problems with the token being put on the battlefield using the following:

Code: Select all

MTG():PutPTTokensOntoBattlefieldTappedAndAttacking( "TOKEN_TWIN_AC_X_X_C_CW_1", 1, EffectController(), power, toughness )

PutPTTokensOntoBattlefield works fine but it doesn't put the token onto the battlefield when adding 'TappedandAttacking'.

[Xander9009]

I'm trying to make Gemini Engine but am having problems with the token being put on the battlefield using the following:

Code: Select all

MTG():PutPTTokensOntoBattlefieldTappedAndAttacking( "TOKEN_TWIN_AC_X_X_C_CW_1", 1, EffectController(), power, toughness )

PutPTTokensOntoBattlefield works fine but it doesn't put the token onto the battlefield when adding 'TappedandAttacking'.

PutPTTokensOntoBattlefield is a function. PutTokensOntoBattlefieldTappedAndAttacking is also a function. But PutPTTokensOntoBattlefieldTappedAndAttacking is not a function. Since the attacking bit can't be easily faked, I'd suggest faking the PT. Either make the token a 1/1 or 0/1 or something and then set its PT the moment it's made, or use PutTokenCopiesOntoBattlefieldTappedAndAttacking. Unfortunately, it'll have the wrong name which may cause problems in some cases. Using that method, you'd also have problems with types and other stuff, so first I'd try the PutTokensOntoBattlefieldTappedAndAttacking and changing the PT.

[migookman]

Would it be possible to code the token 'TWIN' to come into the battlefield tapped and attacking? Then the PutPTTokensOntoBattlefield function would work well (that part already tested).

[Xander9009]

Would it be possible to code the token 'TWIN' to come into the battlefield tapped and attacking? Then the PutPTTokensOntoBattlefield function would work well (that part already tested).

You can make it enter tapped, but there's no way to make it enter tapped and attacking from its own code. At least, not that I know of.

One thing you could try (and I HIGHLY doubt it will work) is to use PutPTTokensOntoBattlefield and store the pointer to the created token in a chest. Then, on the token's pointer, call PutOntoBattlefieldTappedAndAttacking. I doubt it'll work, though. It's meant to be for cards not already on the battlefield, but depending on how the developers coded the function, there is a slight chance it will make a card that's already on the battlefield immediately attack. Keep in mind the this function should, just like PutTokensOntoBattlefieldTappedAndAttacking, require the player to attack as one of the parameters.

[thefiremind]

One thing you could try (and I HIGHLY doubt it will work) is to use PutPTTokensOntoBattlefield and store the pointer to the created token in a chest. Then, on the token's pointer, call PutOntoBattlefieldTappedAndAttacking. I doubt it'll work, though.

I did this for Flash Foliage (of course, blocking instead of attacking), and it was behaving strangely, basically the creatures blocked by the Saproling dealt their damage as though they had trample. So, if you want to go down this road, test it carefully, because it may act strange.

Also notice that the text for Gemini Engine doesn't say "tapped", it just says "attacking". I happened to watch a YouTube video of a MTGO Mirrodin draft and I saw the token come to the battlefield untapped and attacking, so I guess it was right (MTGO had another bug regarding that token, I think it wasn't dealing damage, but that's another story).

[Splinterverse]

Do we still need this thread pinned? Last comment was from 2015. We're down to 330 missing cards and under 400 impossible ones.