Power base stations (PBS)

A PBS (Power Base Station) is a placeable structure in a zone. PBS objects can be connected into a network, which defines territories and enables effects. This is a corporation/structure activity — most actions require the right corporation role.

UI locations follow the client UI overview. The in-client name for "PBS" should be confirmed. Mechanics below are confirmed against the server.

flowchart LR
    subgraph Network["PBS network (one corporation)"]
        R["Reactor\n(fed by fuel items)"] -- "connection" --> DB["Docking base\n(players dock here)"]
        R -- "connection" --> ML["Mill / refinery /\nresearch lab …"]
        R -- "connection" --> TT["Turrets /\narmor repairer"]
        R -- "connection" --> AE["Aura emitter\n(territory buffs)"]
        DB --- MT["Control tower\n(extends the base's reach)"]
    end
    Network --> T["Connected nodes share one territory\n(the corp controls it, sets visibility + standing)"]

What a PBS does

• It is a node in a PBS network.
• Connected nodes form a shared territory the owning corporation controls.
• A network can project effects (buffs/controls) over its territory.
• Some PBS structures can be fed items (fuel) to operate.

Structure families

Every PBS structure comes in small / medium / large tiers. You carry the capsule, research the item (CPRG), and deploy the object — deployment is privilege-gated (see below). The families:

Aura emitter effects

The aura emitter is the main territory buff. Each tier projects one of three level-scaled base bonuses:

• small — sensors lvl1 / engineering lvl1 / industry lvl1
• medium — the same three at lvl2
• large — the same three at lvl3

Sensors extend scanning/recon range, engineering speeds construction, industry speeds production.

The expiring docking base

A special PBS base with a fixed 7-day lifetime (168 h in the content). It cannot be deconstructed — it either expires or is destroyed. The remaining lifetime is announced by an in-game announcer (base channel topic, mail, and MOTD); when it runs out the base is killed and its contents are lost. This is the "rent" model for PBS docking: you don't pay rent, you get a timebox.

Deployment

stateDiagram-v2
    [*] --> Carried: capsule in a container
    Carried --> Researched: CPRG researched (research level met)
    Researched --> Produced: structure produced at the mill / prototype facility
    Produced --> Deployed: deployed in a zone (CEO / deputy / edit-PBS role, construction + blocking radius checks)
    Deployed --> Online: set online (reactor / mining tower fed with fuel)
    Online --> Connected: linked into the network (territory + effects apply)
    Connected --> Online: connection broken
    Online --> Deployed: set offline
    Deployed --> Decommissioned: deconstruction (the expiring base instead expires after 7 days, contents lost)
    Decommissioned --> [*]

• Check deployment — before placing, verify a PBS can be deployed at a position (slope, blocking, and privilege checks). This requires a corporation role (CEO / deputy / edit-PBS).
• Deployment uses the structure's construction radius and blocking radius.

Network & connections

• Get network — view the PBS network you're part of.
• Node info — details of a PBS node.
• Rename a node.
• Make a connection — link two PBS nodes. (Connecting into a network that already has a docking base triggers a specific ownership-transfer case.)
• Break a connection — unlink two nodes.
• Set connection weight — adjust a connection's strength/priority.

Control & state

• Set online — bring a node online/offline.
• Set an effect — configure the effect a node projects.
• Set base deconstruction — flag a base for deconstruction.

Territory

• Get territories — list the territories your network controls.
• Set territory visibility — control whether the territory is visible to others.
• Set standing limit — restrict access by standing.
• Set reinforce offset — adjust reinforcement behaviour.

Feeding

• Feedable info — what a PBS needs and its current feed state.
• Feed items — submit items to power/operate the PBS.

The feedable structures are the reactor and the mining tower. Feeding converts items with an energy value (the corecalories per piece) into the node's core energy buffer, up to its maximum — any player in range can feed a node. What you can burn:

Boosters are the efficient fuel; raw ore is the cheap fallback.

Reimburse

• Get / set reimburse info — configure reimbursement for PBS-related costs.

Logs

• PBS logs — review PBS activity (connections, deployments, etc.).

Practical notes

• This is an officer activity — deployment and most controls need a corporation role.
• Connections define territory — the network you build is what you control.
• Check deployment first — it tells you why a placement would fail (slope, blocking, privileges) before you commit.
• Feeding keeps it running — reactors and mining towers burn fuel items (boosters or raw ore) to hold their core buffer.
• The expiring base is your timebox — 7 days, no deconstruction; plan for the kill.
• Territory visibility & standing let you open or close your zone to others.

 Developer notes: Zone/PBS/PBSCheckDeployment.cs (construction/blocking radius,
 CEO/deputy/editPBS role), PBSMakeConnection.cs / PBSBreakConnection.cs,
 PBSSetConnectionWeight.cs, PBSSetOnline.cs, PBSSetEffect.cs, PBSSetBaseDeconstruct.cs,
 PBSGetNetwork.cs, PBSNodeInfo.cs, PBSRenameNode.cs, PBSGetTerritories.cs,
 PBSSetTerritoryVisibility.cs, PBSSetStandingLimit.cs, PBSSetReinforceOffset.cs,
 PBSFeedableInfo.cs / PBSFeedItemsHander.cs, PBSGetReimburseInfo.cs /
 PBSSetReimburseInfo.cs, PbsGetLog.cs; Zones/PBS/* (IPBSObject, ConnectionHandler). -->