fix: tungsten tailor doesn't trigger when no subs broken#8598
Merged
NoahTheDuke merged 1 commit intomtgred:masterfrom Mar 10, 2026
Merged
fix: tungsten tailor doesn't trigger when no subs broken#8598NoahTheDuke merged 1 commit intomtgred:masterfrom
NoahTheDuke merged 1 commit intomtgred:masterfrom
Conversation
filipesilva
changed the title
filipesilva
commented
Mar 7, 2026
| (can-pay? state side eid (get-card state card) nil cost)) | ||
| (continue-ability state side (break-subroutines ice breaker cost n args) card nil) | ||
| (effect-completed state side eid)))))) | ||
| (if (seq broken-subs) |
Contributor
Author
There was a problem hiding this comment.
seq lifted from the inner if
Collaborator
|
i feel like i had it that way because of a rule in the CR but who can remember. if the tests pass, we're probably fine. |
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
2 participants
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.
Fix #8591