YECL: Limitless Rekindling #9633
Open
+10
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As revealed recently.
Needs support that feels beyond my current expertise. Tested with
ValidCards$ Instantto determine that the resolution process does work as expected.As far as I can determine
ValidCards$in the context ofNameCardlines doesn't parse comma splits or set codes. Looking into the code ofChooseCardNameEffect.java(lines 36-39 and 96-109 ) and comparing withSacrificeAllEffect.java(lines 45-52; which is an effect that can parse commas and set codes inValidCards$) I clearly notice these classes handleValidCards$in ways that seem difficult to reconcile. Still, I followed the latter effect's lead in laying out the putative script herein.