Unity Life Economy

Use unity-cli and unity-game-dev for the project operating contract. Read the economy recipe before changing refill math, save transactions or retry/navigation flow. Use game-design skills when the life-cost or pricing rules are undecided; this skill supplies implementation.

Capture the rules

Inspect currency configuration, save schema/writer, attempt outcomes, retry, home navigation and current tests. Record maximum, starting amount, refill interval, paid-refill cost/currency, timer-start semantics and when an attempt begins charging. Never copy a source game's numeric tuning.

Choose what happens when a life-charge write fails, and whether a failed attempt's retry is free. An attempt latch set before persistence prevents duplicate calls but can also suppress retry after failure; it does not prove that a life was durably charged. Define the intended failure behavior.