Operations

bs_operations has three systems that give factions something to do: a capture-and-hold power station, control points, and mission chains from quest traders. Players read Operations (players).

ensure bs_operations

Migration 044_operations.sql creates the tables. Mission chains are handed out by quest traders (bs_traders).

Power station

Defaults from Ops.Power: it is the Downtown Power Station, 45 m zone, needs 10 players online, 360 minute cooldown, 15 minutes to repair 3 panels, 60 minutes of hold. The faction rank permission to start it is raid (Ops.Settings.startPerm). The member who starts it pays 6 electrical wire, 4 electronics and 30 scrap metal (Ops.Power.cost).

F1 settings

Category Operations. Defaults in brackets.

Group	Settings
Power station	Power station (on), Players online to start (10), Station cooldown (min) (360), Repair time limit (min) (15), Seconds per panel (10), Hold duration (min) (60), Station zone radius (m) (45), Takeover time (s) (45), Minimum hold to win (s) (120), Time in zone for personal reward (s) (180)
Waves	Wave interval (s) (120), Wave size (8), Extra zombies per player in zone (2), Max wave zombies alive (45), Brute chance (0.12)
Rewards	Faction buff (hours) (4), Buff XP bonus (%) (15), Light the winner safezone (on), Winner faction XP (1500), Winner player XP (600), Winner player reputation (40), Winner player cash (400), Loot crate time (min) (20)
Control points	Control points (on), Wake distance (m) (160), Reset when empty (s) (180), Point capture time (s) (60), Garrison size (12), Garrison brutes (2), Defenders (10), Turns hostile after (h) (24, 0 = never), Cache refill (min) (30), Capture XP (300), Capture reputation (20), Capture faction XP (400)
Mission chains	Mission chains (on), Squad scaling (0.5), Squad reward range (m) (250), Retry after fail (min) (10), Heroic chains per day (1), Leave time in defend (s) (25)

Operations editor

F1 > Operations editor shows the live state of the station, the control points and the chains.

• Power station: start it for a faction, or stop it. Panel positions are offsets from the station centre and can be moved here.
• Control points: add one where you stand, edit its label, radius, garrison and brutes, set the owner, disable it. Point defaults are Ops.Points.list in bs_operations/config/config_ops.lua.
• Mission chains: enable, disable, edit or reset a chain. A chain that is not in the config is deleted when you reset it.

Chains are defined in Ops.Chains: faction, tier (story, hard, challenging, heroic), minimum level and reputation, a requires chain, a cooldown, steps (goto, kill, collect, deliver, defend, escort) and a reward. Chains are given by a quest trader tagged with the chain’s faction, or standing in its safezone. Shipped chains: mil_dead_signal, mil_zancudo_ghosts, reb_cut_lines, reb_bolingbroke, civ_medicine_run, civ_doctor, bik_fuel_road, bik_road_kings.

Commands

Staff only.

Command	What
/ops	Status: station phase, number of points, active chains
/ops power start <faction>	Start the power station for a faction
/ops power stop	Stop it

Convoy routes

Convoys (bs_events, off by default, F1 setting) drive along a route. Record your own:

Command	What
/convoyroute start <name>	Start recording. Drive the route in a vehicle: a point is saved every 40 m (500 at most)
/convoyroute stop	Save it. Needs at least 2 points
/convoyroute list	List config and recorded routes
/convoyroute toggle <id>	Turn a recorded route on or off
/convoyroute delete <id>	Delete a recorded route

Routes are stored in bs_convoy_routes (migration 041_convoy_routes.sql). /convoydebug prints the state of running convoys.