- summary: How many of one item sit in one of the character's storages, so a single stack can be reported per location.
- area: Game.Common
- confidence: 0.86
How many of one item sit in one of the character's storages, so a single stack can be reported per location.
- Kind struct
- Area Game.Common
- Named by invented
This name is not Ankama's. It was chosen for this documentation from proven client behaviour, and is a label rather than protocol documentation.
WE CHOSE EVERY NAME HERE. The record, both members and ObjectStorageKind
with all of its values are our descriptive labels, derived from proven client
behaviour. Beta, the 3.2 name map and the current type-name table all fail to
name this record. The BEHAVIOUR below is proven; the SPELLING is not, and a
future official schema may well use different words.
ObjectItem carries a repeated list of these, which is how one stack is
reported as, say, 3 in the inventory and 20 in the bank at the same time. The
client sums nothing for you: it switches on storage and folds each count into
a separate counter.
AN ENTRY WHOSE STORAGE IS UNSPECIFIED IS SILENTLY DROPPED by the client, so do not treat the list as exhaustive of the item's true total.
Not sent on its own — it is only ever reached as an element of ObjectItem.storage_quantities. proven
Used by
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 2 | storage | ObjectStorageKind | Which of the character's storages this count belongs to. WE CHOSE THIS NAME. See ObjectStorageKind. | never |
| 3 | quantity | int32 | How many units of the item are held in the storage named beside it. WE CHOSE THIS NAME. Proven as the count the client folds into one of three tooltip counters. | never |
Recovered with score 240, confidence 0.86, margin 240 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 3.
Aucun avis à afficher.