Electrical Concepts
Electricity concepts for Rust.
Getting Started with Rustricity
Whether encountering Rustricity for the first time or revisiting it after a break, this section provides a structured foundation for understanding how base circuits are designed. It focuses on universal principles that apply to all builds, from the simplest setups to complex, multi-system bases. No prior experience is assumed, but those already familiar with Rustricity will still find guidance on best practices and design clarity.
The Structure of a Base Circuit
Designing electrical circuits in Rust begins with understanding that all base circuits, no matter their size or complexity, follow the same core framework. Every circuit is built from four main stages, with an optional fifth that enhances monitoring and reliability. These stages form the structural foundation for nearly every electrical setup used in a base.
There are four main stages, plus an optional fifth that can be added when needed:
- Power Source
- Battery Backup
- Distribution
- End Devices / Circuits
- (Optional) Component Destruction Detection
To help illustrate how these parts connect, refer to the visual flowchart:
Power Source
This is the starting point of Root Power and the foundation of nearly all circuits. Without a source, nothing else functions. Although not all systems require Root Power directly, it remains the backbone of every sustained and efficient electrical network.
Available power sources include:
- Wind Turbine – Ideal for elevated bases with consistent output
- Solar Panel – Suited for daytime use and roof-based installations
- Small Generator – Fueled by Low Grade Fuel, dependable but requires maintenance
- Test Generator – Available only in creative mode
Battery Backup
After generating power, stability and redundancy becomes essential. A Battery Backup ensures circuit uptime by compensating for dips in power generation or temporary failures.
Options include:
- Inline – Directly powers circuits and recharges with surplus power
- Bypass – Activates only when Root Power is lost or insufficient
- Direct Delivery – Power can be routed directly to circuits without a battery, though this is not recommended for most use cases due to lack of redundancy
💡 Tip: Even a small battery can extend circuit uptime significantly.
Distribution
Once power is stabilized, it must be distributed to the appropriate systems and devices. Distribution is responsible for organizing how power is delivered from the Battery Backup to the rest of the base — including all logic, defense, automation, and utility circuits.
Common methods:
- F-Bus – Fixed outputs using Electrical Branches
- D-Bus – Dynamic load balancing with Splitters
- C-Bus – Configurable distribution via Memory Cells
- H-Bus – Hybrid logic for intelligent routing
- Other Buses – Including specialized and modular variations
The choice of distribution affects circuit responsiveness, power prioritization, and automation capabilities.
End Devices / Circuits
This stage contains the functional goals of the circuit — the systems that perform work or fulfill a specific purpose. These can include individual components or complete mini-circuits made up of sensors, logic, and supporting elements.
An end circuit is any configuration designed to perform a defined task, such as defense, automation, or environmental control.
Examples include:
- Auto Turrets with logic for flipping or authorization control
- SAM Sites with condition-based toggles
- Interior and Exterior Lights tied to time or occupancy sensors
- Industrial and Water equipment like Conveyors and Water Pumps, activated by conditions
- CCTV Cameras with selection and activation logic
- Door Controllers within secure access systems
These circuits determine the power demands of the base and inform design decisions upstream.
⚠️ Tip: Plan each end circuit as a small system. Knowing its components, logic, and power needs helps shape the entire base's electrical design.
Optional: Component Destruction Detection
Component Destruction Detection is used to monitor for problems in the circuit, such as:
- Destruction of downstream components
- Addition or removal of a component
- Changes to Electrical Branch values
This detection can be placed anywhere after the Power Source. A common placement is immediately after the Battery Backup for early warning and centralized monitoring.
With this structure in mind, circuits can be broken down into logical, manageable parts. Planning starts from the desired end devices and works backward to ensure the appropriate infrastructure is in place.
Centralized vs Decentralized Theory
When discussing centralized or decentralized theory, we are referring to two distinct aspects:
- The physical placement of components throughout a base
- The flow of power from generation to the circuits that consume it
A fully centralized system places all core components, such as batteries, switches, logic, and distribution in a single physical location. Power is collected, stored, routed, and managed through one central circuit.
A fully decentralized system assigns electrical responsibility to multiple locations throughout the base. Each area or subsystem maintains its own independent circuit, complete with a dedicated power source, battery, and logic. These circuits function autonomously and are typically not aware of or connected to one another.
Both approaches exist on opposite ends of a spectrum. Most bases will fall somewhere in between — using a mix of centralized infrastructure for critical systems and decentralized elements for redundancy or physical reach.
There is no single “best” layout. The ideal approach depends on:
- Server settings and component limits
- Wipe frequency
- Group size and playstyle
- Base footprint and vulnerability
- Functionality vs redundancy
- Personal comfort with Rustricity design
The best circuit is the one that does what it needs to — when it needs to — in the way that was needed.
This section begins by exploring the physical placement of electrical infrastructure, followed by how these principles apply to circuit layout and power flow.
Physical Locations
When discussing centralized or decentralized locations, we are not referring to the placement of all electrical components throughout the base. This section does not cover:
- Auto Turrets mounted on roofs
- Heaters placed throughout Arctic bases
- The placement of Ceiling Lights in a farm
Instead, the focus is on the core infrastructure — the systems that collect, store, control, and distribute electricity across the base. This includes:
- Collection points from power sources
- Placement of battery backups
- Locations for distribution logic
- Control centers for automation and monitoring
In essence, it’s about where a Windmill sends its power, or where the wire powering an Auto Turret originates. These placements shape the survivability, security, and scalability of a base’s electrical network.
- A well-planned location strategy is just as important as circuit design. Where these systems are placed can determine whether they resist raids or are taken out with a single breach of a wall.
Centralized Locations
A fully centralized location refers to a single room or compact area that houses all of the base’s core electrical components, including batteries, logic circuits, collection and distribution systems. This location serves as the nerve center of the electrical network. In real-world infrastructure, this would be called a Main Distribution Frame (MDF), a central node where power is received, stored, routed, and managed. Due to the nature of its critical role, it deserves protection equal to or greater than that of the Tool Cupboard.
Centralizing components in one location offers major convenience. It’s easier to build honeycomb, add doors and traps, and reinforce one high-value room. However, this comes with a tradeoff: when raiders break into this room, a single rocket will disable every system at once.
Where this room (MDF) is placed must be intentional and pre-planned, not improvised. A well-designed base doesn’t sacrifice bedrooms or loot rooms just to make last-minute space for electrical infrastructure. Planning ahead ensures that this high-value room has both the security and space it needs and that wires can reliably reach the systems they’re meant to power without compromising layout or protection.
For protection, it’s not just about adding walls. Location matters. Positioning the room deep within the core adds raw durability through layered protection and honeycomb. Placing it within the China Wall or in a Gatehouse floor offers protection through misdirection and raiders may overlook it entirely. Regardless of the method, the key is building these locations into the base from the start. They are not just utility rooms, they are critical infrastructure and deserve thoughtful placement from the beginning.
No matter the location, concealing wires is essential. This is not about keeping wires clean and tidy. It's about hiding them from other rustricians so they cannot trace them back to their origin.
- Avoid running wires on the exterior of the base, such as the roof. Bring the wire through the floor and into the interior of the base before routing towards the central location (MDF).
- When running wires along the ground or foundations, take advantage of Wire Slack. Sink them into the foundations or ground and hide them from sight.
- Wires can be 30 meters long, don't be afraid to use the whole amount. Utilize decoy paths or route wires through multiple entry points into the MDF if necessary. Avoid having all wires taking the same path, pointing at the single room.
Wire length is a natural constraint. In small bases, most devices can be reached directly but in large bases, wire extension components may be required. These components must be placed securely. For instance:
If a Blocker is used to extend a wire to a Turret, the Blocker should not be easier to destroy than the Turret itself.
Any passthrough-capable component can serve this function. Items like the Blocker, OR Switch, Memory Cell, Smart Switch are excellent choices because they do not consume any power and they cause no extra Active Usage on batteries. If these components cannot be adequately secured, players can consider components that can camouflage but consume a little bit of power. For instance, the Industrial Light is a reliable alternative. They make a great choice due to their low crafting cost and their ability to stealthy camouflage as just another light on the base.
Decentralized Locations
Fully decentralized locations spread power infrastructure across multiple rooms, making electrical networks more resilient during a raid or just easier to run wires. A decentralized layout distributes core electrical components across two, three or more rooms. Each of these rooms serve as a regional hub that is designed to manage its own power generation, storage, and logic.
In real-world infrastructure, each of these would be called Main Distribution Frames (MDFs). They are central nodes where power is received, stored, routed, and managed for a specific zone or area. They operate completely independently without any interconnections between one another.
- Think of each MDF as a self-contained, localized circuit room, producing and regulating its own power for a specific zone, like the North, South, East and West sides of a base.
However, in some bases, each decentralized room may be interconnected with one another within the overall circuit design. When it does, these decentralized rooms will function as Intermediate Distribution Frames (IDFs). These are secondary distribution hubs linked to a central Main Distribution Frame (MDF). However, whether a room qualifies as an IDF is determined by its electrical role and interconnection, not merely by the fact that multiple rooms exist.
💡 A common example is placing an IDF room near the roof as a collection point for Root Power from wind and solar before forwarding it to a secure MDF deeper inside the base for backup and distribution.
These rooms should be intentionally integrated into the base design, not added as an afterthought, to ensure they're both secure and functional. These locations deserve the same planning and protection as a Tool Cupboard.
They should also be:
- Hard to locate and/or heavily protected
- Placed in areas raiders wouldn’t expect or prioritize, eg. in the floor
- Distributed in a way that reduces the impact if a single one of them is breached
The more spread out these locations are, the better their resilience, especially when a base is large. With very large bases, raiders often "cut a base in half" with rockets. With decentralized locations, even if one room is lost, the others should continue to operate without interruption.
Decentralization also brings efficiency by saving time. By placing power near where it’s used, players reduce the need for long, complicated routes needing lots of running back and forth and/or the use of wire extensions. It can simplify circuit planning by helping eliminate extra components just for distance.
💡 Turrets above the gatehouse don’t need to be powered from deep inside the base. They can be powered by a fully independent MDF built into the gatehouse. This room would include its own power generation, battery backup, turret control logic, and sensors, operating completely separate from the main base infrastructure.
Each decentralized location should avoid drawing attention through visible wiring. Wire concealment is critical. Distribute entry points and leverage full wire lengths creatively.
- Avoid running wires on the exterior of the base, such as the roof. Bring the wire through the floor and into the interior of the base before routing towards the MDF.
- When running wires along the ground or foundations, take advantage of Wire Slack to hide them from sight.
- Wires can be 30 meters long, don't be afraid to use the whole amount. Utilize decoy paths or route wires through multiple entry points into the IDF if necessary. Avoid having all wires take the same path, pointing at these rooms.
Decentralization offers more than just safety, it delivers smart efficiency. With power already positioned near where it's needed, circuits require fewer passthrough components, fewer exposed wires, and fewer compromises. In large bases, these small advantages add up to a major difference.
Circuit Design
When discussing centralized, decentralized, or hybrid circuits, what’s really being described is how electricity moves from power sources to the systems that need it. This isn’t about physical placement of components, it’s about whether everything runs through one single circuit or gets split across multiple smaller ones.
A centralized circuit sends all power into one system that handles everything: battery backup, turrets, sensors, lights, and more. There’s one set of batteries, one set of logic, and one set of wires feeding the whole base. This creates a single, unified circuit.
A decentralized circuit splits things up. Each area or subsystem gets its own power source, battery backup, and logic. These areas or subsystems run independently from one another without relying on a single power core.
This decision impacts how the base is built. A well-designed circuit avoids wasting power, losing everything to one rocket, or needing extra rooms just to stretch wires. Understanding the difference early makes it easier to plan circuits that match the layout, power demand, and playstyle.
Centralized Circuit (Image needed)
In a base, a centralized circuit is one in which all power sources, storage, logic, and distribution are combined into a single unified system. Every electrical component in the base, from turrets and sensors to lighting and water pumps, receives power through this one single circuit.
Power sources such as Wind Turbines, Solar Panels, and Generators feed into a single battery-backed core, typically an Inline Backup (The Kore) or a Bypass Backup (BCN Core). These cores provide built-in double redundancy where if the sources are destroyed, the battery will continue to supply power, or if the battery is lost, direct source power may continue supplying all or part of the circuit. No matter the situation, they will avoid selecting a power path that is supplying 0rW.
Despite this redundancy, centralized circuits have an inherent vulnerability, a single point of failure. In a standard Inline backup, the battery is the point of failure. In modern backups, like the Kore or BCN Core, it’s the final OR Switch that connects the 2 halves of the power core to the distribution system. If this OR Switch is destroyed the entire base circuit goes offline. No subsystems will continue functioning, regardless of battery charge or available source power.
Power Capacity Limits
While centralized circuits can support substantial power loads, they are typically limited to around 1600rW. This limitation arises from 2 sources:
- The mechanics of the Root Combiner, which has a maximum depth of 16 components between it and any connected power source.
AND
- The amount of power sources needed to produce this much power.
If a centralized core is designed to support 1600rW worth of battery backup, that requires combining 16 Large Batteries together using multiple Root Combiners. These, along with the batteries, additional components in the Power Core and the combiners for the power sources, all add to the circuit’s total depth.
In practice, this means a standard BCN Core powering 1600rW will be able to support roughly 16 power sources. These sources will need to be high-elevation Wind Turbines to provide the sustained output needed to maintain such a large centralized system.
This is typically more than enough power for nearly all use cases, but it also marks the practical ceiling for centralized circuits. Beyond this point, circuit depth, wire clutter, and repair difficulty begin to outweigh the simplicity of a single system.
Key Traits
- All power sources are combined into one core
- A single circuit powers every system, subsystem, and device
- Distribution is centralized through a single bus
- No electrical independence between subsystems
- Best suited to small bases or tight, compact layouts
Advantages
- Simplified wiring design
- Efficient power use, no duplicate systems
- Quick to deploy and easy to monitor
- Compact and ideal for limited space
Disadvantages
- Single point of failure at the OR Switch
- Poor scalability in large bases
- Only 1 power core. If it fails, all systems go offline
- Challenging to route wires across long distances without IDF (Intermediate Distribution Frame) closets or wire extensions
Centralized circuits are ideal for smaller bases or self-contained systems where all devices are in close proximity and easy to wire. As base size or power requirements grow, the limitations of a single unified circuit often outweigh its simplicity.
Decentralized Circuits (Image needed)
Decentralizing circuits really comes down to how extreme a player wants to take it. The idea behind decentralizing is adding security and reliability by segmenting different systems and areas with their own independent power supplies and backups. Instead of all systems drawing power from a single unified system, power is divided across separate cores, each responsible for specific locations or functions.
Each decentralized unit is essentially a centralized circuit, complete with its own power source, battery backup, logic, and distribution, but scoped to a limited area or purpose. Basically, any base that is using 2 or more circuits is decentralizing.
For example, a base may have a dedicated circuit for each side, North, South, East, and West, plus an additional core for the roof. The base may dedicate a core to its industrial system, or one for a Farm. Each one operates independently and a breach or failure in one area does not affect the others.
Key Traits
- Composed of multiple self-contained circuits
- Each system has its own power, battery, and logic
- Designed around location, function, or both
- Systems do not rely on a central bus or core
Advantages
- Decentralized circuits offer high resilience, as there is no single point of failure that can bring down the base's entire electrical system.
- Each system has local control, with logic placed close to the devices it manages.
- These circuits scale more easily since new systems can be added without placing strain on a central power core.
- Their structure often aligns better with the physical layout of a base, such as organizing by region with one Main Distribution Frames(MDF) per area.
Disadvantages
- The component cost is higher, as each independent circuit requires its own batteries, switches, branches, and other components.
- The overall system becomes more complex and requires additional planning to maintain clear organization.
- Some logic may need to be duplicated across multiple circuits, leading to redundant setups.
- Monitoring becomes more difficult because each circuit operates independently and must be checked separately.
Decentralized circuits are often the only practical option in large or segmented bases. When distance, compartmentalization, or redundancy is important, decentralization offers greater reliability and flexibility.
Hybrid Circuits (Images needed)
Hybrid circuits centralize for convenience and decentralize for security. Root Power is managed by one part of the circuit and each subsystem or area has its own backup so a failure does not pull everything down.
Recommended approach: Centralize sources, decentralize backups. Root‑combine wind, solar, and generators into one feed and route it to charge or feed separate backups for different areas of the base (North, South, East, West) or systems (turrets, farm, industry, etc). Control stays simple. Risk stays isolated.
Discouraged approach: Decentralize sources, centralize backups. This approach works against both goals of hybridizing. As a thought exercise, let’s consider inline batteries.
- Target: 18 turrets = 180rW.
- Combined inline backup (bad): 2× Large Batteries, each with its own power supply, behind a combiner → each sees 100 Active Usage → each battery needs 125rW at 80% efficiency → for a total of 250rW sustained production of Root Power.
- This approach requires larger amounts of power production and makes the circuit more vulnerable, not more secure.
- Separate inline backup (good): split turrets into 2 groups, 9/9 → batteries will only see 90 Active Usage each → each battery only needs 114rW at 80% efficiency → for a total of 228rW sustained production of Root Power.
Back to the recommended approach. Centralize sources, decentralize backups, then pick an implementation path based on goals:
- Inline (classic inline): Fastest to set up, minimal components, just watch batteries Active Usage and ensure there is enough power production to sustain their loads.
- Nih Core (non-battery-checked bypass): Moderate complexity and built with a single core for collecting and routing Root Power, but each area or subsystem gets its own backup battery.
- The Kore/BCN Core (battery-checked-backups): Has the highest level of complexity and component count. Each area or subsystem has a complete Kore or BCN with a battery. Only the power sources are centralized before routing to each power core.
Inline (classic inline)
Inline hybrid keeps sources centralized and assigns one inline battery per area or subsystem. Each battery must receive an input equal to or greater than, Active Usage ÷ 0.8, to maintain a positive charge. If the priorities of the battery are equal and/or the amount of power each battery needs to receive is equal, use a Splitter to distribute power. When priorities or the amount of power each battery needs differs, use Electrical Branches to fix the amount of power and/or establish the batteries priorities. It’s simple wiring and a fast setup, but continuous operational costs more because every charged rW pays the 20% tax.
Modern Nih Core (non-battery-checked bypass)
Keep main power centralized and route it into a single Nih Core. Set the main Electrical Branch to a value that is needed to support the entire circuit's load. Give each area or subsystem its own OR Switch and battery, then establish the distribution paths for main power and battery charging.
- Send main power from the Memory Cell to either Splitters (even distribution) or to Electrical Branches (fixed power per area or subsystem).
- Feed main power into Input A of an OR Switch for each area or subsystem. This forms the bypass path.
- From the Nih Core’s battery-charge output (the OR Switch that charges the Nih Cores battery), distributes charge to each area or subsystem’s battery using either a Splitter (even) or Electrical Branches (priority).
- Send power from each battery into an Electrical Branch that is set to a value equal to or less than the amount of power getting delivered to Input A of the OR Switch. This prevents the battery from draining when Root Power is sufficient.
- Connect Branch Out from that battery branch to Input B of the area or subsystem’s OR Switch. This forms the battery-backup path.
- Use Control Power to RESET the Nih Cores Memory Cell.
When power production runs low, or a source is destroyed, the batteries for each area or subsystem will take over, and what little power is still getting produced will get routed to the batteries to slow their discharge. The only flaw with this approach is that if a battery is depleted or destroyed, the core will still try to let the battery take over when power production runs low.
The Kore or BCN Core (battery-checked-backups)
Root‑combine power sources once for convenience, then build one core per area or subsystem so battery‑check logic remains accurate. Feed evenly, or branch for priority per area or subsystem. This achieves clean failover with battery verification, but increases work load for the player and component count. Given the per‑subsystem or area core requirement, centralizing sources is optional. Only centralize the power sources when shared monitoring and charge control outweigh the added wiring, otherwise stick with standard decentralization practices and run power sources to their local cores.
- Build a Kore or BCN for each area or subsystem.
- Deliver main power to each core’s main input. Use either Splitters for even distribution, or Electrical Branches for fixed or prioritized power per area or subsystem
- From each core’s main output, distribute power to the components the core is expected to support.
Notes
- Space planning: Each core will need 3 rooms. 1 room for the Root Power path, a second room for the battery backup path with a 3rd, and the most important room, for the OR Switch to combine the 2 sides together. Without the OR Switch, everything that core was powering will be offline. Treat each room as critical infrastructure.
- Source centralization trade: When every subsystem has its own Kore/BCN, centralizing sources is optional. It may be preferential to run power sources to their own local cores.
Key Traits
- Centralized Root Power, decentralized battery backups per area or subsystem.
- Minimal dependencies between areas to prevent a total failure.
- Inline batteries require Active Usage / 0.8 input to hold charge.
- Kore/BCN hybrids require one core per subsystem to preserve battery‑check behavior.
- Source centralization is optional when every subsystem has its own Kore/BCN.
Advantages
- Limits total system failures. One area or subsystem can fall without dropping the rest.
- Centralized power sources simplify distribution and growth.
- Shorter wire runs when backups and distribution live near their loads.
Disadvantages
- Higher component count and build time vs a purely centralized circuit.
- Inline hybrids pay 20% charge overhead and are inefficient for always-on loads.
- Battery-checked bypass hybrids are possible but add complexity that may not pay off for most bases.
If runtime and redundancy are the top goals, a hybrid circuit is not what the player is looking for. Instead, use a primary, centralized BCN Core, then attach secondary backups to every critical area or subsystem. The BCN provides verified failover and simple monitoring. The secondaries add local autonomy and extend battery-only operation when sources and the primary backup are down.
Distribution (Images needed)
Introduction
At the most fundamental level, every electrical system in Rust has the same job: move power from a power source to an end device.
Everything that happens between those two points, batteries, branches, buses, logic, switches, and wiring paths, are all part of power distribution.
Distribution is not about how power is generated, and it is not about what the power is used for. It is about how power travels, what it must pass through, and what happens when that path is damaged or destroyed.
This section focuses on the two broad approaches to power distribution:
- Centralized distribution, where power flows through a single, shared path.
- Decentralized distribution, where multiple paths exist to keep devices online under damage.
Understanding the difference is less about building bigger systems and more about deciding where failure is allowed to occur.
Centralized Distribution
Centralized distribution is how 99.9% of Rust circuits are wired, not because it is optimal, but because it is the natural result of how players learn electricity.
All end devices or sub‑circuits are fed from a single source of power, typically protected by a single battery backup, and routed through one distribution path (usually a branch, splitter, or bus).
This means:
- Power reaches every end device through one path.
- There is one battery maintaining uptime.
- If the distribution path is broken, everything downstream loses power.
This approach concentrates control, logic, and power management into a single location. The tradeoff is simple and brutal: simplicity in exchange for a single point of failure.
Centralized distribution is material‑efficient, easy to reason about, and easy to expand. It is also fragile: one break can shut down an entire section of the base.
Decentralized Distribution
The goal of decentralized distribution is not efficiency. The goal is raw uptime when getting raided and taking heavy damage to a base.
At its simplest, decentralized distribution uses an OR Switch to feed a device or circuit. Imagine an Auto Turret with 2 power inputs.
An OR Switch allows:
- Two power inputs instead of one.
- Power to continue flowing as long as at least one input remains powered.
At the extreme end, this enables:
- Two power sources
- Two battery backups
- Two independent distribution paths
All feeding a single end device or circuit through the OR Switch.
This is not a common or recommended setup. It represents the upper bound of decentralization, included here to define the limits, not the baseline.
For decentralized distribution to matter, the OR Switch must be harder to destroy than the device or circuit it supports. Otherwise, it becomes the weakest link and defeats the purpose.
This approach can effectively double the amount of power being produced, stored, and routed to maintain uptime, but not necessarily.
Partial Decentralization
Full duplication is not required when wire extensions are used. What that means is a player with a single Kore or BCN Core can still decentralize distribution for a device such as an auto turret assuming a wire extension is required.
Example:
- Send 10rW from the core in two different directions.
- Route both paths to an OR Switch near the turret.
This creates redundancy at the distribution level, even though generation and storage remain centralized. If an extension is not required, no redundancy is created.
The turret remains powered as long as either path survives.
However, limitations apply.
When Decentralization Does Not Help
Decentralized distribution provides little or no benefit when:
- The distribution system (F‑Bus, D‑Bus, etc.), logic, and OR Switch are all in the same room and that room is destroyed.
- The OR Switch is easier to destroy than the device it supports.
- A single uninterrupted wire can already reach the destination without needing extension components.
In short: if all paths die in the same explosion, redundancy never existed.
In these cases, decentralization adds complexity without improving survivability.
Where Decentralization Shines
Decentralized distribution becomes valuable when:
- A wire must travel long distances and a wire‑extension component is required.
- The path is likely to be broken during a raid.
These scenarios usually occur during progressive raids, where attackers move through the base over time rather than deleting it instantly.
Any component used to extend a wire should be treated like the OR Switch:
- It should be better protected than the device or circuit it powers.
If one extension component is destroyed, a second path routed through the opposite side of the base can preserve uptime during a raid.
Failure Domains
A failure domain is the smallest damage event capable of disabling a device, circuit, or system.
For example:
- The group of Root Combiners near the roof in a single location, is a failure domain.
- Putting the Electrical Branches for a Kore or BCN Core in the same room as the power core is a large failure domain.
- An electrical closet housing components that control some local turrets is a failure domain.
Centralized distribution often creates large failure domains by placing all electrical components in the same location. A single rocket, C4, or explosive breach can remove power from everything downstream of the distribution point.
Decentralized distribution attempts to shrink or split failure domains by giving power multiple, physically separated paths. In other words, spreading things out into different locations to minimize the impact of any one single breach or failure.
The goal is not to prevent failure entirely, but to ensure that failure happens later, in smaller pieces, in a predictable way and on your terms.
False Redundancy
Not all redundancy is real redundancy.
The following look decentralized but provide little or no added resilience:
- Two independent distribution buses located in the same room, from 2 Power Source and Battery Backups.
- Two OR Switch inputs fed from paths that each require a wire extension, but are located in the same room.
- Two OR Switch inputs fed from the same distribution panel where the wires do not require a wire extension.
If multiple power paths share the same failure domain, the system is still centralized, just more expensive.
Decision Shortcut
Decentralized distribution is rarely needed. Before using it, ask three questions:
- Is the device or circuit raid‑critical?
- Can the power paths realistically be broken independently(wire extension)?
- Will keeping this system online change the outcome of the raid?
If the answer to all three is not yes, decentralized distribution is usually wasted effort.
Cost and Power Tradeoffs
Decentralized distribution always costs more power than centralized distribution.
Either:
- The player reserves double the power for decentralized devices using a single source and battery, or
- The player produces and stores double the power using multiple sources and batteries.
Decentralized distribution does not eliminate power waste, it turns it into redundancy. This is often over‑engineering but it does have practical applications, but only if the player is comfortable wasting power to do it.
Remember:
- Power waste is inevitable.
- The real decision is where the player is willing to waste it.
If power efficiency is the primary goal, centralized distribution with secondary battery backups almost always wins. Decentralized distribution is a raid‑resilience strategy, not an electrical optimization.
Conclusion
At the end of the day, all power distribution is about the same problem: getting power from the source to the device, and deciding what happens when something in between is destroyed.
- Centralized distribution accepts failure in exchange for simplicity. It is efficient, predictable, and sufficient for the majority of builds.
- Decentralized distribution trades efficiency for resilience. It accepts higher cost, higher power waste, and higher complexity in order to keep critical systems online longer during a raid.
Neither approach is strictly better. Each represents a different answer to the same question:
“Where am I willing to let power fail?”
Understanding distribution is not about copying advanced circuits. It is about making intentional decisions instead of accidental ones and building systems that fail the way you expect them to.
Power Theory and Efficiency
Power Theory and Efficiency explain how different forms of power are generated, stored, consumed, and wasted in Rust circuits. This section teaches players how to evaluate designs beyond function, reduce unnecessary drain, and choose smarter strategies.
Introduction
Understanding Rust’s electrical system isn’t just about knowing what components do, it’s about mastering how power flows, what gets consumed, and where inefficiencies can be eliminated. This section explores the different types of power used in Rust circuits and shows how players can optimize circuit design by strategically choosing how and when each type is used.
This section builds a foundation for how to evaluate and compare circuits not just by functionality, but by power efficiency. It answers essential questions like:
- Should a battery be used here, or should Root Power handle the load?
- Can part of this circuit be offloaded to free or logic-only power?
- What’s the real cost of combining batteries or powering always-on components?
Whether you're wiring a small trap base or designing a smart base that runs autonomously, this section helps you think critically about what kind of power you’re using, how much you're wasting, and how much you could save by refining the design.
Key Definitions
Modern circuitry relies on more than just connecting wires, it requires an understanding of how power behaves across different systems. Not all power is equal. Some is generated, some is stored, some is used efficiently, and some disappears without doing any real work.
The following definitions break down the seven core properties of power and explain how they interact with one another. These terms will serve as the foundation for building efficient circuits, selecting battery backups, and minimizing unnecessary power production.
— Root Power, Stored Power, Active Usage, Available Power, Consumed Power, Control Power, and Free Power —
These aren't just random labels, they shape the design philosophy behind every circuit, battery backup, and automation system. Mastering these power mechanics means more efficient setups, longer-lasting batteries, and smarter automation.
If a player misunderstands these properties of power, they are likely to waste electricity, overproduce power, or mismanage their battery systems. Understanding the differences between them is essential for mastering Rustricity.
⚙️ Root Power
Root Power, often called Main Power or Source Power, is electricity generated by power sources such as Wind Turbines, Large Solar Panels, and Small Generators (using Low Grade Fuel). This power is created passively or through fuel consumption and is the core power source for all powered circuits and is measured in rust Watts (rW).
This power is generated externally and does not contribute to Active Usage, regardless of how it is consumed or routed. Root Power supports batteries to overcome Active Usage, directly powers components, and sustains circuit logic. It is the only power form that must be continually produced, and its availability defines the size and complexity of sustainable systems.
Efficiency with Root Power is essential. Every unit of energy wasted, through poor design or unnecessary always-on components, increases the amount of power that must be constantly produced. To improve circuit performance, players should ask:
- What components are always on and can run directly from Root Power?
- Which circuits are not always on and can safely run off batteries to leverage Active Usage?
- What logic, toggle, or timing behavior can be offloaded to Control Power or Free Power?
Designing around Root Power means minimizing waste and maximizing efficiency. Any power not consumed is lost, so systems should aim to allocate Root Power intelligently, combining direct use, battery storage, and offloading logic where possible.
- All Root Power is Consumed Power but not all Consumed Power is Root Power.
🔋 Stored Power
Stored Power, sometimes referred to as Battery Power, refers to the electrical energy held inside a battery, measured in Rust Watt Minutes (rWm). This value is visible when looking at a battery with a Wire Tool equipped and is labeled as the battery’s Capacity.
Stored Power plays a crucial role in battery-backed systems, especially when managing power availability during outages or low production. As components draw power from the battery (Active Usage), this value decreases over time.
Understanding how to work with Stored Power involves two key use cases:
- How long a battery can run a circuit based on its current charge.
- How long it will take to charge a battery to a desired capacity.
🧮 1. Discharge Duration — "How long will this stored energy last?"
To find out how long a specific amount of Stored Power will last, use the following equation.
DischargeTime = StoredPower ÷ PowerDraw
- DischargeTime: The total run time in minutes
- StoredPower: The current or desired rWm in the battery
- PowerDraw: The amount of power the circuit is consuming (rW)
🧪Example:
A Large Battery with 18,000rWm is powering a 75rW circuit:
DischargeTime = StoredPower ÷ PowerDraw
= 18000 ÷ 75
DischargeTime = 240 minutes (4 hours)
🔋 2. Charge Duration — "How long to charge to a specific capacity?"
To find out how long it will take to charge to a specific amount of capacity, use the following equation.
ChargeTime = (TargetCapacity − CurrentCapacity) ÷ (InputPower × 0.8)
- ChargeTime: time (in minutes) to reach the desired rWm level
- TargetCapacity: desired battery charge (rWm)
- CurrentCapacity: current battery charge (rWm)
- InputPower: how many rW are being supplied
- 0.8: battery efficiency (80%)
🧪Example:
A player wants to charge a Large Battery from 3000rWm to 15,000rWm using 100rW of power:
ChargeTime = (TargetCapacity − CurrentCapacity) ÷ (InputPower × 0.8)
= (15000 − 3000) ÷ (100 × 0.8)
= 12000 ÷ 80
ChargeTime = 150 minutes (2.5 h)
🔋 Active Usage
Active Usage, often referred to as Drain, is the number shown in the battery's UI when looking at it while holding a Wire Tool. It represents how much power the battery is currently discharging. This number is critical for inline battery setups, as it dictates how fast the battery drains and how much power must be input to remain neutral.
Since batteries operate at 80% efficiency, the rule is simple:
Power In = Active Usage ÷ 0.8 or Active Usage × 1.25
If a battery has 20 Active Usage, it must receive 26rW of power to avoid draining. This number includes any component actively consuming power from the battery, but not every component that consumes power will increase Active Usage.
Active Usage is a reflection of power being consumed by a component in the system, but not all consumed power generates Active Usage. This means:
- Active Usage is always Consumed Power, but Consumed Power is not always Active Usage.
🗑️ Available Power
When looking at an IO connection on any component, the amount of power that is shown is the amount of power available that could be used.
⚡ Consumed Power
Consumed Power refers to the amount of electricity needed for a component to function or an action to take place, whether or not it generates Active Usage. It applies to components like Timers or Memory Cells that actively require energy to operate but have no Active Usage. It also applies to components such as Auto Turrets, Ceiling Lights, Electric Furnaces, etc, that do have an Active Usage.
- Many of these components will reflect their consumption as Active Usage when powered by a battery.
- However, some components like the Fluid Switch & Pump or the Toggle inputs on items like the Fogger-3000 and the Boom Box, all consume power to function, but do not cause any Active Usage.
This distinction is especially important when using bypass battery backups because they are supplying Root Power to the circuits that need to function. Using Root Power to constantly supply and reserve power for logic or systems even when they are turned off is an inefficient use of Root Power. If a circuit needs 29rW to function but will only register 18 Active Usage on a battery, it is more efficient to switch to an inline and give the battery 23rW. Switching to an inline backup can significantly reduce the need for excessive power production. Bypass backups are ideally used for circuits that are always on and consuming large amounts of power.
- Consumed Power includes all energy used for functionality, regardless of whether or not it registers as Active Usage on a battery.
🟡 Control Power
Control Power is electricity used purely to trigger or toggle components, and it does not contribute to Active Usage but is consumed. These 1rW signals are used in logic and control circuits, enabling behavior such as toggling Timers, resetting Memory Cells, or blocking passthrough on Blockers.
Control Power does not create any Active Usage, and because of that, it can be supplied by batteries that have no power input. These Control Batteries will not drain as long as the circuit only uses these types of signals. This makes it possible to build entire logic systems that never require power production, only a one-time battery installation.
For instance, a Timer powering the Block Passthrough input on a Blocker, the extra input on an AND Switch, or a timing circuit that triggers SET on a RAND Switch, can all be run solely on Control Power. Entire automatic sprinkler systems can be run off of Control Power. If the entire system is composed of logic components with no Active Usage, it can run indefinitely from a charged battery, without needing a power source to recharge.
- All Control Power is Consumed Power, but not all Consumed Power is Control Power.
Once players realize how useful taking advantage of this mechanic is, it will become commonplace to install a battery solely to utilize Control Power.
⚡ Free Power
Some components generate small amounts of free power when triggered without any need for additional input power or even an input connection. These outputs are temporary and low in power (typically 1–2rW), but can be used to trigger logic circuits or send signals without consuming any additional electricity from power sources or batteries.
This generated power is entirely free and is especially useful in circuits where simple player inputs are needed without the need to produce additional power.
Components that Generate Free Power
Component
Output
Trigger Condition
Button
2rW pulse
When pressed by a player
Pressure Pad
1rW pulse
When stepped on
Reactive Target
1rW pulse
When shot and falls flat
Power Multipliers
While the components above are the power source, these ones below need power to provide some Free Power.
Component
Output
Trigger Condition
Seismic Sensor
Up to 3rW
Nearby explosions (requires 1rW input)
Auto Turret
2rW
Actively Has Target, Low Ammo AND No Ammo (required 11rW input)
SAM Site
2rW
Actively Has Target, Low Ammo OR No Ammo (required 25rW input)
⚠️ Other then the Auto Turret and SAM Site which are constant, these pulses are brief — usually under 1 second — and are only suitable for triggering logic (e.g., flipping a Memory Cell or activating a Timer). They should not be relied on for sustained power delivery.
Where Past Meets Present
Now that the different types of power have been defined, the next step is to demonstrate how they interact and how misunderstanding these interactions can lead to inefficient circuit design and wasted electricity.
Historically, this section was called Active Usage vs Power Consumed and focused on the debate between Electrical Branch vs Splitter and the behavior of the Root Combiner. In earlier versions of Rust's electrical system, every component consumed power and generated Active Usage, even when turned off. Players needed to understand these mechanics to build power-efficient circuits, especially when selecting between Inline or Bypass Battery Backups.
Today, things are different. Most components no longer consume 1rW just for being connected, and Active Usage is only registered when a component is both powered and in use. This shift dramatically reduces baseline power requirements for most circuits but understanding how power is handled is still just as important.
⚖️ Electrical Branch vs Splitter Debate
In the past, comparing the Electrical Branch to the Splitter was central to understanding efficiency. Every component consumed 1rW and generated Active Usage, and the way those two components handled power had significant differences — especially with inline battery setups. Today, while most components no longer consume power for themselves or generate Active Usage by default, the legacy of that comparison still matters.
⚡ Electrical Branch
Old Behavior:
- Consumed 1rW for itself
- Registered 0 Active Usage for itself
- Forced Active Usage based on its Branch Out setting
- Blocked the Active Usage of downstream components (like turrets)
If players set the Branch Out to 10rW for an Auto Turret, the battery would see 10 Active Usage regardless of what was connected beyond it. This made Electrical Branches a popular choice for minimizing visible Active Usage, even if actual consumption was higher.
Example:
- 8 Electrical Branches each set to 10rW powering 9 turrets =
- 98rW consumed, 90 Active Usage.
Today:
- Consumes 0rW
- Has 0 Active Usage
- Does not force Active Usage based on Branch Out
- Does not block downstream Active Usage
Now, components connected to Branch Out must be powered on and actually consuming electricity in order to register any Active Usage. The branch simply limits the amount of power available — it no longer masks what’s happening after it. This makes the branch better suited for setting fixed power levels, not for reducing battery draw.
Example:
- 8 Electrical Branches each set to 10rW powering 9 turrets =
- 90rW consumed, 90 Active Usage
🔀 Splitter
Old Behavior:
- Consumed 1rW for itself
- Registered 1 Active Usage
- Divided input power evenly between its 3 outputs but discarded any odd amounts of power
- Did not dynamically adjust if outputs were destroyed
Players using 4 Splitters to power 9 turrets would have 94 Active Usage, and 94rW consumed. Compared to Electrical Branches, the Splitter cost 4 extra rW more drain to the battery.
Today:
- Consumes 0rW
- Has 0 Active Usage
- Divides input power evenly between its 3 outputs and adds any odd amounts of power to Outputs 1 and 2
- Redistributes power dynamically if an output is lost
Modern Splitters are highly efficient in the same 9-turret setup:
4 Splitters = 90rW consumed, 90 Active Usage
🧠 Final Thoughts
Today’s Electrical Branch vs Splitter discussion is no longer about which one uses less power, but rather:
- Which combination of components costs the least amount of resources? 8 Electrical Branches for 9 outputs is 600 Metal Fragments vs 4 Splitters for 9 outputs is only 400 Metal Fragments
- Do you need fixed power distribution with prioritization? → Use Electrical Branch
- Do you need an equally divided distribution that dynamically adjusts? → Use Splitter
Both components have zero overhead now, so the choice comes down to material cost and control vs flexibility. Understanding how they route power, how that interacts with Active Usage and how power is consumed remains essential for smart circuit design.
Electrical Branch and Splitter Prioritizations
Prioritization describes what gets power first and what loses it first when the supply starts to decline. These two components implement it in different ways:
- Splitter: Hands power to Output 1, then 2, then 3. When input falls, it removes power in the same order. It divides whatever power is available across its outputs. Each output receives roughly “input ÷ number of outputs.” If the share for any output drops below what a load needs, that load turns off, but because all shares drop together, multiple loads often fail at once.
- Electrical Branch: Always reserves power for Branch Out even though Power Out will send out power first before Branch Out. In a chain of branches, the earlier branch has higher priority than the later one. It allocates fixed amounts rather than equal shares, reserving a set amount for each load. The first branch is filled first, then any remainder is passed downstream. If supply falls, later branches lose power first while earlier, higher‑priority branches keep running.
Comparative Example - Equal Share vs Fixed Allocation
Lets say there is a target of 30rW for three 10rW loads. Lets say the loads are 3 Auto Turrets.
- Splitter: With 30rW in, the Splitter divides the input so each output is 10rW and all three turrets turn on. Now lets say the input falls to 20rW. Each output will now drop below their 10rW requirement and all three turrets will turn off. This is a simultaneous failure when experiencing a power deficit.
- Electrical Branches: Chain two branches together so there are three effective outputs (Power Out of the first into Power In of the second). Set Branch Out on both to 10. With 30rW in, the first branch supplies 10rW to Turret A and forwards the remaining 20rW to the second branch. The second supplies 10rW to Turret B and forwards the last 10rW to Turret C. If power input falls to 20rW, Turret A and B continue to receive 10rW each, while Turret C receives 0rW and turns off. This is ordered power shedding that preserves higher priority loads longer.
Principle: Splitters equalize and tend to fail everything at once when input is insufficient. Electrical Branch chains allocate fixed amounts in order and shed lower priority loads first.
Application Guidance
Prioritization matters when a circuit can operate under partial power. If the design drops straight to 0rW on failure, priority settings cannot buy time. If the circuit design preserves some power delivery, priority decides which loads stay online and the order in which others shed. The notes below map that logic for common backup types.
- Classic Inline Backup: When the single inline battery depletes or is destroyed, output falls to 0rW immediately. There is no partial power phase to allocate, so prioritization adds material cost without runtime benefit. For nine turrets, four Splitters (4 × 100 Metal Fragments = 400 Metal Fragments) are cheaper than eight Branches (8 × 75 Metal Fragments = 600 Metal Fragments).
- Bypass Backups and Battery-Checked Backups: These designs continue to pass Root Power even if the local battery is depleted or destroyed. When partial Root Power remains, Electrical Branch prioritization keeps higher‑priority loads online and sheds lower‑priority loads in order, extending useful uptime and avoiding a full blackout.
- Series Batteries: When two or more batteries are wired in series on the same electrical path, loss of one does not disable the others. A surviving battery can still deliver some power, so prioritization with Electrical Branches will keep higher priority loads online until the remaining output is exhausted.
Design Rules of Thumb
- Use Splitters when loads are equal in priority and an all or nothing outcome is acceptable.
- Use Electrical Branch chains when loads need a strict priority order or when partial power is expected.
- Set Electrical Branch values to the exact rW needed per load and place the most important load on the earliest branch.
- If input reaches 0rW, neither device helps. Everything turns off.
Root Combiner Behavior
When combining batteries using a Root Combiner, the resulting behavior might not be what one would expect unless being familiar with wiring batteries in series. The output is increased but the capacity stays the same. This is different from running multiple separate batteries in parallel, giving the same output but increasing the capacity, and has important implications on Active Usage.
Each battery connected to a Root Combiner will register the full Active Usage of the connected circuit, there is no load sharing between batteries.
- 2 Large Batteries powering a 200rW circuit = 100 Active Usage per battery
- 2 Large Batteries powering a 60rW circuit = 60 Active Usage per battery
This is true regardless of how much power is actually being consumed by the circuit. The Root Combiner does not split or balance the load between the batteries, each one sees the full value.
This behavior is covered in greater detail in Batteries: Parallel vs Series, but for the purposes of understanding power efficiency here:
- If combining batteries, either fully utilize their combined output, or split the circuit and use separate batteries. Otherwise, the battery drain may be disproportionately high for what the circuit actually needs.
⚠️ Avoid Combining Batteries in Inline Backups
Do not use a Root Combiner to combine batteries in a primary Inline backup.
When batteries are wired in series (via Root Combiner), each one will register the full Active Usage of the circuit, even if more power is being supplied than needed.
- For example, a 200rW circuit powered by two Root Combined Large Batteries will result in 100 Active Usage per battery, requiring 252rW of Root Power just to stay neutral.
- That’s 252rW produced for 200rW usable output, a net loss of efficiency.
Using a Bypass backup instead would allow the same 200rW circuit to run with only 220rW of Root Power, depending on how much power is needed to recharge the batteries.
💡 Tip: Two Large Batteries powering a 120rW circuit through a Root Combiner will still have 100 Active Usage per battery. This means they will last only 4 hours. If a circuit only needs 120rW and uptime is important, split the circuit across two 60rW segments powered by separate batteries to increase the runtime.
Additional Root Combiner Rules
While Root Combiners are powerful tools, there are two important rules that can impact their use in larger or more complex circuits:
- Max Depth Limitation: Root Combiners are subject to a 16-component Max Depth limit. If a power path exceeds 16 components between a Power Source and the Root Combiner, it will result in a Short Circuit / Max Depth error and power will not be delivered past this point. This becomes particularly relevant in pyramid-stacked RC-Bus systems and battery backups with long chains of components.
- No Self-Feeding Power Loops: A Root Combiner will not recombine power that has already passed through itself. If power is routed through a Root Combiner, used in a circuit, and then sent back into one of its inputs (intentionally or not), the combiner will ignore that power source. This fails silently — the Root Combiner simply refuses to recombine that recycled signal. This can occur in circuits with poor layout or in attempts to merge power that has already been merged before. Each input must be a clean, non-circular source.
Basic Dive into Modern Active Usage and Power Consumption
When defining Active Usage, it says:
- Active Usage is always Consumed Power, but Consumed Power is not always Active Usage.
Let’s break down what this means with two clear demonstrations.
⚙️ Active Usage is Always Consumed Power
Take an Auto Turret that is powered, has locked onto a target, but is out of ammo. To use any of its three outputs (Has Target, Low Ammo, No Ammo), it must be given 11rW, 10rW for the turret itself and 1rW for output functionality.
Internally, the turret generates 2rW of Free Power (1rW from 2 outputs if given 11rW). If all three outputs are connected to Industrial Lights, each light will consume 1rW and create 1 Active Usage.
If this setup is powered by a battery, the total Active Usage shown will be 13:
- 10rW for the turret
- 1rW for the first light
- 2rW from the lights consuming the free power
Even if the turret is powered through an Electrical Branch set to 11rW, the result is the same. The turret still generates 2rW of Free Power. The Electrical Branch limits the flow of power to the turret, but it does not limit the Active Usage passed back to the battery. So, the battery still shows 13 Active Usage, despite consuming only 11rW from the branch.
This shows that Active Usage is always tied to power being consumed, even when that power is created internally.
⚠️ Consumed Power is Not Always Active Usage
Now consider a SAM Site configured to "Attack All," with a Smart Switch controlling its Invert Mode input.
- The SAM Site itself requires 25rW.
- The Invert Mode input (to switch behavior) requires 1rW.
So, in total, the setup consumes 26rW. However, when powered by a battery, only 25 Active Usage is shown. This happens because the 1rW sent to Invert Mode is consumed but does not contribute to Active Usage. The battery doesn't count that part of the load, even though it's necessary for the circuit to function correctly.
This illustrates the second half of the principle: Power can be consumed by a components auxiliary inputs without generating Active Usage, which is why it can also be said when defining Consumed Power that Consumed Power includes all energy used for functionality, regardless of whether or not it registers as Active usage on a battery.
To dive deeper into the different power types, how they interact with each other and how players can leverage one against another, the following examples are used to help demonstrate what players should be considering when designing a circuit or selecting a battery backup.
Example: Backup Turrets Using A Splitter
This example demonstrates how a circuit that consumes a lot of power can leverage Active Usage to reduce overall Root Power demand, especially when switching between Bypass and Inline battery backup strategies.
In this setup, there are six Auto Turrets, each with its own backup turret hidden behind a door. When a turret is destroyed, a Door Controller opens the door and secondary turret powers on. This is achieved using the Splitter’s ability to redistribute power when an output is disconnected.
The structure of this circuit is built from two mirrored groups:
- Each group uses 1 Splitter to feed 3 additional Splitters.
- Each of those three outputs connects to:
- Output 1: the primary Auto Turret
- Output 2: an Electrical Branch set to 10
- Branch Out powers the secondary Auto Turret
- Power Out opens the Door Controller
Each group of turrets needs 57rW to function. Each of the 3 local Splitters receive 19rW. When splitting unevenly, Splitters distribute power with Output 1 prioritized over 2 and 3. 10rW is sent to the primary turret, and 9rW is passed to the Electrical Branch. Since the branch is set to 10, the secondary turret remains off because of insufficient power. When the primary turret is destroyed, the full 19rW flows to the Electrical Branch, activating the backup turret and opening the door.
This system powers 6 turrets + 6 backups = 12 turrets total, with a continuous demand of 114rW to keep all logic and primary turrets running.
⚡Solving For Efficiency
If powered using a BCN Core or similar Bypass battery backup, the full 114rW must be reserved at all times. That’s a significant amount of Root Power allocated just for turret logic and failover behavior. To get more than 100rW of power using an Inline Battery backup, like the Kore, 2 batteries would need to be combined and that is never recommended. So what's the solution?
Break the circuit into 2 parts and use two Large Batteries instead. One for each group of 3 turrets. The Active Usage per battery is only 30 (10 per active turret). The remaining 27rW used for logic is classified as Control Power and does not register Active Usage. Each battery, with 30 Active Usage, requires only 38rW of input to stay neutral. Using two batteries, this entire system can be maintained with just 76rW of Root Power instead of 114rW, a 33% savings.
- This example illustrates how introducing inline batteries, even when using a Bypass backup like the BCN Core can result in lower Root Power production requirements.
A bypass backup can benefit dramatically by adding an Inline Secondary battery backup. By placing a battery between the BCN Core’s distribution grid and the turret system, all the power that needed to be reserved for logic is offloaded onto the battery for free because it is Control Power and Control Power does not generate Active Usage. Not only is this a 33% reduction in Root Power requirements, it also added a 325% bonus in battery backup time. After the 4 hours of primary backup power, these turrets will have an additional 13 hours of backup time. This is a huge gain in efficiency.
This demonstrates the power of leveraging a battery to take advantage of Active Usage and Control Power. The more complex and logic driven systems are, the larger the benefit can be by taking advantage of Active Usage and offloading logic control to Control Power.
Example: Flipping Flop Turrets
This example demonstrates how circuits with high baseline power consumption but a lower Active Usage may be more efficiently powered by Root Power directly, rather than through a battery.
In this setup, a group of six Auto Turrets is powered for a period of time, then turned off while a second group of six turrets is powered. The system flips between these two groups using a Memory Cell, creating a rotating turret defense that stays under the turret interference limit while extending coverage.
A Timer triggers the Memory Cell to flip outputs every X seconds, alternating power between the two turret groups. If a turret in the active group locks onto a target, its Has Target output disables the timer, freezing the cycle until the threat is cleared. This ensures defense presence is maintained without flipping turrets unnecessarily during a raid.
The structure of this circuit is built from two mirrored groups:
- Memory Cell Output or Inverted Output → Electrical Branch 1 (set to 3)
- Branch Out → Blocker (used to disable the timer system if any turret has an active target)
- Power Out → Electrical Branch 2 (set to 11)
- Branch Out → Turret 1
- Power Out → Electrical Branch 3 (set to 11)
- Branch Out → Turret 2
- Power Out → Electrical Branch 4 (set to 11)
- Branch Out → Turret 3
- Power Out → Electrical Branch 5 (set to 11)
- Branch Out → Turret 4
- Power Out → Electrical Branch 6 (set to 11)
- Branch Out → Turret 5
- Power Out → Turret 6
- All Has Target outputs → OR Switch network → Block Passthrough input on Blocker
- Blocker Input → Power from Electrical Branch 1 (Branch Out)
- Blocker Output → Splitter
- Power Out 1 → Timer
- Power Out 2 → Timer Toggle
- Power Out 3 → Blocker (which controls SET/RESET of Memory Cell)
When the Splitter receives power, it triggers the Timer and blocks the Blocker. When the Timer ends, it sends power through the final Blocker to SET or RESET the Memory Cell, flipping turret groups.
⚡ Solving For Efficiency
This turret system needs 69rW to function. 60rW is used to power the six turrets, while the remaining 9rW supports the logic that flips turret groups back and forth. That includes the Memory Cell, Timer, OR Switches, and Blockers.
If a player powers this setup with a Bypass Battery Backup, the logic will need Root Power to function, the full 69rW must be produced and supplied at all times. The battery is bypassed entirely, and while this means there’s no charging overhead, it also means no potential savings. Every bit of Root Power must be generated.
On the other hand, an Inline Battery Backup changes the equation slightly. Here, the battery only “sees” the six turrets and registers 60 Active Usage, and because batteries are only 80% efficient, the battery now needs 75rW of input power just to break even.
Even though the logic portion doesn’t create any Active Usage, the battery still needs more Root Power than the bypass setup, about 6rW more, just to hold its charge. That’s not a huge difference on its own, and might be with the cost for an additional 6 hours and 40 minutes of uptime, but this system is designed to scale. If each group was to be increased to 10 or more turrets, and powered by batteries, the gap grows by 25rW or more and that’s significant.
This is a perfect example of when produced Root Power is the better choice. When a circuit’s power demand is primarily functional (e.g., Auto Turrets), there is little efficiency benefit to routing power through an Inline battery. Offloading control logic to a battery works best when that logic makes up a larger portion of the circuit’s power cost. This is not one of those cases.
- Produced Power is ideal for direct-use, high-drain components.
- Inline batteries should be reserved for circuits that benefit from Active Usage scaling or Control Power offloading.
When logic overhead is low and component demand is high, Root Power offers better scalability and efficiency. Not every system benefits from leveraging Control Power or Inline backups. Sometimes, direct Root Power is the smartest approach.
Example: Automatic Sprinklers
This example demonstrates how a circuit can benefit from the player’s understanding of Control Power, power used for logic and timing that does not generate Active Usage. When 30% or more of a circuit’s power is used for logic rather than function, it may be possible to increase efficiency by isolating that portion of the circuit and offloading it onto a standalone battery that doesn’t need to be recharged.
This is a simple watering system for a farm. It contains four Ceiling Lights, four Sprinklers, and a basic timing circuit using two Timers. The left Timer turns the water on (short cycle), while the right Timer resets the loop (long cycle). Water is collected from a Large Water Catcher and delivered to the Sprinklers using a Fluid Switch & Pump.
The structure of the circuit is:
- Power In → Electrical Branch 1 (set to 8)
- Branch Out → Switch → Ceiling Light 1 → 2 → 3 → 4
- Power Out → Electrical Branch 2
- Power In → Electrical Branch 2 (set to 2)
- Branch Out → Short Timer → Electrical Branch 4 (set to 1)
- Branch Out → Toggle on Fluid Switch & Pump
- Power Out → Pump Power input
- Power Out → Electrical Branch 3
- Power In → Electrical Branch 3 (set to 1)
- Branch Out → Long Timer → Block Passthrough input on Blocker
- Power Out (sending 2rW) → Switch → Blocker
- Blocker Output → Splitter
- Power Out 1 → Toggle Short Timer
- Power Out 2 → Toggle Long Timer
When the short timer starts, it enables the pump and Sprinklers. The long timer restarts the short timer and itself, keeping the cycle running. The lights remain on independently.
⚡ Solving For Efficiency
This circuit draws 13rW total:
- 8rW powers the four Ceiling Lights
- 5rW powers the logic system—timers, splitters, blockers, and the pump controller
This means that 38% of the circuit’s energy demand is tied to automation rather than functional components. Understanding how to handle this distribution can greatly improve overall efficiency depending on the power delivery method used. If connected to a Bypass Battery Backup, all 13rW must be provided constantly from Root Power. While this works, it’s not the most power-conscious setup.
By switching to an Inline Battery Backup, only the power that generates Active Usage matters. Since the lights are the only components that produce Active Usage, the battery sees just 8rW of drain. As a result of the battery’s 80% efficiency, only 10rW of power input is needed to maintain charge. This already provides a 3rW savings in Root Power, translating to a 23% improvement in power efficiency. This setup is great for small-scale farms powered by a dedicated solar panel or generator. If players actually use the Switches when they log off, power demand will drop to 0.
Players using a modern Bypass Backup System, like the BCN Core, and just want to leave the lights turned on all the time, can optimize even further by leveraging Control Power. Since the logic components in this circuit do not create Active Usage, they can be powered by a battery that doesn’t need recharging, resulting in zero drain on Root Power. If a modern BCN Core is being used, it already has a battery for Control Power that can be used to supply Control Power for a circuit like this.
In this setup:
- The Bypass Backup only needs to provide 8rW for the lights
- A Control Battery supplies the remaining 5rW for the logic system
This configuration reduces Root Power consumption by 38%, without compromising functionality.
This example highlights the importance of recognizing when a circuit’s automation or logic can be separated from its functional load. By offloading Control Power and understanding where Active Usage is actually generated, players can design systems that are more sustainable, more efficient, and better suited for expansion.
Example: Automatic Furnace
This circuit demonstrates how circuits that don’t need to operate continuously can benefit from smart management of Stored Power. While it’s commonly said that a battery needs Active Usage × 1.25 to stay charged, that formula assumes continuous operation. If a circuit is only active part of the day, the player can input less power, as long as the battery has enough downtime to recover its capacity.
This design uses 6 Electric Furnaces managed by two Conveyors and a filtering system. The furnaces will only activate when Ore is detected. The first Conveyor detects ore and activates the Switch. When both Conveyors detect no items, they trigger an AND Switch that turns the furnaces off. The goal is to minimize energy usage while maintaining full automation.
Power In → Conveyor 1 → Conveyor 2 → Switch → Splitter
- Splitter → 2 additional Splitters → 6 Electric Furnaces
Conveyor 1:
- Checks the Input Box
- If Ore is present, sends Filter Pass → Switch Turn On
- If Ore is absent, sends Filter Fail → AND Switch
Conveyor 2:
- Transfers items as needed
- If smelted ore is absent, sends Filter Fail → AND Switch
When both conveyors signal completion, the AND Switch sends a pulse to the Turn Off input on the Switch, deactivating the furnaces.
This circuit is already intelligently designed by placing the furnaces after the Conveyors. Normally, if a conveyor is going to use an output, it needs to be given 2rW. The exception is when they are passing power through, they will only use 1rW.
⚡ Solving for Efficiency
This system has two clear power states:
- Active: 20rW required (furnaces on + conveyors)
- Idle: 2rW required (just conveyors monitoring)
Powering this from Root Power would require reserving 20rW at all times, whether the furnaces are active or not. Powering from a battery and always supplying 25rW to overcome Active Usage (20 × 1.25) would also be overkill if the system isn’t always running.
If a player can estimate the duration of usage per day, we can calculate the exact Root Power required to keep a battery neutral across that period. For example, let’s say the furnaces are active for 11 hours per day and idle for 13 hours.
📈 Step 1: Calculate Total Daily Capacity Use
Formula:
DailyCapacity = (ActiveUsageActive × MinutesActive) + (ActiveUsageIdle × MinutesIdle)
Legend:
- DailyCapacity: Total rust watt minutes (rWm) used in 24 hours
- ActiveUsageActive: Power draw during activity
- MinutesActive: Minutes the system is on
- ActiveUsageIdle: Power draw during standby
- MinutesIdle: Minutes the system is idle
Example:
DailyCapacity = (20 × 660) + (2 × 780)
= 13,200 + 1,560
= 14,760rWm
Therefore 14,760rWm of capacity will be consumed over a 24 hour period.
🔋 Step 2: Calculate Input Power to Stay Neutral
Formula:
RequiredInput = DailyCapacity ÷ (1440 × 0.8)
Legend:
- RequiredInput: Minimum Root Power input in rW to keep battery neutral
- 1440: Minutes in a day
- 0.8: Battery efficiency
Example:
RequiredInput = 14,760 ÷ (1440 × 0.8)
= 14,760 ÷ 1152
≈ 12.8rW ➞ rounded up to 13rW
By inputting just 13rW constantly into the battery, the system will break even over the day.
📊 Step 3: Check Battery Capacity Requirements
This step verifies if the battery can survive the discharge cycle.
Formula:
NetLoss = (ActiveUsageActive × MinutesActive) - ((RequiredInput × MinutesActive) × 0.8)
Legend:
- NetLoss: Total rWm lost from battery during activity
- ActiveUsageActive: Power draw during activity
- MinutesActive: Minutes the system is on
- RequiredInput: Minimum Root Power input in rW to keep battery neutral
- 0.8: Battery efficiency
Example:
NetLoss = (20 × 660) - ((13 × 660) × 0.8)
= 13,200 - 6864
NetLoss = 6,336rWm
This means the battery will lose 6,336rWm over the 11 hours of operation. A Medium Battery (9,000rWm) would be more than enough to handle the load.
✅ Alternate Example (Quick and Dirty Method)
RequiredInput = ((PowerRequiredActive - PowerRequiredInactive) × (MinutesUsed ÷ 1440) + PowerRequiredInactive) × 1.25
Legend:
- RequiredInput: Minimum Root Power input in rW to keep battery neutral
- PowerRequiredActive: The amount of power the circuit needs to fully function
- PowerRequiredInactive: The amount of power the circuit needs in when not being used
- MinutesUsed: The number of minutes in a day the circuit will be active for
- 1440: The number of minutes in 24 hours
- × 1.25: Battery efficiency
Example: Let’s assume the circuit uses 20rW for 11 hours a day and 2rW the rest of the time it is in standby.
RequiredInput = ((20 - 2) × (660 ÷ 1440) + 2) × 1.25
= ((18) × (0.46) + 2) × 1.25
= (8.28 + 2) × 1.25
= (10.28) × 1.25
RequiredInput = 12.85rW ➞ rounded up to 13rW
Note: This equation does not take into account how much capacity will be consumed during the active time. Not taking this into consideration can lead to the battery becoming depleted.
This balance of charge/discharge is key. It allows players to operate high-drain systems intermittently without needing large-scale power generation. This strategy is ideal for automated systems that react to player input or inventory states. Perfect for furnaces, doors, alarms, or anything event-triggered.
- Reduces constant power draw from 20rW → 13rW, a 35% reduction in Root Power
- Introduces flexibility to scale up without needing more Root Power
- By balancing discharge with recharge cycles, the battery can sustain operations efficiently.
- Smart use of Stored Power can significantly reduce Root Power demands.
Example: The Simple Trap
This example demonstrates how circuits triggered by basic player inputs can greatly benefit from using Free Power for Control Power to reduce Root Power requirements.
The goal of this trap base is simple: trap an intruder between two doors. When the victim steps on a Pressure Pad, one door shuts behind them, and another opens ahead, exposing a deadly room full of Shotgun Traps. A Memory Cell handles the power switching between the two doors. To reset the trap, the base owner presses a Button, but only if they’re detected by the HBHF Sensor, which prevents outsiders from resetting the system.
Power enters a series of 3 Electrical Branches:
- Branch 1 ( Set to 1)
- Branch Out: 1rW to the Pressure Pad → Sends pulse to SET on the Memory Cell
- Power Out: Feeds Branch 2
- Branch 2 (Set to 1)
- Branch Out: 1rW to a Smart Switch → Keeps the Memory Cell Input powered
- Power Out: Feeds Branch 3
- Branch 3 (Set to 2)
- Branch Out: 2rW to the HBHF Sensor (set to authorized players only)
- Power Out: 1rW to the Button
The Button and HBHF Sensor outputs are wired into an AND Switch. When both inputs are active, the AND Switch sends 1rW to the RESET input of the Memory Cell, flipping it back. This provides players with a 2 factor authentication system.
The Output and Inverted Output of the Memory Cell are each connected to a Door Controller, ensuring only one door is powered (and therefore open) at a time.
⚡ Solving for Efficiency
At first, this circuit appears fairly lightweight, it only draws 5rW. A closer inspection shows that only the Door Controller (whichever is currently active) and the HBHF Sensor actually generate Active Usage. That means we could place the entire system on an Inline backup, and only see 2 Active Usage, requiring just 3rW input to remain neutral, already a 40% power savings compared to using Root Power directly.
But things can go further.
Two of the components, the Pressure Pad and the Button, generate Free Power when activated. The Pressure Pad sends a free 1rW pulse to SET, removing the need for an Electrical Branch. Likewise, the Button generates 2rW when pressed, just enough to both power the HBHF Sensor (which needs 1rW) and pass the second 1rW to RESET on the Memory Cell. Now the logic circuit is entirely self-powered, the circuit will only need 1rW to keep the Smart Switch (and by extension, the Memory Cell’s Input) constantly powered.
That’s an 80% reduction in Root Power requirements, from 5rW down to 1rW, all by understanding the components and leveraging Free Power. In larger circuits, small reductions like this can add up fast.
🔍 Pro Tip: The Reactive Target also produces 1rW of Free Power when shot down with no input power, offering another creative input option for similar designs.
This example illustrates how a circuit that relies on player input can do it at zero cost to Root Power. From turning on a Strobe Light, activating fireworks at a distance or calling an Elevator, there are many situations where simple traps or logic systems can be optimized drastically by utilizing these components. Even circuits with low power requirements benefit from minimizing Root Power dependency. Components like the Button and Pressure Pad are not just inputs, they are power sources, and when used wisely, they can eliminate the need for continuous power input entirely in parts of a circuit.
Power Waste and Circuit Efficiency
All circuits can result in some level of wasted electricity. Power waste in this context refers to generating or storing more power than is actually required to support a circuit’s needs. Managing that waste starts with understanding the different types of power and how they interact.
By leveraging Root Power, Active Usage, Control Power, and related mechanics, often in combination, circuits can be built to support loads that would otherwise demand significantly more generation and storage. Circuit efficiency allows effective capacity to exceed what raw power numbers alone would suggest.
The key consideration is not whether waste occurs, it is nearly inevitable, but where it occurs and why. Well-designed circuits intentionally shift waste away from generation and storage and into controlled areas of intelligent consumption. The goal is not zero waste, but maximum leverage from every unit of power. Efficiency is a matter of balance, not the elimination of loss.
Summary
This section redefines how players evaluate and build circuits in Rust. By breaking down the different forms of power and showing how they interact, this section helps players:
- Identify waste in circuit design by understanding where power is being used vs. where it's being drained.
- Leverage Control and Free Power to offload logic components from Root Power.
- Use batteries strategically, choosing between Inline or Bypass backups depending on circuit behavior.
- Reduce overproduction, avoid unnecessary battery drain, and extend circuit uptime through smarter design.
Each example, from turret arrays to sprinklers, auto furnaces, and trap systems, shows how even small adjustments can make a circuit more efficient. The result is not just power savings, but greater design flexibility, lower upkeep costs, and better performance under pressure.
Power Generation
This section covers the concepts behind components that generate Root Power in Rust. Power generation is the starting point of every electrical system and determines the upper limits of what a circuit can support.
Rather than focusing on individual build recipes, this section explains how generation sources behave, what constraints they impose, and how their characteristics influence downstream design choices such as storage, distribution, redundancy, and efficiency.
Each generation method is treated as a system with strengths, weaknesses, and predictable failure modes. Understanding these properties allows players to select the right source, or combination of sources, for a given circuit goal.
Wind Power
Wind turbines are the most common source of large-scale electricity in Rust. They are capable of producing anywhere from 0rW to 150rW of Root Power and, when properly placed, are among the most reliable generation methods available. Their output is influenced primarily by height above buildable ground and physical obstructions in the path of the wind.
Unlike fixed-output generators, wind turbines produce variable power. Their strength lies not in constant output, but in high potential capacity combined with predictable statistical behavior over time.
Turbine Clearance and Obstruction Rules
Wind turbines are large deployables and require significant clearance. Any obstruction that blocks the wind path will cause the turbine to stop spinning and produce 0rW until the wind direction changes.
The critical distance is 15 meters, or 5 square foundations, measured outward from the turbine.
The shape should be a circle but squares are just easier to work with in game. Building outside this zone is always safe. Building inside it is possible, but requires understanding how obstruction checks work.
The Wind Beam
Each wind turbine emits an invisible, narrow "wind beam" from the front of the turbine at the intersection of the blades. This beam:
- Extends 15 meters (5 foundations) outward
- Is aligned with the horizontal drive shaft
- Sits slightly above 2 floors high
If this beam is obstructed by terrain, building pieces, or deployables, the turbine will stop producing power. Because the beam is thin, structures can be built below it without interference. Walls and floors placed beneath the beam do not block power generation.
- Angled roofs on the second floor will block the beam, as they extend just high enough into the third-floor space.
- Where the Double Door Frame exists, not the empty space inside it, will also block the wind beam.
The following items do not block the beam when placed inside a double door frame:
- Chainlink Fence
- Netting
- Open Garage Door
Fully Enclosing a Wind Turbine
It is possible to fully enclose a turbine within a structure if two conditions are met:
- The third floor must be completely free of obstructions out to 5 square foundations.
- Due to stability issues, this is impossible and Double Door Frames are needed. They will block the wind sometimes.
- The space directly above the turbine must be clear for 7 floors.
Meeting these conditions allows turbines to be protected without sacrificing too much power output.
Turbine Rotation
A wind turbine always rotates clockwise and completes a full 360-degree rotation approximately once per hour. This rotation is not cosmetic and helps illustrate changing wind direction and where it is checking for obstructions.
Height and Average Power Output
Knowing how close to the Wind Turbine structures and deployables can be placed is the first step. The next part is knowing how high they need to be built. Turbine height is measured as the vertical distance between the turbine and the buildable ground below it, not elevation above sea level. A turbine placed six floors above ground at the beach will produce the same average power as one placed six floors above ground on a mountain.
Players typically measure height by counting floors down to the foundation, which is sufficiently accurate for design purposes. For precise calculations, foundation height can be included.
The higher a turbine is placed, the higher its average power output and the more frequently it reaches its maximum of 150rW.
Power Fluctuation and Averages
Wind strength varies continuously, causing turbine output to fluctuate over time. Because of this variability, turbines are described using average output rather than instantaneous values.
At any height:
- Output can temporarily reach 0rW (rare)
- Output can reach 150rW (more frequent at higher elevations)
Over long observation periods, most fluctuations fall within approximately ±50rW of the average. To help illustrate this, in the picture below, the blue line shows the amount of power a turbine at ground level was producing over the period of a random hour. It consists of approximately 180 data points. The red line is what is said to be the average output for a turbine at ground level. During this hour, the turbine's max output was only 113rW and its lowest output was 39rW. If this graph was stretched out to 100+ hours, it would show that the most common fluctuations are about 50rW + or - the average output.
Reliability Thresholds
Beyond averages, turbine data can be analyzed to determine how often a turbine produces at least a specific amount of power.
For example:
- If a circuit requires 60rW with a minimum 92% uptime, data shows that a turbine built six floors or higher will reliably meet that requirement.
- If a circuit requires 80rW with a minimum 85% uptime, data shows that a turbine built 9 floors or higher will reliably meet that requirement.
- If a circuit requires 120rW only 6% of the time, data shows that a turbine built on the second floor will meet the requirement.
This type of analysis allows players to design circuits based on guaranteed minimum output, rather than optimistic peak values.
Design Implications
Understanding wind behavior allows players to work in both directions:
- Given a circuit’s power requirement, determine how many turbines and what height are needed
- Given limited space or turbine count, determine how large a circuit can be supported reliably
This knowledge reduces overbuilding, prevents brownouts, and improves overall efficiency.
Solar Power
For Console players, face your panels North, for PC players, keep reading.
Solar panels generate Root Power based on direct line of sight to the sun. Unlike wind power, solar output follows a predictable daily and seasonal cycle, making it a reliable but time-limited generation source.
Seasons and the Rust Year
Rust’s island is located in the southern hemisphere, meaning seasonal behavior is inverted compared to what most players will expect.
- Winter Solstice (June):
- It is the shortest day of the year.
- The Sun will travel its most Northern path.
- Sunrise is the latest.
- Sunset is the earliest.
- During the winter months, solar panels have the lowest total solar production.
- Summer Solstice (December):
- It is the longest day of the year.
- The Sun will travel its most Southern path.
- Sunrise is the earliest.
- Sunset is the latest.
- During the summer months, solar panels have the highest total solar production.
Only an admin can get the exact date and time. This is what players cannot see.
Watching where the Sun rises and sets on the horizon can give a player an idea of the time of year. Some modded servers will have a plugin that gives players a clock and might show the sun up and down times. Some might even show the date.
Sun Path and Panel Orientation
A full Rust day lasts 1 real hour, and a full Rust year spans roughly 15 real days. Over that year, the sun’s path gradually shifts north and south, changing both sunrise/sunset times and the sun’s angle in the sky.
Solar panels generate power only when the face of the panel has line of sight to the sun, and because the sun’s seasonal path changes, panel orientation needs to be a design choice.
- The sun rises in the East and sets in the West
- Panels ramp up power after sunrise, peak when the sun is high, and ramp down toward sunset
- Wipe day is May 20th 2024 1200h(12pm)
For short wipes of 5 days or less, face the panel North and walk away. If players are not joining on wipe day but are still only playing for a few days, orienting panels toward the dominant sun path is very acceptable.
For longer wipes, the most reliable configuration is to place paired panels, with one facing East and one facing West. This approach minimizes the need to reposition panels as the year progresses.
Here is a graph showing roughly how much power a panel was able to collect based on its orientation over the course of an in-game year. Breaking it apart, it shows:
- A North facing panel from the start of wipe and through the first 3 real life days, can collect around 640rWm of power each in a game day.
- A South facing panel won’t start to collect more than 100rWm an in game day for nearly 3 real life days. It will eventually peak with 650rWm collected, but only for 1 real day, and that’s only 7.5 real days after wipe started.
- A West facing panel starts the wipe collecting around 440rWm of power each game day. Over the next 7.5 real days, the amount it collects will increase and peak around 500rWm a game day.
- In an attempt to not clutter the graph, it is implied that the panel directions not shown here are the inverse of their opposites. Meaning:
- Northeast is the inverse of Northwest
- Southeast is the inverse of Southwest
- East is the inverse of West
Obstructions and Line of Sight
Solar panels require an unobstructed view of the sun.
The following block solar output:
- terrain and ground
- cliffs and hills
- trees
- building blocks
Deployable items do not appear to block sunlight.
To take full advantage of a Solar Panel, try to capture the Sun in the morning the moment it rises above the horizon, and all the way to the moment the Sun drops below the horizon at night. In order to accomplish this, line of sight to each horizon is required. The best chance of achieving line of sight to both horizons is by building on top of the highest mountain.
Otherwise, in the mornings, Eastward facing panels on the West side of the map will need to wait for the Sun to get high enough in the sky to clear the hills and mountains. The panels on the East side could catch the sun the moment it peaks above the horizon.
In the evenings, Westward facinging panels on the East side of the map will have the amount of time they could produce power cut short as the Sun moves behind the hills and mountains. The panels on the West side could catch the sun up to the moment it drops below the horizon.
Solstice Solar Yield and Specifics
If a pair of panels are placed so each could see either the East or West horizons, the following could reasonably be expected, within a reasonable margin or error.
The Winter Solstice (June 20 2024):
- Solar Panels facing East can start to capture the Sun around 7:10am.
- Power levels will slowly increase until around 9:05 am when they will be producing a full 20rW.
- This lasts until about 1:30pm. Around this time, it will slowly start decreasing power production until around 3:45pm when it stops.
- The panel facing West can start to capture the Sun around 11:40am.
- A few minutes later at around 1:45pm, it will start producing a full 20rW.
- Around 6:15pm the panel will start decreasing the amount of power produced until about 8:15pm when it stops.
- During the winter solstice, 2 combined panels, 1 facing East and 1 facing West, can collect around 940rWm of power.
The Summer Solstice (December 21 2024):
- Solar Panels facing East can start to capture the Sun around 6:30am.
- Power levels will slowly increase until around 8:20am when they will be producing a full 20rW.
- This lasts until about 2:30pm. Around this time, it will slowly start decreasing power production until around 4:15pm when it stops.
- The panel facing West can start to capture the Sun around 11am.
- A few minutes later at around 1 pm, it will start producing a full 20rW. Around 7 pm the panel will start decreasing the amount of power produced until about 9 pm when it stops.
- During the summer solstice, 2 combined panels, 1 facing East and 1 facing West, can collect around 1075rWm of power.
Capacity Planning
When working with solar panels for a primary source of power, it is very helpful to know how to calculate how much capacity a circuit needs to last 1 in game day. Knowing the capacity will dictate how many panels are needed. Base the number of panels used on the lowest amount of power they will produce on the shortest day of the year.
The Maths
rWm: rust watt minutes (capacity)
rW: Rust Watt (aka power)
S: Seconds
τ: 60 (The number of minutes in an hour)
M: Minutes
A: The battery’s Active Usage
H: Hours
Required Capacity for a Constant Load
To figure out how much capacity is needed to support a circuit of a specific load, use the following equation:
A × τ = rWm
Example: A circuit with an Active Usage of 64rW.
A × τ = rWm
64 × 60 = 3840rWm
Therefore a circuit needing a constant 64rW over the course of 1 hour will consume 3840rWm worth of power.
Determining Panel Count
To figure out how many pairs of panels are needed to support a specific amount to power, use the following equation:
rWm ÷ 940rWm = Solar Panel pairs
Example: A circuit with an capacity requirement of 3840rWm
rWm ÷ 940rWm = Solar Panel pairs
3840rWm ÷ 940rWm = 4.08
Therefore 5 pairs of panels are needed to capture enough rWm to cover the power cost of a 64rW circuit. 2 solar panels make a pair, so 10 panels total.
Runtime Calculations
To figure out how much time a given capacity will run for, outputting a specific amount of power, we use the following equations:
Seconds: (rWm ÷ A = M) × τ = S
Minutes: rWm ÷ A = M
Hours: (rWm ÷ A = M) ÷ τ = H
Design Implications
Solar power excels in predictable, low-to-moderate load systems where space is available for panels and batteries. Its limitations are daylight dependence and seasonal variation.
By designing for the shortest day of the year and pairing panels to capture both horizons, solar systems can be made extremely reliable without constant adjustment.
Power Storage
Battery Backup
A battery backup system in Rust is a circuit designed to automatically supply power when the primary power source fails. It ensures continuity for critical systems like turrets, traps, lights, or communication devices, especially during night cycles, periods of low wind, or fuel shortages. In real-world power infrastructure, similar systems are known as UPS (Uninterruptible Power Supplies) that keep essential devices operational during power outages. Rust may be a post-apocalyptic sandbox, but backup theory remains applicable.
Real-Life Inspiration: Rust vs UPS Systems
In real-world power infrastructure, there are two major types of UPS configurations:
- Bypass (Line-Interactive) UPS: These remain idle during normal operation and only activate when power loss is detected.
- Inline (Double Conversion) UPS: These always supply power through the battery, ensuring seamless delivery and built-in filtering against power fluctuations.
Rust mirrors these designs with its own terms:
Real Life
Rust Equivalent
Description
Line-Interactive UPS
Bypass Backup
Main power flows directly to the circuit. The battery is bypassed unless needed.
Double Conversion UPS
Inline Backup
All power flows through the battery first. The battery is always active.
Additionally, rustricians have introduced a third tier. Battery-Checked Backups which monitor the amount of power the battery bank can supply. If the batteries cannot provide the required amount of power, because some were destroyed or depleted, the circuit will begin feeding Root Power to the circuit, regardless of how much power is available. Some power is better than no power.
Types of Battery Backup Systems in Rust
There are three main styles of backup circuits, each with their own advantages and disadvantages.
1. Inline Backup
- Example: The Inline circuit.
- The battery is always active. It's simple to build and easy to set up.
- Efficiency loss scales poorly when multiple inline batteries are used due to the 80% efficiency rule.
- Best suited for short-term or for circuits that are made up of 30% or more logic components.
2. Bypass Backup
- Example: The Nih Core circuit.
- The battery is inactive unless needed. It's only used if primary power fails to meet the required demand. The power that cannot meet the demand is routed towards the battery to slow the drain and increase runtimes.
- Offers greater efficiency when scaling with multiple batteries. The 80% efficiency rule does not apply allowing for less power generation to remain stable as compared to an Inline backup.
- Best suited for large centralized systems supporting circuits in the multiple hundreds of power with a shared power infrastructure.
3. Battery-Checked Backups
- Examples: The Kore, BCN Core.
- These add logic to check if the battery is present and able to provide the required amount of power. If the battery cannot fulfil its obligations, the system will switch to providing whatever amount of power is available from the source.
- These offer a similar level of efficiency to their non battery checked counterparts but their complexity is slightly higher requiring a greater understanding of their core functions.
- Best suited as the modern replacement and upgrade for a standard Inline or Bypass battery backup. Defenders of a raid often claim their batteries get destroyed before their power sources. Advanced players will understand this is actually a flaw in base design so having the additional, built in redundancy is now highly recommended.
Power Waste and Backup Efficiency
All power cores result in some level of wasted electricity. Waste occurs whenever more power is generated than is actively being consumed or stored. The important consideration is not whether waste happens — it is inevitable — but rather where it happens and how much waste a player is willing to accept.
- Inline Backups waste power when batteries are fully charged. Any additional power that continues to be supplied, beyond what is needed to maintain a positive charge, serves no purpose. Minimize waste by not over producing.
- Bypass Backups waste power when batteries are fully charged but also can cause waste by supplying power to circuits that are turned off. Minimizing power waste relies on efficient use of Root Power.
- Battery-Checked Backups minimize waste more effectively when batteries are destroyed, but still waste power charging batteries that are full and on the conditional logic of circuits that are receiving powering.
- Direct Delivery is a clear example of visible waste. If a power source produces more power than the circuit requires, the excess is immediately lost because there is no storage.
There is no perfect system that avoids waste entirely. Efficient circuit design involves making informed choices. Players should focus on managing waste and deciding how much is acceptable in exchange for faster charging, longer uptime, or greater redundancy. Efficiency is about balance — not total elimination of loss.
Choosing the Right Backup
Selecting the appropriate backup style depends on the application, available resources, circuit design preferences and the player's level of knowledge. The following examples illustrate common use cases:
- Low-demand and fast decentralized deployment:
- Inline backups are suitable for circuits with minimal power requirements or where setup speed and simplicity are prioritized over long-term efficiency. What makes them ideal is they use very few components, so their crafting cost is cheap, and the number of wires players will need to connect is minimal. The battery checked Inline, The Kore, is particularly effective as it allows fallback to the main power source if the battery is destroyed.
- High power, centralized systems:
- Bypass Battery Backups are effective for managing circuits with large power requirements (300–1000rW+), especially when used with multiple batteries and power sources. The bypass design significantly reduces the amount of Root Power that needs to be generated to power both the circuits and charge the batteries. Requiring as little as 425rW to support 400rW of output using four large batteries, their efficiency grows the bigger they get as compared to Inline backups. While bypass backups such as the Nih Core can technically be used in decentralized designs, doing so is generally not practical or recommended. Both from an efficiency and design standpoint, their component complexity and setup requirements make them better suited for centralized systems where multiple circuits share power infrastructure
- Power-critical systems:
- Battery-Checked Cores such as The Kore or the BCN Core, provide greater reliability by ensuring some level of power is present, assuming there is still a power source. The battery must be present and able to support the load. If it cannot, either before or after activation, the system will fall back to primary power, regardless of the amount being produced. These configurations are well-suited for defensive systems like traps, turrets, SAM Sites, communication systems, or other essential setups where complete power failure must be avoided.
Ultimately, the most effective battery backup system is one that performs reliably during a power failure. Regardless of size, complexity and cost, the defining qualities of a successful backup system are consistency and dependability. The one that works, when the player needs it to work, is the best backup.
Power Type Composition
Understanding when to use a Bypass or Inline battery backup is one of the most important decisions a player can make when designing a power-efficient circuit. While both backup types exist to provide battery-stored electricity, the types of power being used in a circuit it supports, especially Root Power, Active Usage, Consumed Power, and Control Power, will help determine which one is better suited for the task.
Inline Backups: Leverage Active Usage
Inline Battery Backups use a battery as the circuit’s primary power source. Root Power is supplied to the battery, which then distributes power to the components. Inline backups only require enough power input to overcome the battery’s Active Usage. Understanding the 80% battery efficiency can result in major Root Power savings by not overproducing:
Power In = Active Usage ÷ 0.8
or
Power In = Active Usage × 1.25
✅ When to Use Inline Backups:
- Circuits with intermittent usage
- Circuits that contain many logic components
- Circuits where the majority of power does not create Active Usage
- Systems that can benefit from Control Power (logic run from a battery with no drain)
- Circuits that can recharge batteries during idle periods (e.g., auto-smelters)
⚠️ Drawbacks:
- Inline batteries must be continuously charged
- If underpowered, they will drain and shut down the system
- Not ideal for circuits with constant, high Active Usage
Bypass Backups: Reserve for Consumption
Bypass Battery Backups use the battery as an emergency source only. Root Power is sent directly to the circuit and only routes through the battery if Root Power fails. The battery is kept fully charged in the background but is not the main source of power.
✅ When to Use Bypass Backups:
- Circuits with high power consumption that are always on
- Any system where battery drain is unacceptable
- Any system where battery Active Usage can be leveraged
- Where Root Power is readily available and consistent
⚠️ Drawbacks:
- Must reserve full power for all components at all times
- Less efficient if the circuit doesn’t need to run continuously
- Requires a greater understanding of efficiency
Key Questions to Decide
- Does this circuit run 24/7, or only sometimes?
- 24/7 → Bypass
- Partial uptime → Inline
- Does the circuit contain a lot of logic components?
- Yes → Inline (or Control-only)
- No → Bypass
- Can the circuit be split into functional and logic parts?
- Yes → Use Hybrid or add Control Battery
- Is Root Power limited?
- Yes → Prioritize Bypass/Control and leverage Active Usage where possible
Summary
- Inline = best when logic dominates or systems run intermittently
- Bypass = best when uptime matters or systems are always active
- Don’t root combine batteries for Inline backups
- Separate functional power (Root/Consumed) from control logic (Control/Free)
- Use power efficiently and strategically to avoid over charging batteries
Batteries: Parallel vs Series
Understanding how batteries function in different configurations is critical for optimizing power systems. In real-life electrical systems, batteries can be wired in series or parallel, each offering different results in terms of power output and energy capacity. The same terminology can be applied to Rust, but with some differences due to the game’s simplified electrical mechanics.
Real-World Analogy
In real-world electrical systems, batteries have two terminals:
These terminals are used to connect batteries in either series or parallel, depending on the desired outcome.
Battery performance is measured using:
- V (Volts): Indicates power output (pressure).
- Ah (Amp hours): Indicates energy capacity (storage).
🔗 Series Wiring (More Power, Same Runtime)
- Batteries are connected by wiring the positive terminal (+) of one battery to the negative terminal (-) of the next.
- The remaining negative (-) and positive (+) terminals are used for the circuit’s input/output.
- This configuration adds voltage while keeping the capacity the same.
- Example: Two 6V 10Ah batteries in series = 12V, 10Ah
- Purpose: Used when a system needs more power but does not require extended runtime.
🔗 Parallel Wiring (Same Power, More Runtime)
- Batteries are connected by joining all positive terminals together and all negative terminals together.
- This configuration keeps the voltage constant while adding capacity.
- Example: Two 6V 10Ah batteries in parallel = 6V, 20Ah
- Purpose: Used to extend the runtime of a system without increasing power output.
Translating to Rust
In Rust, battery behavior is streamlined compared to real-life electronics. There are no positive or negative terminals, and there’s no concept of voltage and polarity. However, the concepts of power and capacity still exist, just in different terms. Instead, everything revolves around two values:
- Rust Watts (rW): This represents the power output, similar to voltage (V) in real life. It’s the amount of energy delivered to components.
- Rust Watt Minutes (rWm): This represents energy storage capacity, similar to Amp-hours (Ah). It shows the total energy a battery is holding.
Each battery in Rust has only two terminals:
- Power In: Used to charge the battery.
- Power Out: Used to supply power to a circuit.
There are no positive or negative terminals, voltage and Amp-hours do not exist, but the two core functions of batteries are still the same, powering circuits and storing energy. So while Rust doesn’t let players literally wire batteries in parallel or series, they can mimic those configurations in terms of outcome by connecting their outputs with 1 of 2 components:
🔗 Series Wiring in Rust (More Power, Same Capacity)
- Component Used: Root Combiner
- Effect: Increases power output, maintains same capacity.
- Example: Two Large Batteries = 200rW output, 24000rWm capacity
🔗 Parallel Wiring in Rust (Same Power, More Capacity)
- Component Used: OR Switch
- Effect: Keeps power output the same, doubles capacity.
- Example: Two Large Batteries = 100rW output, 48000rWm capacity
So while players can’t physically “wire” batteries in series or parallel, the game still gives them the flexibility to design around the same trade-offs. Want more power all at once? Go series with a Root Combiner. Want to stretch your batteries to last longer? Design in parallel with the OR Switch. Want to get the most amount of power all at once and increase the battery life? Combine the two and make a hybrid.
Whether players have wired the batteries outputs into a serial or parallel configuration, they are joined in a way that leaves only a single output connection, just like any battery. The same must be achieved with the battery inputs and to do that, a charging solution is needed.
Applying Series in Rust
To wire two Large Batteries in series in Rust, connect the outputs of both batteries to a Root Combiner. This will merge their outputs into a single line capable of providing 200rW, double the output of one battery, while maintaining the same 24000rWm capacity.
Need more than 200rW? Keep adding:
- More Batteries
- More Root Combiners
Charging & Performance Considerations
All batteries wired in series should be of the same size. This ensures that the batteries will supply the full amount of power, the entire time they are draining. That said, intentionally using mismatched sizes can be done, as long as players are aware that the smaller batteries will drain first.
All batteries wired in series should be charged at the same rate to prevent imbalance. The Splitter will help keep power levels equal across all batteries. If one battery drains completely before the others, a portion of the circuit will lose power. For example, if there are 3 batteries in series and 1 of them empties, 33% of the circuit will go offline because one third of the power is gone.
If only 200rW is needed but there are 300rW worth of batteries, 1 of the batteries is redundant, meaning 1 battery can be destroyed and the main circuit will continue to function. This is a way to create redundancy but it's expensive and there are better and more efficient ways, such as Secondary Batteries.
Series Wiring in Inline vs Bypass
Batteries wired in series can be installed into both Inline and Bypass battery backups, but their performance differs significantly.
- To install batteries in series into a BCN Core, players will need to connect the Splitters to the OR Switch that normally powers a single battery, and the Root Combiner from the batteries to the Electrical Branch that feeds power to the final OR Switch.
- Since Bypass systems power circuits with Root Power directly, bypassing the batteries most of the time, Active Usage consideration is irrelevant.
- The reason the batteries are wired in series to begin with is to provide more Available Power then 1 battery is able to. Because of that, it is reasonable to assume that the Active Usage on the batteries will be maxed out and we accept the fact that they will only run for a minimum of 4 hours.
- A setup like the BCN Core using four Large Batteries in series can supply 399rW for a minimum of 4 hours, assuming all Root Power has been removed.
- If there is still some Root Power but is no longer able to meet the required amount, the batteries take over, and any remaining Root Power is redirected to the battery bank to slow the discharge rate and get longer than 4 hours of backup time.
- The minimum Root Power requirement to keep this running is about 440rW, making it much more manageable than the Inline equivalent.
- Adding additional large batteries increases available power in 100rW chunks while only increasing power production by roughly 110rW (100 for the new output, 10 to maintain charge).
Efficiency Notes
Series wiring of batteries is only recommended in Bypass Backups because they remove taking Active Usage into consideration
- Bypassing Active Usage allows players to focus on efficient consumption of Root Power. Root Power can always be converted into Stored Power to leverage Active Usage later on with intelligent circuit design.
- But, if 200rW of battery power is available, circuit design should aim to use all 200rW, rather than leaving some power underutilized.
- If a circuit only needs 120rW, it might be more efficient to cut the circuit in half. Powering it from 2 independent power cores. At the very least, it will increase the runtime of the battery backup.
If a player chooses to use an Inline Backup, combining batteries to get 200rW to power a circuit that only generates 120 Active Usage, splitting the circuit into 2 independent systems will always be a more efficient option.
- Combining them to get 200rW is going to apply 100 Active Usage to both batteries and needs 250rW to maintain a positive charge.
- Splitting the circuit lets each battery take on 60 Active Usage, making the total power needed only 150rW. Simply by not combining the batteries, players will save roughly 100rW of power production. That's an entire Wind Turbine if it's built on the 8th floor.
- Never use batteries wired in series in an Inline Backup. Separate circuits into groups of 100rW or less.
Be aware: The Root Combiner has a maximum depth of 16 components from itself to the main power source. This theoretical maximum is covered in the Max Depth section under Power Distribution.
Applying Parallel in Rust
To wire two Large Batteries in parallel in Rust, simply connect each battery’s output to an OR Switch. This will merge the battery's outputs into a single line. The OR Switch prioritizes Input A over Input B or whichever has the higher power level and ensures only one battery is active at a time.
How It Works:
- While Battery 1 (Input A) has charge, it will fully power the circuit.
- Once Battery 1 depletes, the OR Switch automatically switches to Battery 2 (Input B) with no interruption to the circuit.
- This method effectively doubles total capacity allowing for twice the runtime, while maintaining the same output limit of 100rW.
Adding more batteries is straightforward: just chain more OR Switches.
- For 3 batteries:
- 2 batteries feed OR Switch 1.
- The output of OR Switch 1 and the next battery feed OR Switch 2.
- The final output goes to the circuit.
- For 4+ batteries: add a third OR Switch and repeat the pattern.
Charging & Performance Considerations
Parallel battery banks must be charged differently than series banks. In series, batteries should be charged simultaneously with a Splitter. In parallel, while a splitter can be used and is in some edge cases, it is highly typically inefficient. Instead, batteries should be charged sequentially, or one at a time.
To charge batteries sequentially, a Sequential Power Distributor is used. This basic charging system uses Memory Cells and the battery’s Fully Charged output to rotate charging between batteries:
- The Memory Cell starts by sending power to Battery 1 from its Inverted Output.
- When Battery 1 is fully charged, its Fully Charged output goes to Set on the Memory Cell. This will flip the Memory Cells outputs to begin charging Battery 2.
- A Control Battery constantly provides power to Reset on the Memory Cell, ensuring the system defaults back to the first battery or any battery that starts to drain.
- The number of Memory Cells needed is always 1 less than the number of batteries.
- 4 Large Batteries in parallel = 3 Memory Cells → results in 96,000rWm capacity (16 hours runtime at 100rW).
While this basic charging solution works, it assumes 2 things. The output power is 100rW, not less, and that no battery will be destroyed. If less than 100rW is needed or there is a concern that a battery might be destroyed, the charging solution needs some design changes.
Advanced Charging
If a circuit needs less than 100rW, or if there is a risk of a battery being destroyed (such as on a PvP server), the charging circuit requires some additional design features:
- If less than 100rW is needed, attach an Electrical Branch to the output of the battery and Branch Out the limited amount of power to the OR Switch. This ensures the output from the batteries will match the circuit’s demand.
- If there is a concern that a battery might get destroyed, a more intelligent design is needed.
- Attach an Electrical Branch to the output of the battery and Branch Out up to all but 1rW to the OR Switch.
- Power Out will send power through a Blocker to Set on the Memory Cell. This will tell the system if the battery is present and needs to be charged.
- When the battery is full, its Fully Charged output will go to Block Passthrough on the Blocker allowing the Memory Cell to flip outputs and charge another battery, or pass power to another Memory Cell.
- Reset on the Memory Cells get constant power from a Control Battery to constantly try and push power to the next battery in line. This is only achieved if a battery is full or missing.
- The last battery in parallel will get its power from the Inverted Output from the last Memory Cell. It doesn't need a blocker but does need an Electrical Branch set to the same value as the rest.
- This kind of intelligent design does require 1rW from each battery.
This setup allows for:
- Safe automatic charging
- Dynamic prioritization
- Resilient operation even if a battery is destroyed
Parallel in Inline vs Bypass Systems
Parallel wiring is an excellent choice to extend the runtime of Inline backups:
- The first battery that gets charged will be the battery that will constantly be actively draining.
- The power given to this system will need to be high enough to overcome the batteries Active Usage just like any Inline Backup.
- Once the first battery is fully charged, the charging system will begin charging the next battery. However, because the first battery is still the one connected to supply the circuit, it will continue to discharge. This causes the system to alternate between topping off the first battery and briefly charging the second, resulting in the Memory Cell flipping back and forth.
- By merely switching which battery connects to which OR Switch input, players have full control over which battery drains first.
- A common practice is to reverse the order the wires are connected to the OR Switch. Instead of left to right, wire them right to left. The bottom battery to the first input and the top battery to the last input on the OR Switches. At some point the battery that is draining and the one that is charging will be the same battery. Once it fills up and becomes full, the system will start charging the next battery and the Active Usage will be transferred to it.
- This will help prevent the system from constantly flipping between batteries while in use.
- Once there is no Root Power supply, the batteries will drain one at a time, extending runtime.
- In the event a battery is destroyed, the next battery takes over seamlessly and any incoming power is automatically transferred to it. It would take destroying every battery before the inline power core would no longer be able to support the desired load.
- This allows for very efficient use of Root Power by charging as many batteries as a player wants.
Bypass Backups
Parallel wiring also works in Bypass systems, but with limitations:
- Since Bypass systems power circuits with Root Power directly (bypassing the batteries most of the time), Active Usage consideration is irrelevant.
- A single parallel battery bank in a BCN Core is treated no differently than if there was only a single battery in terms of the amount of Root Power needed.
- In a BCN Core, 1rW is needed from the battery bank to let it know batteries are still present. The intelligent design of the distributor also needs 1rW from each battery. This means using Large Batteries, only a max of 98rW is usable.
- When Root Power is not enough to support the circuit, the battery bank will take over but is limited to a maximum output of only 98rW using Large Batteries.
- If Root Power fails, parallel batteries take over seamlessly, one at a time extending runtime.
- The more batteries in parallel, the longer the backup time will last for.
- Bypass Backups are typically used for circuits that need more than 100rW. If more power and a larger capacity is needed, a hybrid solution (series + parallel) is required.
Efficiency Considerations
Parallel setups excel in both Inline and Bypass backup. No matter how many batteries are wired together, the entire bank of batteries is treated no differently than a single battery.
- Only one battery discharges at a time.
- Only one battery charges at a time.
- No additional Root Power is required to charge as many batteries as a player chooses.
- Uptime is greatly extended, ideal for critical circuits that must always stay online.
Bottom Line:
The OR Switch is a highly effective way to parallel batteries, it's just the charging solutions that adds a layer of complexity. When uptime is more important than raw power, Parallel wins. For larger circuits needing more than 100rW, players should explore Series or Hybrid configurations.
Applying Hybrid (Series+Parallel) in Rust
Hybrid battery wiring combines the power output advantages of Series with the extended capacity of Parallel. In Rust, this is possible using 2 different methods.
- Method 1: Parallel-Series Hybrid
- Method 2: Series-Parallel Hybrid
Both methods allow players to create extremely powerful, high-capacity battery systems, ideal for large, high-demand circuits that require extended backup run times. Although the outcome of each method is the same, their design philosophy and implantation and limitations differ.
- With Method 1, the only time it will not output 200 is when all of the batteries in 1 bank of parallel batteries are depleted or destroyed.
- If a battery is depleted or destroyed, the next battery in the bank takes over.
- Only once all of the batteries in a single bank are depleted or destroyed, will the output be limited to 100.
- Do not place all batteries in 1 bank in the same physical location.
- With Method 2, the only time it will not output 200 is when 1 battery is depleted or destroyed in each of the series wired battery banks.
- If a battery is depleted or destroyed, the next bank of series batteries will take over.
- Only once 1 battery in all the banks are depleted or destroyed, will the output be limited to 100.
- While still not recommended, it would be more acceptable to keep all batteries in 1 bank in the same location.
- Method 1 has a higher component count compared to Method 2.
- Method 1 relies on a bug/feature of the Splitter being allowed to connect to the Root Combiner.
- Method 1 will be limited in size due to Max Depth before Method 2.
- Method 1 as shown has 3 components before the Root Combiner.
- Method 2 as shown has 1 component before the Root Combiner.
- Therefore Method 2 is able to be designed to handle larger loads.
Parallel-Series Hybrid
How It Works:
- Build Parallel Battery Banks first:
- Batteries are connected to OR Switches allowing one battery to be active at a time.
- Input A is prioritized over Input B when power levels are the same, or whichever is higher.
- Only the first battery in each Parallel Bank will carry 100% of the circuit's load and Active Usage.
- If an Electrical Branch is used to limit a battery’s Available Power, it will not limit the Active Usage the battery could register.
- The remaining batteries in each Parallel Bank will remain idle until the battery before is depleted or destroyed.
- Each bank is treated as a single high capacity battery.
- For example, 3 Large Batteries in Parallel = 100rW output, 72000rWm capacity.
- Then wire these banks in Series using Root Combiners:
- Each bank of parallel batteries needs a Splitter to connect to the Root Combiner.
- Each bank of high capacity batteries is combined to increase the available power.
- Only 1 battery from each bank is active at a time.
- Each bank of batteries needs to receive an equal charge to prevent 1 bank from depleting before the others.
- This is functionally identical to Series behavior, but now multiplied by the number of batteries inside of each Parallel bank.
- For example, 3 Parallel Banks in Series = 300rW output, 72000rWm capacity.
Charging Considerations
Since this hybrid configuration is ultimately a combination of parallel and series wiring, charging the system requires two layers:
1️⃣ Charging the Parallel Banks:
- Each Parallel Bank needs its own Sequential Power Distributor (SPD).
- Inside each bank:
- Only one battery is charged at a time.
- Once a battery is full, the SPD ensures cycling to the next battery.
2️⃣ Charging All Banks (Series Layer):
- The Parallel Banks (now treated like single batteries) are then charged evenly using a Splitter:
- The Splitter evenly divides input power to each SPD (one per Parallel Bank).
- This balances charging across the entire hybrid stack.
Inline Backups (Poor Fit)
Functionality
- In an Inline system like The Kore pictured, circuits are directly supported by the battery. This will result in the first battery in all Parallel Banks supporting the circuit's load. This results in multiple batteries simultaneously draining at the same rate, forcing massive amounts of Root Power to be produced to keep the system functioning.
- If the Active Usage being generated by the circuit is greater than 100, 1 battery in each bank will drain at their maximum rate. Each active battery will require 125rW power input of Root Power production just to maintain its level of charge. More Root Power is needed if charging is desired, and it always is.
- Each parallel bank is designed to charge the top battery first but use the bottom battery first. At some point the battery that is draining and the one that is charging will be the same battery. Once it fills up and becomes full, the system will start charging the next battery and the Active Usage will be transferred to it. This will help prevent the system from constantly flipping between batteries while in use.
- In the event a battery is destroyed, the next battery in the Parallel Bank takes over seamlessly and any incoming power is automatically transferred to it. It would take destroying every battery in 1 of the banks before the inline power core would no longer be able to support the desired load.
- Conclusion: Do not use series batteries in Inline Backups. The result is extremely poor efficiency, far worse than running individual batteries or a bypass backup and leveraging Active Usage.
Bypass Backups (Ideal Fit)
Functionality
- In Bypass Backups (such as a BCN Core), the batteries are only called on when Root Power fails or falls below a set level. When enough Root Power is available, the batteries are charged with the excess power that is being produced. The batteries remain idle and no Active Usage is applied to them. This is the default state a Bypass Backup should be in 80+% of the time making Active Usage considerations irrelevant.
- When Root Power levels get too low, the hybrid battery bank seamlessly takes over for an extended runtime thanks to the large Parallel capacity. Think of each Parallel Bank as just a 3x over-sized battery. At the same time as battery power taking over, the Root Power that is too low to support the circuit is redirected towards the batteries slowing their drain.
- Each parallel bank is designed to charge the top battery first before moving on to the next. When Root Power falls too low, the top battery in each bank will begin to support the circuit and be given an Active Usage to start draining. The redirected power now gets forwarded to the batteries which are actively draining to slow their drain and further extend their runtime.
- In the event a battery is destroyed, the next battery in the Parallel Bank takes over seamlessly and any incoming power is automatically transferred to it. It would take destroying every battery in 1 of the banks before the battery backup would no longer be able to support the desired load.
- The amount of Root Power that needs to be produced increases by approximately 110rW per 100rW of battery output. 100rW to cover the potential load and 10rW to charge the battery.
- Conclusion: It would be an efficient option in Bypass Backups, but due to Max Depth limitations, it scales very poorly.
Series-Parallel Hybrid
How It Works:
- Build Series Battery Banks first:
- Batteries are connected to Root Combiners allowing for greater amounts of Available Power.
- Each battery in the bank will need to be charged equally to prevent 1 battery from depleting before the other(s).
- Only 1 Series Bank carries the circuit's load and Active Usage at a time. This means all the batteries in the bank will be active at this time.
- Each bank is treated as a single battery with a larger amount of available power.
- For example, 3 Large Batteries in Series = 300rW output, 24000rWm capacity.
- Then wire these banks in Parallel using OR Switches:
- Each bank of series wired batteries are connected to OR Switches to control which bank is active. Input A is prioritized over Input B when power levels are the same, or whichever is higher.
- Only 1 bank is active at a time, but all the batteries in that bank are active making it functionally identical to Series behavior, but now multiplied by the number of paralleled banks.
- An Electrical Branch can be used between the Root Combiner and OR Switch if less power is needed. Even if an Electrical Branch is used to limit a bank's Available Power, it will not limit the Active Usage the bank could register.
- Each bank of batteries will be charged one after another.
- The remaining Series banks will remain idle until the battery bank before is depleted or destroyed.
- For example, 3 Series Banks in Parallel = 300rW output, 72000rWm capacity.
Charging & Performance Considerations
Since this hybrid configuration is ultimately a combination of parallel and series wiring, charging the system requires two layers:
1️⃣ Charging the Series Banks:
- Each series bank needs its own Dynamic-Bus for evenly charging the batteries.
- Inside each bank:
- The Splitter is used to evenly divide power to each battery.
- All batteries get charged evenly and at the same time.
2️⃣ Charging All Banks (Parallel Layer):
- The Series Banks (now treated like single batteries) are then charged with a Sequential Power Distributor (SPD):
- The SPD will charge one bank of batteries at a time.
- When one bank is full, it will transfer power to the next bank to charge it.
Inline Backups (Poor Fit)
Functionality
- In an Inline system like The Kore pictured, circuits are directly supported by the battery. This will result in the first bank of series batteries supporting the circuit's load. This results in multiple batteries simultaneously draining at the same rate, forcing massive amounts of Root Power to be produced to keep the system functioning.
- If the Active Usage being generated by the circuit is greater than 100, all of the batteries in the active bank will drain at their maximum rate. Each battery will require 125rW power input of Root Power production just to maintain their level of charge. More Root Power is needed if charging is desired, and it always is.
- Each series bank is designed to be charged left to right. Each series bank is designed to be drained right to left. At some point the battery bank that is draining and the one that is charging will be the same one. Once it fills up and becomes full, the system will start charging the next bank and the Active Usage will be transferred over to it. This will help prevent the system from constantly flipping between battery banks while in use.
- In the event a battery is destroyed, that bank will no longer need the required output and the next battery bank takes over seamlessly and any incoming power is automatically transferred to it. It would take destroying 1 battery in every bank before the inline power core would no longer be able to support the desired load.
- Conclusion: Do not use series batteries in Inline Backups. The result is extremely poor efficiency, far worse than running individual batteries or a bypass backup and leveraging Active Usage.
Bypass Backups (Ideal Fit)
Functionality
- In Bypass Backups (such as a BCN Core), the batteries are only called on when Root Power fails or falls below a set level. When enough Root Power is available, the batteries are charged with the excess power that is being produced. The batteries remain idle and no Active Usage is applied to them. This is the default state a Bypass Backup should be in 80+% of the time making Active Usage considerations irrelevant.
- When Root Power levels get too low, the hybrid battery bank seamlessly takes over for an extended runtime thanks to the large Parallel capacity. Think of each Series Bank as just a single large battery but with 3x more Available Power. At the same time as battery power taking over, the Root Power that is too low to support the circuit is redirected towards the active batteries slowing their drain.
- Each series bank is designed to be charged left to right. When Root Power falls too low, the battery bank on the left will begin to support the circuit and be given an Active Usage to start draining. The redirected power now gets forwarded to the bank which is actively draining to slow its drain and further extend its runtime.
- In the event a battery is destroyed, that Series Bank will no longer meet the required output and the next series battery bank seamlessly takes over and any incoming power is automatically transferred to it. It would take destroying 1 battery in every bank before the inline power core would no longer be able to support the desired load.
- The amount of Root Power that needs to be produced increases by approximately 110rW per 100rW of battery output. 100rW to cover the potential load and 10rW to charge the battery.
- Conclusion: It would be an efficient option in Bypass Backups, but due to Max Depth limitations, it scales very poorly.
Summary
When it comes to extending the runtimes of over-sized battery banks, it can be done, but now it's up to the player to decide what method works best for them. What remains a constant is:
- Inline Hybrid: Often requires overproduction of power, not efficiently scalable and wasteful at scale.
- Bypass Hybrid: Efficient, scalable, and matches the design purpose of high-output, long-runtime backups.
Design Tip: Intelligent circuit design is more efficient than simply stacking batteries. Many players overbuild power cores and battery backups unnecessarily. More power is not always more better. Careful circuit planning, reducing power requirements and proper use of power types will always outperform raw power and battery volume.
Types of Battery Backups
There are several different ways a battery backup can be achieved. The ones listed here are merely the most commonly talked about or used.
Direct Delivery
Direct Delivery refers to a circuit where the power source is connected directly to the components without the use of a battery. This approach provides power in real time and uses no backup system. If the power source is destroyed or stops producing electricity for any reason, the connected circuit will immediately go offline.
This method has been known to be used in the early stages of base development. It provides a quick and effective way to get essential systems online before players have a battery or additional components. Common examples include setting up auto turrets for defense or powering water pumps to start a berry farm.
While Direct Delivery provides a fast early-game advantage, it is not intended for long-term use. As a base grows and power demands increase, introducing batteries for storage and redundancy becomes critical for maintaining uptime, protecting vital systems and increasing efficiency.
Despite its simplicity, this method is rarely used in practice. Many players assume that a battery is required to complete a circuit and often overlook Direct Delivery as a viable option. Some players may attempt to brute force Direct Delivery by overproducing power with additional turbines to compensate for times of low power production, but this approach is highly inefficient and never recommended.
Characteristics of Direct Delivery
- Extremely easy to wire
- Uses minimal components
- Allows quick deployment of essential systems
- If the power source fails, the circuit will instantly shut off
- No redundancy or backup
- Not recommended for critical systems or long-term use
- Often misunderstood or overlooked as a valid early-game tactic
Additional Notes
- This is not a battery backup system, but it is included here for comparison.
- For more resilient and scalable solutions, refer to the remaining sections in the Battery Backup chapter.
Inline Backup
About the Name
The Inline Backup derives its name from the location where it exists within the circuit, in line
between the source and destination.
It's a power delivery method where electricity from a power source is routed through a battery before reaching any connected components. This is the most common and straightforward way to implement a battery backup in Rust. It offers simplicity, reliability, and fast setup, especially in early and mid-game environments.
Inline backups are most effective when fast deployment and minimal setup are prioritized. Their simplicity makes
✅ Benefits
- Simple to wire and build with minimal components.
- Fast to deploy, especially during early games.
- Reliable for low-power circuits (<100rW) when managing their discharge.
- No power flicker due to the battery always being active.
- Ideal for easy decentralized circuit design when ignoring long term efficiency loss.
❌ Limitations
- Always subject to 80% efficiency loss when supplying power, even under normal operating conditions.
- Power waste increases with each additional inline battery, making this method inefficient in large-scale systems unless properly managed and controlled.
- Requires understanding of Active Usage to prevent undercharging or overproducing power.
- Combining batteries in inline setups is inefficient unless used for high burst output, not constant load.
- Provides no built-in redundancy if the battery is destroyed.
How It Works
When a power source is directly connected to a battery:
- 100% of the power is used to charge the battery.
- Batteries are 80% efficient, meaning more power must be supplied than is being consumed.
- Once a battery is fully charged, any input beyond the required maintenance level becomes unused power (waste).
When the battery is connected to a circuit:
- The battery makes power continuously available but only discharges when components draw power.
- If the power source stops producing electricity (due to wind speed, nightfall, or destruction), the battery continues powering the circuit until it is empty or destroyed.
- No switching logic is required, so there is no risk of power flicker, which refers to brief circuit shutdowns when power switches from one source to another.
Calculating Power Needs
To determine how much input power is required to sustain a battery without draining:
Input Power = Active Usage ÷ 0.8 or Input Power = Active Usage × 1.25
For example, if a Large Battery shows 100 Active Usage, then:
100 ÷ 0.8 = 125rW
125rW is the amount required to keep the battery in a neutral state where it neither drains or charges. However, this is not sufficient to build usable capacity. If the battery has just been placed or is in any way partially discharged, it will not fill unless it receives more than the neutral amount.
Providing only a small amount of excess power (e.g., 126rW) will result in extremely slow charging, too slow to be practical within a single wipe. Supplying more (e.g., 150rW) speeds up charging considerably, but also leads to more power being wasted once the battery is full unless the extra is redirected or removed.
- It is recommended to charge batteries to at least 3000rWm before connecting them to active circuits.
- Players using Wind Turbines, Solar Panels or Small Generators should expect downtime periods and ensure batteries are charged enough to survive through low production cycles and recharge after.
This balance is essential: Players must weigh charging speed against over-production, especially in inline systems where the power demand is constant. Early overproduction is acceptable if it ensures batteries reach capacity quickly and can later be scaled back or redistributed.
Fun Fact: Providing only 1rW to a Large Battery results in an estimated 34 real days, or 816 in game days to fully charge.
Estimating Charge Time
To estimate how long it will take to fully charge an empty battery, use the following formula:
Charge Time (minutes) = Power Capacity ÷ (Input Power × 0.8)
- Power Capacity:
- Small Battery: 400rWm
- Medium Battery: 9,000rWm
- Large Battery: 24,000rWm
- Input Power: The amount of power being supplied to the battery (in rW)
- 0.8: The battery's efficiency (80%)
Example: Small Battery (Idle)
- Input Power: 25rW
- Power Capacity: 400rWm
Charge Time = Power Capacity ÷ (Input Power × 0.8)
Charge Time = 400rWm ÷ (25rW × 0.8)
Charge Time = 400rWm ÷ (20rWm)
Charge Time = 20 minutes
The Small Battery will fully charge in 20 minutes if it receives 25rW continuously and has no output load.
Charging While In Use
If the battery is powering a circuit while charging, subtract the power required to support the current load (Active Usage ÷ 0.8) from the input power. The remainder is the surplus, which determines how fast the battery will charge.
Surplus Power = Input Power - (Active Usage ÷ 0.8)
Charge Time = Capacity ÷ (Surplus Power × 0.8)
- Capacity: (Power Capacity - Current Capacity)
- Current Capacity: The rWm value shown in a battery’s UI
- Power Capacity:
- Small Battery: 400rWm
- Medium Battery: 9,000rWm
- Large Battery: 24,000rWm
- Input Power: The amount of power being supplied to the battery (in rW)
- Active Usage: The value shown in a battery’s UI
- 0.8: The battery's efficiency (80%)
Example: Large Battery (Active Load)
- Input Power: 130rW
- Active Usage: 100
- Current Capacity: 3200rWm
Step 1: Calculate how much power is available for charging.
Surplus Power = Input Power - (Active Usage ÷ 0.8)
Surplus Power = 130rW - (100 ÷ 0.8)
Surplus Power = 130rW - 125rW
Surplus Power = 5rW of power available for charging.
Step 2: Calculate the remaining charge time until full.
Charge Time = Capacity ÷ (Surplus Power × 0.8)
Charge Time = (Power Capacity - Current Capacity) ÷ (Surplus Power × 0.8)
Charge Time = (24000rWm - 3200rWm) ÷ (5rW × 0.8)
Charge Time = (20,800rWm) ÷ (4rW)
Charge Time = 5200 minutes
Charge Time = 5200 minutes ÷ 60 minutes
Charge Time = 86.6 hours
With only 5rW of surplus power, it would take 3 days, 14 hours and 40 minutes of real-time to fully charge the Large Battery with a current capacity of 3200rWm.
Step 3(Optional): To figure out how much time a given capacity will run for, with no input power and outputting a specific amount of power, we use the following equations:
Seconds = (Current Capacity ÷ Active Usage = Minutes) × 60
Minutes = Current Capacity ÷ Active Usage
Hours = (Current Capacity ÷ Active Usage = Minutes) ÷ 60
The Kore
About the Name
The Kore is named after its creator, Korrektor, a highly respected member of the Rust community for his contributions to advanced circuit design. The name is a play on his name and the word "core," reflecting its importance as a foundational upgrade to traditional inline backup systems. (I'd personally like to rename it to the KorrektCore so it can still be a play on his name, but also the words correct and core, so it would be pronounced as the correct core)
The Kore is an upgraded Inline Backup and introduces battery health awareness. It retains all the speed and simplicity of a traditional inline design, while adding a crucial failover feature. If the battery is destroyed, the system automatically switches to the main power source, ensuring that the circuit remains powered.
Precisely because of its simplicity, players should upgrade their important or critical Inline Backups to a Kore as soon as they are able. The setup is easy, components are minimal, and it significantly improves resilience.
✅ Benefits
- Simple to build with minimal components
- Fast and reliable for decentralized circuit setups
- No flicker during normal operation
- Only switches if the battery is destroyed
- Maintains circuit uptime even if the battery is removed
- More resilient than a standard Inline backup
❌ Limitations
- Still subject to 80% battery efficiency loss when active
- Power waste increases with each additional Kore unit used
- Requires understanding of Active Usage for proper power budgeting
- Combining batteries in inline setups is inefficient unless used for high burst output, not constant load
- Only 99 of 100rW from a Large Battery is available to the circuit, due to 1rW being used to maintain SET on the Memory Cell
How It Works
The Kore follows the core structure of a traditional Inline Backup: The battery powers the circuit full-time, while the main power source charges the battery. The key upgrade is its ability to detect when the battery is destroyed and immediately switch over to the power source, without the need for manual interaction or external switching.
This is accomplished using a Memory Cell, a Small Battery, an Electrical Branch and an OR Switch, making it simple, efficient, and highly reliable. The Small Battery is used as a representation of Control Power, and is used to RESET the Memory Cell.
Power Flow Logic
- Power Source → Memory Cell
- Power from the main source (e.g., Wind Turbine) enters the Memory Cell through its main input.
- Inverted Output → OR Switch → Circuit
- The left output of the Memory Cell (Inverted Output) connects to an OR Switch that feeds into the circuit. This becomes the fallback power path if the battery is destroyed.
- Normal Output → Large Battery
- The right output (Output) sends power directly into a Large Battery, keeping it charged.
- Battery Output → Electrical Branch → Memory Set + OR Switch
- Power from the battery is sent into an Electrical Branch.
- 1rW is branched off to the SET input of the Memory Cell. This tells the system the battery is present.
- The rest of the power is sent to the OR Switch, powering the circuit.
- This means only 99 of the 100rW from a Large Battery is available for use.
- Small Battery → RESET
- A Small Battery is connected to the RESET input of the Memory Cell. This is used to flip the system when the battery is no longer present.
- Side ports do not contribute to Active Usage, so this battery never drains, and does not need to be recharged.
As long as the battery is functioning, SET receives power, and the Memory Cell continues to route power through its normal output. If the battery is destroyed, SET loses power while RESET continues to receive it. This causes the Memory Cell to flip, sending power through the Inverted Output and allowing the main power source to directly power the circuit.
This fallback ensures that some power, however limited, reaches the circuit instead of a complete loss.
Calculating Power Needs
To determine how much input power is required to sustain a battery without draining:
Input Power = Active Usage ÷ 0.8
For example, if a Large Battery shows 99 Active Usage, then:
99 ÷ 0.8 = 124rW
124rW is the amount required to keep the battery in a neutral state where it neither drains or charges. However, this is not sufficient to build usable capacity. If the battery has just been placed or is partially discharged, it will not fill unless it receives more than the neutral amount.
Providing only a small amount of excess power (e.g., 125rW) will result in extremely slow charging, too slow to be practical within a single wipe. Supplying more (e.g., 150rW) speeds up charging considerably, but also leads to more power being wasted once the battery is full unless the extra is redirected or removed.
- It is recommended to charge batteries to at least 3000rWm before connecting them to active circuits.
- Players using Wind Turbines, Solar Panels or Small Generators should expect downtime periods and ensure batteries are charged enough to survive these low production cycles and recharge after.
This balance is essential: Players must weigh charging speed against over-production, especially in inline systems where the power demand is constant. Early overproduction is acceptable if it ensures batteries reach capacity quickly and can later be scaled back or redistributed.
Fun Fact: Providing only 1rW to a Large Battery results in an estimated 34 real days, or 816 in game days to fully charge.
Estimating Charge Time
To estimate how long it will take to fully charge an empty battery, use the following formula:
Charge Time (minutes) = Power Capacity ÷ (Input Power × 0.8)
- Power Capacity:
- Small Battery: 400rWm
- Medium Battery: 9,000rWm
- Large Battery: 24,000rWm
- Input Power: The amount of power being supplied to the battery (in rW)
- 0.8: The battery's efficiency (80%)
Example: Medium Battery (Idle)
- Input Power: 80rW
- Power Capacity: 9000rWm
Charge Time = Power Capacity ÷ (Input Power × 0.8)
Charge Time = 9000rWm ÷ (80rW × 0.8)
Charge Time = 9000rWm ÷ (64rWm)
Charge Time = 141 minutes, or 2 hours and 21 minutes.
The Medium Battery will fully charge in 2 hours and 21 minutes if it receives 80rW continuously and has no output load.
Charging While In Use
If the battery is powering a circuit while charging, subtract the power required to support the current load (Active Usage ÷ 0.8) from the input power. The remainder is the surplus, which determines how fast the battery will charge.
Surplus Power = Input Power - (Active Usage ÷ 0.8)
Charge Time = Capacity ÷ (Surplus Power × 0.8)
- Capacity: Power Capacity - Current Capacity
- Current Capacity: The rWm value shown in a battery’s UI
- Power Capacity:
- Small Battery: 400rWm
- Medium Battery: 9,000rWm
- Large Battery: 24,000rWm
- Input Power: The amount of power being supplied to the battery (in rW)
- Active Usage: The value shown in a battery’s UI
- 0.8: The battery's efficiency (80%)
Example: Large Battery (Active Load)
- Input Power: 130rW
- Active Usage: 99
- Current Capacity: 500rWm
Step 1: Calculate how much power is available for charging.
Surplus Power = Input Power - (Active Usage ÷ 0.8)
= 130rW - (99 ÷ 0.8)
= 130rW - 124rW
Surplus Power = 6rW of power available for charging.
Step 2: Calculate the remaining charge time until full.
Charge Time = Capacity ÷ (Surplus Power × 0.8)
= (Power Capacity - Current Capacity) ÷ (Surplus Power × 0.8)
= (24000rWm - 500rWm) ÷ (6rW × 0.8)
= (23,500rWm) ÷ (5rW)
Charge Time = 4700 minutes
= 4700 minutes ÷ 60 minutes
Charge Time = 78.3 hours
With only 6rW of surplus power, it would take 3 days, 6 hours, 20 minutes of real-time to fully charge the Large Battery with an Active Usage of 99 and a current capacity of 500rWm.
Step 3(Optional): To figure out how much time a given capacity will run for, with no input power and outputting a specific amount of power, we use the following equations:
Seconds = (Current Capacity ÷ Active Usage = Minutes) × 60
Minutes = Current Capacity ÷ Active Usage
Hours = (Current Capacity ÷ Active Usage = Minutes) ÷ 60
Dual-Cell
About the Name
The Dual-Cell Battery Backup was optimized and popularized by Korrektor. Its name reflects a deliberate design constraint: it is engineered to operate with exactly two batteries, not fewer, not more.
This is not an arbitrary limitation. Two batteries allow the system to alternate load and recovery in a controlled way that single-battery or traditional parallel systems cannot replicate efficiently.
The purpose of the Dual-Cell backup is to extend runtime and improve survivability using a single primary power source, while avoiding the inefficiencies and fragility of classic parallel battery designs.
Instead of keeping multiple batteries fully active at all times, the Dual-Cell backup time-slices the load, allowing one battery to actively support the circuit while the other rests and recharges. This creates longer effective runtime and preserves redundancy during partial base failure.
At any given moment:
- One battery is actively supporting the circuit
- The other battery is charging and recovering
A timing circuit continuously flips which battery is active. This oscillation is intentional and controlled. No battery is expected to sustain the full load indefinitely. This concept, Alternating Load Cells, is the defining characteristic of the Dual-Cell design.
✅ Benefits
- Uses a Splitter’s dynamic behavior to automatically redistribute power if one battery is destroyed
- Provides up to 10 hours of backup runtime under optimal conditions
- Enables battery redundancy while using a single Wind Turbine as the primary source
- Well-suited for decentralized base designs where partial destruction is expected
❌ Limitations
- Always subject to the 80% battery efficiency loss during normal operation
- Requires understanding of Active Usage to avoid undercharging or impractical charge cycles
- Hard-limited to roughly 80 Active Usage due to charge-versus-drain timing constraints
- Offers no redundancy if both batteries are destroyed
How It Works
The Dual-Cell Battery Backup is an inline, alternating-load backup built around a single primary power source. Rather than keeping both batteries active simultaneously, the system deliberately forces only one battery to carry the circuit at a time, while the other is allowed to recover.
A Wind Turbine mounted at optimal height (10th–11th floor) feeds a Splitter, which supplies both batteries continuously. However, the turbine alone does not provide enough power to sustain full load on both batteries at once. This is intentional.
A dedicated timing circuit periodically flips which battery is allowed to support the circuit. When Battery A is active, Battery B is charging. When Battery B becomes active, Battery A rests. This oscillation prevents either battery from being fully drained and dramatically increases total usable runtime.
The timing mechanism is crude by design but reliable:
- An intentionally empty small battery is trickle-charged.
- A Laser Detector applies a constant drain.
- When the small battery reaches the output threshold, it toggles a Memory Cell.
- The Memory Cell swap reverses which battery is permitted to feed the circuit.
- The Laser Detector immediately begins draining the small battery again.
This creates a self-resetting oscillation of roughly five seconds per cycle. No external timers are required, and the system naturally stabilizes as long as charge input exceeds drain during the recovery phase.
The key constraint is balance. Each large battery must:
- Lose power while active
- Gain more power while resting than it lost while active
With one Wind Turbine, this balance reliably caps out at roughly 80 Active Usage. Above that, recovery time becomes longer than drain time and the system collapses into slow death.
Power Flow Logic
- Power Source → Splitter → Batteries
- - Power from a single Wind Turbine is sent directly into a Splitter. Each Splitter output runs directly to one battery.
- - No wire extensions are allowed here. Extensions break the Splitter’s dynamic redistribution behavior, which is what allows the system to continue operating if one battery is destroyed.
- - If one battery is lost, the Splitter automatically reallocates all available power to the remaining battery without player intervention.
- Battery 1 → Memory Cell → OR Switch → Circuit
- Battery 1’s output is controlled by the Memory Cell.
- - The Inverted Output of the Memory Cell feeds Input A of the primary OR Switch.
- - The Normal Output is routed through an Electrical Branch set to burn 1rW, then into Input B of a secondary OR Switch.
- - That secondary OR Switch feeds back into Input B of the primary OR Switch.
- When the Memory Cell is in this state, Battery 1 is authorized to support the circuit and Battery 2 is effectively blocked.
- Battery 2 → Electrical Branch → Timing Circuit
- Battery 2 feeds the timing system.
- - An Electrical Branch set to 1rW trickle-charges a small, fully discharged battery.
- - The small battery feeds:
- - The Toggle input of the Memory Cell
- - A Laser Detector, which exists solely to drain it
- Once the small battery accumulates enough charge to output power, it toggles the Memory Cell. The Laser Detector immediately starts draining it again, resetting the cycle.
- This is the heartbeat of the Dual-Cell system.
- Electrical Branch → OR Switch → Circuit
- Battery 2’s remaining power (after feeding the timing circuit) is routed into Input A of the secondary OR Switch.
- When the Memory Cell flips, both inputs of the secondary OR Switch are energized, allowing Battery 2 to take over the circuit load while Battery 1 enters its recovery phase.
- The system then waits for the next flip.
Design Considerations
Room Separation Is Mandatory
This backup only achieves redundancy if it is physically separated:
- Battery 1 in its own room
- Battery 2 in its own room
- Timing and logic components in a third room
If raiders destroy one battery room, the other battery continues operating automatically. If everything is stacked in one place, you’ve built a very expensive single point of failure.
Load Discipline Matters
This design is hard-capped at approximately 80 Active Usage with a single Wind Turbine. Pushing beyond that does not cause immediate failure, it causes slow, deceptive failure where batteries appear functional but never fully recover.
If more load is required:
- Add East + West Solar Panels to supplement turbine output
- Or introduce a second turbine feeding a separate battery, not merged upstream
Overproduction is acceptable. Underproduction kills the system quietly.
Scalability Strategy
For larger bases, multiple Dual-Cell backups can be deployed, each supporting its own circuit group. Three turbines can be combined and split across two Dual-Cell systems, improving resilience without wasting excess power.
Do not try to brute-force this design by stacking batteries. That defeats the entire point.
This Is Not a Parallel System
Treating this like a traditional parallel battery bank will lead to bad assumptions, bad math, and dead turrets. The Dual-Cell is about controlled alternation, not shared load.
If both batteries die, the system is done.
OR/Blocker
The OR/Blocker Battery Backup is one of the earliest and previously most well-known battery backups in Rust. Often mistakenly called "Infinite Power Loop", this circuit dates back to Rust’s 2019 electrical system, where batteries could either charge or discharge, but not both. In that era, batteries lacked Active Usage tracking and always pushed out maximum power. The so-called "Infinite Power Loop" was a real exploit back then, just not this one. This circuit simply offered the first bypass battery backup, not unlimited power.
Today, the OR/Blocker method may be obsolete, but it can still function as a basic bypass battery backup, where the main power source feeds the circuit, and excess power charges the battery. When the main power source fails or drops too low, the system automatically switches to battery power to keep everything running. While considered outdated due to newer mechanics, the OR/Blocker can still be found in use today.
✅ Benefits
- Easy to build using minimal components
- It does work for centralizing power and battery backup for larger circuits.
- Was designed to support circuits 200rW and above using root-combined batteries
- Automatic switching without any player interaction
❌ Limitations
- Outdated logic that ignores modern battery mechanics allowing for simultaneous charging and discharging
- Uses outdated mechanics of the OR Switch requiring a Blocker. Today, the OR Switch has the ability to block the inactive input.
- Without modernization, it causes power flicker when switching from main source to battery
- Wastes power during battery discharge because main power continues flowing through the first Branch Out, but is no longer used.
- Not optimized for circuits under 100rW. Those are better served by an Inline Backup or The Kore.
How It Works
The OR/Blocker Battery Backup was the traditional bypass design where an attached circuit is normally powered by Root Power from the main power source. Excess power is used to charge a battery, which only activates when the main source drops below a usable threshold. A Blocker was used to prevent battery discharge during normal operation, while an OR Switch provides a seamless transition between main power and battery power during outages.
While this circuit today will get the job done, its structure does not take advantage of Rust’s modern electrical mechanics resulting in significant power waste during periods of low production.
The detailed logic and wiring order for this setup are outlined below.
Power Flow Logic
- Main Power Source → Electrical Branch 1
- Splits power into two directions:
- Branch Out → OR Switch → Circuit
- Remaining power → Electrical Branch 2
- Electrical Branch 2
- Branch Out: Sends 1rW to the Blocker to keep the battery output blocked
- Remaining Power: Sent to the battery to charge it
- Battery → Blocker → OR Switch
- Battery is prevented from discharging while the Blocker is powered
- When Blocker loses power, battery output flows to the OR Switch and powers the circuit
The nature of this system reserves power for the main circuit with the first Electrical Branch. That power during low production periods of time is just sitting there getting wasted. At the time, a flicker was caused but could be mitigated by modifying the system but at best, that will make this setup better suited as a secondary battery backup, which is covered in its own section.
Design Considerations
- It was designed for high-demand, centralized circuits.
- Works best when paired with multiple root-combined Large Batteries, allowing for 200rW or more to be delivered.
- The Splitter is the best way to get as close to even charging across all batteries.
- Active Usage is irrelevant. This setup was designed to get around the batteries single state design, but today it could be used as just another bypass backup. Bypass backs should only be relying on the batteries less than 20% of the time allowing players to ignore any Active Usage considerations.
- The minimum runtime of the battery would be 4 hours, assuming it has a full charge and an Active Usage of 100.
- It was not recommended for circuits under 100rW. There are simpler and more efficient options like the Inline or Kore which are preferred.
- This circuit only serves as a stepping stone toward more advanced bypass backups like the Nih Core, which are capable of recovering the wasted power and preventing flicker while offering sustained, dynamic backup behavior.
Nih Core
About the Name
The Nih Core was named by the Rust community in honor of its creator, Nih. Although Nih himself did not choose the name, it has been widely adopted as a sign of respect for his contributions to advanced Rust electricity design.
The Nih Core is the modern version of, and replacement for, the OR/Blocker. It allows circuits to be powered directly with Root Power from the main power source while using the excess to charge the backup battery. When the main power source enters periods of low production or is destroyed, the battery automatically takes over. Once the main power returns to sufficient output, the system switches back.
What makes it a Nih Core, and superior to older methods is its ability to take full advantage of a battery’s simultaneous charge and discharge capabilities. When the battery is powering the circuit, any insufficient power from the main source is redirected to the battery. This reduces battery drain and extends the runtime of backup power.
✅ Benefits
- Efficient modern bypass system using current Rust electrical mechanics
- Significantly reduces wasted power during battery discharge
- Automatically switches between power sources with no flicker
- Excellent for central power systems supporting over 100rW
- Designed to be compatible with multiple batteries using Root Combiners
- Will not attempt to switch to batteries if they are unable to support the required load
❌ Limitations
- Requires multiple components and a solid understanding of Power Flow
- The added complexity can be difficult to troubleshoot without a solid understanding of the logic
- If the battery depletes or is destroyed while active, main power must return to a sufficient level before power will be restored
- Not always suitable for small circuits under 100rW (Inline or Kore can often be better)
- Max Depth must be managed carefully when scaling with many batteries or power sources
How It Works
The Nih Core is a modern bypass-style battery backup system designed to solve the inefficiencies of older designs like the OR/Blocker and mitigate the over production of power often experienced by Inline backups. Its defining feature is the ability to redirect the flow of power to take advantage of a battery's ability to charge and discharge at the same time, while still maintaining full control over when the battery is actually used.
The system powers a circuit using Root Power from a main power source, typically a Wind Turbine or Solar Panel, and uses any excess power to charge one or more batteries. The battery is kept on standby and does not supply power unless the main source fails or produces insufficient output. This setup allows the battery to remain fully charged and unused until needed.
How power flows through the series of Electrical Branches will dictate the state of the Memory Cell, which will decide whether main or backup power should be used:
- Electrical Branch 1 is configured to match the circuit’s expected load (e.g., 99rW). If the main source can satisfy this Branch Out amount, the circuit is powered directly by the main source.
- If the main power source drops below the set value, power to the SET input on the Memory Cell is lost, causing it to flip outputs and activate battery backup through the OR Switch.
The battery itself is connected to its own Electrical Branch, which is also set to the same value as Electrical Branch 1 (e.g., 99rW). This is crucial:
- If the battery provided more than the expected load to the OR Switch, the OR Switch would prioritize the higher input (battery) even when main power is still producing enough, causing unnecessary battery drain.
- Matching the set values ensures the battery never overrides the main source unless it is truly needed.
During battery-powered operation, any partial power still coming in from the main source is automatically redirected to the battery for charging, helping slow down battery drain and extending backup time.
Power Flow Logic
Each Electrical Branch in this setup plays a critical role. The first branch is configured to match the expected circuit load (e.g., 99rW). When main power drops below this value, the system triggers the battery to take over. The Memory Cell's SET and RESET inputs are responsible for determining when this switch occurs, based on power availability.
- Main Power Source → Electrical Branch 1 (Set to 99)
- Branch Out → Memory Cell Input - Root Power bypass
- Power Out → Electrical Branch 2 - Excess power overflow
- Electrical Branch 2 (Set to 1)
- Branch Out → Memory Cell SET input - Root Power is present signal
- Power Out → OR Switch 2 Input A - Excess power powerflow
- Memory Cell
- Output (Right) → OR Switch 1 Input A - Root Power primary route
- Inverted Output (Left) → OR Switch 2 Input B - Root Power failover route
- OR Switch 2
- Power Out → Battery input - Charging power
- Battery → Electrical Branch 3 (Set to match circuit load, e.g., 99)
- Branch Out → OR Switch to Circuit - Battery backup power route
- Power Out → Memory Cell RESET input - Flips output when SET loses power
Using the next image, it is possible to see where power exists and where it doesn’t when the Nih Core is running off of Main Power vs Battery Power.
- Green Wires: show the path of the power that is being used and/or consumed.
- Red Wires: show where there is no power.
- Blue Wires: shows power that is present and standing by from the battery, but not generating any Active Usage.
When power from the source is sufficient, the Memory Cell remains SET and uses the main power path to the circuit. The battery is charged passively in the background. When main power drops below the first Branch setting, SET loses power, and the Memory Cell flips, activating the battery via the top OR Switch no longer receiving power on Input A.
While the battery powers the circuit, any remaining power from the main source is redirected to charge the battery, helping reduce the battery’s drain rate.
It is important to note that If the battery is ever depleted or destroyed, the circuit will avoid trying to switch to the battery and remain on the main source, even if it doesn't have enough incoming power to meet the set demand.
Design Considerations
- Power scaling favors the Nih Core. In an Inline setup, each Large Battery requires 125rW to stay neutral when powering 100rW of Active Usage. Adding more batteries (for 300rW, 400rW or 500rW) massively increases the baseline power generation needed 500rW for 400rW of load.
- The Nih Core bypasses this scaling problem. Circuits are powered directly by the main source most of the time, meaning batteries remain idle. Only a small amount of power is needed to charge the batteries during normal operation, rather than constantly feeding them.
- Real-world example:
- A 400rW load using Inline backups would require over 500rW of power just to maintain battery charge.
- The same 400rW load with a Nih Core can be sustained with as little as 421rW of production, 400rW for the circuit, 1rW for logic, and small surplus amounts (roughly 5rW per battery) for passive battery charging. At this rate, it will take a little more than 3 real life days to fully charge the batteries. Increase the surplus to increase the charging rate.
- Efficiency increases the larger the circuit gets, because batteries are not actively drained except during failover, and even then, any remaining power is redirected to slow the battery drain.
- Flexibility during base growth. Early on, players can temporarily lower Electrical Branch values (e.g., setting 99rW down to 50rW) to accelerate battery charging while the base's load is still small.
- Battery sizes should be the same size for consistent drain rates if using multiple batteries. If a player chooses to use different size batteries, they need to design their circuit by taking into account that when the smaller battery is empty, the circuit will have less power to function on. Using a Fixed Bus, ie Electrical Branches, to build in prioritization will be required to ensure the circuits with the highest priority get power first and the circuits with the lowest priority receive power last. When the smaller battery is depleted, only the circuits with the lowest priority will go offline.
- Scaling requires attention to Max Depth. Bases with many sources and batteries (e.g., 16 power sources and 16 batteries) can hit Rust’s Max Depth limitation, see Short Circuit / Max Depth for important planning details.
Advanced Branch Configuration
While setting Electrical Branch 1 and Electrical Branch 3 to matching values is standard, they do not have to be identical.
- The Electrical Branch connected to main power (Electrical Branch 1) can be set higher than the Electrical Branch connected to the battery’s output (Electrical Branch 3) to support additional non-critical circuits during normal operation. These extra circuits will automatically shut off during battery failover if the batteries cannot cover the full load.
- The battery branch (Electrical Branch 3) can be set lower if players want to conserve battery life and only power critical systems during failover.
- Important: The battery branch (Electrical Branch 3) must never be set higher than the main power branch (Electrical Branch 1), or the OR Switch will incorrectly prioritize the battery even when main power is available.
This flexibility allows players to prioritize what stays online based on available power without needing complex wiring changes.
Nih Core Variants
Like most things with rustricity, there are always more than 1 way to accomplish anything. The Nih Core is no different. The version that has been discussed in detail above is the recommended version specifically because it has the built in safety of not swapping to the battery if it is depleted or destroyed. These next 2 versions are not uncommon to see players use and more accurately replicate the original Nih Core, including its flaw of swapping to the battery when it was depleted or destroyed. However, they do have the benefit of not costing 1rW from the battery.
Variant 1 - The Classic Nih Core updated for post 04/2024 rustricity mechanics.
This variant of the Nih Core is the most similar to its original design that used a Splitter to control the logic, and a Blocker to stop the battery from draining. Today, the Splitter is replaced with an Electrical Branch to still control the logic, and either nothing replaces the Blocker or an Electrical Branch is used to limit power to the OR Switch if a player is working with power loads less than the batteries output. There is nothing wrong with using this version, as long as the player understands that when power production is running low, the core will flip to the battery, even if it is depleted or destroyed.
Version 2 - The Updated Classic Nih Core, utilizing Control Power, a new mechanic post 04/2024.
This variant acts exactly like the original design, including its flaw, but introduces the idea of Control Power with the Small Battery to RESET the Memory Cell. Control Power allows more of the power produced to be used for the main backup battery and powering the attached circuits. The original design used a Splitter to control the logic, and a Blocker to stop the battery from draining. Today, the Splitter is replaced with a Small Battery and 1rW from an Electrical Branch to still control the logic, and either nothing replaces the Blocker or an Electrical Branch is used to limit power to the OR Switch if a player is working with power loads less than the batteries output. There is nothing wrong with using this version, as long as the player understands the flaw in the original design. When power production is running low, the core will flip to the battery, even if it is depleted or destroyed. This is the reason the original BCN was created.
BCN Core
About the Name
The BCN Core stands for Battery-Checked Nih Core. Created by SwiftCoyote, it enhances the original Nih Core by introducing battery health awareness just like The Kore.
The BCN Core is a direct upgrade to the Nih Core. It retains the same bypass and battery-charging mechanics, but introduces automatic fallback when backup batteries are destroyed or depleted while actively running on battery power.
In standard Nih Core designs, if batteries failed while active, the system would remain stuck waiting for main power to fully recover. The BCN Core corrects this by forcing an immediate return to whatever main power is available, even if it is insufficient to meet the original demand.
This makes the BCN Core more resilient for bases relying on centralized battery backup systems that are likely to be raided.
✅ Benefits
- Efficient modern bypass system using current Rust electrical mechanics
- Significantly reduces wasted power during battery discharge
- Automatically switches between power sources with no flicker
- Excellent for central power systems supporting over 100rW
- Designed to be compatible with multiple batteries using Root Combiners
- Automatically recovers to main power if batteries are destroyed or drained
- Prevents systems from becoming stuck waiting for main power recovery
- No manual reset or intervention needed after battery failure
❌ Limitations
- Wiring is slightly more complex than a standard Nih Core, requiring additional components and precise setup
- Requires an understanding of Power Theory to grasp the concept that allows the Small Battery to be used without giving it a charge, and then use it for more.
- Players must understand Power Flow, including the Memory Cell priorities and OR Switch input behavior affect power routing
- Efficient scaling requires understanding Max Depth rules to avoid max depth errors when centralizing large numbers of power sources and root combined batteries
How It Works
The BCN Core builds directly on the Nih Core's structure, maintaining the same bypass-first and passive battery-charging behavior during normal operation. Root Power supports the circuit directly most of the time, while excess or the remaining power charges the backup batteries.
If main power production falls below the reserved threshold, a blocker allows power from the battery to reach the Memory Cell’s SET input. This causes the Memory Cell to flip outputs, switching the circuit over to battery power through the top OR Switch.
While running on battery power, any remaining main power, the amount that was insufficient to fully run the circuit, is automatically redirected to help charge the batteries. This extends backup runtime and improves overall system efficiency during low production periods.
If the batteries are later destroyed or fully depleted while active, the Memory Cell automatically flips back to using whatever main power is available because of the power present on RESET. This fallback prevents circuits from remaining offline unnecessarily and ensures some continuous operation whenever possible.
A Small Battery is used as a representation of Control Power, and is used to power the Memory Cell RESET input. The side inputs do not generate Active Usage, the Small Battery does not drain during any operation, making it ideal for this role without needing to receive power. Players should make attempts to use Control Power where possible to help improve the efficiency of connected circuits.
During normal conditions, the BCN Core retains all the efficiency advantages of the Nih Core:
- Root Power supports the circuit directly most of the time allowing players to leverage other power types within connected circuits.
- Batteries remain idle and charge passively.
- Battery drain only happens during actual failover.
Power Flow Logic
- Main Power Source → Electrical Branch 1 (Set to Circuit Load, e.g., 99)
- Branch Out → Memory Cell Input - Root Power bypass
- Power Out → Electrical Branch 2 - Excess power overflow
- Electrical Branch 2 (Set to 1)
- Branch Out → Block Passthrough on a Blocker - Root Power present signal
- Power Out → OR Switch charging the battery - Excess power overflow
- Memory Cell
- Output (Right) → OR Switch to Battery - Root Power primary route
- Inverted Output (Left) → OR Switch to power a Circuit - Root Power failover route
- Battery → Electrical Branch 3 (Set to match expected load, e.g., 99)
- Branch Out → OR Switch to Circuit - Battery backup power route
- Power Out → Blocker Input - Battery presence signal
- Blocker Output
- Output → Memory Cell SET input - Battery presence signal
- Small Battery
- Connected → Memory Cell RESET input - Failover signal on battery failure
Using the following picture, it is possible to see where power exists and where it doesn’t when the BCN Core is running off of Main Power vs Battery Power.
- Green Wires: show the path of the power that is being used and/or consumed.
- Red Wires: show where there is no power.
- Blue Wires: shows power that is present and standing by from the battery, but not generating any Active Usage.
When main power falls below the expected value:
- SET gains power from the Large Battery.
- The Memory Cell flips, activating the battery through the top OR Switch.
If the battery later becomes empty or destroyed while active:
- SET loses power.
- The Memory Cell automatically flips back to main power — even if main power is still below the original threshold — preventing complete circuit failure.
Advanced Branch Configuration
While setting Electrical Branch 1 and Electrical Branch 3 to matching values is standard, they do not have to be identical.
- The Electrical Branch connected to main power (Electrical Branch 1) can be set higher than the Electrical Branch connected to the battery’s output (Electrical Branch 3) to support additional non-critical circuits during normal operation. These extra circuits will automatically shut off during battery failover if the batteries cannot cover the full load.
- The battery branch (Electrical Branch 3) can be set lower if players want to conserve battery life and prioritize only critical systems during backup operation.
- Important: The battery branch (Electrical Branch 3) must never be set higher than the main power branch (Electrical Branch 1), or the OR Switch will incorrectly prioritize the battery even when main power is available.
This flexibility allows players to fine-tune which systems stay operational based on power availability without needing to rewire the core.
Design Considerations
- Power scaling favors the BCN Core. In an Inline setup, each Large Battery requires 125rW to stay neutral when powering 100rW of Active Usage. Adding more batteries (for 200rW, 300rW, 400rW) massively increases the baseline power generation needed.
- The BCN Core bypasses this scaling problem. Circuits are powered directly with Root Power most of the time, meaning batteries remain idle. Only a small amount of power is needed to charge the batteries during normal operation, rather than constantly feeding them.
- Real-world example:
- A 400rW load using Inline backups would require over 500rW of power just to maintain battery charge.
- The same 400rW load with a BCN Core can be sustained with as little as 421rW of production, 400rW for the circuit, 1rW for logic, and small surplus amounts (roughly 5rW per battery) for passive battery charging. At this rate, it will take a little more than 3 real life days to fully charge the batteries. Players can increase the amount of excess power to decrease the charging time as needed.
- Efficiency increases the larger the circuit gets, because batteries are not actively drained except during failover, and even then, any remaining power is redirected to slow the battery drain.
- Flexibility during base growth. Early on, players can temporarily lower Electrical Branch values (e.g., setting a 99rW Branch down to 50rW) to accelerate battery charging while the base's load is still small.
- Battery sizes should be the same size for consistent drain rates if using multiple batteries. If a player chooses to use different size batteries, they need to design their circuit by taking into account that when the smaller battery is empty, the circuit will have less power to function on. Using a Fixed Bus, ie Electrical Branches, to build in prioritization will be required to ensure the circuits with the highest priority get power first and the circuits with the lowest priority receive power last. When the smaller battery is depleted, only the circuits with the lowest priority will go offline.
- Scaling requires attention to Max Depth. Bases with many sources and batteries (e.g., 16 power sources and 16 batteries) can hit the Root Combiners Max Depth limitation, see Short Circuit / Max Depth for important planning details.
NEXUS
Coming Soon
Secondary Battery Backup
A Secondary Battery Backup provides an extra layer of protection for a base's most critical circuits after the primary backup system fails. It acts as a backup for the backup making it rarely used, but essential when needed.
Although the chances of needing a Secondary Backup on a typical day are extremely low, the benefits can outweigh the added costs. Installing them provides a way to use excess power after the primary batteries are full, while adding critical redundancy to base defenses.
There are two versions of Secondary Backups, the Secondary Inline and the Secondary Bypass. Both can be integrated into any part of a circuit, but they are ideally used to protect smaller, high-priority sections. The type of primary backup in use will influence which secondary method is best suited.
With an Inline Primary Backup, a Secondary Bypass is preferred. With a Bypass Primary Backup, either Secondary Inline or Secondary Bypass can be used, but depending on the attached circuit, one of the two methods will always be more efficient over the other.
✅ Benefits
- Simple to make with minimal components.
- Great for creating redundant backups while improving decentralization within a centralized circuit.
- Adds extra survivability to bases without major cost after setup.
- No flicker of power when switching onto the backup.
- Efficient use of otherwise wasted power after primary backups are charged.
- No limitation to the number of secondaries that could be added.
- Secondary Inline can be leveraged over Root Power to increase efficiency in some use cases.
❌ Limitations
- Secondary Inline systems introduce a 20% efficiency loss.
- Secondary Bypass batteries should be fully charged before installation, else a recharging solution is needed.
- Adds more wiring complexity when integrating into existing circuits.
- Secondary Bypass backups require precise Electrical Branch configuration for proper failover.
- Requires a good understanding of Power Theory to understand when a secondary could be used to leverage power and increase efficiency.
How It Works
A Secondary Battery is designed to sit between a player's primary battery backup and a sub-circuit. There are 2 different methods, each with their own use case and functionality.
- A battery is installed inline between the circuit's power source and the circuit itself.
- Image Example: The Auto Turret is the circuit needing power and the Electrical Branch is its source of power.
- The Electrical Branch will need to send just enough power to the battery to maintain a neutral charge. In this case it's 13rW to maintain the 10 Active Usage caused by the Auto Turret.
- Due to the battery’s efficiency tax, this is a 20% efficiency loss and would not be recommended. Use a Bypass Secondary instead.
- If the connected circuit was not an Auto Turret but a circuit where 20% or more of the power consumed did not generate Active Usage, efficiency gains can be dramatic.
- An OR Switch is installed inline between the circuit’s power source and the circuit itself.
- Image Example: The Auto Turret is the circuit needing power and the Electrical Branch is its source of power.
- The source Electrical Branch only needs to send the amount of power the circuit needs to Input A on the OR Switch to be passed on to power the circuit.
- A fully charged battery is connected to its own Electrical Branch with Branch Out connected to Input B of the OR Switch.
- The branch value but be equal to the amount of power on Input A.
- The OR Switch prioritizes power from Input A when both inputs receive the same amount of power. This allows the battery to sit idle and not drain unless the primary backup system fails.
- Fully charged batteries are recommended to avoid having to install a charging system. This makes Secondary Backups cheaper to design, build and maintain. However, the NEXUS is a recharging solution players can explore.
Important Wiring Behavior:
- For a Secondary Bypass Backup, set both Electrical Branches (Main and Battery) to provide the exact amount needed (e.g., both set to 10rW for an Auto Turret).
- Secondary batteries should be pre-charged before being installed to avoid extremely long charging times in case of emergency.
Power Flow Logic
- Secondary Inline Backup:
- Source of power → Inline Secondary Battery → Circuit that needs power
- The battery is always active. Primary power needs to be enough to maintain the charge.
- Secondary Bypass Backup:
- Source of power → Electrical Branch → OR Switch Input A → Circuit - The bypass route
- Secondary Battery → Electrical Branch → OR Switch Input B → Circuit - The backup route
- Main power takes priority. The battery remains idle unless the primary backup fails.
Design Considerations
- Choose the right type:
- Players need a solid understanding of Power Theory and a working knowledge of the different types of power.
- Use Secondary Inline backups whenever 30% or more of the circuits consumed power does not generate any Active Usage.
- Use Secondary Bypass backups whenever it would require more power from the source then the circuit consumes to function.
- Avoid stacking Primary Inline Backups + Secondary Inline backups due to excessive inefficiency. Stacking Inline backups only compounds the 20% efficiency loss and if not properly regulated.
- Pre-charge the batteries:
- Charging a Large Battery with 1rW takes over 800 hours (34 days).
- Pre-charging with 400rW can fully charge a Large Battery in about 75 minutes.
- A battery’s max input = Output x 4
- Installing fully charged batteries helps to mitigate a couple issues:
- With Inlines, it prevents the need for players to increase the power they give to it at the start, and then forcing them to return later to reduce it.
- With Bypass, it prevents the need for players to design and build a charging system for them. The goal is that if they are ever used, it’s a last resort, so how much effort is it worth?
- If precharging is unattractive or not possible, increase the amount of power to the inline and build a charging system for the bypass.
- Controlling Electrical Branch Values:
- For Secondary Bypass backups, ensure both inputs on the OR Switch are receiving the same amount of power to prioritize the primary power source over the backup.
- Only set enough power to meet actual device needs and avoid unnecessary surplus.
- For Secondary Inline backups, do the math on the Active Usage and give it only exactly what it needs to remain as efficient as possible.
- Root Combining Secondary Batteries:
- When trying to combine multiple batteries, adding too many components between the Power Source and a Root Combiner can trigger the Max Depth wiring error. The depth at which a Secondary Backup will be used will exceed this limit. This should be avoided to prevent wiring headaches and stick to single battery solutions only.
- Material Cost vs Survivability:
- Extra batteries and OR Switches increase material cost and require the additional space and time to install.
- Yes, they offer massive uptime gains after system-wide failures, but what are the chances they will be needed, and does the player have the space to properly separate components?
HazCore (Updating)
About the Name
HazCore is named after Hazdr, who helped popularize the design through practical use and iteration. In some communities this core is also known as a CPD (Central Power Distributor).
The HazCore is a Decentralized Nih Core that follows a very specific design philosophy. This means it is a bypass backup that supplies connected circuits with Root Power from the main power source most of the time, using the excess to charge decentralized batteries. When main power enters periods of low power production, the batteries will take over and the insufficient amount of power gets redirected towards the batteries slowing their discharge.
What makes this design a HazCore is how explicit it is in 3 key areas:
- How much power gets allocated per circuit or subsystem.
- What power bus is used to distribute the Root Power to each circuit or subsystem.
- What power bus is used to charge the batteries with the excess power.
✅ Benefits
- Combines centralized power efficiency with decentralized backup resilience
- Guarantees fixed, predictable Root Power delivery per circuit
- Prevents over-allocation by hard-limiting circuit size
- Prevents total system failure by decentralizing battery backups
- Extends backup runtime from roughly 4 hours to roughly 8 hours per circuit using large batteries
- Automatically redistributes charging power if a battery is destroyed
- Scales cleanly as subsystems are added or removed
❌ Limitations
- Requires strict adherence to 50rW per circuit
- More components than a basic Nih Core
- Higher planning overhead during initial design
- Inefficient if used for very small or low-importance circuits
- Not designed for use with large, shared battery banks
How It Works
PPCore (Push-Pull Core)
Coming Soon
Distribution of Power
This section explains how electricity actually moves through a circuit: how power propagates, the order components process it, how delays and depth limits affect behavior, where short circuits occur, and the rules that govern how power flows and fails.
Power Bus Theory
In the real world, a power bus is a common electrical conductor, or group of conductors, that collects and distributes electrical power into multiple circuits or devices. In Rust, power also needs to be collected and distributed into multiple circuits or devices. The real world has things like a Slack Bus, PV Bus, PQ Bus and so on, each serving a specific purpose or role. In Rust, there are recurring distribution circuits players use, each with a specific purpose or role, but have never been recognized as Rust's version of a power bus.
When power needs to be moved from point A to point B, most players already know how to do it instinctively and without putting too much thought into it. The purpose with this section is to name, define, explain and formalize these patterns players are already using, but without realizing it.
Over time, players naturally combine branches, splitters, and logic components in repeatable ways. Power Bus Theory gives those patterns clear names and definitions, so they can be easily discussed, compared, and reasoned about without re-explaining the wiring every time.
By assigning names to common power flow structures, it allows experienced players to communicate designs quickly and helps newer players understand why a branch is used instead of a splitter, or why one structure scales better than another.
The goal is shared language and clearer thinking:
- A way to describe common power layouts quickly
- A framework for deciding which structure fits the job
- A bridge between intuitive building and intentional design
Power Bus Theory turns “stuff players wire automatically” into tools players can analyze and optimize.
In any circuit, electricity must need to get from point A to point B and more. Typically travelling from places like a power source (Wind Turbine, Solar Panel, Generator) to components that need it (turrets, lights, doors, automation systems). A Power Bus provides the structure and organization to manage this flow of power. It controls how much power goes where, in what order, and under what conditions.
A Power Bus can be as simple as a single component or as complex as a multi-component distribution system. Its job is to direct power in a way that matches the needs of the circuits it supplies.
Think of a Power Bus like the electrical breaker or fuse panel in a real home:
- It splits power into different circuits (kitchen, furnace, lights).
- It limits how much power each circuit can draw (10A, 15A, 125A).
- It keeps everything organized, efficient, and safe.
In Rust, instead of breakers or fuses, players will use Electrical Branches, Splitters, Root Combiners and Memory Cells to collect and distribute power. Choosing when to use each bus is entirely situational and depends heavily on circuit type, function, and priorities. Here are key questions players should ask:
- How critical is the circuit or component?
- Does it need strict prioritization?
- What is the primary power source?
- Is Active Usage a concern?
- Is the circuit always active or event-driven?
- What is the best way to simply reduce demand?
- Will this circuit be expanded later?
- Is material cost a concern?
- Is simplicity or resilience more important?
- What happens if part of the bus is destroyed?
- What combination of buses is needed to best serve a circuit's needs?
At its core, a Power Bus helps manage:
- Capacity: How much power is delivered.
- Priority: What gets power first during shortages.
- Resilience: How the system behaves if power drops or components fail.
- Efficiency: How much Root Power must be produced to meet needs.
Fixed Bus (F-Bus)
A Fixed Bus, or F-Bus is a Power Bus where specific, fixed amounts of power are reserved for each connected circuit or component. It guarantees that each destination always receives the same amount of power, regardless of whether or not that circuit is actively consuming power. It is the most stable and predictable form of power distribution, sometimes trading efficiency for reserved power delivery and strict prioritization.
In an F-Bus, each output is set to a specific value, providing an exact amount of power to each circuit or device. This power is reserved and always held, regardless of whether the downstream device is online, idle, damaged, or destroyed, the bus will still send the configured power.
It’s equally useful for both end devices (like turrets or lights) and for powering logic components (like splitting signal paths or sending reset triggers). Any time an Electrical Branch is used to explicitly control power levels to a specific location, an F-Bus is created. This simple mechanism becomes a powerful way to control power flow.
Core Structure
When players start working with components that have multiple outputs, it's very important to know the order in which they output power.
- Electrical Branch: Power Out updates first, then Branch Out. Removal of power follows the same order.
An F-Bus can be a single Electrical Branch or a chain of them. As each Electrical Branch receives power, it will reserve power for the Branch Out connection, pass along the rest via Power Out, and then release the reserved power out Branch Out. Assuming there is constant power, this structure ensures consistent delivery of power, regardless of how many components are active or inactive.
Example structure:
Source of Power → Electrical Branch (Branch Out: 11) → Turret 1
└ Power Out → Electrical Branch (Branch Out: 30) → Lights
└ Power Out → Electrical Branch (Branch Out: 3) → CCTV
Prioritization & Load Shedding
Load shedding is the ability to control what parts of a circuit shut down first to maintain the run times of more important areas during periods of low power. The F-Bus does this through prioritization. By reserving power first before passing on the rest, the first Electrical Branch to receive power has the highest priority. The last Electrical Branch has the lowest. When the input power starts to decrease, branches with the lowest priorities will lose power first. The highest-priority circuits at the beginning of the F-Bus will stay powered as long as enough power is available. Once a Branch Out value equals or exceeds incoming power, lower-priority Electrical Branches past it will brown out.
Benefits
- Efficient power delivery: circuits and components receive only their needed amount of power.
- Prioritization: branches towards the beginning maintain power longer during shortages.
- Predictable behavior: makes power degradation graceful, not sudden.
- Great for critical defense systems: support specific and predictable power delivery.
- Supports scaling: can be extended with additional branches or chained buses.
Limitations
- Inefficient for idle or event-driven circuits: power is reserved even when the circuit is unused.
- Higher baseline power demand: total power production must cover all reserved Branch Outs.
- Material costs per output: each Electrical Branch costs 75 Metal Fragments for 2 outputs.
- Does not limit battery Active Usage: reserved power does not limit the Active Usage that an Inline system can experience.
- Material and wiring complexity: large F-Bus chains can become harder to manage.
Dynamic Bus (D-Bus)
A Dynamic Bus, or D-Bus, is a type of Power Bus where incoming power is automatically and evenly distributed across all connected outputs.
It is built using one or more Splitters and is ideal for circuits where each connected device or component needs the same amount of power and power shedding prioritization is either unnecessary or undesirable.
A D-Bus is dynamically responsive. As input power levels change, or as devices are added, removed, and destroyed, the Splitters automatically adjust how power is divided.
Core Structure
When players start working with components that have multiple outputs, it's very important to know the order in which they output power.
- Splitter: Power Out 1 updates, then Power Out 2, then Power Out 3. Removal follows the same order.
The D-Bus is built using the Splitter, either as a standalone unit or in groups. Each output receives an equal portion of the available power, making this bus ideal when every connected component needs the same amount of power.
A common D-Bus pattern is a pyramid or cascade:
- One Splitter → Two Splitters → Six outputs.
This is ideal when identical devices need to be powered, such as turrets, water pumps and batteries wired in series.
- All outputs should receive roughly equal power (within 1rW of each other when dealing with odd amounts of power).
- It makes the division of power easily predictable.
- Beware: this reduces available power per output quickly if power is limited.
An uncommon D-Bus pattern is a chain:
- Output 3 of Splitter A → Input of Splitter B → Output 3 of Splitter B → Input of Splitter C
- Beware: Each link in the chain further reduces the available power at the final outputs.
Each chained Splitter is splitting up to 1/3rd of original power, by up to 3 times. This significantly reduces available power the further down the chain the Splitter is placed, and removes the ability for future expansion. This wiring is not recommended unless extremely low draw circuits are being powered or the player has a solid understanding of the dynamics of this method.
Load Shedding & Priority Behavior
Load shedding is the ability to control what parts of a circuit shut down first to maintain the run times of more important areas during periods of low power. The D-Bus does not allow for easy management of load shedding. Once there is not enough input power, the connected outputs will cease to function, even if there is enough total power remaining to maintain 1 or 2 of the connected circuits or components.
Although a D-Bus is generally "equal," Splitters have built-in output priority:
- Power Out 1 is powered first.
- Power Out 2 is powered next.
- Power Out 3 is powered last.
- This order is the same when the Splitter loses power.
This order of Power Flow also generally means that after all 3 outputs send power, the component that is connected to Power Out 1 will be the next component to perform an action, followed by the component connected to Power Out 2 then Power Out 3.
This priority is also applied when splitting odd amounts of power. Any remaining power that cannot be divided equally between the connected outputs is given to Output 1 first, followed by Output 2.
This is important for signal-based circuits or sequenced activation.
It can be used to control the order of actions such as:
- Which Memory Cell is triggered first.
- Which door opens first.
- Which signal path activates last.
Benefits
- Power efficient: when all circuits require the same wattage
- Automatically redistributes: power when outputs are removed
- Low material cost: 1 Splitter = 100 metal fragments, 3 outputs
- Great for identical devices: or logic circuits with equal signals
- Simple to design: no need to configure individual output amounts
- Easy signal sequencing: using output order for logic circuits
Limitations
- No load shedding prioritization: all outputs are treated equally
- All circuits fail together: if input power drops below required threshold
- Limited control: over which outputs stay active under strain
- Chaining splitters: reduces output power quickly and may limit scalability
Configurable Bus (C-Bus)
A C-Bus, short for Configurable Bus, is a logic-based power distributor that only activates when power is specifically needed. It operates as a conditional bypass circuit that intelligently diverts and applies power to a circuit only when triggered, thereby saving energy during idle periods.
It is not a physical component like the Splitter or Electrical Branch, but rather a logic design that combines multiple components, specifically the Memory Cell, Electrical Branch, and OR Switch. Without the logic system in place, the bus does not exist.
The C-Bus can be thought of as an intelligent F-Bus. Instead of always reserving power like a traditional F-Bus, it reserves power only when activated, returning unused power back to the main line.
Core Structure
When players start working with components that have multiple outputs, it's very important to know the order in which they output power.
- Memory Cell: When switching from one output to the other, Output always reacts before Inverted Output. If the Memory Cell is in its default state (power coming from Inverted Output) and receives a pulse on Set, the Output will start sending power before Inverted Output stops sending power. If a pulse is then applied to Reset, the Output will stop sending power before the Inverted Output starts sending power. This means that when toggling states, there is a brief moment where both outputs will be active or inactive simultaneously before settling into the final state.
Every C-Bus consists of three components:
- Memory Cell: acting as the power path controller.
- Electrical Branch: regulates the amount of power delivered when active.
- OR Switch: merges bypass and active power paths.
At its core, every C-Bus has two paths:
- Main Line - default power flow
- Circuit Path - activated power flow
Main Line (Default State):
- Power passes from the Inverted Output of the Memory Cell to the OR Switch and continues on.
- The destination circuit remains unpowered.
Circuit Path (Siphon State):
- Memory Cell switches to the Output, which powers an Electrical Branch.
- The Branch Out is set to deliver a defined amount of power to the destination circuit.
- The remaining power flows through Power Out, merges via the OR Switch, and rejoins the main line.
This creates an on-demand power distributor with no wasted reserved power during idle periods. What controls the activation and deactivation is entirely dependent on the situation and player preference.
Operational Modes
C-Buses can operate in 4 distinct modes, depending on how the Memory Cell is controlled:
Auto Set Auto Reset (Fully Automatic)
- The Memory Cell is controlled via SET and RESET inputs.
- When the trigger (ex: HBHF Sensor) provides power to SET, the Circuit Path automatically activates.
- When the trigger stops sending power, RESET is automatically activated, returning flow to the Main Line.
Behavior: Circuit turns on when the trigger is present, turns off automatically when the trigger disappears.
This Auto Reset behavior can be achieved through another method. It doesn't need to use a second Electrical Branch as demonstrated.
- The goal is simply to have power applied to Reset for the system to automatically reset after activation.
- If players are already taking advantage of Control Batteries, like the one used in The Kore or a BCN Core, then the second Electrical Branch is not needed
Manual Toggle (Player Controlled)
- The Memory Cell is controlled via TOGGLE input.
- Players manually activate/deactivate the Circuit Path with a button (or any momentary signal).
- Outputs remain in the last state until toggled again.
Behavior: Circuit stays ON or OFF until the player manually changes it.
Auto Set Manual Reset (Hybrid Control)
- The Memory Cell is SET automatically by a trigger (ex: Laser Detector).
- RESET is controlled manually by the player (ex: Button).
- Useful for circuits that must be acknowledged or intentionally reset after an automatic activation.
Behavior: Automatically turns on when triggered, but requires player intervention to turn off.
Inverted Set Auto Reset (Failure Controlled)
In the previous methods, power was always bypassing the circuit until called upon. This is a more advanced variation where the Memory Cell is Set by default and only Resets when the circuit fails.
- Power flows through the circuit (ex. SAM Site) and Sets the Memory Cell
- Control Power is used to supply power to the Memory Cells Reset.
- If the circuit (ex. SAM Site) is destroyed, power it no longer applied to Set and Reset flips the power path.
- Beware: In its default state, the Memory Cell will not send power to the circuit (ex. SAM Site). That means Set will also not get power. Players will need to toggle the Memory Cell first, power the circuit and get power to Set before connecting Control Power to Reset.
Behavior: Automatically swaps the power path when there is a failure of the circuit.
Benefits
- Power-efficient: no energy waste when the target circuit is inactive.
- Flexible: supports manual, automatic, or hybrid logic triggers.
- Perfect for situational circuits: e.g., farms, traps, alarms.
- Reduces standby power draw: freeing power for higher-priority needs.
- Can reintroduce unused power: back into the grid via OR Switch.
Limitations
- Requires more components: than D- or F-Bus.
- Complexity: increases with each logic variation.
- Requires understanding: of Memory Cell behavior and logic principles.
Root Combiner Bus (RC-Bus)
An RC-Bus, or Root Combiner Bus, is a specialized wiring structure used to merge electricity from multiple sources into a single unified power line. It acts as a power aggregator, collecting electricity upstream before it is stored, regulated, or distributed.
Unlike output-focused bus types like the F-Bus or D-Bus, the RC-Bus does not route electricity to components. Instead, it gathers electricity from solar panels, wind turbines, generators, batteries, and other valid sources, and delivers it downstream through one clean, centralized line.
Core Structure
An RC-Bus is built entirely from Root Combiners. Each Root Combiner merges power from two sources, like Solar Panels, Wind Turbines, or Generators, into a single output.
- Each Root Combiner has two inputs and one output.
- To combine more than two sources, multiple Root Combiners are chained in tiers or pyramid formations.
- The final output becomes the main power line, typically sent to a battery bank or core system.
The RC-Bus performs no distribution, only collection. It is designed solely for upstream power merging.
Two important factors must be considered when designing RC-Bus layouts:
- Max Depth Limit: Each component in the power path contributes to signal depth. If any path from a power source to the final Root Combiner exceeds 16 components, it will trigger a Max Depth error. This includes sources, batteries, logic components, and combiners. For detailed examples, see the Max Depth & Short Circuit Errors section.
- Battery Behavior: When combining batteries through Root Combiners, each battery registers the full Active Usage of the circuit. This can cause excessive battery drain if not properly planned for. For a more detailed breakdown, see Root Combiner Behavior in Power Theory and Efficiency section.
Combiner Layouts
When building an RC-Bus, players must choose how to structure their Root Combiners. There are two main methods, and while both technically work, only one is recommended for long-term stability.
Daisy Chain (Not Recommended)
Most new players instinctively use this method due to its simplicity but it comes with hidden risks.
- How it works:
- Connect Combiner 1 to two power sources.
- Take the output of Combiner 1 and connect it to one input of Combiner 2.
- Add a third power source to Combiner 2’s remaining input.
- Continue this process in a linear chain: each new Combiner merges the previous output with one new source.
- What’s the problem?
- Each Combiner in the chain adds one unit of depth between the final output and the earliest source.
- The Root Combiner system in Rust has a Max Depth limit of 16 components.
- Daisy Chains quickly reach this limit, especially when mixing in batteries or other logic components.
- Result:
- A few extra devices or a battery backup can push your circuit over the limit, resulting in Max Depth / Short Circuit errors.
- This layout becomes unstable and hard to expand or troubleshoot as a circuit grows.
Pyramid (Recommended)
A structured, layered layout that minimizes depth and supports larger builds.
- How it works:
- Combine power sources in pairs, filling one Root Combiner at a time.
- Once all sources are paired, combine their outputs into new Root Combiners.
- Repeat the pairing process layer by layer, until all power is unified at the top of the pyramid.
- Why it’s better:
- Only each layer adds to circuit depth, not each individual Combiner.
- A pyramid that combines 8 sources only reaches 4 depth, compared to 8 depth for a daisy chain.
- Much more scalable, reliable, and organized for large RC-Bus trees.
- Design Tip:
- If one source remains unpaired at any layer, add another Combiner to merge it with the leftover from a previous layer.
Benefits
- Efficient scaling: supports many power sources
- Clean consolidation: reduces wire clutter by merging lines early into a single output
- Compatible with all source types: solar, wind, generators and batteries
- Maximizes output control: ideal for feeding into downstream bus systems like the BCN Core
Limitations
- No load sharing for batteries: batteries combined in series will each register the full Active Usage of the circuit
- Subject to Max Depth: chaining too many components or wiring inefficiently can break the circuit
- One-way design: does not allow for looping power through itself that has already passed through it once before
- Requires planning: depth, layout style, wire length and placement must be considered to avoid errors
Hybrid Bus (H-Bus)
A Hybrid Bus, or H-Bus, is a composite power distribution system that combines multiple bus strategies, Fixed (F-Bus), Dynamic (D-Bus), and Configurable (C-Bus), within a single architecture. The H-Bus is not a standalone design, but rather a philosophy and approach to solving complex power routing needs using the most effective bus type for each part of a circuit or subsystem.
Rather than sticking to a single distribution method, the H-Bus leverages the strengths of each individual bus style to balance efficiency, control, scalability, and reliability. This makes it the most flexible and capable bus system.
Note: While the H-Bus may sound advanced, many players already use hybrid strategies without realizing it. Connecting F-Bus segments for turrets, D-Bus cascades for Electric Furnaces, and C-Bus siphons for conditional systems, all within the same circuit, is an H-Bus in action.
Core Structure
The H-Bus is built around segmented power layers, with each segment powered and regulated by the bus style that best fits its function:
- RC-Bus segments collect power from multiple sources into a single usable line.
- F-Bus segments provide precise and reserved power where reliability, predictability and prioritization are required.
- D-Bus segments handle mass distribution where devices have the same draw and power can be evenly split.
- C-Bus segments dynamically provide power to systems as required.
The combined cluster of these segments is the H-Bus. It is often powered from a common source and is either directly attached to one another or separated by any number of components, including switches, logic components, batteries and lights, to isolate or synchronize operation.
Each segment can be debugged and modified independently, but overall performance is optimized through central planning.
Benefits
- Maximum flexibility: combine multiple bus types to suit each circuit's needs
- Efficient power use: minimizes waste by assigning the right distribution method per device group
- Supports complex designs: ideal for large or layered systems with varying power demands
- Modular by design: easy to expand, segment, or upgrade over time
- Built-in prioritization and logic: enables smart control, fallback behavior, and automation
- High resiliency: segments can continue functioning independently even if others fail
Limitations
- High learning curve: requires solid understanding of RC-Bus, F-Bus, D-Bus, and C-Bus behaviors
- More complex wiring: can be difficult to troubleshoot without labeling or documentation
- Increased component usage: typically uses more branches, switches, and logic parts
Short Circuit / Max Depth
The Short Circuit / Max Depth error is a single in-game warning message that appears when certain rules are violated in the electrical, water, or industrial systems. It is displayed in red text when looking at an IO connection, but despite appearing as one message, this error actually represents two separate problems: a Short Circuit, or a Max Depth violation.
When players encounter this error, it will appear as red text when looking at an input or output connection of a component. However, the game does not tell players which of the two problems occurred, it’s up to the player to determine whether they’ve created a Short Circuit or exceeded the Max Depth.
This section of the handbook explains:
- What a Short Circuit is, why it happens, and how to resolve it
- What a Max Depth violation is, how it's triggered, and how to avoid it
- How these rules apply independently to the electrical system
Short Circuit
A Short Circuit occurs within the electrical system when power is wired into a loop and ends up feeding back into itself. This creates a recursive condition where power has no true destination, and instead endlessly cycles through the same path. Rust detects this and cuts the connection off.
In short: loops are invalid unless specifically structured to avoid this condition.
Why Would Players Do This?
In today’s Rust, there is no valid reason yet to intentionally create a power loop. However, this was not always the case. In the past, batteries behaved differently:
- They were either charging or discharging, not both.
- When discharging, they always output full power (e.g., 100rW for a Large Battery).
- This meant that the amount of Available Power players saw on an IO connection was actually draining from a battery.
Players discovered ways to reuse unused battery output by feeding it back into the battery, a trick known as the “Infinite Power Loop.” This was a real Infinite Power Loop, not the OR/Blocker battery backup from the past and worked until Active Usage was introduced.
What Changed?
Batteries now calculate Active Usage, meaning:
- A battery only discharges the amount of power a circuit actually needs.
- The number seen at an IO connection is showing Available Power that can be used and is not contributing to Active Usage.
- If the battery has no Active Usage, it does not drain and there is no wasted power to “loop-back”.
Additionally:
- Batteries today add their own Active Usage when charging. This value is 4x their max output. For a Large Battery, this is 400.
- Creating a loop now causes the battery to count the amount of power in the loop back as Active Usage, resulting in a 20% efficiency reduction with zero benefit.
Feeding power back into a battery is not only useless, it actively harms power efficiency.
How to avoid a Short Circuit
Rust automatically detects when a power path forms a loop. If the total number of components involved in the loop is 8 or fewer, the game issues a Short Circuit error.
However, you can bypass this detection by increasing the loop size to 9 or more components. While this removes the error, the loop still offers no practical benefit.
Max Depth
A Max Depth violation happens when the number of components from and including a Power Source to a Root Combiner exceeds a hardcoded limit of 16. This is one of the most common causes of confusion when players build advanced centralized power networks.
Despite showing the same Short Circuit / Max Depth error message, this is an entirely different issue than a Short Circuit.
Understanding Max Depth
When electricity travels from a Power Source to a Root Combiner, it may pass through many electrical components along the way, including branches, splitters, switches, lights, batteries, etc.
If the total number of components in that power path exceeds 16, the Root Combiner will stop functioning and display the Short Circuit / Max Depth error on one of its inputs.
- Power paths are not allowed to exceed 16 components between a Power Source and a Root Combiner. If this happens, the Root Combiner will reject the input entirely.
This rule applies to every unique path. This includes circuits that use multiple power sources and multiple Root Combiners, such as in RC-Bus, or circuits that create many possible routes for power, like C-Bus layouts. Rust checks each one individually, and only one needs to exceed the limit to break the system.
Quick Tip: How to Count Components
When checking Max Depth, every electrical component the power passes through counts as 1. Players don’t need to memorize examples, they just need to ask themselves:
“Does this component exist along the path power needs to take between the power source and the Root Combiner?”
If yes, it counts.
Preventing Max Depth Errors
There is no way to bypass the Max Depth limit, it is hardcoded. However, following best RC-Bus design practices, players can delay or eliminate the risk of hitting it:
- Use a Pyramid structure when combining power: pair sources into Root Combiners layer by layer.
- Avoid routing power through non-essential components before reaching the Root Combiner.
- Place Root Combiners closer to your power sources rather than centralizing too early.
- Take full advantage of wire length to prevent using another component to extend a wire.
Learn more about RC-Buses and Pyramid stacking in the Power Bus Theory section.
Troubleshooting Max Depth Violations
If a player is seeing a Short Circuit / Max Depth error and suspect it's due to Max Depth, here's how to narrow it down:
- Begin by identifying which Root Combiner input is showing the error.
- From that input, trace the entire wire path back to the power source.
- Count every component that power flows through, batteries, splitters, branches, etc. Include the power source.
- If any single path exceeds 16 components, that path is invalid and will trigger the error.
- Repeat this process for each power source connected to the combiner. The error occurs if only one of them breaks the limit.
It’s always the longest path that matters, not the average, and not the shortest.
This becomes especially tricky in:
- Circuits where power is split and re-merged (like a C-Bus)
- Setups that combine power from distant locations using multiple RC-Buses
- Battery backups with shared outputs routed through combiners
These designs introduce multiple valid paths, making it harder to troubleshoot a Max Depth violation. Players must manually check each path to ensure compliance, or plan ahead, to avoid accidentally hitting the 16-component limit.
Circuit Delay and Power Flow
Rust evaluates power via queues. This section covers two effects of queue‑based execution:
- Circuit delay: How long changes take to propagate.
- Power flow: The order in which devices act when supply changes.
Exact timings depend on server hardware and workload, so this section will describe relative behavior rather than talking in terms of fixed milliseconds.
Circuit Delay
Rustricity, aka Electricity, Fluid (water), and Industrial each maintain their own queue. Each queue is single threaded and therefore actions are handled one after another. The more items in a queue the greater the delay increases. The host machine’s hardware and workload determine how quickly these queues advance.
Circuit delay is specifically the time it takes components to receive, process and react. Under perfect conditions, each of these steps could be measured in single digit microseconds, but when considering all the other tasks that need CPU time, it is possible for a queue to become overwhelmed turning microseconds into milliseconds and even actual seconds. Turning things off is often faster than turning things on and a practical way to observe this delay is to pulse a chain of as many lights as possible and watch how long it takes for the chain to turn on and off.
To better conceptualize delay without using an absolute measurement of time, let’s call each advancement of the queue an Operational Step. It’s a relative unit, a movement through the queue, a component receiving power, a component processing the power, a component sending out power, not a fixed number of micro or milliseconds:
- Pass-through Components: Such as lights, have a single Input and Passthrough, or Power Out, and process at similar speed. From the moment a light receives power, turns on and sends power out is = 3 Operational Steps. Two lights in series = 6 Steps, three lights = 9 Steps.
- Multi‑Output Devices: Advance one additional step per output stage.
- Splitter: Has 3 outputs and each is served one at a time. From input, dividing the power and the last output sending power = 5 Operational Steps.
- Electrical Branch: Has 2 outputs where Power Out is served first, then Branch Out served second, but has to process how much power to reserve = 4 Steps.
- Memory Cell: Has 2 outputs and must ensure its in the correct state = 4 Steps.
Multi‑Input Devices: Evaluate one input change at a time.
- OR, XOR, AND, and Root Combiner consume 2 operational steps when an input changes state. If two inputs change, they will consume 3 Steps across those changes.
As players begin building their circuits, expanding them to hundreds of components, the server ends up trying to work through thousands of components. Work only advances one step at a time through these queues, so the longer the chains, and more active the devices, will actively increase observable delay.
Power Flow
Power flow is the path electricity takes through a circuit and the order in which it happens. Due to the nature of rustricity, executing one operation at a time, the game establishes a deterministic order. What turns on first, what turns off first, and how multi‑output devices stage their outputs.
An easy way to visualize flow is to build a simple chain of lights. With a Switch feeding four lights in series, turning the Switch on powers Light 1, then Light 2, then Light 3, then Light 4. Turning it off removes power in the same order.
When players start working with components that have multiple outputs, it's very important to know the order in which they output power.
- Electrical Branch: Power Out updates first, then Branch Out. Removal of power follows the same order.
- Splitter: Power Out 1 updates, then Power Out 2, then Power Out 3. Removal follows the same order.
- Memory Cell: When switching from one output to the other, Output always reacts before Inverted Output. If the Memory Cell is in its default state (power coming from Inverted Output) and receives a pulse on Set, the Output will start sending power before Inverted Output stops sending power. If a pulse is then applied to Reset, the Output will stop sending power before the Inverted Output starts sending power. This means that when toggling states, there is a brief moment where both outputs will be active or inactive simultaneously before settling into the final state.
When multi‑output devices are used together, these per‑device rules compose into a predictable sequence. For example, an Electrical Branch connected to Splitters will update its outputs before any downstream Splitter updates its outputs, producing a numbered order through the chain, 1 - 8. This is both the order each output starts and stops outputting power.
The Memory Cell acts similarly to the Electrical Branch. 1 output will react before the other, the only difference is 1 output is losing power while the other is gaining power. Starting in the default position and flipping power from the Inverted Output to the Output, the process flow like this:
1 - Output will send out power first.
2 - Inverted Output will lose power next.
3, 4 and 5 - Will send out power one at a time in order, followed by
6, 7 and 8 - Losing power one at a time, in that order.
The order of operation is the exact same when flipping power back over to Inverted Output from Output.
When players start working with components that have multiple inputs, it's very important to know the order of reception (which input must be powered first). Some devices are agnostic to which input is powered first and others require the main input before any other input before changes will be recognized.
Agnostic to input order:
- Memory Cell - It doesn't matter if the side inputs or the main input gets power first. Once the main input receives power, it will put itself into the correct configuration based on what side inputs are receiving power.
- Counter - Sending power to the side inputs, it will count up or down and clear with no power provided to the main input. Only once power is provided to the main input will the screen turn on to display the number. If the number shown is the same as the target number, power will be sent through.
- RAND Switch - Sending power to the side inputs will Set and Reset the RAND Switch with no power provided to the main input. Only once power is provided to the main input will power pass through or not depending on the state of the switch. The side inputs only react when they are provided with power. Having constant power on them when the main power is removed or received will not affect the switch and it will remain in the same state.
- Blocker - Sending power to the side input before sending power to the main input will block power from passing through. However, if power is sent to the main input first and the very next operation sends power to the side input, it should still block power from passing through. If the delay between sending power to the main input then to the side input is long enough, power will get sent through before it gets blocked.
Requires main input first:
- Conveyor - If players want to use the secondary inputs to turn the conveyor on or off, power must be sent to the main input first. If power is sent to the secondary input first, when the main input receives power, the conveyor will remain in whatever state it was in before the main input lost power.
- Timer - If players want to use the secondary input to toggle the timer on, power must first be sent to the main input. If power is sent to the secondary input first, when the main input receives power, the timer will not toggle on. This is the best component to use when troubleshooting a suspected power flow issue.
- Boom Box - If players want to use the secondary input to toggle the boom box on to play music, power must first be sent to the main input. If power is sent to the secondary input first, when the main input receives power, the boom box will not toggle on and not play music.
- Elevator - If players want to use the secondary inputs to call the elevator to a floor, power must first be sent to the main input. If power is sent to the secondary inputs first, when the main input receives power, the elevator will not be called to a floor.
That covers how power flow is shaped by components with multiple outputs and how some components will function or not based on the order power is received. It was also briefly discussed how flow is structured when multiple components get connected, but this next part is going to further expand on that. What you are looking at is an outdated Nih Core. It still works but you are not going to build this version today because the modern version is better and faster. However, for our purposes here, it can still be used to demonstrate power flow through a complex circuit. One thing to note is the Splitter. I cannot explain why other than the belief that outputs, like the Memory Cells Output, have a higher priority allowing it to interrupt another component's process.
The left side shows the order of operation when switching from battery backup to windmill power.
Main Power:
- The amount of power coming into the Nih Core rises above 106.
- Power is sent out Power Out to the next Electrical Branch.
- Power coming out of Branch Out to the Memory Cell rises to its set amount.
- Power is sent out Power Out to the OR Switch.
- Power is sent out Branch Out to the Splitter.
- Power is sent out to the Large Battery.
- Power is sent out to Set on the Memory Cell.
- Power is sent out the Memory Cells Output.
- Power is sent out to Reset on the Memory Cell.
- Power is sent out to Block Passthrough on the Blocker.
- Power stops coming out of Inverted Output on the Memory Cell.
- Power stops coming out of Power Out on the Blocker.
- Power from the Memory Cells Output is now the power passing through the OR Switch.
- The battery enters its Off state.
The right side is the order of operation when switching from windmill power on to battery backup.
Battery Power:
- The amount of power coming into the Nih Core drops below 106 triggering the flip but must drop below 101 for it to look like the example pictured.
- Power stops coming out of Branch Out to the next Electrical Branch.
- Power coming out of Branch Out to the Memory Cell drops below its set amount.
- Power stops coming out of Power Out to the OR Switch.
- Power stops coming out of Branch Out to the Splitter.
- Power stops coming out of the OR Switch to the Large Battery.
- Power stops going to Set on the Memory Cell.
- Power stops coming out of the Memory Cells Output.
- Power stops going to Reset on the Memory Cell.
- Power stops going to Block Passthrough on the Blocker.
- Power is sent out the Memory Cells Inverted Output.
- The battery enters its On state and sends power out to the Blocker.
- Power stops coming out of the OR Switch.
- Power is sent out the OR Switch to the Large Battery.
- Power is sent out the Blocker to the OR Switch.
- Power is sent out the OR Switch.
Summary
Queue-based execution is central to how Rust processes electrical, water, and industrial systems. Circuit delay emerges from the one-step-at-a-time progression of each queue, while power flow reflects the precise order in which components evaluate their inputs and update outputs. By understanding Operational Steps, output sequencing, and which components require main input first, players can predict and control the behavior of even the most complex circuits.
