SpaceELS for FiveM: Install, Restrict the Editor and Test Your Vehicles

SpaceELS is SpaceDev's emergency-vehicle lighting and siren controller for FiveM. It provides configurable stages, vehicle profiles and an in-game editor. Before enabling it for players, restrict that editor: the configuration reviewed here sets RequireAdminForBuilder = false, and the server authorization function permits profile editing when that setting is false.

These notes cover the creator's source at revision 7364326, reviewed on 10 October 2026. They are a source review and installation checklist, not a completed gameplay test or performance benchmark. Check changes in later releases before applying the same configuration.

Download and identify the resource

Use the SpaceELSv2 repository. Its README calls for a resource folder named SpaceELS. The repository name and the installed folder name are different.

1. Extract the resource into resources/SpaceELS/, with fxmanifest.lua directly inside that folder.
2. Keep the client/, server/ and html/ directories, config.lua and vehicle_profiles.json together.
3. Configure editor access and one test vehicle before starting the resource.
4. Add ensure SpaceELS to the test server's configuration, then inspect the startup log.

The reviewed manifest loads Lua scripts and an HTML interface without declaring an ESX or QBCore dependency. That alone does not establish compatibility with every vehicle, other siren controller, or GTA V edition. Confirm the target edition separately.

Restrict the profile editor

In the existing Config.ELS table, set RequireAdminForBuilder to true. Configure a deliberate staff permission through AdminPermission or the supported identifier list. With a nonempty AdminPermission, the server also accepts the spaceels.admin ACE permission. Read the configuration alongside the server authorization code; hiding an interface is not a substitute for enforcing the permission.

Test an ordinary account and an allowed staff account separately. The ordinary account should be unable to open the editor or save and reset profiles. Confirm that a saved staff change persists after a restart. Back up vehicle_profiles.json, because the server writes profile changes to that file.

This check is especially important on a public server: an unrestricted editor makes your vehicle configuration available to people who are not responsible for maintaining it.

Start with one known vehicle

Vehicle profiles are keyed by model name. Match the stages and extras to the actual vehicle you are testing; do not copy the example profile and assume that its extra numbers match another model. Keep the original vehicle and profile files so that a failed change is easy to reverse.

The configuration also includes passenger control and optional environmental lighting. Decide whether passengers should be allowed to operate lights and sirens, then test that decision with a driver, a passenger and a nearby observer. Compare another controller only after disabling conflicting control logic for the test.

Default controls

The reviewed README lists these defaults. Existing player keybindings can differ, so check FiveM's keybinding settings when a key does not perform the expected action.

Action	Command	Default key
Open the ELS interface	els or elsui	U
Cycle the light stage	els_stage	J
Cycle siren tones	els_siren	Left Ctrl
Sound the airhorn	+els_horn	E
Open the vehicle-profile editor	/controlels	No default listed

Check synchronization and recovery

1. Cycle every configured light stage and siren tone while another player observes the vehicle.
2. Enter and leave driver and passenger seats, switch vehicles and confirm that the configured access rules still apply.
3. Save a profile, restart SpaceELS and confirm the saved settings and interface behavior.
4. Reconnect both clients and repeat the controls. Check for missing interface assets and client or server errors.
5. Test multiple active emergency vehicles in a representative location, including the optional lighting effects.

The creator advertises a low idle resource-monitor reading. It is not a measured result for your vehicle fleet, visual settings or server activity. Use the Cfx.re profiler and a repeatable scene to investigate a performance problem; do not use an idle figure as proof of zero cost.

If this is your first resource installation, follow the FiveM server setup guide first. Keep the resource disabled on the public server until its access rules, vehicle behavior and recovery checks meet your requirements.