BetterStorage:Loading Mechanism
| |
| Type | Item |
|---|---|
| Stack size | 1 |
| Quality | Epic |
| Network role | Goes into the Storage Core |
| Storage | Keeps up to 64 chunks loaded (default) |
| Crafted at | Storage Assembler III or IV |
The Loading Mechanism keeps every chunk of a network loaded while it sits in the Storage Core. With it, a terminal far away from the core still sees the whole network.
Recipe
| Ingredients | Output | Station | Time |
|---|---|---|---|
| 4 Lodestone Plate, 2 Processor, 1 Memory Module II | 1 Loading Mechanism | Storage Assembler III or IV, Storage System | 5 s |
Lodestone comes from the Devastated Lands.
Putting it in
- Open the terminal.
- Click the Loading Mechanism in your inventory panel. It goes into the Storage Core and appears in the Loader column.
- To take it out, click it in the Loader column.
If the core already has a Loading Mechanism, a second one is stored in the network like any other item.
What it does
- All chunks that contain blocks of the network stay loaded and keep running, even when no player is near.
- The chunk with the Storage Core is always included.
- If the network covers more chunks than the limit, the chunks closest to the core are kept loaded. The limit is 64 chunks per network by default and can be changed in the configuration.
- When the network grows, new chunks are added right away. Chunks that are no longer part of the network are released after a short delay.
- Taking the mechanism out or breaking the core releases all chunks at once.
- After a server restart the chunks are loaded again automatically.
Loaded chunks keep ticking: plants grow and mobs move there. That costs server performance, which is why there is a limit.
Status
- The Loader column of the terminal shows "Not active", "15 chunks loaded" or, at the limit, "64 of 80 chunks".
- The Storage Observer shows the same information.