This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
item:nanomachines [2016/01/14 01:28] inari rework page to hopefully be better, remove outdated info |
item:nanomachines [2018/03/21 07:59] payonel |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| === Basic Usage === | === Basic Usage === | ||
| - | The player has to "eat" them before they can be used. Once ingested, a power indicator in the HUD, positioned left of the item bar, will indicate how much energy the nanomachines have left. Their energy can be recharged by standing close to a [[block:Charger]]. | + | The player has to "eat" them before they can be used. Once ingested, a power indicator in the HUD, positioned left of the item bar, will indicate how much energy the nanomachines have left. Their energy can be recharged by standing close to a [[block:Charger]]. Energy is slowly used over time proportional to the number of active inputs. A small amount of energy is still lost over time even when all inputs are deactivated. |
| They provide a certain number of "inputs" that can be toggled, causing many different effects on the player, ranging from visual effects such as particles spawning near the player, to select potion effects and some more rare and special behaviors. | They provide a certain number of "inputs" that can be toggled, causing many different effects on the player, ranging from visual effects such as particles spawning near the player, to select potion effects and some more rare and special behaviors. | ||
| Which input triggers what effect depends on the current configuration of the nanomachines, the actual "connections" being random per configuration. Which input does what is not clear to the player until they try it. The configuration can be changed by ingesting a new batch of nanomachines. Additionally, enabling too many inputs at a time has severe negative effects. | Which input triggers what effect depends on the current configuration of the nanomachines, the actual "connections" being random per configuration. Which input does what is not clear to the player until they try it. The configuration can be changed by ingesting a new batch of nanomachines. Additionally, enabling too many inputs at a time has severe negative effects. | ||
| + | |||
| + | See the `nanomachines` section in the config for fine tuning to your preference. | ||
| To dispose of nanomachines, the player has to drink [[item:Grog]]. | To dispose of nanomachines, the player has to drink [[item:Grog]]. | ||
| Line 25: | Line 27: | ||
| Programming the machines happens through wireless messages. The range nanomachines are able to receive messages from is only about two meters, though this can be circumvented easily by using a tablet to send the messages. However, the nanomachines do not check which device sent the messages they receive. | Programming the machines happens through wireless messages. The range nanomachines are able to receive messages from is only about two meters, though this can be circumvented easily by using a tablet to send the messages. However, the nanomachines do not check which device sent the messages they receive. | ||
| - | A simple protocol is used to control the machines: each packet consists of multiple parts, the first of which must equal the string "nanomachines". The second part is the command name. Additional parts are parameters for the command. The following commands are available: | + | Nanomachines react to a simple, proprietary protocol: each packet must consist of multiple parts, the first of which is the "header" and must equal the string `nanomachines`. The second part must be the command name. Additional parts are parameters for the command. The following commands are available, formatted as `commandName(arg1, ...)`: |
| - | - `setResponsePort(port:number)` | + | - `setResponsePort(port:number)` - Set the port nanomachines should send response messages to, for commands that have a response. |
| - | Set the port nanomachines should send response messages to, for commands that have a response. | + | - `getPowerState()` - Request the currently stored and maximum stored energy of the nanomachines. |
| - | - `getTotalInputCount()` | + | - `getHealth()` - Request the player's health state. |
| - | Request a message with the total number of available inputs. | + | - `getHunger()` - Request the player's hunger state. |
| - | - `getSafeInputCount()` | + | - `getAge()` - Request the player's age in seconds. |
| - | Request a message with the number of safe inputs. | + | - `getName()` - Request the player's display name. |
| - | - `getInput(index:number)` | + | - `getExperience()` - Request the player's experience level. |
| - | Request a message with the current state of the input with the specified index. | + | - `getTotalInputCount()` - Request the total number of available inputs. |
| - | - `setInput(index:number, value:boolean)` | + | - `getSafeActiveInputs()` - Request the number of *safe* active inputs. |
| - | Set the state of the input with the specified index to the specified value. | + | - `getMaxActiveInputs()` - Request the number of *maximum* active inputs. |
| - | - `getActiveEffects()` | + | - `getInput(index:number)` - Request the current state of the input with the specified index. |
| - | Request a list of active effects. Note that some effects may not show up in this list. | + | - `setInput(index:number, value:boolean)` - Set the state of the input with the specified index to the specified value. |
| - | - `getPowerState()` | + | - `getActiveEffects()` - Request a list of active effects. Note that some effects may not show up in this list. |
| - | Request a message with the currently stored and maximum stored energy of the nanomachines. | + | - `saveConfiguration()` - Requires a set of nanomachines in the players inventory, will store the current configuration to it. |
| For example, in OpenOS: | For example, in OpenOS: | ||
| - `component.modem.broadcast(1, "nanomachines", "setInput", 1, true)` will enable the first input. | - `component.modem.broadcast(1, "nanomachines", "setInput", 1, true)` will enable the first input. | ||
| - | - `component.modem.broadcast(1, "nanomachines", "reconfigure")` will reconfigure the nanomachines. | + | - `component.modem.broadcast(1, "nanomachines", "getHealth")` will get the player's health info. |
| === See also === | === See also === | ||