Editing Guide to Nanites (section)

=Nanites=
==Implanting==
[[File:Nanite_chamber.gif|thumb|Nanite Chamber]]
Nanite implantation can be done through the Nanite Chamber. A second person must operate the chamber from outside and begin the implanting process, at the end of which a new swarm will take root in the host. <br>

Another method is to build a [[Machines#Public_Nanite_Chamber|Public Nanite Chamber]]. Use a multitool on the Public Nanite Chamber circuit board first to choose which [[#Cloud|backup cloud]] you want it synched to. If you don't multitool the board it will default to [[#Cloud|cloud]] 1. Build the chamber using a machine frame. The public nanite chamber will automatically implant nanites into anyone who enters it, without the need for a second person. 

==Nanite Tools==
There are currently three tools that can be used by nanite programmers. 
===Nanite Scanner===
Use this to scan implanted people. It will give you a readout with information about current [[#Volume|nanite volume]], which [[#Nanite_Types|nanite programs]] are currently implanted and their active/inactive status. If a nanite swarm contains the "Stealth" [[#Utility_Programs|utility program]] you will not be able to see the list of programs. 

===Nanite Remote Control===
A remote used for sending signals to implanted nanites. Change its settings and then click anywhere or on a target to activate it. For example you can set the code to be the trigger code you gave the "Host Scan" program. Using this in hand will open a menu. Settings:
*'''Signal Code''': Which code you want it to signal. 
*'''Signal Mode''': Choose between "off" (makes remote do nothing), "local" (only signals the user), "targeted" (signals whoever you click directly on), "area" (signals anyone within your line of sight) and "relay" (signals any existing nanite programs that have a chosen "relay code"). 
*'''Save Current Setting''': Lets you save current setting to a list, with a name of choice. Not saved between rounds. 
*'''Lock Interface''': Locks the settings. Alt-click the remote to unlock. 

===Nanite Communication Remote===
A remote used for sending custom messages to the "Skull Echo", "Forced Speech" and "Hallucination (message only)" programs. The settings are very similar to those of the Nanite Remote Control. The difference is you set a ''Comm Code'' and ''Message'' instead of ''Signal Code'' and ''Relay''. The programs installed must have the same ''Comm Code'' to be able to signal them with this remote.

==Volume==
If wearing a [[Research_items#Diagnostic_HUD|diagnostic HUD]] [[File:Diag_glasses.png]] you will be able to see a bar next to implanted people, which is a nanite volume meter. Nanites generally expend a part of their volume while their programs are active. Luckily, modern technology allows them to integrate with the host's metabolism to replicate without interfering with biological processes, causing them to have a slow but steady growth rate. 

Nanites by default have a safety threshold where they'll stop using nanite-consuming programs. This threshold can be customized in an individual by entering a Nanite Chamber, and having a second person operate the connected nanite chamber control console.If the swarm reaches a population of 0, there's none left to replicate, and the nanites are completely removed. 

==Programming==
Nanite swarms can contain nanite programs. These programs can have a huge variety of effects, and are loaded into a nanite swarm in two main ways: uploading them manually with a Nanite Chamber or by syncing them with a Cloud Backup.
Once loaded programs cannot be directly modified; instead, a copy of the same program with the desired programming must be uploaded again to overwrite the previous one.
There is no limit to the amount of loaded programs, but using too many at once will usually rapidly deplete the nanite population.

==Cloud==
Nanite swarms can be set with a Cloud ID. If so, they will, every 30 seconds, copy the programming of the Cloud Backup with the same ID, if it has been set.
Cloud backups are controlled by Cloud Control Consoles. They can create new backups (with codes from 1 to 100), as well as upload programs from a disk into the selected backup.
Cloud control consoles also serve as storage, meaning that if they're disabled they will no longer sync with connected nanites, and that if all cloud consoles are destroyed, all backups will be lost.

Cloud synchronization has several benefits over direct chamber programming: it can update programs without a second person to operate the chamber, it will reset programming in case of tampering or data corruption, and can be updated remotely by a second person. Of course, the last part also makes it very risky, since anyone could upload malicious programs at any time if they have a console to do it with.