- summary: Life regeneration has ended; the message also carries life values the current client ignores.
- area: Game.Character
Life regeneration has ended; the message also carries life values the current client ignores.
Kind event · Area Game.Character
Ends the life regeneration that LifePointsRegenBeginEvent started.
WHAT TO DO
1. Stop adding regenerated life: keep the life you have at this moment. 2. Nothing else: the client reads none of its values.
THE CURRENT CLIENT DOES NOT READ ITS VALUES. Beside life_points_gained (the
one int32 with explicit presence, named from beta) the message declares two
plain int32, which match beta's life_points and max_life_points, and from
3.7 a one-value enum. No client build reads any of them, so which plain int32 is
the current life and which the maximum cannot be proven: they stay obfuscated
and the generated proto marks them unread. Do not guess from their order.
FOR LIFE, USE THE CHARACTERISTICS. Current life is tracked in the character
sheet (CharacterCharacteristicsEvent); between updates the client estimates
regeneration locally from the rate it was given.
When you may send it
- Requires
character_selectedinferred
Related messages
- Unsolicited - nothing you send causes this inferred — the client reacts to it without having asked for anything
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 4 | life_points_gained | int32 | How much life was regained, when the server says so. Explicit presence: absent is not the same as zero. Named from its explicit presence, not from client behaviour: the current client never reads it. | never |