Collectible Card Game Headquarters

Where is Sidisi? I have the latest version of Forge (1.5.31), and I'm aware that sometimes not all cards in a set get added with the update. But I had an idea for building a sultai deck using Sidisi, but it won't work without her, and I noticed she isn't among the available cards. Will she be made available soon, or will I just have to make do without?

(also, is there a place on this website where you can post suggestions for cards to add to the collection? In addition to Sidisi, I have a few in mind that I've been needing for use in my other decks)

ajacobs899 wrote:Where is Sidisi? I have the latest version of Forge (1.5.31), and I'm aware that sometimes not all cards in a set get added with the update. But I had an idea for building a sultai deck using Sidisi, but it won't work without her, and I noticed she isn't among the available cards. Will she be made available soon, or will I just have to make do without?

(also, is there a place on this website where you can post suggestions for cards to add to the collection? In addition to Sidisi, I have a few in mind that I've been needing for use in my other decks)

Hi,

Please have a look at # 16 in the Forge FAQ: http://www.slightlymagic.net/forum/viewtopic.php?f=26&t=16129&p=168359#p168359.

Short answer - Sidisi isn't quite scriptable yet. She's trickier than she looks, because of that "one or more" clause. If you got a zombie for each creature milled, she'd be a snap. She'll be added as soon as one of the volunteer devs figures out a way, which will probably take some back-end coding.

I just committed some backend changes and a card definitions for Sidisi, so expect to see her in the next beta.

Myrd, is Rakshasa Vizier scriptable in this same manner?

friarsol wrote:Myrd, is Rakshasa Vizier scriptable in this same manner?

Yes, I think so. Just a matter of adding the new OncePerEffect tag to the trigger for it.

Myrd wrote:

friarsol wrote:Myrd, is Rakshasa Vizier scriptable in this same manner?

Yes, I think so. Just a matter of adding the new OncePerEffect tag to the trigger for it.

Well, Rakshasa Vizier works a bit differently, since it actually has to know how many cards were exiled. Could this be used for cards like Dromad Purebred?

Marek14 wrote:

Myrd wrote:

friarsol wrote:Myrd, is Rakshasa Vizier scriptable in this same manner?

Yes, I think so. Just a matter of adding the new OncePerEffect tag to the trigger for it.

Well, Rakshasa Vizier works a bit differently, since it actually has to know how many cards were exiled.

Wait, I'm confused (and pulling us further from this thread's original topic). Since Rakshasa Vizier puts a number of counters equal to the number of cards exiled, how is its ability any different in practice from "Whenever a card is put into exile from your graveyard, put a +1/+1 counter on..."? That wording seems functionally equivalent, and scriptable without the new tag. Just a changezone trigger.

What am I missing here? There's gotta be something, please educate me!

Zirbert wrote:What am I missing here? There's gotta be something, please educate me!

The wording is such that it would only trigger once per batch of cards instead of for each card individually and that's an important distinction. I can't think of any situation off the top of my head where that would matter, but I'm sure there is one. While it could be implemented as you've put it, it would not be a correct implementation and could result in behavior that was not expected.

KrazyTheFox wrote:

Zirbert wrote:What am I missing here? There's gotta be something, please educate me!

The wording is such that it would only trigger once per batch of cards instead of for each card individually and that's an important distinction. I can't think of any situation off the top of my head where that would matter, but I'm sure there is one. While it could be implemented as you've put it, it would not be a correct implementation and could result in behavior that was not expected.

I see your point. A hypothetical "Whenever one or more +1/+1 counters are placed on a creature, do <x>" trigger would behave differently each way. It would go off once for each counter done the wrong way, but once per batch (even though sometimes the "batch" would be a single counter) using the correct wording. Best to do it right, of course.

Thanks!

KrazyTheFox wrote:

Zirbert wrote:What am I missing here? There's gotta be something, please educate me!

The wording is such that it would only trigger once per batch of cards instead of for each card individually and that's an important distinction. I can't think of any situation off the top of my head where that would matter, but I'm sure there is one. While it could be implemented as you've put it, it would not be a correct implementation and could result in behavior that was not expected.

Well, situations where it matters are for example Stifle (you can Stifle the whole trigger, while in the other implementation you could Stifle only one counter). Or Strionic Resonator.