Sal’s Kewl Korner

Home / Documentation / Sal's Kewl Station Alert

Sal's Kewl Station Alert — owner's manual

A live CAD call board on any wall of any station interior, placed by walking it onto the wall rather than typing coordinates. Stations, apparatus rosters and footprints created in game. A demo feed that works before you own a CAD. This manual covers installation, building your fire department, the tones, the lights, the bay doors, the whistle, the voice, every part of the board, run cards, street boxes, hydrants and the run book, and the editable integration hooks, for server owners.

documents resource version 0.0.14-beta↓ PDF

Overview

This is a public beta, version 0.0.14-beta. Everything in this manual is built and in the download, but the resource has not yet been run on a production server. If anything behaves differently from what this manual says, please report it on the Discord.

The CAD dispatches, and the house goes out.

The lights come on, because that is what wakes people. A soft signal starts to rise. Six seconds in the tones drop, the bay doors run up, and the whistle on the roof winds from a low note to a high one and holds it. Then a voice reads the run — Station 1, structure fire, 2400 block Alta Street, Engine 1, Ladder 1. Time out 0347 — and reads it again once the tones have stopped ringing. The television on the dayroom wall pulls that call to the top and says ALERT. Somebody in the kitchen presses the reset at the watch desk and the noise stops, and dispatch can see who it was and how long they took.

That is what this resource is, and every single thing in that paragraph is timing. Nothing happens at the same instant as anything else. A system that fires eight events at once does not feel like a firehouse, it feels like a light switch — so the center of this resource is a small declarative scheduler that you write your own sequences against, and the paragraph above is one of the eight that ship.

Three things make it different from the obvious way of building this:

  • Nothing is streamed and no audio file ships. Every tone, ramp, whistle and bell is a recipe — a description of a sound — synthesized at the moment it is needed. No download, no streamed asset, and no audio licensing question, ever. A board is a rectangle in the world rather than a prop for the same reason: it works in your station interior whoever made it and whenever they made it, including one released after this resource and a bare wall in a station with no television in it at all.
  • Everything about your fire department is created in game. Your houses, their apparatus, the footprint of each building, and where every light, speaker, bay door and whistle is. There is no configuration file we could ship that would be right for your station, because we have never seen it.
  • You ask for a house, never for a device. No caller anywhere — not a CAD, not a web console, not another resource, not a player — can name a door, a doorsystem hash or a lock id. See Setting a station off for why that is the most important sentence in this manual.

It ships showing invented calls, so you can see the whole thing working before you have wired it to anything.

On top of the alerting, the Operations & run cards page runs the fire department itself: run cards and box alarms, out-of-service apparatus and move-ups, who is riding what, station messages, street pull boxes, hydrants, pre-plans, turnout time and the run book. See Operations & run cards.

What ships

All of it. This manual documents behavior that is in the download you have.

AlertingThe sequence engine, eight sequences, rule matching per call, and per-house copies of a sequence. Rotating lights and LED strip. Bay doors with five drivers. The whistle, the house speakers, two-tone paging, the soft-start ramp, and the bell and firehouse gong with the coded tap-out. Voice annunciation, from a phrase bank or as text. The reset point at the watch desk. Night mode. Auto-clear, failed-to-respond retone and escalation, and scheduled tones.
Firehouse devicesUnit status lamps, door buttons and the bay buzzer, door isolation, traffic lights, the rip-and-run printer and the logbook. ox_target and qb-target support. Hiding the MLO's own props.
OperationsRun cards and box alarms, greater alarms, out-of-service apparatus, move-ups, riding assignments, station messages, broadcasts and the banner, street pull boxes, hydrants, pre-plans, turnout time and the run book.
The boardThe call board on any wall, per-board filters, priority colors, the unit strip, live run timers, held cleared calls, explicit CAD link states, texture replacement onto an MLO's own television, a one-line ticker layout, a house logo and an idle page.
Your departmentStations, apparatus rosters and footprints created in game. Two example stations ship, and they are yours to change or delete.
FeedsThe demo feed, which ships enabled, and Sal's Kewl CAD on the same server.
Open seamsTwelve integration hooks, all of them fired, shipping readable and editable outside the escrow. The framework adapter too.

A station with no devices can be toned and nothing will happen. That is the commonest thing to go wrong on a new install and it is not a fault: this resource does not know where your bay doors are until you tell it.

Make a station, walk its footprint, then stand where each light, speaker, door and whistle belongs and add it. stationalert status in the server console names every house of yours that has nothing in it. See Devices.

Everything is built in game, in one panel. /stationalert opens the builder: pick the station at the top, then a page on the left. Nothing about your firehouse needs a command typed into chat, and nothing needs a coordinate typed into a config file.

The commands are all still there, and they are not deprecated — a server console has no panel, a deployment script has no hands, and an owner who has edited html/ and broken the builder still has to be able to run their firehouse.

Requirements

ServerFiveM, any recent artifact
Frameworkqb-core, qbx_core, es_extended, or none at all
DependenciesNone.

The framework is detected at runtime. On a standalone server permissions fall back to the ace alone and everything else works normally — a station television on a standalone server is a perfectly reasonable thing to want.

Optional integrations are also detected at runtime and are deliberately not listed as dependencies. Listing an optional resource as a dependency makes the whole thing refuse to start on a server that does not run it, which is the opposite of optional.

Sal's Kewl CADBridge sals_kewlcadbridge 2.1.0 or newer for the board; any 2.x for tone-outs
Sal's Kewl Dispatch3.14.4 or newer for its pager tone-outs to set houses off. See Sal's Kewl Dispatch
The portalA subscription that includes Sal's Kewl Dispatch, for the Station Alert settings page. The Dispatch resource itself does not have to be running. See Settings on the portal

Installation

  1. Drop the sals_kewlstationalert folder into your resources/.

  2. Add it to your server.cfg:

    ensure sals_kewlstationalert
  3. Give yourself permission to build. Placing boards, creating stations and adding devices change the map, so all three are ace-gated — and nothing grants the ace by default.

    The quickest way, with the server already running and you in game. In the server console:

    stationalert ace        # who is online, and who has it
    stationalert ace 1      # grant it to player 1

    That takes effect immediately. No restart of the server, no restart of the resource, and no reconnecting. If your builder is already open, press RE-CHECK on the banner in it.

    It is kept across restarts, in data/grants.json, so there is nothing to add to server.cfg. Take it back with stationalert revoke 1. If you would rather use server.cfg, this line does the same:

    add_ace identifier.license:YOURS sals_kewlstationalert.admin allow

    A player who is refused a command is told in chat, and the reason and the exact fix (their id and the command above) go to their F8 console and to the server console.

    In game, /stationalert ace tells you your own id and the exact line.

    Why the identifier and not a group? add_ace group.admin sals_kewlstationalert.admin allow works perfectly well — but only if you are actually in group.admin, and being a txAdmin admin does not put you there. That is the single commonest thing to get wrong here, so the command grants straight to your identifier: one line, and it cannot be wrong.

    Skip all of this and the builder still opens, as VIEW ONLY: you can change what an existing board shows, and every build button is dead. It says so, names the ace, and gives you the command.

  4. Restart, and check it came up. In the server console:

    stationalert status

    You should see the demo provider running, a healthy link, a handful of calls, and your stations.

Keep the data/ folder when you update. These five files are your fire department, your placements and your history. They are yours, not ours:

  • data/stations.json — every house, its apparatus, its footprint, and every light, door, speaker and whistle in it
  • data/screens.json — your board placements
  • data/ops.json — run cards, pre-plans, street boxes and crew
  • data/hydrants.json — the hydrants surveyed and added
  • data/journal.json — the run book

A download ships an empty data/, so copying a new version over the old one folder-and-all is how somebody loses their firehouse. Copy the files, or keep the folder aside and put it back.

Your first five minutes

A house that alerts properly, start to finish, without opening a text editor or typing a single command beyond the one that opens the builder.

  1. Stand in your apparatus bay and run /stationalert. The builder opens.
  2. Station & apparatus — + New station. Give it an id (sta1) and a name (Station 1). The id is what everything else stores and never changes; the name is what the board says and can change whenever.
  3. Tick off your apparatus. The checklist is built from the callsigns the feed already knows about, so you are picking from a list rather than typing. Anything not on it yet can be typed in.
  4. Walk the footprint. Press WALK IT. A ring is drawn on the ground and follows you; press SPACE to drop the middle where you stand, Q and E to size it until it covers the building, then ENTER. See Stations for why this one matters more than it looks.
  5. Lights, doors & sound — + ADD A LIGHT, DOOR OR SPEAKER — QUICK FIT. This is the step that makes the house alert. You are walked through five things one after another — a bay rotator, bay speakers, a bay door, the roof whistle and the reset point at the watch desk. Each one shows you what it will do while you position it; walk it where it belongs and press ENTER.
    About ninety seconds. See Devices.
  6. TEST IT. Click any device in the list and press TEST IT. The light runs, the speakers drop the tones, the whistle winds, the bay door opens and closes itself. This is where you find out that the speaker is inside a wall, rather than an hour later.
  7. What happens on a call — TONE IT. Pick the house and set it off for real. Lights, ramp, tones, doors, whistle, and the announcement on the board. Press the reset point in the world, or SILENCE, to stop it.
  8. Place a board. Back in SCREENS, press + PUT A NEW SCREEN ON A WALL. You are handed a live board already showing calls. Walk it onto the dayroom wall, square it up, press ENTER.
  9. Leave it running. The demo feed opens a new call every half minute or so, and with Config.Alerting.Auto on — it ships on — the house tones itself when one of your own trucks is assigned. Press DISPATCH A DEMO CALL if you would rather not wait.

Steps 5 to 7 are the resource. Everything before them is telling it what your fire department is, and everything after is the television on the wall. If you only do one thing after installing this, do QUICK FIT and then TONE IT.

If the board does not appear at all, run /stationalert winding and cycle it — see Troubleshooting.

The builder, and what changed in 0.0.14-beta

/stationalert opens the builder. It is organized around one station at a time: pick the station in the header and every page is about it. Nothing needs saving: a change is saved the moment you make it. No setting in this manual needs a file edited.

OverviewA setup checklist for the station (green is done, amber is missing, each with a button that takes you to the fix), TEST THIS STATION and SILENCE, and the station's id.
ScreensThe call boards on its walls, with a preview, what each shows, its frame and its size.
Lights, doors & soundEvery device in the building.
Station & apparatusIts name, departments, units and footprint.
Tones & voiceWhat it sounds like, and making your own tone sets.
What happens on a callThe alert sequences, and a way to test one.
Operations & run cardsCrew, messages, run cards, street boxes, the run book.

Frames round a screen

A screen on a bare wall wears a frame, picked per screen from fifteen swatches on the Screens page: slim, wide and frameless black, slim and wide silver, white, gunmetal, chrome, fire engine red, navy, wood, brass, industrial with a safety stripe, rugged, and a broadcast monitor with a red stripe. Or no frame. The power light in the frame is green when the screen is on and red when it is off. A screen painted onto the building's own television keeps that television's frame.

The back of a screen

A screen faces the person who placed it. Stand behind one and, if you have building rights, you see a dark panel marked BACK OF SCREEN. Move it, stand where people will read it, press SPACE to turn it to face you, then ENTER. In 0.0.13-beta every screen faced into its wall; screens placed then correct themselves when you update.

Your own tone sets

On Tones & voice, press NEW TONE SET. Name it, pick a style (a two-tone page, one long tone, three short beeps or a hi-lo warble), pick a pitch from the list or type your own frequencies, press PLAY IT, then SAVE. Then choose it under TONE SET for the station. Yours can be changed or deleted; the ones that ship cannot. They are kept in data/tones.json, which no update touches.

With Sal's Kewl CAD

With CAD bridge 2.7.0 or newer the CAD finds your stations by itself and lists them as "in game", with their apparatus. On an older bridge, type the station's id (shown beside its name in the builder) as the station's slug in the CAD.

Stations

A station is a house: a name, the departments that run out of it, the apparatus that belongs to it, and where it is.

Why a station has a footprint

A station record did not originally have coordinates, and the argument for giving it some is not that a record looks tidier with a position on it. It is that four things cannot be answered without one:

  • The turnout clock — apparatus crossing the footprint is what stops it. That is the number a fire department actually cares about.
  • "In quarters" — whether somebody is inside the house, which decides whether they hear the walls or their pager.
  • Acknowledge proximity — who is close enough to silence the whistle.
  • The blip on the map.

A station with no footprint still matches calls by callsign exactly as it would otherwise, and simply cannot answer those four questions. Nothing breaks; the builder tells you what is missing.

The apparatus roster

