Energy, Stamina and skill points: capacity or recovery?

A larger bar and a faster refill solve different problems

Increasing capacity allows more units to be held at once; increasing recovery adds units faster over time. They are not interchangeable. Before choosing a skill-point option, read exactly what that option says it changes. This guide does not assert that every version offers both choices or that a particular point split is universally best.

The official promotional interface shows separate Energy, Stamina and Health meters. Third-party guides disagree on some action-resource labels. Identify the meter that actually decreases during your chosen action rather than merging the three into one budget.

Measure one resource without guessing its rate

1. Record the current value and maximum on the relevant bar.
2. Make sure the value is below the cap.
3. Record a start time and any visible active bonus.
4. Observe a known interval without spending the resource.
5. Record the gain and whether the bar reached its maximum.

If the bar reaches its cap before the interval ends, gain divided by the whole interval understates the uncapped recovery rate. Use a shorter observation or a visible refill timer. Do not extrapolate an online observation to offline recovery unless you have checked that state too.

Estimate what a longer absence can store

Under a constant-rate model, stored resource after t hours is min(capacity, starting amount + recovery per hour × t). Illustrative values: start at zero, recover 10/hour, stay away for eight hours. A capacity of 40 stores only 40; a capacity of 60 stores 60. The extra capacity captures 20 units that otherwise could not be held.

If you return after two hours, both capacities hold 20. The larger cap provided no extra usable resource in that shorter interval. A capacity choice therefore depends on how often you return and how much you spend, not merely the largest possible number on the bar.

Connect a point choice to an action

List the next action’s resource cost and any minimum requirement. If you cannot hold enough units for one action, capacity can be a direct blocker. If you regularly return with the bar below its cap, a higher maximum alone may not change your next session. If the option changes a different stat, compare that stat with the objective it serves instead.

Do not assume that spending a point is reversible or that a level-up restores resources. Read the current confirmation and reset rules. Use one deliberate change and observe the result where possible. The job planner allocates the budget you already have; it does not forecast refills or level-ups.

Build around your real visit pattern

A player who checks every hour and one who returns twice a day have different storage needs. Record when you actually reach the cap over several sessions. Then decide whether the lost storage opportunity matters more than the other upgrade you would postpone.

Use the short-session routine to choose a manageable schedule. If the limiting requirement is cash or equipment rather than resource storage, return to the bottleneck diagnostic. A resource model is useful only when it addresses the action you want to perform.

Would a higher cap help your next visit?

The larger cap matters only after the smaller cap would have filled. With a nonzero starting amount, time to full is (capacity − starting amount) ÷ recovery per hour. At 30/40 and 10/hour, the smaller bar fills in one hour. At 30/60 it fills in three hours.

A full bar cannot prove how quickly it recovered while you were away. The endpoint has lost that information. When comparing recovery, observe below the cap. When comparing capacity, use your actual time away and the next action’s cost. Then allocate the available units in the job budget planner.