Category:CARBON

"&lt;&gt; wollen wir unsers nicht lieber cocoa nennen? &lt;&gt; :D &lt;&gt; carbon ist deprecated &lt;&gt; und läuft nicht auf 64 bit"

Planned

CARBON stands for Completely Automated Redstone Binary-Operated Node, and is the name of the railway system in the Overworld. It is named after /r/mcpublic's railway system.

The basic principle is the same as on /r/mcpublic: each possible destination in the network has a unique ID, called the CARBON code, which can be selected using a series of levers by setting them to its binary representation. The system will then send the selected destination along with the minecart using redstone, and router nodes will read the signal to decide where to send the minecart.

Wurstmineberg's version of CARBON will add new features not present on /r/mcpublic: the railway network will be divided into logical units called nodes, each with a system to prevent minecarts from colliding or corrupting each other's destination signal. The network will also work for minecarts with chests, and may in some cases connect to the Soup, meaning that some Soup channels will also be accessible as CARBON destinations.

Usage
With a routing system as heavily automated as CARBON, anyone using the network should try to follow these rules and guidelines:


 * Only enter registered CARBON codes marked as usable (see for the full list). The behavior of the CARBON network when unregistered ccs (or a cc for which the routing is still being installed) are entered is undefined: it may do anything from defaulting to 's base as a destination, to breaking a router node beyond repair, to dumping you or your items into.
 * When using private extensions of the CARBON network, similar restrictions may apply. Please see the extension's documentation for details or ask the owner directly.
 * Do not exit the minecart while you are on the tracks, even while standing still. All destinations will be clearly marked as such and/or have to eject you automatically.
 * Also, please try not to die while using CARBON, as this will cause all sorts of issues.
 * If you accidentally exited a minecart, or died while using the system, please immediately alert anyone who is currently online so that they won't use the system, and contact a GoldCart employee.
 * If someone else has broken CARBON in this way, you should assume that the entire network in malfunctioning until it has been reviewed by a GoldCart employee. Please use some other means of transportation instead, for example the Newther Hub system.
 * Do not log out while you are in the minecart, even while standing still.
 * Please do not use CARBON while you are on a train IRL.
 * If you lose connection or the server restarts while you are on the tracks, please relog as soon as possible in order to minimize delays caused by other carts waiting for your node to be unlocked.
 * If you log out for an extended period of time while in the CARBON system, we may temporarily remove you from the whitelist and manually unlock the node(s) you were using. This does not mean that we don't want you on the server anymore; it simply allows us to continue to use CARBON. Instead, please contact a GoldCart employee if you want to play again, so that we can manually lock and reprogram the node(s) your cart was using before re-whitelisting you.
 * If anything seems wrong (e.g. your minecart is going in a wrong direction or standing still for an extended period of time), please stay in your cart and contact a GoldCart employee.

Note that these are only a draft as we are still working out some of the details of the system.

Destinations
This table is a draft of planned destinations and their CARBON codes. None of these have been registered yet.

Registration
A registration system is yet to be determined, and will depend on the number of bits which can be encoded serially in the CARBON system. However, here are some ideas:


 * As has been discussed early in the design process, a registered destination will normally have two CARBON codes, one for players and one for items. The code for players will be an even number (ending in binary digit ), and the code for items will be that number plus one. For example, a destination might have cc   for players, and cc   for items.
 * If the number of serializable bits is high enough, entire sections of codes may be reserved for certain regions on the map to make routing easier. For example, codes  to   may be reserved for spawn.
 * Like /r/mcpublic, we should have a cc for the End, which will route you to the nearest stronghold. A similar cc for the Newther Hub network may be nice to have too.
 * The system can be integrated with the Soup, but there is no need to waste ccs for this. A destination accepting items can just drain them into its Soup channel wherever appropriate.