The roster is how a call becomes this house's call: any call with one of these callsigns assigned to it is yours.

Callsigns are matched loosely — case and punctuation are ignored — because a CAD and a human rarely agree on whether it is E1, e-1 or Engine 1. All three match the same truck.

The builder shows a checklist of the units that exist, read from the feed, rather than a text box. Typing E1 into a game menu is genuinely worse than editing a config file; picking three trucks off a list is genuinely better.

Keeping your houses in version control

Stations can also be listed in Config.Stations, which is the right choice if your server lives in git. Those are locked in the builder: visible and tunable, but not renamable or deletable in game, so nobody can quietly remove a house that the next restart puts back.

The two example stations (Station 1 and Station 2) are ordinary stations from the first start: rename them, change them or delete them in the builder like any other.

Devices: what a house alerts with

A station on its own is a name and a roster. A device is a thing in that station that does something when the house is toned: a rotating light, a run of LED strip, a bay door, the whistle on the roof, the speakers in the bunk room, the reset button at the watch desk.

A house with no devices can be toned and nothing will happen. The activation is accepted, checked and journaled, and then there is nothing to run. stationalert status names every station of yours in that state, out loud, because this is the commonest thing to go wrong.

Making one

Open /stationalert, go to Lights, doors & sound, pick the house, and press + ADD A LIGHT, DOOR OR SPEAKER.

What opens is a palette rather than a form: cards that say what a thing is for. Bay rotator — the red beacon in the apparatus bay. Sweeps, and takes its color from the call. Pick one and you are put in the world holding it; walk it where it belongs and press ENTER.

That is the whole job. A device placed off the palette needs no further editing to be correct — every field it has is already set to something sensible for the thing it is. You can change all of them afterwards, because a template is a starting point and not a type.

QUICK FIT is the button to press on a new house. It walks you through the five things a house cannot alert without — a rotator, bay speakers, a bay door, the whistle and the reset point — one after another, without stopping to reopen the panel between each one.

About ninety seconds of walking round your own station, and the house alerts properly at the end of it.

The preview is the real device

A rotator in the wrong place is invisible until an alert happens, and then it is wrong in front of everybody. So while you are positioning something, it does what it will do:

a lightruns, at its real color, rpm and reach
a stripdraws the run you have walked, with its emitters at the real density
speakers, a belldraw their radius as a ring that follows the ground
the whistlethe same, and it is 300 m across, which is the correct thing to be alarmed by
a bay doordraws the clearance volume it will never close on
a reset pointdraws how close you have to stand to press it

The keys are the ones the board placer uses, because somebody who has placed a board should not have to learn a second tool: WASD to move, Q and E for up and down, the arrows to turn, SPACE to bring it back to arm's length in front of you, SHIFT to go faster, ENTER to place, BACKSPACE to cancel.

TEST IT

The single most useful button in the builder. It makes that one device do its thing, right now, on its own — so nobody places a speaker and finds out an hour later that it was inside a wall.

It is not a real alert: nothing is journaled as a run, nothing dedupes against anything, and it cannot be confused with the house going out. A door is the exception and has to be, because a door is operated by the server: testing one really opens it, and it closes itself on its own timer exactly as it would in a sequence.

Seeing what a house already has

While the Lights, doors & sound page is open, every device in the selected house is drawn in the world, colored by kind, with the selected one showing its reach. A list of nine ids means nothing; nine markers in a bay means everything.

They follow the panel's selection rather than your position, so you can walk out onto the ramp and look back at where the whistle is. The MARKERS button turns them off for somebody taking a screenshot.

A house that cannot alert says so. In amber, at the top of its own list, naming what is missing — and specifically, because "no speakers" is actionable and "misconfigured" is not. With no speakers there are no tones, no ramp and no voice at all.

Where they are stored

In data/stations.json, beside the station they belong to, because a house and the things in it are one thing you back up or copy to your test server. Two files that have to be kept in step is two files somebody will get out of step.

Doing it from a console instead

Every one of these is also a command, and they are not deprecated — see Commands. A server console has no panel, a deployment script has no hands, and a broken html/ must not take the firehouse with it.

The kinds

kindwhat it is
lightA rotator. Any color, any rpm, and either a sweeping beam, a hard flash or a steady lamp. Optionally washes the whole room in its color.
stripLED strip. A run, not a point — see below.
doorA bay door or an apparatus gate. Five drivers — see below.
sirenThe whistle. Outdoor, heard across the town, default 300 m.
speakerHouse speakers. Indoor, default 40 m, so they fill a station and do not leak into the street. The tones, the ramp and the voice all come out of these.
bellA struck house bell, or the big firehouse gong. Quieter than the whistle, and what the coded tap-out uses. Can be rung by hand. See The firehouse gong.
resetThe acknowledge point at the watch desk. Press E and the noise stops.
indicatorA small steady lamp. Lights with the alert, or, bound to one rig's callsign, becomes that rig's status lamp over its bay.
relayFires an event or an export of your own with the alert attached. How you light your own sign or drive something we have never heard of. It is the only kind with no position.
buttonA door button by the bay, and optionally the bay buzzer you hit from the driver's seat.
trafficlightA stop/go lamp in the bay, the street signals held red, or a signal prop of your own held red.
printerThe rip-and-run printer. Prints the run ticket when the house is toned.
logbookThe book at the watch desk. Press E to read the house's runs.

The last four, and the status lamp, are covered in Lamps, buttons, traffic lights and the printer.

Zones

Every device has a zone — bay, bunk, dayroom, anything you like — and a sequence step can name a zone instead of the whole house. It is a field on the device form.

This is how you light the apparatus bay red for a medical without waking the bunk room, which is what most departments actually do. The shipped ems sequence does exactly that.

A strip is a run

That single fact drives its whole design. It has a path, a direction along that path, and effects that travel it.

So placing one is walking it. Pick a strip off the palette and the tool puts you at one end; press SPACE at each corner, BACKSPACE to take the last corner back, and ENTER when you reach the other end. The run and its emitters are drawn as you go, so what you walk is what you get.

The emitters redistribute themselves evenly along the whole path by length, so a run with one long leg and one short one has evenly spaced lights rather than a cluster at the corner. MOVE re-walks a run you want to change.

Six effects: solid, flash, pulse, chase (a lit segment traveling the run), wipe, and alternate — two colors in blocks, which is the red-and-white bay strip every apparatus floor in America has.

The emitter budget is capped and the cap is enforced when you author, not when you run. A bay wrapped in a four-hundred-emitter strip is a support ticket that says "this resource tanks my FPS", and that is a ticket worth designing out.

Bay doors

The only device here that can ruin somebody's night, so it has the strictest rules in the resource.

Place the door in the doorway, then pick how it opens from the dropdown on its form. Drivers are detected at runtime and none of them is a dependency, so the resource never refuses to start on a server that does not run your doorlock.

driverhow it opens
nativeThe game's own door system, for MLO doors registered with it. Needs the doorsystem hash.
ox_doorlockIts own export. Needs the lock id.
qb-doorlockIts own event. Needs the lock id.
poseA plain object moved between a recorded closed position and a recorded open position. This is the one for sliding gates and roll-ups in MLOs with no door entry at all, which is most of them.
eventFires an event you name. The escape hatch for the one custom gate script you wrote.

The form then asks for whatever that driver needs — a doorsystem hash, a lock id, or nothing — and shows no rows for the drivers you did not pick.

The pose driver has nothing sensible to type, so you record it instead. Leave the door shut and press RECORD CLOSED; open it and press RECORD OPEN. The form says which of the two is still missing until both are set.

Set the object's model as well when a bay has more than one identical roll-up, or they all find the same object.

The rules doors follow

  • A door never closes on an entity. The volume underneath is checked first, from the server's own entity list and from the clients near the door. If something is there the close waits and retries, and past the give-up time the door is left open and it is logged. Crushing somebody's ladder truck is worse than an open door, every time.
  • Doors close themselves. On autoCloseSeconds, default 90; when the alert clears; and when the resource stops, so a restart never leaves a county of bay doors standing open.
  • Server-authoritative, one writer. There is no event a client can send that opens a door. Two drivers have to be applied on the client because the natives they use only exist there, but applying a state the server already decided on is not the same as deciding it.
  • Rate limited per station, independently of the alert path, so a misbehaving CAD cannot cycle a bay door at 4Hz even when every other check has passed.

TEST IT on a door's form opens it for real, which is the fastest way to check you wired one correctly. It closes itself on the timer on the same form. From a console, /stationalert doors <station> open|close does the same.

A door can also be isolated for maintenance, so nothing moves it. See Door isolation.

The firehouse gong

The big old bell on the apparatus floor: low, long and clashing. It is a bell device with the gong profile. Pick gong as the bell's PROFILE in the builder, and press PLAY next to it on the Tones & voice page to hear it first. The recipe is Config.Audio.Bells.gong.

Ringing it by hand

Walk up to the bell and press E (or use your target menu). Each press is one strike, and a bell will not take another press for a couple of seconds, so nobody can hammer it.

Who may ring it is set per bell, in the builder's WHO MAY RING IT BY HAND field, or for every bell in Config.DeviceDefaults.bell.manual:

quartersAnybody standing inside the station footprint, and the fire and EMS jobs. The default — a bell on the wall of a real house has no lock on it
jobThe operating jobs in Config.Access.Jobs only
anyoneAnybody at all
offNobody. Only sequences ring it

How close you have to stand is Config.DeviceDefaults.bell.reachMeters, 1.8 m by default.

Ringing it from outside

/stationalert bell sta1           -- three strikes
/stationalert bell sta1 5         -- five strikes
/stationalert bell sta1 5-5-5     -- a coded signal

This rings every bell in that house. It needs a fire or EMS job or the ace. 5-5-5 is the line-of-duty-death signal, the one coded signal every American firehouse still knows. Any code works the same way: 2-3 taps box 23.

Another resource can ring it with the RingBell export — see Exports.

A gong you can see swing

The gong works with no prop at all: it is heard, not seen. To have a bell you can see that swings on every strike, give it a model:

  1. Stream the model yourself, the usual way. Put it in a stream/ folder in a resource of your own, and start that resource before this one. A resource of your own is recommended, so an update to this resource never touches it. No prop ships with this resource.
  2. In the builder, select the bell and type the model name into PROP MODEL. To use it for every bell, set Config.DeviceDefaults.bell.model instead.

The prop is spawned where you placed the bell, and it swings once per strike, in time with the sound — whether the strike came from a sequence, a hand on the bell, the command or the export.

A model that is not streamed is skipped with one line in F8, and the bell keeps ringing. Printers and street boxes take a model the same way (Config.PullBoxes.Model for the boxes).

Lamps, buttons, traffic lights and the printer

Every one of these is placed the same way as any other device: Lights, doors & sound, + ADD A LIGHT, DOOR OR SPEAKER, walk it into place, ENTER. Their settings are on the device's form, and their defaults are in Config.DeviceDefaults.

Unit status lamps

Give an indicator a UNIT (a callsign such as E1) and it becomes the lamp over that rig's bay:

greenIn quarters
redOut on a call
amberOut of service

A status lamp is always on. It follows the unit, not the alert, and its COLOR setting is ignored while it is bound. Leave UNIT empty for a lamp that only lights with the alert. Indicator lamps are steady by default.

Door buttons and the bay buzzer

A button is bound to doors in the same house — tick them on its form, or tick none to mean every door in the house. Its WHAT IT DOES field is toggle (open if closed, close if open), open only, or close only. Press E at it.

Tick Also a buzzer, from the driver's seat and the same doors open from inside a vehicle within BUZZER REACH of the door (25 m by default), on the Station bay door buzzer key.

The buzzer key ships unbound. Each player sets it themselves, in the game's key bindings under FiveM. Tell your members it exists.

Buttons and the buzzer are for the fire and EMS jobs only. A bay door is the one device in this resource that can hurt somebody, and a civilian wandering into the bay is exactly who should not be opening it. They never reach a door in another house, and they never move an isolated door.

Door isolation

For maintenance. On a door's form, set ISOLATION to Isolated CLOSED or Isolated OPEN. The door is held where it was put: no alert, button, buzzer or CAD moves it until you set it back to In service. An isolated door does not close itself on a timer, and the isolation survives a restart.

Traffic lights

One trafficlight device, in three kinds. Pick one in its KIND field:

Stop/go lamp in the bayRed while its doors are closed or moving, green only once every door it watches is fully open. Tick the doors on its form
Hold the street signalsThe game's own traffic signals within REACH of the device (35 m by default) are held red while the rigs pull out. Place it at the intersection in front of the house
A signal of your ownAn addon signal prop you name in SIGNAL MODEL, placed anywhere and held red the same way

