New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recent ETB Changes causes problems with LKI #668
Comments
the trigger is probably something else to be fixed too, it should only indirect related to this issue |
I pushed 613 snaps that reverts #663 on my branch, so users will stop spamming the etb issue on discord. Gonna update future snaps until this is resolved. |
i also need to check if this part is still valid, and if it is maybe it can be done better: if (toBattlefield && !copied.getEtbCounters().isEmpty()) {
for (final ReplacementEffect re : copied.getReplacementEffects()) {
re.setSuppressed(true);
}
} i tested it with this line enabled or disabled, it doesn't seems to have a difference |
fixed the bugs for now but there might be some corner cases when there is something like Grumgully that does additional +1/+1 counters the corner case there would be that they only be affected by themselves (i think) and not the other Corpsejack Menace. |
I finally found the corner case i have been looking for, because i was only testing it with Mowu, Loyal Companion:
This one should apply
This should not
This also not for this, the PutCounter Replacement needs to check if it is ETB Counters, and then needs to check lastStateBattlefield stuff especially if multiple of such would enter at the same time |
@Hanmac |
closed for now |
This Section there by #663 causes problems:
https://github.com/Card-Forge/forge/blob/master/forge-game/src/main/java/forge/game/ability/AbilityUtils.java#L223-L225
Without the setting for LKI the test fails, but in game it works as it should
With the setting for LKI the tests pass, but in game it becomes broken
Can one of you guys check what should be done there? @Agetian @tool4ever @Northmoc
somehow fix the tests?
The text was updated successfully, but these errors were encountered: