Re: Community Wad
Yup i know, i have to admit i go with one problem at a time, and for me making the "basic" card was the priority, but it seems it was much complicated to code than expected. I guess i will wait for Xander9009's response to see if his way is better and more effective than mine (which i think it will, and by far).sweetLu wrote:A complete rule compliant Static Orb will be a little complicated. For starters you cannot have the filter for selecting which two permanents to untap set to all permanents. For instance, you cannot untap a creature affected by Frost Breath 's ability. So you would need to filter out any permanent that otherwise would not untap.
Secondly, it would take some work to make it rule compliant with other orb-like cards. For instance if Winter Orb and Static Orb are in play you have to apply both of their restrictions. So possible combinations include up to either 1 land and 1 non-land or 2 non-land permanents. Or more simply if you have 2x Static Orb in play you could only untap 2 permanents. With the quick look of what you have you would be able to untap 4 permanents. The best way to handle multiple orb effects, IMO, would be to use a token manager and have the individual orbs set some values in a game chest depending on the applicable restrictions.
Thirdly, you shouldn't let me talk because I made Winter Orb and didn't account for either of these things besides accounting for multiple copies of Winter Orb. I have a semi-compliant version floating around somewhere if you would like an example.
Edit: to actually answer your question you should be able to add something like this to the return part of the triggered ability:
"and EffectSource():IsTapped() == false"
You could probably get the exact syntax off Trinisphere
Thanks for the reply