Why Satiety, Energy or Alcohol Can Cost HP after Foundation
Understand the demo’s post-Foundation resource-threshold change, inspect stage HP and read the current drinking buff instead of inventing universal limits.
FAQ
Does reaching a threshold always mean immediate death?
Is the old warning below 30 a current death threshold?
What does the new drinking buff do numerically?
What changed after Foundation?
After Foundation Establishment, reaching a Satiety, Energy or Alcohol threshold deducts the corresponding stage HP first. That is the specific change in the October 31 demo announcement. Check the meter and HP together before treating the result as an unrelated combat hit, an instant-death rule or proof that your status display has broken.

This is a diagnosis of a documented post-Foundation rule, not a universal resource table. The announcement does not supply every threshold value, the amount of HP lost per unit, or a safe food-and-drink rotation for every character.
What should you record when HP changes unexpectedly?
Record the character’s actual realm and the resource that reached its displayed boundary. Then compare the relevant stage HP before and after the action. This separates the documented threshold behavior from a different failure, such as an old display problem or an effect whose description changed. Do not assume that pushing every resource to its maximum is always the correct objective.
| Record | Why it matters |
|---|---|
| Realm before the action | The cited change explicitly concerns behavior after Foundation |
| Satiety, Energy or Alcohol before and after | Identifies the resource event rather than guessing from a single HP value |
| The affected stage HP | Checks the specific consequence described in the update |
| Active buff and displayed resource cap | Separates a modifier from the base display |
| Installed build and action taken | Makes a later discrepancy reproducible |
Read what your actual meter describes. A low-resource warning and an upper limit are different observations; the published change does not justify inventing one common numeric boundary for all three resources.
Why should you re-read the drinking buff?
The November 2 update adjusts the post-drinking buff and adds an effect description. It does not publish the new numerical effect in its text. Read the current buff before deciding that an older description, screenshot or remembered value is still correct.
The October 31 notes also correct Stamina/HP issues and resource-cap buffs not refreshing. Those are dated fixes, not a guarantee that every later surprising value is harmless. If a cap or HP display still seems inconsistent, preserve the active effect and before-and-after state rather than silently replacing one number with a community guess.
How do you distinguish older advice from the current rule?
The September 9 Playtest note improves a warning when Satiety or Energy is below 30. That is a warning change from an earlier test; it is not a universal current death threshold. The public demo later changes warning flashes, and October 31 specifically changes post-Foundation consequences. Keep those scopes separate.
Success here means identifying the triggering resource and the corresponding HP change, or preparing a focused report when the observed sequence differs. It does not mean proving an invincible resource loop. Include your realm, meter values, stage HP, buff and build in that report.
Use the beginner guide for the demo’s broader progression and the dated update history to place older advice. Resource thresholds are also separate from gathering misfortune and inheritance choices. Checked November 7, 2026; no personal gameplay or exact recovery formula is claimed.
Related Articles
camp
Marriage and Dual Cultivation: Check the NPC Requirement
Distinguish ordinary NPC relationship options from special characters with realm requirements, using the developer’s Demo clarification without an invented bypass.
camp
Vow Power Stuck? Check the Camp Progression Branch
Find the official Camp and event sources of Vow Power, follow the reported Guiyuan Chart lead and separate a community route from a guaranteed boss solution.
combat
Preview Enemy Count and Level Before Entering a Battle
Use the developer’s map-preview advice before committing to combat, and keep repeated failed escape reports separate from a guaranteed RNG or victory formula.
Was this helpful?
Thanks for the feedback!