-
Notifications
You must be signed in to change notification settings - Fork 9
Address
#Definition
Address are used by Bytecart to identify a specific station in the world.
Address are composed of 3 parts :
Address are represented by putting the 3 parts together, separated by a dot : region.ring.station
Any address may be shifted to hold some properties :
- +32 to station number mark the first cart of a train.
Any address belong to a subnet. The subnet is identified by the region and the ring number.
Address sharing the same region numer and the same ring number are in the same subnet. Stations in the same ring must have an address in the same subnet, i.e same region and ring number.
22.7.11 designates station #11 in the subnet 22.7.0 (i.e in region #22, track #7).
22.7.7 is an address in the same subnet: the station is located in the same ring.
22.4.10 is an address in another subnet, and necessarily in another ring.
Address can be represented in 2 forms :
- litterally in the form region.ring.station in commands and on signs.
- in inventories of player or storage cart to be readable by ByteCart devices (see below).
- in books prepared as tickets
ByteCart use internal functions to write address in tickets. Parameters are written litteraly in books and are readable by anyone. This is the default system.
Prior to v1.3.1, ByteCart was using an alternate system to store address in inventory. This system still exists as a legacy system.
In legacy system, ByteCart uses an algorithm that reorganizes inventory to write an address, without giving or removing any items. If conditions are not met to write the address, an error is triggered.
Address can be set in inventory or books by several means:
mego sets address in player's inventory or in book
sendto sets address in storage cart, in inventory or book, including a full stack of items for TTL
Left-click the signs or pass over them with a cart to activate them.
BC7010 updates player's inventory or book, has no effect on storage cart.
BC7011 updates storage carts (including TTL) and player's inventory, or book in cart or player inventory.
When a player wants to travel to a specific station from any point of the network, he needs to get a ticket and set his destination address before riding a cart. The inventory is the place where each ByteCart device will look for a ticket when performing routing operations.
When one wants to send a storage cart, one will use the inventory of the storage cart to store a ticket.
Same principle is applied with legacy system.
An address can be "written" in inventory of player or storage cart by filling slots #0, #1 and #2 with each part of the address. See Inventory slot number to match slot number with cell of inventory window. The slots can be filled with whatever type item of the game. Commands and signs can do this automatically.
For example, to set destination address 12.25.10 in an inventory, one would put 12 cobbles in slot 0, 25 wheat in slot 1 and 10 wood in slot 2. we can also use only cobbles if we want.
As such, a player will be transported to station 12.25.10 when using the network.
Filling the inventory of a storage cart follow the same rules, with additional requirement : the slot #3 must contain the TTL. Putting a full stack (64 items) in slot #3 is a good practice.