The street holds are started by a trafficlight hold step in a sequence and last HOLD seconds (45 by default) unless the step says otherwise. The shipped default, fire-structure, ems and box-alarm sequences all have one.

The rip-and-run printer

When the house is toned, the printer chatters and holds the run ticket: the call, the box, the units, the riding list, the pre-plan and the nearest hydrant. Press E at it to rip the ticket and read it. Anybody may. The ticket stays until the run ends.

Give it an optional PROP MODEL of your own and a sheet of paper appears on it while a ticket is waiting. The printer is started by a printer print step, which the shipped default, fire-structure, ems and box-alarm sequences already have.

The logbook

Put a logbook on the watch desk. Anybody can press E at it to read the house's runs. See Turnout time and the run book.

ox_target and qb-target

If ox_target or qb-target is running, the bell, door buttons, street boxes, the printer and the logbook get target options. Without one, they use the E prompt. It is detected at runtime and is never a dependency. Config.Target chooses: 'auto' (the default), 'ox_target', 'qb-target', or 'none' for the E prompt always.

Hiding the MLO's own props

For a prop in the way of a board or a door — the MLO's own television, a vending machine, a sign. On the Operations & run cards page, under HOUSE LOOK, press HIDE AN OBJECT, aim at it in the world and confirm. It is hidden for everybody, only near that house. UNHIDE next to it in the list puts it back. This needs the ace.

Sequences: what happens, and when

A sequence is a list of steps, and each step has an offset in seconds from the moment the house is toned. That is the whole idea.

['fire-structure'] = {
    match = { agency = 'fire', priority = { 1, 2 } },
    steps = {
        { at = 0.0,  device = 'light',   action = 'on',      color = 'priority' },
        { at = 0.0,  device = 'strip',   action = 'flash',   color = 'priority' },
        { at = 0.0,  device = 'screen',  action = 'alert' },
        { at = 0.0,  device = 'speaker', action = 'rampup',  profile = 'gentle' },
        { at = 1.0,  device = 'printer', action = 'print' },
        { at = 3.0,  device = 'door',    action = 'open' },
        { at = 3.0,  device = 'trafficlight', action = 'hold', seconds = 60 },
        { at = 6.0,  device = 'siren',   action = 'blast',   seconds = 20, blasts = 1 },
        { at = 6.0,  device = 'speaker', action = 'toneout', tones = { 'STATION1' } },
        { at = 14.0, device = 'speaker', action = 'announce' },
        { at = 24.0, device = 'speaker', action = 'announce' },
    },
},

They live in Config.Sequences. Eight ship, and they are meant to be edited rather than admired:

defaultRequired. Runs when nothing else matched. Deliberately modest: lights, a ramp, tones, doors. No whistle — a house that blows the town whistle for a lift assist gets complaints.
fire-structureA working fire, priority 1 or 2. Everything, including the whistle and the voice twice.
box-alarmA street box was pulled, or a run card toned the house for a box. The box number is tapped out on the bell first — four, one, two for box 412 — then the house goes out like a working fire. Matches no call on its own; street boxes use it by name, and run cards can (Config.RunCards.Sequence).
fire-serviceFire, priority 3 and below. No whistle.
emsThe bell instead of the whistle, the soft tones, and the lights only in the bay.
policeThe board and a light. Nobody annunciates a traffic stop.
testWhat /stationalert test runs. Fifteen seconds, and it exercises every kind of device so you can hear that they are all wired.
whistle-onlyOne blast. What a scheduled noon whistle uses.

Five things to know before you edit one

  1. A step names a device KIND, not a device. device = 'light' means every light in the house being toned, so one sequence works in a station with four rotators and in a station with one. Narrow it with zone = 'bay', or with only = { 'sta1.door.bay1' } when you really do mean the one door.
  2. Matching is first match wins, and default must exist. If you delete it the resource puts a minimal one back and says so loudly in the console, because an unmatched call has to alert something. Silence is the one failure a fire dispatch cannot have.
  3. Offsets are seconds, they are decimals, and they may repeat. Two steps at the same at happen together and that is normal.
  4. A step that fails is just a step that failed. No step blocks another, none retries, and none can abort the sequence. Your doorlock resource being down means the doors do not open. It does not mean the tones do not drop.
  5. The whole timeline is sent at once and every client runs its own clock against it. That is what makes a player who walks into the bay eight seconds in join the sequence already in progress: they see the lights that came on at zero, they do not hear the tone-out that finished at six, they hear the whistle that is still blowing at the point it has reached, and they get the voice that is still to come. A client that hitches for 400 ms cannot hear the whistle after the voice.

Which one runs

Rules are checked most specific first, not in the order you wrote them — a Lua table has no order, so ordering it by how specific each rule is makes the answer the same on every restart. A rule naming a call type beats one naming a priority, which beats one naming an agency, which beats one naming only a station. Ties break on the name.

