Input and ideas from SoCraTes 2024

[lisihocke]

Own observation:

• In the demoed round, lots of duplicates had been drawn by chance - we should consider limiting them

Feedback collected:

• The X to close a card is implicitly meaning "fix", let's label it accordingly
• Game without goal is also interesting
• Multiple actions per round allowed?
• Idea: fixing takes time
• Stacking
• Network scanning card: duration vs. action (mismatch)
• The more oopsies, the more costly to fix
• Invest in features to get more income
• Add consultant card
• Use different presets (e.g. legacy system)
• Idea: health bar - certain attacks only hit if too low
• Proactive action to protect system
• Try to hire someone - how lucky do you get?
• Event: increase resources
• System indicators
• Reflect investment in features vs. technical neglect
• Get inspired by other games
• Attacks cost money or reputation
• Rewrite card: discard all open cards, draw same number
• Roles and different goals
• Buy defensive cards
• Card: dissatisfied employee
• Defense measures: updated dependencies
• Win condition: only win if all roles win
• Spend resources over time (or lose)

[maschmi]

• scenarios
• evaluation cards :cactus:
• invests into features
  • create features to earn more resources/money?
• invest into security :cactus:
• indicators: resources, reputation, numer of oopsies,

[maschmi]

• penalty if to many oopsies are open -> because of technical debt and moral
• can we model company health/moral?
• can we create a card to model legacy code base? -> increases fix cost