shaoster / unmuted2021 Goto Github PK

We could make any positive resource counts flash when the player clicks the "next turn" before confirming end turn.

And also fix the layout to support 4 columns if necessary.

There are already separate functions in Action.js that return a true/false for whether the obtain/perform is valid.
We could extend this function to also return a "reason" if the requested move is not valid, and then provide that feedback in the UI.

Potential UI changes:

1. Add a highlighted/flashing style to the resource icon that's preventing the move.
2. When clicked or hovered, pop up a text description explaining why the move is invalid.

Status effects are temporary conditions.

For now they are defined by:

• A name
• A set of effects
• An ending trigger.

• Events can set 2 thresholds for story points:
  • Top threshold cleared gives buffs.
  • Bottom threshold cleared survives.
  • Bottom threshold failed loses.
• Special cards can increase story points.

Update the text at: https://github.com/shaoster/apex2021/blob/main/src/component/Keyword.js#L237

Consider re-using text at https://github.com/shaoster/apex2021/blob/main/src/component/Keyword.js#L133

• Pictures
• Music

In the hand "To Obtain" should just be removed.
We'll just avoid using Remodel-style game mechanics.

Instead, we should consider adding clearer information for cost to play.

Currently it's a bit hard to grok how many turns you have until the major events.

Having a centralized place where you can see all past and upcoming events makes things easier to keep track of.

It should just keep playing its current song in loop.
Events can trigger song change.

The styling for the text shadows is at https://github.com/shaoster/apex2021/blob/main/src/App.css#L143

See https://developer.mozilla.org/en-US/docs/web/css/text-shadow for how the text-shadow style works.

The #fff just means white. In CSS, colors can be represented a couple of ways:

1. Actual text, like black. This is not preferred.
2. rgba(<redvalue>,<greenvalue>,<blue value>,<transparency).
3. # (In this case red/green/blue are hexadecimal digits between 0 and f. In hex, a is 10, b is 11, etc...).
4. # (In this case redred, etc... refer to 2 hex digits for a total number between 0 and 255).

Not all of the options necessarily involve buying with money.
Some opportunities cost energy instead.

If we:

1. add more cards to the shop
2. time-bound the opportunities in the shop (i.e. events can clear the shop before adding their own cards)

...then the "attention" resource becomes scarce again to force players to choose between various options.

Create an Events concept.

Events can:

• Add cards to discard pile.
• Add cards to Shop.
• Create a temporary status effect.