A rule can match on agency, priority, codes (your CAD's own call-type codes, which is the most precise rule there is) and stations. Set priority = <number> on the sequence itself to force the order by hand.

The What happens on a call tab shows all of this. One card per sequence with its steps drawn on a timeline, its match rule in the words the config uses, and how long the whole thing runs.

The timeline is the reason the tab exists. Reading a Lua table of offsets does not tell you that the whistle comes eight seconds after the lights; a bar chart tells you in a second, and it draws the two steps that genuinely last — the ramp and the whistle — at their real length.

Sequences are made and changed in the builder, on the page called What happens on a call:

  • NEW SEQUENCE makes one as a copy of one that works.
  • WHEN IT RUNS on a sequence's card says which calls it is for: a department, some priorities, some dispatch codes, or only when picked by name.
  • CHANGE ITS STEPS changes it for every station. A sequence that ships can be put back with UNDO MY CHANGES.
  • One station can have its own timing: see Timing one house.

Yours are kept in data/sequences.json, which no update touches.

The same tab has TONE IT: pick a house, optionally force a sequence by name, and set it off. It goes through the same one funnel a CAD does, so it is rate limited, journaled and hooked identically — the builder gets no exception. From a console, /stationalert sequences prints the same list and the match order.

Every action

kindactions
light, indicatoron, off
stripon, flash, off
dooropen, close
sirenblast — with seconds, blasts, gapSeconds, profile
speakerrampup (a profile), toneout (a list of tones), announce, say (your own text), off
bellring (strikes, gapSeconds), tap (a code: { 2, 3 } taps 2-3, and 'box' taps the call's own box number), off
screenalert, normal
trafficlighthold (seconds) — signals held red while the rigs pull out; release
printerprint — the rip-and-run ticket
relayfire
alloff — the panic button, in sequence form

Sequences are validated when the resource starts, step by step. A step that names a device kind that does not exist, or tells a door to blast, is dropped with a console line naming the sequence and the step number — and the rest of that sequence still runs. A typo in your door step must not cost the house its tones.

Timing one house

Houses differ. The volunteer house opens its doors later; the one with the long bay lights the strip first. Rather than a near-copy of a sequence per house, you can give one house its own copy of a sequence and move its steps in game.

  1. Open /stationalert, go to What happens on a call, pick the house, and press EDIT THE PICKED SEQUENCE FOR THIS STATION on the sequence you want to change.
  2. Change the steps. Each row is a time in seconds, a device kind, an action, and options written as words: zone=bay, tones=STATION1, profile=steam, seconds=12, blasts=3, strikes=3, code=2-3 or code=box, text="anything". + STEP adds one; × removes one.
  3. Press PLAY HERE. It runs the sequence to you alone, against that house's real devices, so you hear and see what the house will do. Doors stay put during PLAY HERE, and relays do not fire.
  4. Press SAVE FOR THIS STATION. A step with a mistake in it is refused by name; the rest are kept.

The copy wins for that house only. Which calls run the sequence is still decided by the match rule in the config files; the house only owns the steps. The copy is stored in data/stations.json with the house.

USE THE SAME AS EVERY STATION throws the copy away and the house goes back to the sequence in the config files. Editing a house's copy needs the ace.

A house's copy is checked like any other sequence. If every usable step has been removed from it, the house falls back to the config sequence and the console says so. A house never goes silent because somebody emptied its timeline.

Tones, the ramp, the whistle and the bell

No audio files ship with this resource and none are streamed. Every sound below is a recipe in Config.Audio — a description of a sound — synthesized in a browser page at the moment it is needed.

Three things that buys you: nothing to download, no "this resource is too large" warning, and no audio licensing question, ever. It is also why you can make a tone set of your own in the builder in a minute.

The tones

Two-tone paging, in the shape every American firehouse knows: an A tone for a second, then a B tone held for three. The numbers that ship are real Motorola Quick Call II frequencies.

STATION1, STATION2Two-tone paging. Make your own in the builder: see below
ALLCALLOne long tone, which is what a county drops when it wants every house listening
ALERTThree short attention beeps, before a voice announcement
SOFTA quiet two-tone, for EMS at three in the morning

The ramp

A rising signal over three to eight seconds that wakes a sleeping house without the cardiac event. It is its own thing and not a volume fade over the tones: the pitch does not move, the level does, and a pulse rate makes it insistent without making it loud. It stops the moment the tones drop.

Three profiles: gentle (six seconds, pulsing), fast (two and a half), and hum (eight seconds, no pulse at all — the one people ask for after a week of the pulsing one).

The whistle

The old-time fire whistle, and a different animal from the house speakers: outdoor, heard across the town, with a long mechanical wind-up and a longer coast down.

The coast down is the part every cheap imitation gets wrong, so it is the part modeled most carefully. The default is modeled on a recording of a real town fire siren. Like the motor in a real siren, it spins up fast and levels off at the top (668 Hz) in about four and a half seconds. It holds there, then coasts down against air drag, dropping pitch fast at first and then lingering, to about 280 Hz in ten seconds. It gets quieter as it slows. That lingering bottom end is the whole sound of a fire whistle.

steamThe town fire siren: a real siren's tone, wind-up and coast down. The default
electricThe same motor model, higher and quicker
airhornA blast, not a wind-up
euroTwo-tone hi-lo

Blast patterns are part of the step: seconds, blasts, gapSeconds. Three blasts means the box, which is how a real whistle signaled.

The bell, and the coded tap-out

A struck bell — several inharmonic partials that decay at different rates, which is why it sounds like metal rather than like a sine wave.

action = 'tap' with code = { 2, 3 } strikes twice, pauses, and strikes three times: box 23. That is how a house was told where the fire was before anybody had a radio, and it costs nothing to keep. code = 'box' taps the call's own box number, which is what the box-alarm sequence does.

The gong profile is the big old firehouse bell, and a bell can be rung by hand. See The firehouse gong.

Hearing them before you choose

The Tones & voice tab lists every tone set, ramp, whistle and bell this server has — ours and any you have added — each with a name, a sentence saying when you would want it, and a PLAY button.

Choosing a tone set out of a dropdown you have never heard is guessing. Pressing a button next to each one and picking the one you like is not. It plays for the person who pressed it and nobody else.

What one house sounds like

A sequence step has to name some tone set, because it has to say something. A house that has chosen its own overrides it.

That is on the same tab: pick a station, and set its tone set, its whistle profile, and whether it annunciates at all. Any of the three can be left as "whatever the sequence asks for", which is the default and what every station did before this existed.

This is the setting that makes one sequence work in four stations. Without it, a department with four houses needs four nearly identical sequences whose only difference is which pair of frequencies drops and which whistle blows — and that is how a config file becomes something nobody maintains.

How loud, and to whom

Every device has a radius. Inside it, how loud a sound is for one player is worked out from the distance, whether they are indoors, their own volume setting, and night mode — and it is re-worked while the sound plays, so somebody driving past the station during a whistle hears it swell and fade.

Indoors a whistle on the roof is muffled, not absent. That distinction is most of the feel of the thing.

The player's own volume

A slider at the top of the Tones & voice page, or /stationvolume 40.

No permission and no server round trip, because it is their ears and nobody else's business. It is remembered on their machine and applied to whatever is already playing, so turning the whistle down while the whistle is going turns the whistle down.

Night mode, which ships ON

Between 22:00 and 06:00 game time, the level is capped and every ramp becomes the gentle one. Config.Alerting.NightMode.

A full-volume tone-out at 0300 is a genuine complaint on a server with a night shift. Some servers will switch this off, and they should have to choose to.

If you already have an audio system you would rather use, open integrations/hooks/client/audio.lua. Return true and you own that sound; the built-in synthesis stays quiet for it. It is per sound, so you can put the tones through your own player and leave the whistle and the voice to us.

Voice annunciation

"Station 1, structure fire, 2400 block Alta Street, apartment building, Engine 1, Ladder 1, Battalion 1. Time out 0347."

Read twice, the second time after the tones have stopped ringing. The address is read the way a dispatcher reads one — "2400 block Alta Street", not "two thousand four hundred Alta".

Two tiers you can use, and it falls down them on its own

tierwhat it iswhat it costs
bankThe phrase bank: short clips in audio/bank/, assembled from slotsRecording or buying about 120 clips, once
textNo audio. The announcement is written on the board and shown on screen to anybody in quartersNothing

Config.Voice.Tier ships as 'auto', which uses the best one available. With nothing configured you get the text tier.

The words always arrive. With no clips the announcement still reaches every board in the station and every player inside the footprint — it is read rather than heard. That is a supported configuration, not a broken one, and it is also what makes the annunciation work for a player who plays with the game muted.

The phrase bank

No clips ship, and that is deliberate rather than lazy: a voice is a licensing question, and the one we shipped would be the one every server sounded like. audio/bank/ is yours.

The announcement is built as a sentence and as a list of slots, and the bank plays the slots back to back:

STATION_1  TYPE_STRUCTURE_FIRE  DIGIT_2 DIGIT_4 DIGIT_0 DIGIT_0  BLOCK_OF
STREET_ALTA_STREET  UNIT_E1  UNIT_L1  TIME_OUT  DIGIT_0 DIGIT_3 DIGIT_4 DIGIT_7

It sounds like a concatenative annunciator from 1994, because that is exactly what it is. That is the aesthetic, not a compromise. A firehouse annunciator has never sounded smooth and should not start now.

Record the ten digits first — every address and every time out comes out of those, so ten clips gets you something usable. The full vocabulary, the file format and the recording notes are in audio/README.md in the download. A missing clip is skipped rather than an error, and a street the bank has never heard of falls back to "at the reported location", which is what a real dispatcher says when they cannot read the cross street.

Hosted text to speech

No AI keys of your own. Communities can't use their own OpenAI, Anthropic or other AI keys with our scripts, so the hosted text to speech tier (Config.Voice.Tier2) stays off. Leave it as it ships. AI usage is included in the base subscription fee for limited amounts and subject to fair use terms. AI pricing and policies may change with at least 30 days' notice to current subscribers.

The phrase bank and the text tier are what a server runs. The tones never wait for anything. Whatever the voice is doing, the tones drop on time.

What gets read, and for whom

Config.Voice decides how many times it is read and how far apart, and whether the station, the call type, the location, the units and the time out are each included.

Config.Voice.Agencies is per agency, and police ships false. Nobody annunciates a traffic stop.

Silencing a house

A whistle nobody can shut off is not a feature. It is a support ticket at 4am.

The reset point

Put one at the watch desk:

/stationalert device add sta1 reset

Stand at it during an alert and press E. The whistle stops, the ramp stops, any announcement still to come is canceled — and the lights and the board stay on, because the run is still running and a house that goes dark the moment somebody is awake is a house nobody can find their boots in.

Who it is stamped as, and how long they took, goes in the journal and to your acknowledge hook. That second number is the one a chief actually cares about.

Acknowledging is deliberately the most open action in the resource. No job and no ace: anybody physically at the station can shut the noise off. Somebody standing in the kitchen at 0300 should not need a permission, and being there is the control — which the server checks again for itself rather than believing the client.

What the reset stops is configurable, under Config.Alerting.Acknowledge. It can also close the doors and kill the lights if that is what your department does.

Before you have placed one

/ack works for anybody standing inside a station's footprint. Leave it on until the reset points are in.

An alert always ends

Three ways, and one of them cannot fail:

  • The call closes. Config.Alerting.ClearWithCall, on by default, and almost always the right moment.
  • An admin ends it. /stationalert silence sta1 from the console. Different from acknowledging, and journaled differently.
  • The clock runs out. Config.Alerting.AutoClearSeconds, default 180. The backstop that means there is always an end.

When an alert ends, the lights go out, the boards go back to normal, and any bay door that alert opened is closed.

Toning it again

One alert per house at a time. A second one is a retone: the first ends and the new one begins, rather than two timelines playing over each other in the same building. The board says RETONE.

A retone does not slam the bay doors shut and run them back up — the new alert adopts the doors that are already open.

Failed to respond

Nobody acknowledged and nothing left the house, so tone it again. Config.Alerting.Retone, off by default: a department that does not want it finds it infuriating, and one that does will turn it on within a day.

It retones Times times, AfterSeconds apart, and then, with Escalate on, tones the next house. See Failed-to-respond escalation.

The noon whistle

Real towns blow the whistle at noon whether or not anything is on fire. It is a test of the whistle and the loudest piece of world-building in this resource. Config.Schedule, off by default, in game hours.

Placing a board

You place a board by walking it onto the wall. There is no coordinate to type and no measuring to do.

W A S DMove it around
Q ERaise and lower
Arrow keysRotate. Tap for coarse, hold for fine
SPACEAim it at me — the fastest way out of a mirrored board
[ ]Narrower and wider
; 'Shorter and taller
SHIFTHold for four times faster
ENTERPlace it
BACKSPACECancel

What you are aligning is the real board. The preview is not a placeholder — it is a live screen running through the real renderer, showing real calls at the real size. What you line up is exactly what you get.

The one thing that confuses everybody

A board's heading is the direction somebody stands to read it, not the direction the board's own face points. Get it backward and the board renders mirrored, readable only from behind the wall.

You will never need to think about this, because SPACE aims the board at you and that is almost always what you want.

Sizing with a keyboard instead

Some server builds cannot read the bracket and quote keys. If yours cannot, the placer says so, and you set the width and height numerically in the builder panel afterward — which is easier anyway for getting a board to exactly 1.60 m.

Boards kept in a config file

Every board is placed, changed and removed in the builder.

What a board shows

The filter is the product. A firehouse does not want the whole county's traffic stops on its dayroom wall.

Every board decides for itself, so the one in the dayroom and the one in the apparatus bay do not have to agree.

The important setting

agency Everything your station's departments are running, with your own runs pulled to the top and highlighted. The default, because a board that is blank most of the evening is a boring wall.
assigned Only calls this house is on. Truer to a real alerting board. The screen shows IN QUARTERS the rest of the time.
all Everything in the CAD, police included.

The rest

  • Agencies. Only these call kinds. Empty means whatever the station's own departments are.
  • Priorities. Only these. Empty means all of them.
  • Rows. How many calls fit before the board stops listing and says +3 more. Depends how big your board is, so it is per board.
  • Hold cleared. How long a closed call stays on the board, grayed and marked CLEARED, so somebody walking in from the bay sees that the last run just cleared. Zero hides them immediately.
  • Unit strip. Your apparatus along the bottom, in the order the station lists them — E1, L1, BC1, and not alphabetically, because that is the order a firehouse thinks in. A truck the CAD does not know about still appears, as unavailable: a missing truck is information.

When the CAD link drops

The board keeps showing the last calls it had and marks itself: the header goes amber and says CAD LINK SLOW, then NO CAD LINK.

It never blanks itself. A display that goes empty when its link drops is a display claiming there are no calls, and that is the one wrong answer a status board must never give.

What else the board shows

Besides the calls, a board carries the operations side of the house when there is something to show:

Ticker, logo and idle page

The ticker layout

For a screen over a doorway or along the watch desk. Select the board on the Screens page and set its LAYOUT to A one-line ticker. It scrolls the same runs on one line.

Give a ticker a long, thin size, about eight times as wide as it is tall. The filter settings work the same as on a full board.

A logo in the header

On the Operations & run cards page, under HOUSE LOOK, pick the house and paste an image address into LOGO. It must start with https:// or nui://. The logo shows in the header of every board in that house and on the logo idle page. A roughly square PNG with a transparent background looks best.

The idle page

Under the same heading, WITH NOTHING TO SHOW decides what the boards in that house show when there are no calls:

boardThe normal board. The default
logoThe house logo, large
clockA clock

Every idle page still shows the banner and the house's turnout averages for the shift and the week.

The logo and the idle page are set per house and need the ace. A station kept in a config file is locked here, like the rest of its settings.

Painting onto the MLO's television

If your station interior has a television whose texture can be replaced, the board can be painted onto that — real bezel, real glass, nothing to line up. It is better when it works.

It is an override rather than the default because it needs the model's texture names, which are specific to that MLO and have to be found or shipped as a preset. Pick one from the list in the builder, or name the model, texture dictionary and texture directly.

Three things to know before you use it

  1. It is per model, not per prop. The swap applies everywhere that model appears on the map. Two stations whose interiors use the same television model will show the same board — whichever claimed it first. The answer is to use a rectangle for one of them.
  2. It cannot report failure. A wrong texture name fails silently, so the checks are done beforehand and anything that does not pass falls back to drawing a rectangle.
  3. An MLO update can break it. A renamed texture would blank the screen. It falls back instead.

The fallback is the point. Keep the position and size on a replace-mode board, because that is what it draws if the texture is not there. A misconfigured override costs you a bezel, never the board.

Adding a preset

Presets live in data/mlo-presets.lua and adding one is a data change, not code. You need three names: the model, its texture dictionary, and the texture on the screen face. OpenIV or CodeWalker on the MLO will tell you. If you find working names for a popular station MLO, send them over and they will ship for everybody.

Where the calls come from

The demo feed, which ships enabled

Config.Feed.Provider is 'demo' out of the box. It invents plausible fire and EMS traffic: real dispatch codes, a believable mix that is mostly medical with the occasional working structure, and units that are assigned, go en route, arrive on scene and then clear.

This is a supported feature, not a stub to be deleted. It is how you evaluate the resource before you own a CAD, how you check a board is lined up before wiring anything to it, and how you shoot a video of your station without waiting for a real structure fire.

It assigns your apparatus, read from your stations, so the "this house's run" highlighting works without you configuring anything.

NewCallEveryA new call opens somewhere in this window, in seconds
CallLifeHow long a call lives before it clears
MaxCallsNever more than this at once, so it looks like a firehouse and not a disaster movie
StartWithHow many are already running at boot, so a board is never blank the first time somebody walks past

Sal's Kewl CAD

Set Config.Feed.Provider to 'cad'. That is all — it reads the CAD on the same server, with no keys and no URLs.

It finds either half of the family: sals_kewlcadbridge (CAD 2.x, where the in-game resource talks to a hosted service) or sals_kewlcad (1.x). The console says which one it found, because that is the first question worth asking when a board is empty on a server that has both installed.

Calls arrive when they happen, pushed by the CAD rather than waited for. The poll stays on as a backstop, because one missed push would otherwise leave the board wrong until the next call came in. You can raise PollMs once you are event-driven, and stationalert status says which of the two is actually happening:

cad       link up, board pushed by event, 3s old

If the CAD is not running at all, the resource says so once and falls back to the demo feed rather than showing an empty wall.

If the CAD is running but too old, the board goes to NO CAD LINK rather than back to the demo feed. That is deliberate, and it is the opposite of the other fallback: on a live server a wall confidently showing invented calls is worse than a wall admitting it has nothing. The console names the export that is missing.

No feed at all

Set Config.Feed.Provider to 'none'. The board stays empty and the feed tones nothing. A pulled street box still opens its own call.

This is how you turn the demo off on a server with no CAD. Setting 'cad' there does not do it, because a CAD that is not running falls back to the demo feed.

Departments the CAD knows and this resource does not

A CAD deals in more kinds of department than a firehouse does — sheriff, state_police, whatever your server invented. A call whose kind matches none of your stations' departments shows on boards set to "every call in the CAD" and tones nothing.

That is on purpose. Mapping an unknown department onto a default would mean a firehouse woken at three in the morning for a highway stop, which is worse than a call no board claims as its own. Config.Feed.Cad.AgencyMap is where you say that sheriff means police to you; it ships with the obvious three already in it.

Letting the CAD tone a house

Dispatch presses the button in the CAD and the firehouse goes out. Pressing it again for the same call retones the house. On by default; set Config.Feed.Cad.AcceptToneOuts = false if you would rather only tone houses from in game.

A tone-out from the CAD goes through exactly the same checks as every other way of setting a house off — both rate limits, the dedupe, your authorize hook, the journal. It is not a side door, and a CAD stuck in a retry loop hits the same limit a misbehaving script would. See Setting a station off.

The acknowledgment goes back the other way: when somebody presses the reset at the watch desk, the CAD is told who it was and which units are on the call, so a dispatcher watching the board sees the house answer. That happens in integrations/hooks/server/acknowledge.lua, which is the one shipped hook that actually does something — so if you want to send something else, or nothing, it is one file and it survives an update.

Which house did the CAD mean

The CAD identifies a station by its own id; this resource identifies one by the id you typed in the builder. Three ways of joining them up, tried in this order:

The slug The CAD gives every station a slug, and it is deliberately the same shape as a station id here. Name the house sta1 in both places and there is nothing to configure. This is the way it is meant to work.
A map you write Config.Feed.Cad.Stations, for when they do not match. Keyed by the CAD's slug or its uuid — paste whichever one its owner panel showed you:
Stations = {
    ['north-side']   = 'sta1',
    ['9f1c2a44-...'] = 'sta2',
}
The name Off by default. Config.Feed.Cad.MatchByName = true matches the CAD's station name against yours.

Why matching by name is off. Two houses called "Station 1" will exist on somebody's server — one per agency is a completely normal way to name them. Toning the wrong firehouse is the worst thing this resource can do, so you have to ask for this, and even switched on, a name matching two houses is refused rather than guessed at.

The one mistake neither system can catch. Nothing stops a CAD slug that is perfectly valid from colliding with a different station's id here: the CAD has a house slugged sta1, you have a sta1, and they are two different buildings. Both sides think they agree and the wrong house goes out.

That is inherently your mapping rather than anything either resource can detect. When you set a slug in the CAD, check it against the station ids on your Station & apparatus page.

A tone-out that matches nothing is refused and said out loud, naming the station and the slug it arrived with. A tone-out thrown away in silence is a firehouse that did not go out with nobody knowing why.

A tone-out that arrives before its own call reaches the board still works: the call is built out of the tone-out itself rather than refused.

Polling and staleness

PollMsHow often the provider is asked. The feed only sends clients what changed, so a short poll is cheap. 2000 is the default.
StaleSecondsNo answer for this long and the board goes amber
DeadSecondsPast this it stops claiming the calls are current

Sal's Kewl Dispatch, and no dispatcher on duty

Most servers have nobody on the dispatch desk most of the time. The AI dispatcher, the Public Safety Simulator, and Sal's Kewl Dispatch's own fire and 911 handling do the work, and the station has to go out anyway.

It does. Every pager tone-out Sal's Kewl Dispatch sends sets off the house it was for, as well as the pagers: speakers, lights, bay doors, the board. It does not matter who sent it:

  • a dispatcher at the console or the in-game desk
  • the AI dispatcher
  • the Public Safety Simulator paging a fire or EMS call
  • Dispatch's fire script adapter, its unanswered-911 fallback, or its CAD pull

This works whatever Config.Feed.Provider says, CAD or no CAD. It needs Sal's Kewl Dispatch 3.14.4 or newer. With no CAD supplying the board, the call goes on the board too, for Config.Dispatch.BoardMinutes.

Which house goes out

1. A run card When the tone-out says where the call is (the simulator, the fire adapter and the 911 fallback all do) and one of your run cards covers that spot, the houses on its first alarm go out. The closest house, skipping rigs that are out of service. Once you have drawn run cards, this is the normal case.
2. Your map Config.Dispatch.ToneSets, from tone set to house. Use it for an all-call, or when your tone set names differ from your houses:
ToneSets = {
    ['STATION1'] = 'sta1',
    ['ALLCALL']  = { 'sta1', 'sta2', 'sta3' },
}
3. The house's tone set A page on STATION1 sets off the house whose tone set (Station & apparatus page) is STATION1. If two houses share a tone set, neither goes out and the console says so.
4. The nearest house Off by default. Config.Dispatch.NearestHouse = true tones the house nearest the call when nothing above matched. It guesses, which is why you have to ask for it. Useful before you have drawn run cards, when Dispatch pages every fire on one shared tone set.

A tone-out that matches no house is said once in the server console, with the tone set's name. stationalert status counts them:

dispatch  listening, 14 tone-out(s) heard, 12 house(s) set off, 2 matched no house, last 40s ago (STATION3)

Repeats, retones and one incident

  • The simulator pages a house once for every unit it assigns. That is one alert, not four.
  • A dispatcher, or the AI desk, pressing TONES again is a retone, every time.
  • One incident, one alert. The same fire can reach a house as a CAD call, a CAD tone-out and a radio page, each numbered its own way. An automatic tone of a house that was toned less than Config.Alerting.CollapseSeconds ago (90) is treated as the same incident and does not set it off again. The new call still shows on the board. A person is never held back by this.

The recommended setup for a server with nobody on the desk

Run cardsDraw them for your first-due areas, so the closest house goes and not every house on the tone set
Config.RunCards.ToneOnCreatetrue, the default. A CAD call tones its card the moment it opens
Sal's Kewl CAD, call type Auto tone-outOff. The CAD's automatic tone-out sets off every alerting station in the agency. Let the run cards here choose instead
Config.Alerting.CollapseSeconds90, the default
Config.Alerting.Auto.NobodyAssignedAfter60, the default. A call nobody assigns tones its station anyway
Config.Feed.Provider'cad' with Sal's Kewl CAD, otherwise 'none'. 'none' stops the demo inventing calls; Dispatch's calls still reach the board

With a person on the desk nothing changes: they press TONES in the console or Tone Out in the CAD, and the house goes out.

A call nobody assigns still goes out

A person on the desk is not on every call. They get busy, and the AI dispatcher may answer in their place. So a fire or EMS call with no units on it after Config.Alerting.Auto.NobodyAssignedAfter seconds (60) tones its station anyway: its run card, or the nearest station when Config.Dispatch.NearestHouse is on. A call any station already went off for, a pulled street box, and a call that was already old when the server started are left alone. Leave it on even if a person usually dispatches; 0 turns it off.

To ignore Sal's Kewl Dispatch entirely, set Config.Dispatch.AcceptToneOuts = false.

Setting a station off

Four things can set a house off: the feed automatically, a dispatcher in game, a web console, and somebody else's CAD or app. All four land on one server function. No surface has its own path, none can skip the checks, and the journal has one shape.

What happens, in order, every time:

  1. The request is checked for shape, and the station has to exist.
  2. Your authorize hook decides whether this caller may tone this house.
  3. Two independent rate limits. Per station, which protects the players in the building no matter how many things are asking. Per source, which catches one caller stuck in a retry loop. Either limit on its own leaves the other hole open, which is why there are two.
  4. Deduplication. One alert per station per call, for the life of that call — not a time window. Feeds re-poll, providers glitch, and a CAD reassigning a unit can hand the same call back as though it were new. A deliberate retone is a separate act and is exempt.
  5. Your activate hook is told it is happening, before anything would make a noise.
  6. It is written to the journal, accepted or refused.

Only then does the sequence engine pick a sequence, build the timeline and push it to everybody who can see or hear the house. Everything above happens first, every time, whichever of the four surfaces asked.

By hand, that is:

/toneout sta1                     -- the one to bind
/stationalert tone sta1           -- the same thing, spelled out
/stationalert test sta1           -- a fifteen-second drill

With no call named, the house's current run is used — which is what a dispatcher means nine times out of ten. With no run either, it is an all-call with no call attached, which is a legitimate thing to want.

/stationalert journal prints every activation, accepted or refused, with who asked and why it went the way it did. It is the first thing to look at when somebody says the house did not go off.

The line that does not bend

A caller names a station and a call. It never names a device, a door, a doorsystem hash or a lock id. There is no field anywhere in the API or the hooks that accepts one.

You ask for a house; the server looks up what that house has and decides what it does. That is not us being precious about an API — it is the difference between a station alerting resource and a remote door opener for anybody who can post JSON at your server.

The Operations & run cards page

Everything in this part of the manual is about running a fire department rather than making a noise. Most of it is set up on the Operations & run cards tab of /stationalert, and the day-to-day parts also have chat commands.

The top of the tab shows three chips — OPERATE, ADMIN and BROADCAST — lit for the rights you have. Anything you lack the right for is grayed out and says why.

part of the tabwhat it is forwho
CREW & APPARATUSOut of service, back in service, and who is riding which seat. See Out of service and Riding assignmentsjob or ace
MESSAGESStation messages, broadcasts and the banner. See Messagesjob or ace; broadcast and banner need the broadcast ace
RUN CARDSBoxes, their alarms and alternates, and the ACTIVE CALLS list with the greater alarm buttons. See Run cardscards: ace; greater alarms: job or ace
MAPPre-plans, street pull boxes and hydrants. See Street pull boxes and Hydrants and pre-plansace
HOUSE LOOKA house's logo, its idle page, and hidden map objects. See Ticker, logo and idle pageace
JOURNALTurnout times and the run book. See Turnout time and the run bookjob or ace

"Job" means the operating jobs in Config.Access.Jobs, on duty. "Ace" means the build ace, sals_kewlstationalert.admin. See Who may do what.

Everything made on this tab is saved in data/ops.json, data/hydrants.json and data/journal.json. Keep all three when you update. See Your data.

Run cards and box alarms

Real dispatch does not tone whoever is free. It tones a set assignment tied to a piece of the map: box 412 is Engine 1, Engine 3, Ladder 2 and Battalion 1, every time. A run card is that box: an area of the map, and the units it sends on the first, second and third alarm.

Without a card for a spot on the map, nothing changes. The house whose apparatus the CAD assigned is the house that goes off, exactly as before.

Making a card

  1. Operations & run cards page, RUN CARDS, + NEW. Give it a BOX NUMBER (412) and a NAME (Downtown).
  2. Under 1ST ALARM, click the units it sends, in order. Solid pills are on the card; click a dashed one to add it, a solid one to take it off. Do the same for 2ND ALARM and 3RD ALARM if you want them.
  3. Under ALTERNATES, add the units to take, in order, when a unit on the card cannot go.
  4. Press SAVE.
  5. Walk the area. A card without an area is never used, because a call is matched to a box by where it is.
    • WALK AREA — stand in the middle and size a ring with the arrow keys or the mouse wheel. ENTER keeps it.
    • WALK BOUNDARY — walk the corners of the district. E drops a corner, BACKSPACE takes one back, ENTER finishes. At least three corners.

Making and editing cards needs the ace.

What a card does

  • A call that opens inside the box tones the houses those units run out of, the moment it opens, without waiting for dispatch to assign anybody. That is Config.RunCards.ToneOnCreate, on by default.
  • A unit that is out of service or already committed is skipped, and the first free alternate is taken instead. That is the reason a card beats a hand-typed list.
  • The board shows the call's box number.
  • Config.RunCards.Sequence picks the sequence a card tone runs. It ships nil, which matches normally, so a working fire still gets the whistle. Set it to 'box-alarm' to tap the box number on the bell first.

Greater alarms

To bring in the next row of the card:

/alarm 412          -- the next alarm on the call in box 412
/alarm 412 3        -- straight to the third alarm

The first argument is the call's number, its id, or the box number. Or use the 2ND ALARM and 3RD ALARM buttons under ACTIVE CALLS on the RUN CARDS part of the Operations & run cards page — press once to arm, again to confirm.

The houses the next row brings in are toned. A house already toned for that call is not toned again. The board shows 2ND ALARM or 3RD ALARM on the call. A call no card covers has no next alarm, and the command says so.

Sounding a greater alarm needs a fire or EMS job or the ace. Escalating a working fire is a chief's call, not a builder's.

Run cards can be switched off entirely with Config.RunCards.Enabled = false.

Out of service, move-ups and escalation

Out of service

/oos E1 at the shop     -- out of service, with a reason
/ins E1                 -- back in service

Or OUT OF SERVICE and BACK IN SERVICE on the Operations & run cards page, under CREW & APPARATUS. Needs a fire or EMS job or the ace.

The CAD's own out-of-service statuses count too. They are listed in Config.Units.OosStatuses (oos, out of service, 10-7 and so on) and matched loosely.

An out-of-service unit shows OOS on the unit strip, its status lamp goes amber, and run cards skip it for the next alternate.

Move-ups

When every rig in a house is committed or out of service, another house is asked to cover it. The cover house gets an amber notice on its boards, and the notice clears itself when a rig comes back. Meanwhile the empty house's runs fall to its run card alternates on their own.

Say which house covers which on the portal's Station Alert page, under Picking the house (advanced): turn move-ups on and pick the covering station for each house from the list.

Failed-to-respond escalation

With Config.Alerting.Retone on (it ships off), a house nobody answered is retoned Times times, AfterSeconds apart. After the last retone, with Escalate on, the next house is toned: the first free alternate on the call's run card, or the house named as cover in Config.RunCards.MoveUps.Cover. Both houses' boards say so.

Retone = {
    Enabled      = true,
    AfterSeconds = 120,
    Times        = 1,
    Sequence     = nil,    -- nil re-runs whatever matched the first time
    Escalate     = true,
},

Earlier builds retoned an unanswered house over and over until the rate limit stopped it. In this beta a retone no longer re-arms itself: it retones Times times and then escalates.

Riding assignments

Who is the officer, who is driving, who has the nozzle.

/riding E1 officer Capt. Reyes
/riding E1 driver me
/riding E1 clear

Or the seat fields on the Operations & run cards page, under CREW & APPARATUS, with CLEAR SEATS to empty a rig. me puts your own character's name in the seat. Needs a fire or EMS job or the ace.

The seats are Config.Units.Seats: officer, driver, nozzle, backup and hydrant by default. Rename them to whatever your department calls them.

The officer shows on the board's unit strip, and the whole riding list is printed on the rip-and-run ticket. With Config.Units.ReadOfficer on, the voice reads the officer too — "Engine 1, Captain Reyes". It ships off, because names are long and runs are short.

Messages, broadcasts and the banner

A message is not an alert: no sequence, no doors, no whistle. It is text on the boards.

greenA station message — "training at 1900", "Engine 3 at the shop" — on one house's boards, or several
blueA broadcast, on every board on the server
amberA move-up notice, posted automatically
/stationmsg sta1 Training at 1900 in the bay
/stationmsg sta1 60 Engine 3 at the shop until further notice
/broadcast 15 All companies: radio test at the top of the hour

The number is how many minutes it stays up. Leave it out for Config.Messages.DefaultMinutes (30). The longest is a day (MaxMinutes) and the most text is 220 characters (MaxLength).

On the Operations & run cards page, under MESSAGES: pick who it goes to under TO (ALL, or one or more houses), type it, press SEND. ON THE BOARDS NOW lists what is up, with a button to take each one down.

When a message lands, players in quarters hear a soft two-note chime on the house speakers — the CHIME tone. Turn it off with Config.Messages.Chime = false.

The banner

One standing line along the bottom of every board on the server, until somebody takes it down.

/banner burnban Burn ban in effect for the county
/banner redflag Red flag warning until 2000
/banner info Annual inspections this week
/banner clear

Burn ban is orange, red flag is red, info is gray. The same controls are under BANNER on the Operations & run cards page.

Who may

A station message needs a fire or EMS job or the ace. A broadcast, a station message to all, and the banner land on every board at once, so they have their own ace, Config.Access.BroadcastAce:

# server.cfg
add_ace identifier.license:YOURS sals_kewlstationalert.broadcast allow

Anybody with the build ace can always broadcast.

To send messages somewhere else as well — Discord, your own app — edit integrations/hooks/server/message.lua.

Street pull boxes

The numbered fire alarm boxes on street corners. Any player may pull one — no job, no permission. It is the one part of this resource a civilian can use, and it puts the fire department into ordinary roleplay. A false alarm is a legitimate outcome.

Placing one

Operations & run cards page, MAP, PULL BOXES. Type the box number and the corner (5th & Main), then press PLACE. Walk it onto the corner, face the street, turn it with the left and right arrow keys, and press ENTER. Placing boxes needs the ace.

Give the box the same number as a run card, so the card says who goes. With no card for that number, the nearest station with a footprint goes.

With no prop set, a box is drawn as a small red marker. To put a real box on the corner, set Config.PullBoxes.Model to a model you stream, or to any base-game prop name.

What a pull does

  1. A BOX ALARM call opens at the box, on every board.
  2. The box number is tapped out on the bells of the houses that go, then those houses are toned with the box-alarm sequence (Config.PullBoxes.Sequence).
  3. The pull is written in the journal with the name of whoever pulled it.
  4. Your pullbox hook runs.

The call stays on the boards for Config.PullBoxes.CallMinutes (20) if nothing clears it, because a pulled box with no CAD behind it has nobody to close it.

Rate limits

Two, so a box is not a toy:

BoxCooldownSecondsPer box. One corner cannot be pulled again for 300 seconds
PlayerCooldownSecondsPer player. One player cannot walk a street pulling boxes; 180 seconds between pulls

Resetting a box

With Config.PullBoxes.RequireReset on (the default), a pulled box stays tripped until it is reset in person, like the real ones. Walk up to it and press E. Resetting at the box needs a fire or EMS job. Somebody with the ace can also press RESET next to it in the list on the Operations & run cards page.

Getting it into your CAD

integrations/hooks/server/pullbox.lua runs after every pull, by which point the box is tripped, the call is on the boards and the houses are toned. It is where you tell anything else — most usefully your CAD, so a dispatcher sees the box come in as a real call. The shipped file does nothing and has a commented example; check your CAD's export name before you switch it on.

Config.PullBoxes.Enabled = false turns street boxes off.

Hydrants and pre-plans

The nearest hydrant

Every call shows its nearest known hydrant — distance, bearing, and the flow if it is known — on the board and on the rip-and-run ticket. Only hydrants within Config.Hydrants.MaxDistance (250 m) are shown.

The map fills itself in

The game can only find hydrants near a player, not three miles away. So with Config.Hydrants.Survey on (the default), every player's client quietly reports the hydrant props it passes, and the server keeps them in data/hydrants.json. After a few evenings of normal play, the city is covered. The props it looks for are in Config.Hydrants.Models.

Until then, a call in an area nobody has driven yet may have no hydrant listed.

Adding your own

For MLO yards and private mains: Operations & run cards page, MAP, HYDRANTS, stand at the hydrant and press ADD HERE. Then set its flow (gallons a minute) and main size (inches) in the list. Adding and deleting hydrants needs the ace. NEAREST sets a waypoint to the closest one.

/hydrant

Anybody can type /hydrant. It drops map blips on the nearest hydrants to your house's current call, or to you if there is no call, and sets a waypoint to the closest. Config.Hydrants.Blips (6) is how many, and BlipSeconds (120) is how long they stay.

Pre-plans

Building information pinned to a spot on the map: what the building is, what will hurt you, and where the water goes in.

  1. Stand at the building. Operations & run cards page, MAP, PRE-PLANS. Type a name and press NEW HERE.
  2. Fill in what you know: OCCUPANCY, HAZARDS, STANDPIPE, FDC, KNOX BOX and NOTES.
  3. Set COVERS (m): how close a call has to be to pick this pre-plan up. 40 m by default (Config.Preplans.DefaultRadius).

A call within that reach shows the pre-plan on the board and on the ticket, and /preplan opens it for anybody whose house has that call. Making pre-plans needs the ace.

Turnout time and the run book

Turnout time

How long from the tones to wheels out of the house. The clock starts when the house is toned and stops at whichever comes first:

  • somebody who was in quarters drives out of the station footprint, or
  • the CAD marks one of the house's units en route (Config.Turnout.EnRouteStatuses).

Each run is shown against the NFPA 1710 standard: 80 seconds for fire, 60 for EMS (Config.Turnout.Standards). The idle board shows the average for the shift and the week; a shift is Config.Turnout.ShiftHours (12) real hours.

A house needs a footprint to time a turnout — see Stations.

The run book

Every run written down: the time, the call, the sequence, who silenced it and how fast, the turnout, and how it ended. Refused activations are in there too. It is kept across restarts in data/journal.json, up to Config.Journal.MaxRuns (400) runs.

Three ways to read it:

  • A logbook device on the watch desk. Anybody presses E at it.
  • The JOURNAL part of the Operations & run cards page: TURNOUT (this shift and this week) and THE BOOK.
  • The command:
/stationalert runs            -- every house
/stationalert runs sta1       -- one house
/stationalert runs sta1 50    -- the last 50

The command needs a fire or EMS job or the ace, and marks a run that missed the standard as over standard. It is the first place to look when somebody says the house did not go off.

Commands

commandwhowhat
/stationalertjob or aceOpen the builder
/stationalert place [id] [station]aceGo straight to placing a board
/stationalert move <id>acePick a board up and move it
/stationalert delete <id>aceDelete a board
/stationalert listanyoneEvery board
/stationalert stationsanyoneEvery station, and whether it has a footprint
/stationalert statusanyoneProvider, link health, counts, how many settings you have changed, and how the portal is reaching this server
/stationalert demo forcejob or aceOpen a demo call now
/stationalert demo clearjob or aceClear the demo calls
/stationalert windingaceCycle the triangle winding

stationalert status works in the server console and is the fastest way to answer "it does not work" — faster than a screenshot. It reports the feed, the link, the counts, every alert running right now, and every station of yours that has no devices.

Toning a house

commandwhowhat
/toneout <station> [call] [sequence]job or aceTone a house. The one to bind
/stationalert tone <station> [call] [sequence]job or aceThe same thing, spelled out
/stationalert test <station>job or aceA fifteen-second drill that exercises every kind of device
/stationalert silence <station>job or aceEnd the alert from the console
/stationalert doors <station> open|closeaceMove the bay doors by hand
/stationalert sequencesanyoneEvery sequence, its length, and the match order
/stationalert journal [n]job or aceEvery activation, accepted or refused, and why
/stationalert runs [station] [n]job or aceThe run book: runs, acknowledge times, turnout
/stationalert bell <station> [n | 5-5-5]job or aceRing a house's bells, or tap a code
/ackanyone in quartersAcknowledge, where no reset point is placed yet
/stationvolume [0-100]anyoneThis player's own volume. No permission, no round trip
/stationalert aceanyoneYour own id, whether you can build, and the line that would let you
stationalert ace [id]console onlyWho has building rights, or grant them to a player. Works at once and is kept across restarts
stationalert revoke [id]console onlyTake a grant back. On its own, lists the grants Station Alert keeps

Operations

commandwhowhat
/oos <unit> [reason] · /ins <unit>job or aceOut of service, back in service
/riding <unit> <seat> <name | me> · /riding <unit> clearjob or aceWho is riding what. Seats are in Config.Units.Seats
/alarm <call, number or box> [level]job or aceSound the next alarm on a run card
/stationmsg <station | all> [minutes] <text>job or ace (all: broadcast ace)A message on a house's boards
/broadcast [minutes] <text>broadcast aceA message on every board
/banner <burnban | redflag | info> <text> · /banner clearbroadcast aceThe standing line on every board
/hydrantanyoneNearest hydrants to your house's call (or to you): blips and a waypoint
/preplananyoneThe pre-plan for your house's call, if there is one
Station bay door buzzer keyjobOpens the bay from the driver's seat. Ships unbound; each player sets it in the game's key bindings

Building a house

The builder does all of this and is the way it is meant to be done: /stationalert, the Lights, doors & sound page, + ADD A LIGHT, DOOR OR SPEAKER. See Devices.

These are the same operations from a console, and they are not deprecated. A server console has no panel, a deployment script has no hands, and an owner who has edited html/ and broken the builder still has to be able to run their firehouse.

commandwhowhat
/stationalert device add <station> <kind> [id]aceA device where you are standing
/stationalert device list [station]anyoneEvery device, or one house's
/stationalert device delete <id>aceDelete one
/stationalert device move <id>aceMove it to where you are standing
/stationalert device power <id> on|offaceSwitch one off without deleting it
/stationalert device zone <id> <zone>aceWhat a sequence step narrows to
/stationalert device point <id>aceAnother corner on a strip's run
/stationalert device door <id> driver <driver>aceHow that door opens
/stationalert device door <id> hash|lock|model <value>aceWhat that driver needs
/stationalert device door <id> pose closed|openaceRecord where the door is right now

Kinds: light, strip, door, siren, speaker, bell, reset, indicator, relay, button, trafficlight, printer, logbook. See Devices.

The keybinds

The builder is available as a keybind and it ships unbound. Assign it in the game's own keybind settings, under Sal's Kewl Station Alert. A resource that grabs a key on install is a resource fighting whatever you already had on that key.

The Station bay door buzzer key ships unbound for the same reason. Each player sets it in the game's key bindings. See Door buttons and the bay buzzer.

Who may do what

Two main levels, because moving a television and changing what it shows are different acts — plus a separate right for anything that lands on every board, and a short list anybody may do.

Building Placing, moving and deleting boards. Creating, editing and deleting stations, including rosters and footprints. Adding, moving, configuring and deleting devices, including door isolation. Run cards, pre-plans, street boxes, hydrants, a house's logo and idle page, hidden objects, and a house's own copy of a sequence.
The ace, sals_kewlstationalert.admin — which nothing grants by default. See below.
Operating Changing what an existing board shows — its filter, the unit strip, switching it off. The demo controls. Crew and out-of-service, station messages, greater alarms, door buttons and the bay buzzer, resetting a pulled street box.
The jobs in Config.Access.Jobs, on duty if RequireOnDuty is set.
Broadcasting A message on every board, and the banner.
Config.Access.BroadcastAce (sals_kewlstationalert.broadcast), or the build ace.
Anybody Pull a street box, ring the bell in quarters, read the logbook, rip a ticket, acknowledge in quarters, /hydrant and /preplan.

A battalion chief rearranging the board is not an administrative act, so it does not need an admin. Taking Engine 1 off a station's roster is, because that decides which calls are that house's runs — which is to say it decides when the tones drop. So every station edit is ace, including the roster.

Devices do not split at all, and the reason is the bay door. A device list is the list of things the server will operate on somebody's behalf, so adding to it, moving something in it, or pointing one at a different doorsystem hash is construction every time. Switching one off could reasonably have been operations and is not, for the same reason: a bay door somebody switched off is a bay door that stops opening for calls, and whoever has to work out why should find it behind the same permission as everything else about that door.

Granting the ace

Nothing grants it for you. A fresh install has no principal the ace is allowed for, so the builder opens as VIEW ONLY for everybody until you grant it.

Live, with the server running:

stationalert ace        # in the SERVER console: who is online, and who has it
stationalert ace 1      # grant it to player 1, immediately

An ace granted this way takes effect on the next permission check, which is the next thing that player does — so no restart, no reconnect, and no reopening the panel. Press RE-CHECK on the view-only banner and it goes away.

The grant is kept across restarts in data/grants.json, and stationalert revoke 1 takes it back. The server.cfg way still works too:

# server.cfg
add_ace identifier.license:YOURS sals_kewlstationalert.admin allow

In game, /stationalert ace tells a player their own id, whether they have the ace, and the line. It grants nothing — a command a player could use to grant themselves a building permission is a privilege escalation, and no check on "are you already an admin" makes that safe, because the whole point is that the person asking is not one yet. Granting is console-only, which means it is whoever can already stop the server.

Why an identifier rather than a group. add_ace group.admin sals_kewlstationalert.admin allow is correct and does nothing on its own: it says what group.admin may do, and you also have to be in group.admin. Being a txAdmin admin does not put you there. That is the thing that catches almost everybody, so the command grants straight to the identifier instead.

The ace's name is Config.Access.AcePermission if you would rather it were something else.

The broadcast ace

Broadcasting is granted the same way, with its own ace:

# server.cfg
add_ace identifier.license:YOURS sals_kewlstationalert.broadcast allow

Give it to whoever runs your dispatch or your chiefs. Anybody with the build ace can already broadcast. The name is Config.Access.BroadcastAce.

The builder grays out what you cannot do rather than offering buttons that always refuse, and the VIEW ONLY chip explains why and names the ace. That is a courtesy, not the check — every write is checked again on the server.

Settings on the portal

About 160 settings can be changed from the Station Alert page of the portal at dispatch.salskewlscripts.com, the same portal you already use for Sal's Kewl Dispatch. A change is live for every player at once. A few settings need a restart; they are tagged RESTART and the page says so when you save one.

You need a subscription that includes Sal's Kewl Dispatch, and you have to be signed in as someone who may manage the community. You do not need a CAD.

The quick start

The first time you open the page it offers a quick start. It asks four questions:

  1. Where do your calls come from? A CAD, Sal's Kewl Dispatch or the simulator, calls made in game, or the demo feed.
  2. Who dispatches most of your calls? The AI dispatcher or nobody, or a person assigning units in a CAD. If you run the AI dispatcher, pick the first: stations go off the moment a call opens, and the AI dispatcher's pages set them off too. Whichever you pick, a call nobody assigns within a minute still sets its station off.
  3. How is a station picked? Run cards, the nearest station, or tone sets.
  4. Any extras? Quiet nights, and toning a house again when nobody responds.

Before it saves anything it lists every setting your answers will change. It ends with the steps that are still left to do in game. You can run it again at any time; it only changes the settings it shows you.

The pages

The settings are in pages, in the order you would set a department up: calls, dispatch, the house, the alert, voice, sound, sequences, boards, units, street boxes, the map, messages, devices and access. Each page shows the simple settings first. Check Show advanced for the rest.

Wherever a setting names something of yours, you pick it from a list rather than typing it: your stations, your sequences, your tone sets, the ramps, sirens and bells, your agencies and your units.

Two more pages edit what you built in game:

Your stationsName, departments, apparatus, tone set and whistle
Run cardsThe units on each alarm

What the page cannot do. It cannot build a station, place a device, walk a footprint or draw a run card's area. Those are positions in the game world and are made with /stationalert. The page tells you which of them are still missing.

Squawky

Squawky, the portal's help, is in the corner of the page. It knows these settings, and it can see what is built on your server and what Dispatch has paged. Ask it something like "why didn't my station go off?" and it works through the usual causes in order.

Squawky never changes anything on its own. It proposes a change, shows you exactly what it would set, and you apply it or you do not.

Where your changes are kept

data/settings.json holds only what you changed. A setting you reset goes back to its default. Keep data/ when you update, as always. A second copy is kept in the server's own storage and is put back if the file goes missing.

How the portal reaches your server

There are two roads, and you do not choose between them:

Through DispatchOn a server running Sal's Kewl Dispatch 3.15.0 or newer, the portal comes through it. Nothing to set up.
Station Alert's own linkOn a server that does not run the Dispatch resource, or runs one older than 3.15.0, Station Alert links to the portal itself with the same link key.

The key is already in server.cfg if you have ever run Dispatch (set sals_dispatch_key "..."). Otherwise copy it from the portal's Game server page:

set sals_stationalert_key "paste-the-link-key-here"

Use set, never setr. Whoever holds that key can change this server's settings, and setr sends it to every player.

set sals_stationalert_link "false" turns the link off. No port is opened either way, and nothing in game depends on the link: with no key, a wrong key or the portal down, stations are toned exactly as before.

stationalert status has a portal line that says which way the portal is reaching you, and a settings line with how many settings you have changed.

Configuration

Change settings on the portal, not in a Lua file. See Settings on the portal. There are three layers, lowest to highest:

defaults.luaOurs. Read it; do not edit it. Every setting, its default and why, commented in plain language. Every update replaces it. It was called config.lua until 0.0.13-beta.
data/Yours. Everything you made or changed: stations, screens, devices, tone sets, sequences, building rights and portal settings. The download never contains it, so an update cannot overwrite it.
data/settings.jsonYours. What you changed on the portal. Beats both files above.

Nothing is configured by editing a file. Stations, screens, devices, tone sets and sequences are made in the builder; the server's settings are on the portal. If you made a config.local.lua on 0.0.13-beta it still loads, and nothing in it is lost; new installs no longer get one.

To update, copy the new folder over the old one, letting it overwrite, then refresh and restart. Do not delete the old folder first: data/ lives only there.

The settings people actually change, all in defaults.lua and most of them on the portal too:

Config.Feed.Provider'demo', 'cad' or 'none'
Config.Feed.CadWhether the CAD may tone your houses, and how its stations map onto yours. See Where the calls come from
Config.DemoHow busy the invented traffic is
Config.FilterThe defaults every board starts with
Config.Board.PriorityColorsWhat a priority 1 looks like
Config.Board.FlashSecondsHow long a new call flashes so somebody in the kitchen notices. Zero turns it off
Config.Board.Clock2424-hour, or AM/PM
Config.Render.DrawDistanceHow far away a board still draws
Config.Render.DetailDistancePast this it keeps drawing but stops updating every tick
Config.Dui.MaxSurfacesHow many boards can be live at once. Four is plenty for a dayroom, a bay and a watch desk
Config.AccessThe build ace, the jobs, and BroadcastAce for broadcasts and the banner
Config.Persistence.SaveDelayWrites are batched this many ms after the last change

And the alerting half:

Config.SequencesWhat actually happens when a house is toned. See Sequences
Config.DevicesDevices kept in version control rather than made in game
Config.DeviceDefaultsWhat a device gets when it does not say otherwise, per kind
Config.AudioThe tone, ramp, whistle and bell recipes, and the master gain
Config.VoiceWhich annunciation tier, what gets read, and how many times
Config.Alerting.AutoWhether the CAD tones houses on its own, on assignment or on call creation
Config.Alerting.CollapseSecondsOne incident, one alert: how long an automatic re-tone of the same house is ignored. 90; 0 turns it off
Config.DispatchSal's Kewl Dispatch tone-outs: on or off, the tone set to house map, the nearest-house fallback, whether the call goes on the board
Config.Alerting.NightModeQuiet hours, the level cap, and the forced gentle ramp. Ships on
Config.Alerting.AutoClearSecondsThe backstop that means an alert always ends
Config.Alerting.AcknowledgeWhat the reset stops, and whether /ack is allowed
Config.Alerting.RateLimitHow often a house can be set off, per station and per caller
Config.Alerting.DoorRateLimitThe same for doors, independently
Config.Alerting.RetoneFailed-to-respond retone, and Escalate to the next house. Ships off
Config.Alerting.BroadcastRadiusHow far from a house an alert is sent at all
Config.ScheduleThe noon whistle. Ships off

And operations:

Config.OpsWhere the operations files are kept: data/ops.json, data/hydrants.json, data/journal.json
Config.RunCardsRun cards on or off, toning on call creation, the sequence a card tone runs, and move-up cover houses. See Run cards
Config.TurnoutThe turnout standards (NFPA 1710: 80 s fire, 60 s EMS), the CAD's en route statuses, and the shift length
Config.UnitsThe seats on a rig, reading the officer aloud, and the CAD's out-of-service statuses
Config.MessagesHow long messages last, how long they can be, and the chime
Config.PullBoxesStreet boxes: the prop, rate limits, whether they need resetting, what the call looks like, and its sequence
Config.HydrantsThe survey, the hydrant props it looks for, how far a hydrant can be and still show, and /hydrant's blips
Config.PreplansPre-plans on or off, and how far a new one reaches
Config.JournalHow many runs the book keeps
Config.Targetox_target, qb-target, or the E prompt. 'auto' by default

Updating from 0.0.12-beta or older? Your old config.lua is no longer loaded, and the console warns about it at every start until it is gone. If you changed anything in it, set those settings on the portal, then delete or rename config.lua. Every setting you never changed simply takes its default from defaults.lua.

Config.Debug.Enabled ships false and should stay that way. Turn it on only while you are working on something.

Your data

Six files in data/ are yours. Keep them when you update.

stations.json Your fire department: every station you created in game, its apparatus roster, its footprint, and every device in it — the lights, the bay doors, the speakers, the whistle, the reset point.
The devices share this file on purpose. A house and the things in it are one thing you back up, copy to your test server, or hand to somebody else, and two files that have to be kept in step is two files somebody will get out of step.
screens.json Every board you placed — where it is, how big, and what it shows.
ops.json Run cards, pre-plans, street boxes and crew.
hydrants.json The hydrants the survey found and the ones you added.
journal.json The run book: every run, its acknowledgment and its turnout.
voice/ Rendered speech, cached, one file per phrase. Deleting the contents costs you money rather than data — every phrase is re-rendered the next time a call needs it. Keep the folder itself.
It never ships: the packaging script refuses to build a release containing one of these.
settings.json The settings you changed from the portal, and only those. Delete it and every setting goes back to its default. See Settings on the portal.
mlo-presets.lua Ours. Texture names for televisions in common station MLOs. Overwrite it on update.

One more folder is yours, outside data/: audio/bank/, where your voice clips go. Nothing ships in it. See Voice annunciation and audio/README.md.

The folder has to exist. The server cannot create it, so if you delete it nothing you place survives a restart — and the console says so on every save. mlo-presets.lua ships in there, which is what normally keeps the folder around.

None of the JSON files is written until there is something to put in it, so a fresh install having no stations.json is normal.

If one of them is corrupt

An unreadable file is reported in the console and left alone. The resource starts anyway with nothing loaded from it. That is deliberate: a station you cannot see is a bad afternoon, but a file quietly overwritten with an empty one is a lost afternoon.

Note the trap. Once the resource is running with nothing loaded, the next thing you place saves over the broken file. If stations.json looks wrong, copy it somewhere before you touch the builder.

Records that can be read are kept. One unreadable station does not cost you the rest of them — it is skipped, named in the console, and everything else loads.

Editing the integrations

The integrations/ folder ships readable and editable, outside the escrow, because it is meant to be edited. Read integrations/README.md first.

A hook is a decision this resource refuses to make for you, because no two fire departments agree on the answer. Each one is a plain Lua file with working code in it that you can read.

I want to…Open
Use my own notification resourcehooks/client/notify.lua
Change which house a call belongs tohooks/server/match.lua
Decide who may tone a stationhooks/server/authorize.lua
Post to Discord, feed my stats, page a talkgrouphooks/server/activate.lua
Send a pulled street box to my CADhooks/server/pullbox.lua
Send station messages and broadcasts somewhere elsehooks/server/message.lua
Fit a framework we do not supportserver/framework.lua

Making your changes survive an update

Do not edit our files if you can avoid it — an update overwrites them, because the download carries the file names we wrote.

Instead, copy the file to a name of your own in the same folder. Both load, yours registers second, and yours wins. The console tells you which file won at boot. Our file gets replaced on every update and never touches your copy.

hooks/server/match.lua              <- ours. Gets overwritten.
hooks/server/match-ourdept.lua      <- yours. Survives forever.

The rules

  • A hook gets data and helpers, never authority. It cannot open a door by returning true.
  • A broken hook is not a broken server. Every call is wrapped. A hook that errors prints once and is skipped; the station keeps working.
  • A missing hook is not an error. Delete a file and that event does nothing.
  • Any .lua you drop into hooks/server/ or hooks/client/ is loaded. A file in the wrong one of those two folders is almost always what a mysterious error in here turns out to be.

Every hook

All twelve fire. Nothing in the folder is a placeholder.

filefires when
server/match.luaDeciding whether a call belongs to a station
server/authorize.luaDeciding whether a caller may tone a house
server/activate.luaA request to set a house off, before anything happens
server/alert.luaThe sequence has been scheduled, so it knows what will happen and when
server/device.luaA device was told to do something. Every device, every step
server/acknowledge.luaSomebody hit the reset at the watch desk
server/cleared.luaAn alert ended, and why
server/message.luaA station message, broadcast or move-up notice was posted
server/pullbox.luaSomebody pulled a street box — after the call is open and the houses are toned
client/notify.luaA message is being shown to the player
client/alert.luaAn alert landed on this machine. Your screen effects go here
client/audio.luaA sound is about to play. A full override

Two are worth reading twice.

device fires from the server, not the client, and it fires for every selected device on every step — the lights coming on, the tones dropping, the whistle winding up, the doors moving. The server is the only place that can honor that, because it is the only place that sees the whole house rather than one player's earshot. It fires a lot, in the moment when timing matters most, so keep it fast and never block.

audio is the one hook that can take something over. Return true and you played that sound yourself; the built-in synthesis stays quiet for it. It is per sound, so you can put the tones through your own player and leave the whistle and the voice to us. Respect ctx.gain — it already has distance, occlusion, the player's own volume and night mode in it.

Nothing else can take anything over. authorize can refuse an activation and that is the only veto in the list.

Exports

Setting a house off

local alertId, err = exports['sals_kewlstationalert']:Activate({
    station = 'sta1',
    call    = {
        id         = 'myalarm-42',
        kind       = 'fire',
        type_label = 'ALARM ACTIVATION',
        priority   = 3,
        location   = '2400 ALTA ST',
        assigned   = { 'E1' },
    },
})

call can also be the id of a call already in the feed, as a string. Leave it out entirely for an all-call.

The invoking resource is stamped as the actor from GetInvokingResource, so nothing can claim to be another resource in the journal.

Reading the state

exports['sals_kewlstationalert']:Stations()
exports['sals_kewlstationalert']:StationAt(coords)        -- which house is here
exports['sals_kewlstationalert']:StationCalls('sta1')
exports['sals_kewlstationalert']:StationCommitted('sta1') -- anything out?
exports['sals_kewlstationalert']:StationsForCall(call)    -- who would get it
exports['sals_kewlstationalert']:ActiveCalls()
exports['sals_kewlstationalert']:Units()
exports['sals_kewlstationalert']:FeedHealth()             -- 'ok'|'stale'|'dead'
exports['sals_kewlstationalert']:Screens()
exports['sals_kewlstationalert']:SetPower(id, on)
exports['sals_kewlstationalert']:Journal(20)

The alerting half

exports['sals_kewlstationalert']:ActiveAlerts()
exports['sals_kewlstationalert']:StationAlert('sta1')     -- what is running here
exports['sals_kewlstationalert']:Acknowledge('sta1')      -- stop the noise
exports['sals_kewlstationalert']:ClearStation('sta1')     -- end the alert
exports['sals_kewlstationalert']:StationDoors('sta1', true)
exports['sals_kewlstationalert']:GameClock()              -- hours, minutes, night
exports['sals_kewlstationalert']:Announce('sta1', 'text') -- pre-render a phrase

Ringing the bell

exports['sals_kewlstationalert']:RingBell('sta1', { strikes = 3 })
exports['sals_kewlstationalert']:RingBell('sta1', { code = { 5, 5, 5 } })

Rings every bell in that house, and returns how many it rang. Like everything else here, it takes a station, not a device.

StationDoors takes a station and a direction. It does not take a door, a doorsystem hash or a lock id, and there is no export anywhere that does. The server looks up what that house has and operates that.

What comes back when it says no

err_bad_stationYou did not name a station
station_unknownNo house by that id
err_unknown_callThat call id is not running
err_rate_limitedToo many, too fast
err_already_tonedAlready toned for that call
no_permissionYour authorize.lua said no
err_no_devicesRequest was fine, but that house has no lights, doors, speakers or whistle to run

Every attempt is journaled either way, so you do not need to log them yourself to find out what happened.

Languages

No user-facing string is hardcoded. locales/en.lua is the baseline.

To add a language, copy it to locales/xx.lua, change the table key at the top, translate the right-hand side, and set Config.Locale. Missing keys fall back to English rather than showing a blank, so a half-finished translation is usable.

locales/ ships outside the escrow, so your translation survives as a file you own.

Performance

Every board is a browser page, and a browser page costs memory like a browser tab. So the resource is built around not having many:

  • A fixed pool of surfaces, Config.Dui.MaxSurfaces, created on demand and handed to the nearest boards in view. They are taken back the moment you walk away, so the pool follows the player rather than staying on whichever board was seen first.
  • Nothing renders for a board nobody is near or facing. Out of range, out of the camera, or behind the wall — all three cull.
  • Call data is only sent to players standing at a board. A server where nobody is in a firehouse sends no call traffic at all.
  • Boards repaint on change, not on a timer. Run timers and the wall clock tick inside the page itself, so a running clock is not a reason to rebuild anything.

Measured figures will be published here before the full release. The design targets above are what the resource is built to; putting numbers next to them needs a populated server rather than a test box.

Troubleshooting

The portal's Station Alert page cannot reach the server

Run stationalert status in the server console and read the portal line.

The link key was refusedCheck sals_stationalert_key (or sals_dispatch_key) in server.cfg against the portal's Game server page
The subscription does not include the portal linkThe community's subscription has lapsed or does not include Dispatch
The platform could not be reachedThe server cannot make an outbound HTTPS request. Station Alert keeps retrying on its own
The link is offsals_stationalert_link is "false", or the address is not an https one

None of these affects alerting. Stations are toned the same with the link down.

The board is blank

Run stationalert status in the server console. If the provider says demo and there are active calls, the feed is fine and the problem is rendering — try the next item.

No board appears at all

Run /stationalert winding and cycle through the three settings, keeping whichever shows the board.

Which way round a triangle has to be wound to be the front face is a property of the server build and cannot be asked from a script, so it is a setting. The default (both) draws every triangle twice and always works; the other two draw it once and halve the cost. This is about cost, not about getting a picture.

If the console mentions DrawSpritePoly, your server build is too old to draw boards at all.

The board is mirrored

Its heading is backward. Move it and press SPACE to aim it at you.

Two boards are showing each other's calls

Run /stationalert status, which reports which surface each board holds. This should not happen; if it does, it is worth a Discord message.

Placements do not survive a restart

The data/ folder has to exist. The console says so on every save when it is missing.

A station I edited keeps reverting

That id is in a config file as well as data/stations.json. Config wins by design, and the console names the ids that collided.

The console says config.lua is still in the resource folder

It is left from 0.0.12-beta or older and is no longer loaded. Move anything you changed in it to the portal, then delete or rename it.

The apparatus checklist is empty

The list comes from the feed. Open the builder once with the demo provider running and it fills in. On a brand new server the builder asks for a feed snapshot when it opens, so this should resolve itself.

A replace-mode board shows a rectangle instead of the television

The texture could not be claimed — wrong names, the model is not nearby, or another board already claimed that model. The fallback is working as intended. Check the console, which names the txd and txn it tried.

The builder says VIEW ONLY and the buttons do nothing

You do not have the ace. Placing boards, creating stations and adding devices all need sals_kewlstationalert.admin, and nothing grants it by default.

Nothing needs restarting. In the server console:

stationalert ace        # who is online, and who has it
stationalert ace 1      # grant it to player 1

Then press RE-CHECK on the banner in the panel. The grant is live but not saved; the command prints the server.cfg line that makes it permanent.

Being a txAdmin admin is not enough on its own, and an ace allowed for group.admin does nothing if you are not in group.admin — see Granting the ace.

The panel opens at all because Config.Access.Jobs lets a fire or EMS job change what an existing board shows without being an admin. Building is a different act and needs the ace.

Click the VIEW ONLY chip in the panel and it says all of this, with the line to copy. The server console also says it once per player, naming the ace — so the owner sees it where they are already looking.

The CAD toned a station and nothing happened here

Read the server console: an unmatched tone-out is refused out loud and names the station and the slug it arrived with. Either give that house the same id as the CAD's slug, or add it to Config.Feed.Cad.Stations — see Which house did the CAD mean.

If the console says nothing at all, check Config.Feed.Cad.AcceptToneOuts and that Config.Feed.Provider is 'cad'.

The CAD toned one station and the WRONG house went off

A slug collision: the CAD's slug for one house matches the id of a different house here, and both sides think they agree. Compare the slugs in the CAD's owner panel against the ids on your Station & apparatus page.

If MatchByName is switched on, turn it off and use the slug or the map instead — two houses sharing a name is the other way this happens.

The board is empty and the CAD is definitely running

Run stationalert status. The cad line says whether the link is up and whether the board is arriving. If the console mentions an export that does not exist, the CAD bridge is older than this resource expects — update it, or set Config.Feed.Provider = 'demo' until you do.

I toned a house and nothing happened

It has no devices. Open /stationalert, go to Lights, doors & sound and pick that house: the panel says in amber what is missing. QUICK FIT fixes it in about ninety seconds.

stationalert status says the same thing in a server console, and the export returns err_no_devices for the same reason.

err_already_toned

One alert per station per call, permanently, for the life of that call. A deliberate retone is /stationalert tone again, which is a new alert and says RETONE on the board.

The lights work but there is no sound

First: does that house have a speaker? The tones, the ramp and the voice all come out of one, and the Lights, doors & sound page says in amber when there is none. Then press PLAY on the Tones & voice page — if that is silent too, the problem is the audio engine rather than the house.

The sound is synthesized in the builder's own browser frame. Open the F8 console and look for [sals_kewlstationalert] audio. If you have edited anything in html/, that is where to look first.

Check /stationvolume too — it is remembered per player, on their machine.

The whistle is far too quiet at three in the morning

That is night mode and it ships on. Config.Alerting.NightMode.

The voice says nothing

Expected with no phrase bank. The announcement still reaches the board and anybody in quarters. See Voice annunciation.

A bay door will not open

If its driver is native, that MLO's door is probably not registered with the game door system, and the console says so once. Switch the device to the pose driver on its own form and record its two positions.

TEST IT on that door's form opens it without waiting for a call, which is the fastest way to find out which driver your MLO wants.

A bay door will not close

Something is standing under it. It retries, and past the give-up time it is left open and logged. That is deliberate, and it is the safe way round.

A bay door will not move at all, for anything

Check its ISOLATION on the door's form. An isolated door is held where it was put until it is set back to In service.

The bay buzzer does nothing

The Station bay door buzzer key ships unbound; each player sets it in the game's key bindings. The button also needs Also a buzzer ticked, the player needs a fire or EMS job, and the vehicle has to be within the button's BUZZER REACH of the door.

A street box says it has already been pulled

With Config.PullBoxes.RequireReset on, a pulled box stays tripped until somebody with a fire or EMS job resets it at the box, or somebody with the ace presses RESET on the Operations & run cards page.

A call shows no hydrant

Nobody has driven past one near there yet, or the nearest is beyond Config.Hydrants.MaxDistance. The survey fills the map in with normal play. Add one by hand on the Operations & run cards page for an MLO yard or a private main.

A run card never tones anybody

It has no area. A call is matched to a box by where it is, so a card has to be walked with WALK AREA or WALK BOUNDARY after it is saved. Check that Config.RunCards.Enabled and ToneOnCreate are on.

Support

Discord: discord.gg/CVWZb6AEwy

When reporting something, the single most useful thing you can paste is the output of stationalert status from the server console, plus anything the console said with [sals_kewlstationalert] in front of it.

If you have found working texture names for a station MLO that is not in the preset list, send them — they will ship for everybody.

Didn’t find it? Ask Squawky, or open a ticket on Discord and tell us what you already tried.