nivmizzet1 wrote:fallenangle wrote:nivmizzet,
You could theoretically have the MC question create a delayed trigger if the option were chosen to draw cards, which you could code with a trigger block that returned true only when the conditions under which you wanted the player to draw cards had been met. You'd have to REALLY love your auto-skipping in order to go to that length to do it; but it shouldn't be too hard to do.
It's not so much that I love auto-skipping, it's that I love combo decks, and in particular infinite combos. When a deck is designed around triggering an ability over and over, it becomes painful to the point where it's almost unplayable when you have to wait between each trigger.
Can you point me to a card that uses a delayed trigger, or even a delayed trigger on a MC if there is one, so that I can have a go at implementing it for
Fecundity?
No need. It's working properly, including auto-skip. The issue with it is that there were still a couple instances of TriggerObject() that hadn't been replaced with TriggerObjectLKI(). I replaced all instances of TriggerObject() and TriggerObjectLKI() and tested it, and it worked as it should, including auto-skipping when I had a full hand and plenty of library left. For the record, I changed the auto-skip to ">=" for both hand count and library count. This way, as soon as you have 7 cards, it starts auto-skipping. Doesn't really matter much, though...
nivmizzet1 wrote:tmxk2012917 wrote:Second, when I sacrificed Wild-Field Scarescrow, I could not search for lands in my library.
I haven't checked the code to see if it should work, but are you sure you had basic land cards left in your library?
I checked the code, and it was using "EffectController = EffectController()". This kind of variable (where the name of the variable is identical to the function name) has been known to cause problems. I've fixed this, and I'll test it soon. I don't know if it would cause the problem described, but it seems likely.
As for the planeswalkers, there shouldn't be any issues with them, but "shouldn't" and "aren't" can easily be two different things. If you can find a way to consistently replicate the issue, then we will definitely look into it. Without making sure it can be replicated, I have no idea where to start.