tool4ever
tool4ever
I think for now I might just skip those canPay checks before stack But to not confuse newer players it's probably better something not enabled by default like Full Control
It might not be a new thing per se since older cards like _Wheel of Sun and Moon_ already had rulings to kind of keep the RE "merged" into a...
This rule is also related, since it kind of makes one RE "override" another: >701.20g. If an effect would cause a player to shuffle a library at the same time...
This is related to #4014 We need a cleaner and robust recursion bailout method
I want to do a big refactor to check all ExileOnMoved usage but that's something for my backlog
Always happy for help you need more details?
This card was never implemented in a way that actually works... I might look into it if Alchemy releases a clone effect that's perpetual since that could then be used...
Thanks for checking again: Yea looks like I didn't catch all possible problematic situations, this may be tricky to prevent fully (though I wonder if you were really already using...
If we remove the param and script it with extra effect either before or after ControlGain it might be cleaner without engine workarounds?
Currently `AbilityUtils.resolveSubAbilities` should try and fill the WaitingTrigger from the previous events with the currently available ones Would have to test it handles this interaction correctly though