-
Notifications
You must be signed in to change notification settings - Fork 591
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
Dependency Graphs #6869
Dependency Graphs #6869
Conversation
maybe remove this, and separate them inside the layers loop? |
I think right now I do need them pre-sorted once, so I can always start checking from the earliest |
@Hanmac |
Look what I meant: I think filtering the list for CDA first would help |
Feel free and try to tweak it 🤔 I tested the sub-issues and easier ones work now, those have been linked for closing |
@tool4ever should we add more test cases? |
@Hanmac |
with rest i mean, what is above? what code (not related to this MR) takes the most amount of power? |
@tool4ever i think you can move the Comperator into a Const if you want but i still think removing the CDA first from the list and then sorting by timestamp / dependency later separate might be better? |
There's no benefit from multiple sort calls since CDA need timestamp order too and this will also make sure they get applied first anyway. I'm already skipping them for dependency order right now until a case for it gets supported. ➡️ Comparator extracted and converted to native Java |
i haven't found an example for CDA dependency yet, because they can only affect itself, it needs to be something on the same card, or gained something via copy layers The Full dependency is only in effect when the TreeTable are replaced with LinkedHashMap |
Indeed more work / PR will still remain... Luckily with such effects:
But is anything else needed here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this is good for now?
We just need to update the other effects soonish
This implements the algorithm I've outlined in #5642 :)
StaticEffect
so it can undo single layers onlyTo handle more cases
generateStaticAbilityResult
will need additional logic for the other layers.But just comparing the affected objects should already support quite a lot.
Closes #4680
Closes #1850
Closes #4108
Closes #4841
Closes #6669