Electricity Wire Routing and Power Grid Visual Guide
Build a readable Abiotic Factor power grid with verified outlet, Plug Strip, Plug Board, Cable Reroute, battery, and downstream-device rules.
Published · Last reviewed
What this guide solves
A working cable does not prove that the whole base has a good power layout. When every bench, refrigerator, light, and defensive device hangs from one unlabeled chain, a single disconnected segment is difficult to find. Batteries also discharge according to their downstream network, so an apparently simple series can perform differently from parallel branches.
This guide uses the current power rules to build a grid that can be inspected from the wall outlet to one device at a time. The branch names are an editorial organization method. The connector capacities, discharge formula, and default night values come from the linked references.
Verified power rules
| Rule | Practical meaning |
|---|---|
| A live wall outlet has unlimited throughput | Splitting the active outlet does not reduce normal daytime power |
| Plug Strip has three output slots | Use it for a small branch |
| Plug Board has six output slots | Use it when one labeled zone needs more outputs |
| Cable Reroutes extend a socket | They move the cable path but do not create a powered device load |
| Batteries charge while live power is upstream | A battery can charge and pass power to downstream devices |
| Batteries discharge during an outage | Drain depends on every powered device downstream |
| Plug Strips, Plug Boards, and Cable Reroutes are not counted as loads | The devices connected through them are counted |
| A battery connected in series is counted downstream of the battery before it | Long battery chains lose efficiency |
These rules distinguish a distribution component from a consuming device. A Plug Board adds sockets, but the six objects connected to it are what matter to the upstream battery during an outage.
Recommended readable layout
Use this flow for a normal base:
Wall outlet
-> root Plug Strip or Plug Board
-> food branch battery -> refrigerator and food devices
-> workshop branch battery -> crafting and repair devices
-> defense branch battery -> traps or defensive devices
-> comfort branch -> lights and noncritical equipmentThe named branches are not a hidden game mechanic. They make the real network visible. When the refrigerator loses power, start at the food branch instead of unplugging the workshop.
Build order
- Select the wall outlet that will act as the upstream source.
- Place one root Plug Strip or Plug Board where every branch remains visible.
- Give each output a purpose before connecting a device.
- Use Cable Reroutes to carry a branch along walls or ceilings.
- Place the branch battery before the devices that need outage coverage.
- Split again only after the branch battery if several devices share it.
- Connect one device and verify it before adding the next.
- Record how many consuming devices sit downstream of each battery.
Connecting one device at a time creates a known-good checkpoint. If the third device fails, the first two connections do not need to be rebuilt.
Plug Strip or Plug Board
| Need | Use | Verified capacity |
|---|---|---|
| Small branch | Plug Strip | Three cable slots |
| Larger branch | Plug Board | Six cable slots |
| More distance without another split | Cable Reroute | One continued cable path |
| More than six devices | Another labeled branch | Capacity depends on the added connector |
Do not place another connector only because the cable looks untidy. Use a Cable Reroute for distance and a Plug Strip or Plug Board for branching. This keeps the diagram aligned with what the component actually does.
Cable Reroute placement
The Cable Reroute page says it is created while holding a Power Socket and using the Fire action with one Tech Scrap available. The placement preview changes from green through yellow to red as it approaches its range limit. It cannot be placed outside that radius.
Reroutes can attach to walls and ceilings and can be chained without a fixed count limit. The real constraint is Tech Scrap and whether the finished route is readable.
Use these placement rules:
- Keep each reroute visible from the previous checkpoint when possible.
- Follow wall edges instead of crossing doors and work areas.
- Turn corners at a reroute rather than stretching a diagonal cable through the room.
- Keep different branches on separate wall heights or sides.
- Stop extending when the preview turns red and place the next reroute from the last valid point.
Packaging a Cable Reroute returns Tech Scrap rather than a reusable reroute item. Plan a relocation with that behavior in mind.
Battery discharge formula
The current Mechanics power section gives this outage formula:
runtime in seconds = 5 x total battery charge / downstream device countFor a Makeshift Battery, total charge is 50. One downstream device therefore receives 250 seconds from a full battery:
5 x 50 / 1 = 250 secondsOn default settings, the power outage lasts 270 seconds. A single full Makeshift Battery falls 20 seconds short for one device. The Makeshift Battery page documents two batteries in series powering one device for 375 seconds, and three in series powering two devices for about 270.83 seconds.
Series and parallel comparison
Series batteries do not behave like a simple sum because each upstream battery counts the batteries and devices after it as downstream loads.
| Layout | Documented result |
|---|---|
| One Makeshift Battery -> one device | 250 seconds |
| Two Makeshift Batteries in series -> one device | 375 seconds |
| Two Makeshift Batteries in parallel -> one device on each branch | 250 seconds for each device |
| Two Makeshift Batteries in series -> two devices | About 208.3 seconds |
| Three Makeshift Batteries in series -> two devices | About 270.83 seconds |
Choose the layout from the required outcome. Two separate devices usually need separate readable branches. A short documented series can cover a critical single device through the default night, but adding batteries indefinitely becomes less efficient.
Outage-planning worksheet
For each battery, list only the consuming devices downstream of it.
| Branch | Battery charge | Downstream devices | Calculated runtime | Required runtime |
|---|---|---|---|---|
| Food | Enter current total | Count refrigerator and other loads | 5 x charge / count | Enter server outage |
| Workshop | Enter current total | Count active benches and equipment | 5 x charge / count | Enter server outage |
| Defense | Enter current total | Count powered defenses | 5 x charge / count | Enter server outage |
| Comfort | Enter current total | Count lights and optional loads | 5 x charge / count | Enter server outage |
The default 270-second night is only the correct requirement when the world uses the documented default cycle. If server settings differ, measure or obtain the actual outage duration and use that value.
Critical and optional branches
Do not give every device the same outage priority.
| Priority | Example decision | Outage response |
|---|---|---|
| Critical | Food storage or a required defensive system | Provide verified full-outage coverage |
| Operational | Bench needed for the planned night task | Power only when that task is active |
| Optional | Decorative lighting or convenience device | Allow it to shut down first |
The examples are planning categories, not claims that every named item draws a special amount. Under the documented formula, the number of downstream devices is what matters to the battery.
Troubleshooting from upstream to downstream
Inspect in one direction:
- Confirm the wall outlet is active for the current time of day.
- Confirm the root connector receives an upstream cable.
- Follow the named branch through every Cable Reroute.
- Check the branch battery's upstream input and charge indicator.
- Count its downstream devices again.
- Check the final connector and the target device.
- Disconnect the newest device if the branch failed immediately after it was added.
Randomly reconnecting cables changes the evidence. Preserve the last known-good segment until the failing segment is identified.
Daytime works, nighttime fails
If the devices work while the outlet is active but fail during the outage, the cable path is probably not the first issue. Check:
- Was the battery fully charged before the outage?
- How many consuming devices are downstream?
- Is another battery in series adding to the upstream load?
- Does the calculated runtime cover the world's outage duration?
- Is a noncritical device using capacity intended for a critical branch?
Move optional devices to another branch before adding more batteries. A larger unlabeled chain is harder to verify and may preserve the same underlying load problem.
Multi-floor routing
Treat each floor as a zone connected to the same documented upstream rules. Carry one feeder path with Cable Reroutes, then create a labeled branch at the destination floor. Do not hide every split in the vertical run.
Outlet -> root distribution
-> ground-floor food battery -> food devices
-> stairwell Cable Reroutes -> upper-floor Plug Board
-> upper workshop battery -> workshop devices
-> upper optional branch -> lightsThis diagram makes the upper-floor battery's downstream network explicit. The Cable Reroutes themselves do not add battery drain.
Failure recovery
| Failure | Likely cause | Recovery |
|---|---|---|
| One whole zone is dark | Branch input or first reroute disconnected | Start at the root and inspect that branch only |
| One device is dark | Final cable or device connection failed | Preserve the branch and reconnect the final segment |
| Battery empties early | Downstream count was wrong | Remove optional loads and recalculate |
| Full Makeshift Battery misses the end of night | One-device runtime is 250 seconds, below the default 270 | Use a documented full-night layout or a higher-capacity battery |
| Series chain performs poorly | Upstream batteries count downstream batteries as loads | Shorten the series or split into parallel branches |
| Cable cannot reach | Placement exceeded reroute radius | Add a reroute at the last valid preview position |
Completion condition
The grid is ready when every important device can be traced from the wall outlet through one named branch, every battery has a recorded downstream count, and the calculated runtime covers the intended outage. Optional devices should be separable without disconnecting critical food, workshop, or defense equipment.
Sources
The Mechanics power section provides outlet throughput, downstream load, series/parallel, and outage rules. The Energy page provides outlet and nightly power context. The Makeshift Battery page provides its 50 charge, 250-second single-device runtime, and documented night configurations. Plug Strip, Plug Board, and Cable Reroute provide the connector capacities and placement behavior.
Related guides and tools
Sources & References
Power flow and battery discharge rules come from the current Mechanics power section and Makeshift Battery page; Energy provides outlet and night context. Connector capacity and cable placement come from the Plug Strip, Plug Board, and Cable Reroute pages.
Editorial contribution
Converts current power-network rules into a labeled branch layout, outage calculation, inspection order, and recovery checklist.
- abioticfactor.wiki.gg: Energy →
- abioticfactor.wiki.gg: Mechanics →
- abioticfactor.wiki.gg: Battery (Makeshift) →
- abioticfactor.wiki.gg: Plug Strip →
- abioticfactor.wiki.gg: Plug Board →
- abioticfactor.wiki.gg: Cable Reroute →
Sources support factual claims. Route choices, comparisons, and recovery guidance are editorial synthesis and may change with game updates.
Author
The editorial desk maintains source-backed Abiotic Factor route notes, item checks, and practical decision guides.
About our editorial team →