[wip after 1.3.0]
The Maintenance Unit is an element that is used to repair damage to constructs, or to disassemble whole constructs into is constituent elements and voxels/
To repair a construct the unit take a stored snapshot of a constructs blueprint that is saved in the core and by consuming scrap or elements return the construct to its original state, even if entire sections are destroyed.
When a player opens the maintenance unit interface the unit will scan for all constructs within a 1 km range and will list all constructs the player has repair rights and build rights.
A maintenance unit must be connected to a container or a container hub and only one maintenance unit can be connected to that hub or container.
The repair unit is ideal in the following circumstances;
- Voxel damage due to PvP
- Taking restore points when performing complex voxel work to easily revert changes
Maintenance units are not addressable via lua and have one container/hub input link
Units can only repair/restore one unit at a time.
Snapshots[]
There are two types of snapshots Automatic and Manual. An automatic snapshot is taken when a player modifies part of a construct and a manual snapshot is taken by selecting the core RMB > Construct > Advanced > Take Manual Snapshot. These two mechanisms provide the player with two restore points. After selecting the construct to repair the player will be presented with the current snapshots stored in the constructs core and they can choose between Automatic and Manual snapshot.
Once OK is selected the repair lockdown timer of 15 starts, at this stage nothing is changing on the construct. A final window will appear at the end of the timer where the player can choose to approve or reject the snapshot restore.
Currently if you select cancel the ship will still be locked out for the repair time in the table below
Repair times[]
Each construct size has a repair time regardless of the number of elements or volume of voxels. During repair a player cannot enter build mode, pilot or tokenize the construct. All other programming boards continue to work and containers are accessible.
| Core Size | Repair Time |
|---|---|
| XS | 4 hours |
| S | 6 hours |
| M | 8 hours |
| L | 12 hours |
For more information, see the Scrap page.
The repair time is the same regardless of the tier of scrap used, although the volume required will be less for higher tier scrap