- summary: Take back every capital point spent on the six base characteristics: they return to 0 and the points return to the capital. Sent empty.
- area: Game.Character
Take back every capital point spent on the six base characteristics: they return to 0 and the points return to the capital. Sent empty.
Kind request · Area Game.Character
Undoes the characteristic points the character has spent: the six base
characteristics go back to 0 and every point spent on them returns to the capital
(StatsPoints). It is the opposite of CharacterCharacteristicUpgradeRequest.
HOW TO SEND IT
1. SEND IT EMPTY. It has no member to fill.
2. NO CONFIRMATION, NO CHECK ON SEND. The client's reset button sends it at once:
no question to the player, and nothing between the click and the send tests
level, fight or points. Treat the server as the judge of whether a reset is
allowed.
3. READ THE RESULT in the next CharacterCharacteristicsEvent: strength,
vitality, wisdom, chance, agility and intelligence (StatId 10 to 15) with a base
of 0, and StatsPoints (characteristic 3) raised by every point that had been
spent.
4. ALSO EXPECT an InventoryWeightEvent with the new maximum weight, and a
TextInformationEvent (message id 470 in the observed session).
OBSERVED (same character, two captures): on 3.7.7.6 it spent 8 points (1 each on
strength, vitality, chance, agility and intelligence, 3 on wisdom), leaving 37
StatsPoints and a maximum weight of 1146. On 3.7.8.7 this request was answered by
InventoryWeightEvent (maximum weight 1141), CharacterCharacteristicsEvent
(all six bases 0, StatsPoints 45 = 37 + 8) and a TextInformationEvent with id 470.
PADDING. 3.5.9.11 declares an optional int32 and a six-value enum in it; the client never writes them. Send it empty on every build.
When you may send it
- Requires
character_loadedinferred - Raised by: the player clicks the reset button of the character sheet's characteristic boost panel (the full panel; the minimized panel's reset does nothing) proven
Related messages
- Nothing answers it - send it and move on inferred — no dumped build declares a reset reply; the new characteristics arrive through the unsolicited
CharacterCharacteristicsEvent, as observed