nanites
Sanity is low, stay addicted.
Vars | |
| start_time | Separate list of protocol programs, to avoid looping through the whole programs list when cheking for conflicts |
|---|---|
| stealth | Timestamp to when the nanites were first inserted in the host |
Procs | |
| add_program | Adds a nanite program, replacing existing unique programs of the same type. A source program can be specified to copy its programming onto the new one. |
| adjust_nanites | Modifies the current nanite volume, then checks if the nanites are depleted or exceeding the maximum amount |
| cloud_sync | Syncs the nanites to their assigned cloud copy, if it is available. If it is not, there is a small chance of a software error instead. |
| delete_nanites | Deletes nanites! |
| reject_excess_nanites | Handles how nanites leave the host's body if they find out that they're currently exceeding the maximum supported amount |
| set_nanite_bar | Updates the nanite volume bar visible in diagnostic HUDs |
| sync | Syncs the nanite component to another, making it so programs are the same with the same programming (except activation status) |
Var Details
start_time
Separate list of protocol programs, to avoid looping through the whole programs list when cheking for conflicts
stealth
Timestamp to when the nanites were first inserted in the host
Proc Details
add_program
Adds a nanite program, replacing existing unique programs of the same type. A source program can be specified to copy its programming onto the new one.
adjust_nanites
Modifies the current nanite volume, then checks if the nanites are depleted or exceeding the maximum amount
cloud_sync
Syncs the nanites to their assigned cloud copy, if it is available. If it is not, there is a small chance of a software error instead.
delete_nanites
Deletes nanites!
reject_excess_nanites
Handles how nanites leave the host's body if they find out that they're currently exceeding the maximum supported amount
IC explanation: Normally nanites simply discard excess volume by slowing replication or 'sweating' it out in imperceptible amounts, but if there is a large excess volume, likely due to a programming change that leaves them unable to support their current volume, the nanites attempt to leave the host as fast as necessary to prevent nanite poisoning. This can range from minor oozing to nanites rapidly bursting out from every possible pathway, causing temporary inconvenience to the host.
set_nanite_bar
Updates the nanite volume bar visible in diagnostic HUDs
sync
Syncs the nanite component to another, making it so programs are the same with the same programming (except activation status)