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.

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

Lock piles from being viewed without owner consent #2222

Open
brine opened this issue Jul 31, 2023 · 0 comments
Open

Lock piles from being viewed without owner consent #2222

brine opened this issue Jul 31, 2023 · 0 comments

Comments

@brine
Copy link
Contributor

brine commented Jul 31, 2023

From a facebook community post:

Is there any appetite for preventing your opponent from looking at your deck without your consent? We have a small band of players/accounts that do this on a regular basis. I am proposing making it hidden zone that can only be viewed after granting permission by the user explicitly. Thoughts?

From Discord:

I might have asked this previously, but is there a way to lock the Decks so that player A can't right-click on player B's deck and look at > all cards?

Suggested solution:

Add a protected setting to piles, configurable in the game def, in-game pile submenu, and python. 3 states: - "True", "False", "Ask"
A Protected pile cannot be viewed by non-owner players.
The "Ask" state will send a view request dialog to the owner asking to grant permission to view.

Dialog options:

  • "Always" (sets the protected setting to False, pile behaves as it currently does).
  • "Yes" (Grants permission to view the pile via a network call. A message is posted in chat when they stopped looking (it already does this?). If the player wants to view again, they have to send a request again).
  • "No" (denies the request)
  • "Never" (sets the protected setting to True, will lock the deck from access, won't prompt the dialog anymore)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant