- summary: Why an inventory stack changed; the client only acts on the quest origin.
- area: Game.Common
- confidence: 0.91
Why an inventory stack changed; the client only acts on the quest origin.
- Kind enum
- Area Game.Common
- Named by beta
The origin carried by ObjectQuantityEvent (and by the item-added event).
WHAT THE CLIENT DOES WITH IT. Exactly one thing: when the origin is
ORIGIN_QUEST it announces the gained amount in chat. Every other value -
ORIGIN_UNDEFINED and the two unnamed ones - is treated identically: the
inventory is updated silently.
TWO VALUES HAVE NO NAME. The protocol has grown: two values in the reference
build, a third by 3.2, a fourth by 3.4. No dumped client, string table, type
table or descriptor names the two newer ones, so they keep their obfuscated
names. If you meet one, treat it like ORIGIN_UNDEFINED; that is what the client
does.
ORIGIN_UNDEFINED is the default: an update whose origin is absent from the
wire arrives as this value.
Not sent on its own — an enum is never sent on its own. inferred
Used by
Values
| Value | Number | Meaning |
|---|---|---|
ORIGIN_UNDEFINED | 0 | No particular origin; the client updates the inventory silently. Named from beta's numbering, not client behaviour. It is the default when the origin is absent. |
ORIGIN_QUEST | 1 | The stack changed because of a quest; the client announces the gained amount in chat. |
Recovered with score 115, confidence 0.91, margin 115 over the runner-up. A margin close to the score means nothing else came near; a thin margin means a decoy nearly won. Members recovered: 2 of 4.
Aucun avis à afficher.