tool4ever comments

Results 117 comments of


                                            tool4ever

Differ Between Control Untap Haste Effects

I don't have a better idea besides refactoring such scripts into UntapEffect -> ControlGainEffect and storing the current controller while running `collectTriggerForWaiting`

ThisTurnEntered can sometimes fail as source for Discarded

A card or global field might track if it got revealed before But the cost payment rollback could be problematic

DMU: Enlist mechanic

Thanks, I'll try to update it later I could open another PR for easier commenting if you want?

Information about illegal targets must still be provided by the engine in some cases

It could probably be fixed the same way I did _Yosei, the Morning Star_ with `RememberOriginalTargets$`

Information about illegal targets must still be provided by the engine in some cases

_Biomantic Mastery_ is another case

Implement CR 800.4m

Well that Detain was just an example - there's lots of different effects that could get stuck in limbo like _Shapesharer_ cloning making a mess I think we can just...

Kamigawa tap lands don't work correctly when changing control.

Old branch in case someone wants to pick it up: https://github.com/Card-Forge/forge/tree/untapRework

CountersPutAI: shouldPumpCard is too restrictive for instant speed PutCounter

@Agetian friendly ping if you still want to finish this? :)

CountersPutAI: shouldPumpCard is too restrictive for instant speed PutCounter

Sure, I'll try to get those ideas I mentioned above working here

CountersPutAI: shouldPumpCard is too restrictive for instant speed PutCounter

This was indeed quite tricky and while I tried to be more generic some of my hopes seemed to be out of reach. But the charm case should behave properly...