feat: define action completion costs
This commit is contained in:
@@ -220,6 +220,12 @@ an asset catalog.
|
||||
|
||||
Translate the desired animated-film warmth into an original style:
|
||||
|
||||
Keep the gameplay camera as an elevated third-person/top-down player follow
|
||||
with gentle dead-zone lag. This supports the cozy farm-builder read and lets
|
||||
the player watch several villagers at once. Presentation presets may stage the
|
||||
same camera for repeatable captures, but should not replace gameplay with a
|
||||
free orbit or close over-the-shoulder view.
|
||||
|
||||
| Element | Direction |
|
||||
| --- | --- |
|
||||
| Terrain | Broad painterly color regions and exaggerated silhouettes |
|
||||
@@ -665,11 +671,10 @@ Completed:
|
||||
Next:
|
||||
|
||||
1. Replace the remaining player capsule with a matching stylized presentation,
|
||||
then revisit runtime camera framing so the waterfall and village action
|
||||
remain readable in the same authored shot.
|
||||
2. Continue with the action precondition/material-cost contract and
|
||||
relationship consequence work in `LEARNING_ROADMAP.md` before expanding
|
||||
visual scope further.
|
||||
while preserving the elevated top-down follow, gentle dead-zone lag, and
|
||||
cozy farm-builder readability.
|
||||
2. Continue with the relationship consequence work in `LEARNING_ROADMAP.md`
|
||||
before expanding visual scope further.
|
||||
|
||||
Do not start with GIS data, a full city, a large asset pack, or more NPC
|
||||
mechanics. The next proof is a beautiful stage for the systems that already
|
||||
|
||||
Reference in New Issue
Block a user