- 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
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
The record's name is Ankama's: the client's type-name table spells InventoryQuantity
(see the reverse-engineering notes). Both MEMBERS and ObjectStorageKind with all of
its values are still our descriptive labels, derived from proven client behaviour: no
oracle names them. The BEHAVIOUR below is proven; those spellings are not.
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 |
|---|---|---|---|---|
| 1 | 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 |
| 4 | storage | ObjectStorageKind | Which of the character's storages this count belongs to. WE CHOSE THIS NAME. See ObjectStorageKind. | never |