Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Arcs] Limit on flipping the Council while secured #113

Closed
jdyearsley opened this issue Jul 10, 2024 · 2 comments
Closed

[Arcs] Limit on flipping the Council while secured #113

jdyearsley opened this issue Jul 10, 2024 · 2 comments
Assignees
@jdyearsley
Labels
errata Confirmed errata that needs to be put in production files, the FAQ/errata doc, and/or Card Library

Comments

@jdyearsley
Copy link

Currently, some cards (e.g., Council Intrigue) interact weirdly with the Council while it's secured and tucked. The rulebook will need an added limit on flipping it while it's currently secured.
@jdyearsley jdyearsley added the ruling Rules problem that needs a ruling label Jul 10, 2024
@jdyearsley jdyearsley self-assigned this Jul 10, 2024
@jdyearsley jdyearsley added errata Confirmed errata that needs to be put in production files, the FAQ/errata doc, and/or Card Library and removed ruling Rules problem that needs a ruling labels Aug 26, 2024
@jdyearsley
Copy link
Author

Actually, it may be better to allow this behavior and just return the Council to the Court. Talking with Cole about this.

@jdyearsley
Copy link
Author

Yup, I've reversed this thinking. It's just a lot cleaner to allow it. I've updated the campaign FAQ and relevant card FAQs, added "If it flips while tucked under a card, return it to the Court." to the rulebook, and updated the production doc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jdyearsley jdyearsley

Labels
errata Confirmed errata that needs to be put in production files, the FAQ/errata doc, and/or Card Library
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jdyearsley