Skip to content
Blixt

Blixt Racing

Blixt Racing is a coming soon racing app and resource for FiveM servers. It is planned as a standalone blixt-racing resource that can integrate with Blixt for device surfaces and trusted server exports.

Status

Section titled “Status”
  • Status: COMING SOON.
  • Folder name: blixt-racing.
  • Resource name: blixt-racing.
  • Resource type: standalone FiveM resource, with Blixt integration.
  • Support and release questions: Blixt Discord.

Racing is not currently sold on the public landing pages. Release or preview instructions will be posted with the download when it is available.

What it does

Section titled “What it does”

Racing is intended for in-character racing communities:

  • Race discovery and signups.
  • Track or route listings.
  • Lobbies, classes, and entry rules.
  • Results, leaderboards, and history.
  • Device integration through Blixt when installed.

Exact feature scope may change before release.

Planned install order

Section titled “Planned install order”

For release or preview builds, start dependencies before Racing. If you want Blixt device integration, start blixt before blixt-racing.

ensure oxmysql


# Optional but recommended for Blixt device integration:
ensure screenshot-basic
ensure pma-voice
ensure blixt


# Release/preview only once available:
set blixt:trusted_resources "blixt-racing"
ensure blixt-racing

The folder must stay named blixt-racing.

Dependencies

Section titled “Dependencies”

Expected dependencies:

  • oxmysql: required for persistent races, results, and leaderboard data.
  • blixt: optional for standalone operation, required for Blixt device integration.
  • Framework: qbox, qbcore, esx, or standalone support is planned where server identity and permissions are needed.

Important convars

Section titled “Important convars”

For Blixt integration, trust Racing before it starts:

set blixt:trusted_resources "blixt-racing"

If multiple apps need trust:

set blixt:trusted_resources "blixt-business,blixt-racing"

This trust setup is for release or preview builds only. Do not add random resources to the trust list; trusted resources can use privileged Blixt server exports.

Configuration

Section titled “Configuration”

Racing is expected to ship with its own resource config for racing-specific settings such as classes, permissions, track rules, result retention, and leaderboard behaviour. The exact config reference will be published with the release.

If Blixt integration is enabled, app visibility can be managed from blixt/config.json the same way as other external apps:

  • Add racing to featured app lists to promote it.
  • Add racing to required home apps if every player should keep it.
  • Add racing to disabled app lists if it should be hidden on a device.

Privacy and roleplay rules

Section titled “Privacy and roleplay rules”

Racing should expose in-character racing data, not hidden framework metadata.

  • Leaderboards should show the chosen racer identity, not account identifiers.
  • Results should avoid leaking license, citizen ID, wallet, inventory, or job metadata.
  • Private races should only reveal participants and routes to eligible players.
  • Admin-only moderation data should stay out of normal player UI.
Section titled “Related resources”