Supported integrations

77. Other scripts it connects to automatically

Nothing to set up. The start-up line lists what was found. phone:diag shows every script the phone considered and why it used or skipped each one. To force one, set Config.Providers.<area> in config/config.lua to the resource name, or 'none' to switch that area off.

Scripts written for other phones (police, EMS, job and boss-menu scripts) keep working when they send mail, texts or notifications through events: the phone answers the common event names other phones use. A script that calls another phone's exports needs one change (see "No such export" in section 11).

• A script that starts after the phone, or restarts, is picked up within about two seconds.
• When a supported script is running but its exports differ from the ones the phone knows (an older or newer version), a yellow line names the script and what is missing, and the phone uses the next option.
• Each area in Config.Providers has a comment beside it in config/config.lua: bank, voice, housing, garage, inventory, dispatch, keys, vehiclelock, fuel, doorlock, society (company accounts), statement (bank history), accounts (shared accounts) and more. For a script that isn't listed, write a provider: developers/custom_provider_template.lua.
• Every script, and exactly how the phone talks to each one, is in Integrations.
• These integrations are covered by automated tests built from each script's published API. They have not all been run on live servers with every one of these scripts.

Housing, by script:

Company management (the Services app)

Every employee of a Config.Services company gets a duty switch. Boss grades also get the employee list, and can offer jobs, promote, demote, fire and use the company account. Every action is checked on the server, and a boss can only manage grades below their own.

Hiring is an offer the player accepts. Nobody gets a job they didn't agree to, and nobody can be hired from across the map:

1. The boss opens Services > Your Company > Hire. Players within 8 m who are not in the company are listed; Offer Job sends the offer. A typed player ID must also be within 8 m.
2. The player gets a notification that opens the offer, with Accept and Decline. The starting grade is the company's lowest.
3. On Accept the server checks again that the boss still manages the company and that the two are still within 8 m, then sets the job. The boss is told either way.

A player has one open offer at a time. An offer lapses after 2 minutes, or when either player leaves. Offers and hires go to the activity log.

Garage: car photos, locks, positions

• Photos of every car, add-on cars included: in game, with the phone.admin ace, run /phonecarphotos (cars with no photo yet), /phonecarphotos all (every car again) or /phonecarphotos <model>. Every vehicle is photographed against the sky, cut out and saved through the phone's media store (needs screenshot-basic), about a second each. Backspace or Esc stops it. Without a photo, players see the official picture (Config.Garage.imageUrl), then a drawing. Run it again after adding cars.
• Lock / Unlock from the app (Config.Garage.remoteLock) uses qbx_vehiclekeys or Renewed-Vehiclekeys when running, and the game's own lock otherwise, which is what qb-vehiclekeys, wasabi_carlock, MrNewbVehicleKeys, cd_garage and similar read. For another lock script, register a provider in bridge/server/vehiclelock.lua (example inside).
• Directions to a garage need its position: from your garage script, or Config.Garage.garages. Impound lots: Config.Garage.impounds.
• Config.Providers.garage forces one garage script. For an in-house one, see Custom Garage.

Switching from another phone

1. Remove the old phone first: take its folder out of resources and delete its ensure line.
2. Scripts that use the common phone events (mail, texts, notifications, invoices) need nothing: the phone answers those event names itself.
3. Scripts that call another phone's exports by name get No such export in the console. Switch those calls to exports.phone:.... The matching calls (SendMail, SendMessage, Notify, SendBill, DispatchAlert ...) are in Exports, usually one line per call.
4. Bring your players' data across with phoneimport in the server console. Run phoneimport --dry-run first to see what would be copied, then phoneimport. Players keep their phone numbers, and contacts, calls, chats, photos and more come across where the old phone had them. The old tables are only read, and a second run never duplicates anything. Which old phones it reads, and exactly what comes across from each, is in Importing Data.

The old phone's tables that share a name with this phone's are renamed to old_<name> at first start (section 2). Nothing is deleted. What does not carry over: direct writes into another phone's own tables, mail and notification buttons, texts from a script to a player who is offline (delivered live only), attachments on script texts, and opening apps by script.

Other scripts: HUD and dispatch scripts that read the common state bag names (phoneOpen, phoneNumber, onCallWith, speakerphone, flashlight ...) keep working. phone_api in the server console prints the add-on API; Custom Apps shows how to add your own app.