-
Notifications
You must be signed in to change notification settings - Fork 571
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
WrappedAbility Timestamp issue #4842
Comments
Yea there should be no reason to keep it: For the most part only changezone triggers should be able to find the new object anyway?
|
@tool4ever yeah that is my end goal that we don't need "LKICopy" anymore, and have the Effect handle all the stuff |
A simple example where things get messed up currently:
but if we can figure out game timestamps now porting those other changes should lead to some quick wins :) |
Needs #117 |
@tool4ever what exactly is still missing? i thought we ported most of that MR into smaller ones? |
until |
oh okay that's what you mean, yeah we should make smaller MR to port all the APIs if able |
Problem with Trigger and Timestamps:
forge/forge-game/src/main/java/forge/game/trigger/WrappedAbility.java
Lines 503 to 522 in 93a52a4
WrappedAbility does mess with the Triggered Objects,
but the better way would be to have the Effects handle it
currently the way is to update the Effects with
equalsGameTimestamp
to check if the timestamp is still OK or use LKI insteadfor this, it might be better if the Triggered Objects where LKI to begin with so they can't be messed up again?
it would be better if all effects are updated, and the Part could be removed from WrappedAbility
The text was updated successfully, but these errors were encountered: