NDA
Type: meta? (must be unblockable)

Description:
Look architecture card of any player. Each player could play this card once per game.

Quantity = number of players

Social interaction:

• Swear you won't tell anybody (can be broken immedietly :)
• Tell the reason why you need to know player's architecture

Joke:
Classified

Hi @sobolevn 👋🏽

I'd to like to start the translation to PT-BR of the game but I want to do in way it's easy for future maintenance and new languages, so I have a proposal.

First we define some variables in a YAML file like this which is basically a translation table:

general:
  first_player: Алисы
  second_player: Бориса
  hand: Рука
  table: Стол
  hidden_card: Закрытая карта
  reset: Сброс
  card:
    attack:
      name: Атака
      types:
        error: Ошибка
    component:
      name: Компонент
      types:
        internal_process: Бекенд

Then all the diagrams must use template tags to get the values (eg.: {{ general.first_player }}), we're going to render using Jinja and once we've done it we can render using Drawio API, finally we just save in the folder!

The render process can be done locally and we verify using the CI/CD if the process was executed or automate the repository to commit it self in the master branch after a merge.

WDYT?

Warning
Attack
Place on someone's component. Has no effect.

Treat warnings as errors
Attack/black card
Converts all warnings on components into errors
Directed by Robert B Weide

Can be played at any time, cancels the previous played card.

We have two subcategories in DEFENSE:

• played by reaction
• played in turn

Often it looks unobvious what and when play, even with reaction icon. I suggest split it into two categories

• Defense component
• Defense action

OR

Make aditional info, e.g. add + component icon|text

Scrum|Deploy It!
type: meta

Play card against another player. This player must deploy component in his turn or

• pass the turn
• draw 1 (2,3,..) card from hand (weak?)
• give 1 (2,3,..) card to scrum master (you) (OP?)

Things to consider:

• Component might be deployed twice, so bonuses might increase
• Some architecture cards require 2 copies, some just 1. It must be balanced
• Bonuses must be very gentle, they should not give a massive advantage
• They should not increase the turn timings

Example:

• If "Frontend" is deployed, you can look at 1 card before drawing it, then decide to take it or to fold it. If two "Frontend" components are deployed - you can look at 2 cards, etc

For example: "what did you animals break in your house?" is a bad question, because it has finite amount of answers. It is not good for playing over-and-over again. I need to rethink all such details.

UDP
Type: meta

Play this card against another player. Affected player cannot take card from deck in his turn, either by turn action or by card action.

Я бы вам рассказал шутку про UDP, но, боюсь, она до вас не дойдет