The shop
What fills the shop, what a client asks for, and what a server answers.
What fills it
A client’s catalogue of items is its own: no message sends or changes it. A client sets its shop up for its own champion, and what a match sells is settled by the client’s own data. A client filters nothing out of the shop by the champion’s level.
Loadout does nothing to the shop: a client fills its shop from its own data,
and takes the items it suggests from its champion’s own data.
In 1.0.0.58–1.0.0.129
The data of the map
VersionSyncnames lists the items that cannot be bought, and can list the only items the shop holds. No mode or variant has a list of its own, and nothing a server sends changes what can be bought.
In 1.0.0.58–1.0.0.60
A client uses the map’s list of the items the shop holds only where a setting of its own turns it on.
In 1.0.0.96
Suggested items are kept per champion, whatever the map or the mode.
Buying and selling
A client asks to buy with BuyItem, to sell or throw away an item with
RemoveItem, and to swap two slots of its inventory with SwapItems. Closing
the shop sends nothing.
In 1.0.0.25–1.0.0.69
A client never asks to swap two slots: it has no
SwapItems.
Opening the shop sends TutorialShopOpened, in any match, except while the
shop is locked.
In 1.0.0.126–1.0.0.129
Opening the shop while the match is paused sends nothing.
A client asks to buy only where the item is one the match sells and priced within the champion’s gold.
A client asks for an item not built from others only where a slot is free or holds the same item below its stack limit.
In 1.0.0.25–1.0.0.60
A client asks for an item a player holds only one of even where the player holds it already, and an item that can be used in the shop needs a slot as any other does.
A client asks only while the shop is not locked, with the champion dead or near a shop of its side.
In 1.0.0.126–1.0.0.129
A client never asks for an item a player holds only one of and holds already.
In 1.0.0.126
A client asks only with the shop open.
A client never places an item itself. It shows a purchase only when a server
answers with ItemAdded, a sale or loss with RemoveItemAnswer, and a swap
with SwapItemsAnswer. A server can also set a slot (InventorySlot), set the
whole inventory (InventorySnapshot), change an item’s charges
(ItemCharges), or report an item used (ItemUsed).
ItemAdded places the item and removes nothing: a server sends a
RemoveItemAnswer for each part an item built from others takes up. Gold
falls only as replication states the champion’s gold, and a purchase a server
never answers places nothing and spends nothing.
In 1.0.0.58–1.0.0.129
A purchase a server never answers still plays the sound of buying.
Undo
Where VersionSync’s features set shopUndo, the shop has an undo button, which
is enabled while ShopUndoCount gives the champion undos to spend. Pressing it
sends ShopUndo, whatever the count.
Closing and locking
CloseShop closes the shop where it is open. A message that locks the shop
alone, InputLock or InputLockToggled, closes it and turns off its key.
A message that locks other input along with the shop stops the shop opening, but leaves an open shop open and its key on.
Messages
Each message of this system in this book, with each layout it has across the book’s patches and every note its definition carries. A layout is the message’s body, after the header its channel’s family puts in front (see Messages).
Loadout
What a server sends to lay out everything a champion brought to the match: the runes set before it began, its summoner slots and the choices made alongside them. The header names the unit this is about.
In 1.0.0.25–1.0.0.57
Command 83 on events, sent by the server, reliable.
A client’s shop is set up by the Loadout of its own champion: until that arrives the shop opens empty, with no items, no suggested items and no builds, and is drawn at a size that does not fit the screen. A server sends one for every champion at spawning, between SpawnStart and SpawnEnd.
| Field | Type | What it is |
|---|---|---|
| runes | 30 × u32 | The runes set before the match, thirty places. |
| summoners | 2 × u32 | The spells in the champion’s summoner slots, by the numbers their names give. |
| choices | 80 × Choice | The choices made alongside them, 400 bytes that a client keeps as one block. |
| level | u8 | The player’s account level. |
In 1.0.0.58–1.0.0.62
Command 83 on events, sent by the server, reliable.
A client sets the champion’s two summoner slots from summoners, a zero leaving its slot as it was, and keeps the runes, the choices and level. It changes nothing in the shop.
| Field | Type | What it is |
|---|---|---|
| runes | 30 × u32 | The runes set before the match, thirty places. |
| summoners | 2 × u32 | The spells in the champion’s summoner slots, by the numbers their names give. |
| choices | 80 × Choice | The choices made alongside them, 400 bytes that a client keeps as one block. |
| level | u8 | The player’s account level. |
Vectors (1)
In 1.0.0.63–1.0.0.127
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.63–1.0.0.73 | 89 |
| 1.0.0.74–1.0.0.81 | 90 |
| 1.0.0.82–1.0.0.96 | 94 |
| 1.0.0.97–1.0.0.102 | 95 |
| 1.0.0.103–1.0.0.106 | 96 |
| 1.0.0.107–1.0.0.108 | 97 |
| 1.0.0.109 | 98 |
| 1.0.0.110–1.0.0.123 | 43 |
| 1.0.0.124–1.0.0.125 | 44 |
| 1.0.0.126–1.0.0.127 | 44 |
A client’s shop is set up by the Loadout of its own champion: until that arrives the shop opens empty, with no items, no suggested items and no builds, and is drawn at a size that does not fit the screen. A server sends one for every champion at spawning, between SpawnStart and SpawnEnd.
| Field | Type | What it is |
|---|---|---|
| runes | 30 × u32 | The runes set before the match, thirty places. |
| summoners | 2 × u32 | The spells in the champion’s summoner slots, by the numbers their names give. |
| choices | 80 × Choice | The choices made alongside them, 400 bytes that a client keeps as one block. |
| level | u8 | The player’s account level. |
In 1.0.0.128–1.0.0.129
Command 44 on events, sent by the server, reliable.
A client’s shop is set up by the Loadout of its own champion: until that arrives the shop opens empty, with no items, no suggested items and no builds, and is drawn at a size that does not fit the screen. A server sends one for every champion at spawning, between SpawnStart and SpawnEnd.
| Field | Type | What it is |
|---|---|---|
| runes | 30 × u32 | The runes set before the match, thirty places in runs of nine, nine, nine and three. A place holds zero where nothing was set. |
| summoners | 2 × u32 | The spells in the champion’s summoner slots, by the numbers their names give. |
| choices | 80 × Choice | The choices made alongside them, one place each, and how far each was taken. A place stands empty where nothing was chosen. |
| level | u8 | The player’s account level. |
BuyItem
What a client sends to buy an item from the shop. The header names the sender’s champion.
In every range of this book
Carried on requests, sent by the client, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.25–1.0.0.81 | 41 |
| 1.0.0.82–1.0.0.96 | 44 |
| 1.0.0.97–1.0.0.102 | 45 |
| 1.0.0.103–1.0.0.106 | 46 |
| 1.0.0.107–1.0.0.109 | 47 |
| 1.0.0.110 | 128 |
| 1.0.0.111–1.0.0.116 | 129 |
| 1.0.0.117–1.0.0.118 | 130 |
| 1.0.0.119–1.0.0.123 | 131 |
| 1.0.0.124–1.0.0.129 | 135 |
| Field | Type | What it is |
|---|---|---|
| item | u32 | Which item, by the number the client knows it as. |
RemoveItem
What a client sends to be rid of an item. The header names the sender’s champion.
In 1.0.0.25–1.0.0.98
Carried on requests, sent by the client, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.25–1.0.0.81 | 43 |
| 1.0.0.82–1.0.0.96 | 46 |
| 1.0.0.97–1.0.0.98 | 47 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot. |
| sell | u8 | A client sends 1. |
Vectors (4)
one-on-1-0-0-75, one-on-1-0-0-81, one-on-1-0-0-96, one-on-1-0-0-98
In 1.0.0.99–1.0.0.125
Carried on requests, sent by the client, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.99–1.0.0.102 | 47 |
| 1.0.0.103–1.0.0.106 | 48 |
| 1.0.0.107–1.0.0.109 | 49 |
| 1.0.0.110–1.0.0.125 | 9 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot. |
| sell | u8 | A client sends 1 from the shop or a hotkey, and 0 after an answer to a purchase. |
Vectors (4)
one-on-1-0-0-99, one-on-1-0-0-106, one-on-1-0-0-109, one-on-1-0-0-125
In 1.0.0.126–1.0.0.127
Command 9 on requests, sent by the client, reliable.
| Field | Type | What it is |
|---|---|---|
| which | 1-byte bits | |
| which.slot | bit 0 to 6 | Which slot. |
| which.sell | bit 7 | Set to sell the item, clear to throw it away. |
Vectors (1)
In 1.0.0.128–1.0.0.129
Command 9 on requests, sent by the client, reliable.
| Field | Type | What it is |
|---|---|---|
| which | 1-byte bits | |
| which.slot | bit 0 to 6 | Which slot. |
| which.sell | bit 7 | Set to sell the item, clear to throw it away. A client always sends it set. |
SwapItems
What a client sends to move an item from one slot to another. The header names the sender’s champion.
In 1.0.0.70–1.0.0.123
Carried on requests, sent by the client, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.70–1.0.0.81 | 45 |
| 1.0.0.82–1.0.0.96 | 48 |
| 1.0.0.97–1.0.0.102 | 49 |
| 1.0.0.103–1.0.0.106 | 50 |
| 1.0.0.107–1.0.0.109 | 51 |
| 1.0.0.110–1.0.0.123 | 34 |
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item leaves, 0 to 5. |
| to | u8 | The slot it goes to, 0 to 5. A client never sends the slot named by from. |
In 1.0.0.124–1.0.0.127
Command 35 on requests, sent by the client, reliable.
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item leaves, at most 37. |
| to | u8 | The slot it goes to, at most 37. A client never sends the slot named by from. |
Vectors (1)
In 1.0.0.128–1.0.0.129
Command 35 on requests, sent by the client, reliable.
| Field | Type | What it is |
|---|---|---|
| from | u8 | |
| to | u8 |
TutorialShopOpened
What a client sends as its player opens the shop. It carries nothing of its own. The header carries zero.
In 1.0.0.25–1.0.0.73
Command 148 on requests, sent by the client, reliable.
A client sends it every time its player opens the shop, in any game. Where a script of the client’s has locked the shop, the shop does not open and nothing is sent.
No body.
Vectors (1)
In 1.0.0.74–1.0.0.81
Command 149 on requests, sent by the client, reliable.
A client sends it only in the tutorial: where the version answer names the mode TUTORIAL and the map’s own data marks it as a tutorial map, as map 12’s does; elsewhere it never sends this.
No body.
Vectors (2)
In 1.0.0.82–1.0.0.96
Command 153 on requests, sent by the client, reliable.
A client sends it whenever its player opens the shop, in every mode and on every map.
No body.
Vectors (1)
In 1.0.0.97–1.0.0.123
Carried on requests, sent by the client, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.97 | 154 |
| 1.0.0.98–1.0.0.102 | 155 |
| 1.0.0.103 | 157 |
| 1.0.0.104–1.0.0.106 | 162 |
| 1.0.0.107–1.0.0.108 | 163 |
| 1.0.0.109 | 164 |
| 1.0.0.110–1.0.0.116 | 91 |
| 1.0.0.117–1.0.0.118 | 92 |
| 1.0.0.119–1.0.0.123 | 93 |
A client sends it only in the tutorial: where the version answer names the mode TUTORIAL and the map’s own data marks it as a tutorial map, as map 12’s does; elsewhere it never sends this.
No body.
In 1.0.0.124–1.0.0.129
Command 96 on requests, sent by the client, reliable.
A client sends it each time the shop opens, in any mode and on any map, except while a script lock keeps the shop shut or the match is paused.
No body.
Vectors (1)
ItemAdded
What a server sends to set what sits in one of a unit’s item slots. The header names the unit this is about.
In 1.0.0.25–1.0.0.81
Command 42 on events, sent by the server, reliable.
There is no charges field: a client takes an item’s charges from the item’s own data. A client applies it only to a champion’s item slots.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | The slot it went to, 0 to 36. A larger value than 36 has no defined effect. |
| item | u32 | Which item, by the number the client knows it as. For an item it does not know, a client empties the slot and still takes inSlot. |
| inSlot | u8 | How many of the item the slot holds now; a client applies zero as well. The slot’s charges come from the item’s own data. |
Vectors (2)
In 1.0.0.82–1.0.0.96
Command 45 on events, sent by the server, reliable.
There is no charges field: a client takes an item’s charges from the item’s own data. A server sends it to units nobody is buying for.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | The slot it went to, 0 to 36. A larger value than 36 has no defined effect. |
| item | u32 | Which item, by the number the client knows it as. For an item it does not know, a client empties the slot and still takes inSlot. |
| inSlot | u8 | How many of the item the slot holds now; a client applies zero as well. The slot’s charges come from the item’s own data. |
Vectors (1)
In 1.0.0.97–1.0.0.98
Command 46 on events, sent by the server, reliable.
There is no charges field: a client takes an item’s charges from the item’s own data. A server sends it to units nobody is buying for.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | The slot it went to, 0 to 36. A client rejects the message from 37 up. |
| item | u32 | Which item, by the number the client knows it as. |
| inSlot | u8 | How many of the item the slot holds now; zero leaves the slot as it was. The slot’s charges come from the item’s own data. |
Vectors (1)
In 1.0.0.99–1.0.0.123
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.99–1.0.0.102 | 46 |
| 1.0.0.103–1.0.0.106 | 47 |
| 1.0.0.107–1.0.0.109 | 48 |
| 1.0.0.110 | 108 |
| 1.0.0.111–1.0.0.116 | 109 |
| 1.0.0.117–1.0.0.118 | 110 |
| 1.0.0.119–1.0.0.123 | 111 |
There is no charges field: a client takes an item’s charges from the item’s own data. A server sends it to units nobody is buying for.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | The slot it went to, 0 to 37. A client rejects the message from 38 up. |
| item | u32 | Which item, by the number the client knows it as. |
| inSlot | u8 | How many of the item the slot holds now; zero leaves the slot as it was. The slot’s charges come from the item’s own data. |
| activate | u8 | What this carries is not recorded. Where it is not zero, a client refreshes the slot and, where the slot holds an item, sends RemoveItem for it with sell clear; a server sends zero. |
In 1.0.0.124–1.0.0.127
Command 114 on events, sent by the server, reliable.
It answers no request: where inSlot is above zero, a client puts item and inSlot in the slot whether or not anything asked for it. There is no charges field: a client takes an item’s charges from the item’s own data. A server sends it to units nobody is buying for.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | The slot it went to, 0 to 37. A client rejects the message from 38 up. |
| item | u32 | Which item, by the number the client knows it as. |
| inSlot | u8 | How many of the item the slot holds now; zero leaves the slot as it was. The slot’s charges come from the item’s own data. |
| activate | u8 | What this carries is not recorded. Where it is not zero, a client refreshes the slot and, where the slot holds an item, sends RemoveItem for it with sell clear; a server sends zero. |
Vectors (1)
In 1.0.0.128–1.0.0.129
Command 114 on events, sent by the server, reliable.
A server sends it to units nobody is buying for.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | The slot it went to. A client rejects the message from 38 up. |
| item | u32 | Which item, by the number the client knows it as. |
| inSlot | u8 | How many of the item the slot holds; zero leaves the slot as it was. The slot’s charges come from the item’s own data. |
| activate | u8 | Nonzero readies the item’s own spell, in the slot four past the item’s, and has the client answer with RemoveItem for it. |
RemoveItemAnswer
What a server sends to confirm an item left a slot. The header names the unit this is about.
In 1.0.0.25–1.0.0.96
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.25–1.0.0.81 | 44 |
| 1.0.0.82–1.0.0.96 | 47 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 36. A larger value than 36 has no defined effect. |
| left | u8 | How many are left in the slot; zero empties it, item and charges cleared. |
Vectors (3)
In 1.0.0.97–1.0.0.98
Command 48 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 36. A client drops the message from 37 up. |
| left | u8 | How many are left in the slot; zero empties it, item and charges cleared. Either way a client cancels any spell or action its player had picked. |
Vectors (1)
In 1.0.0.99–1.0.0.125
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.99–1.0.0.102 | 48 |
| 1.0.0.103–1.0.0.106 | 49 |
| 1.0.0.107–1.0.0.109 | 50 |
| 1.0.0.110–1.0.0.125 | 11 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 37. A client drops the message from 38 up. |
| left | u8 | How many are left in the slot; zero empties it, item and charges cleared. Either way a client cancels any spell or action its player had picked. |
Vectors (4)
one-on-1-0-0-99, one-on-1-0-0-106, one-on-1-0-0-109, one-on-1-0-0-110
In 1.0.0.126–1.0.0.127
Command 11 on events, sent by the server, reliable.
A client takes it only for a champion, and ignores it for any other unit.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 37. A client drops the message from 38 up. |
| left | u8 | How many are left in the slot; zero empties it, item and charges cleared. Either way a client cancels any spell or action its player had picked. |
Vectors (1)
In 1.0.0.128–1.0.0.129
Command 11 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 37. For a higher one a client does nothing at all; for 0 to 37 it updates the slot and tells its screens the inventory changed, whatever left is. |
| left | u8 | How many are left in the slot; zero empties it, item and charges cleared. Either way a client cancels any spell or action its player had picked. |
SwapItemsAnswer
What a server sends to confirm an item moved between slots. The header names the unit this is about.
In 1.0.0.25–1.0.0.81
Command 46 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item left, 0 to 36. A client swaps the two slots named whatever their values, so a server keeps both within range. |
| to | u8 | The slot it went to, 0 to 36. A client swaps the two slots named whatever their values, so a server keeps both within range. |
Vectors (2)
In 1.0.0.82–1.0.0.96
Command 49 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item left, 0 to 5. A client does not check it, and a value above 36 can bring the client down. |
| to | u8 | The slot it went to, 0 to 5. A client does not check it, and a value above 36 can bring the client down. |
Vectors (1)
In 1.0.0.97–1.0.0.123
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.97–1.0.0.102 | 50 |
| 1.0.0.103–1.0.0.106 | 51 |
| 1.0.0.107–1.0.0.109 | 52 |
| 1.0.0.110–1.0.0.116 | 64 |
| 1.0.0.117–1.0.0.118 | 65 |
| 1.0.0.119–1.0.0.123 | 66 |
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item left, 0 to 5. A client ignores the message for any other. |
| to | u8 | The slot it went to, 0 to 5. A client ignores the message for any other. |
In 1.0.0.124–1.0.0.127
Command 68 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item left, 0 to 37. A client ignores the message where it is 38 or more. |
| to | u8 | The slot it went to, 0 to 37. A client ignores the message where it is 38 or more. |
Vectors (1)
In 1.0.0.128–1.0.0.129
Command 68 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| from | u8 | The slot the item left. |
| to | u8 | The slot it went to. |
InventorySlot
What a server sends to set one slot of a unit’s inventory. The header names the unit. A client empties the slot, then fills it where count is above zero, and refreshes the shop where the unit is its own champion.
In 1.0.0.97–1.0.0.98
Command 44 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 36. A client ignores the message from 37 up. |
| item | u32 | The item. It has no effect where count is zero. |
| count | u8 | How many. Zero leaves the slot empty. |
| charges | u8 | Its charges. |
Vectors (1)
In 1.0.0.99–1.0.0.127
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.99–1.0.0.102 | 44 |
| 1.0.0.103–1.0.0.106 | 45 |
| 1.0.0.107–1.0.0.109 | 46 |
| 1.0.0.110–1.0.0.116 | 82 |
| 1.0.0.117–1.0.0.118 | 83 |
| 1.0.0.119–1.0.0.123 | 84 |
| 1.0.0.124–1.0.0.127 | 86 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 37. A client ignores the message from 38 up. |
| item | u32 | The item. It has no effect where count is zero. |
| count | u8 | How many. Zero leaves the slot empty. |
| charges | u8 | Its charges. |
In 1.0.0.128–1.0.0.129
Command 86 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 39. A client ignores the message from 40 up. |
| item | u32 | The item. It has no effect where count is zero. |
| count | u8 | How many. Zero leaves the slot empty. |
| charges | u8 | Its charges. |
ItemUsed
What a server sends after an item in a unit’s inventory is used. The header names the unit.
In 1.0.0.74–1.0.0.96
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.74–1.0.0.81 | 47 |
| 1.0.0.82–1.0.0.96 | 50 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 36. A larger value than 36 has no defined effect, and a client ignores the message where the slot is empty. |
| left | u8 | How many are left in it; zero empties the slot. |
| charges | u8 | How many charges it holds. |
Vectors (3)
In 1.0.0.97–1.0.0.98
Command 51 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 36. A client ignores the message from 37 up, and where the slot is empty. |
| left | u8 | How many are left in it; zero empties the slot. |
| charges | u8 | How many charges it holds. |
Vectors (1)
In 1.0.0.99–1.0.0.127
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.99–1.0.0.102 | 51 |
| 1.0.0.103–1.0.0.106 | 52 |
| 1.0.0.107–1.0.0.109 | 53 |
| 1.0.0.110 | 158 |
| 1.0.0.111–1.0.0.116 | 159 |
| 1.0.0.117–1.0.0.118 | 160 |
| 1.0.0.119–1.0.0.123 | 161 |
| 1.0.0.124 | 165 |
| 1.0.0.125 | 166 |
| 1.0.0.126–1.0.0.127 | 167 |
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot, 0 to 37. A client ignores the message from 38 up, and where the slot is empty. |
| left | u8 | How many are left in it; zero empties the slot. |
| charges | u8 | How many charges it holds. |
In 1.0.0.128–1.0.0.129
Command 167 on events, sent by the server, reliable.
| Field | Type | What it is |
|---|---|---|
| slot | u8 | Which slot. |
| left | u8 | How many are left in it; zero empties the slot. |
| charges | u8 | How many charges it holds. |
CloseShop
What a server sends to close a client’s shop. The header carries zero.
In every range of this book
Carried on events, sent by the server, reliable, under these commands:
| Builds | Command |
|---|---|
| 1.0.0.25–1.0.0.73 | 146 |
| 1.0.0.74–1.0.0.81 | 147 |
| 1.0.0.82–1.0.0.96 | 151 |
| 1.0.0.97 | 152 |
| 1.0.0.98–1.0.0.102 | 153 |
| 1.0.0.103 | 155 |
| 1.0.0.104–1.0.0.106 | 160 |
| 1.0.0.107–1.0.0.108 | 161 |
| 1.0.0.109 | 162 |
| 1.0.0.110–1.0.0.129 | 15 |
No body.