TrafficRP
TrafficRP is a FiveM roleplay server owned by Not License, built from scratch by r4tedx as lead developer, with around six months of work and ongoing maintenance.
Roleplay server: TBA. Development and maintenance are ongoing.
My role in TrafficRP
I built TrafficRP from scratch for its owner, Not License, taking the lead developer role across the FiveM server build. The engagement has involved around six months of development, and I continue to work on the project as its lead developer and maintainer.
The server uses QBOX with Lua resources, a Svelte HUD and a React loading screen, with TypeScript and Tailwind for interface development. The build brings together server setup, resource integration and custom player-facing systems.
My involvement continues beyond the initial build through maintenance and ongoing development. The roleplay server is TBA; community updates are available in the TrafficRP Discord.
The brief and my responsibility
Build a complete roleplay server for Not License and continue maintaining it. My responsibility covered the QBOX setup, integrating resources, custom player interfaces and ongoing development across the server.
Building the server from scratch included both custom development and integration of existing resources. QBOX and third-party dependencies remain distinct from the custom systems I developed.
A modular HUD connected to QBOX
The HUD separates framework integration, status, vehicle information, compass, weapon information, settings and UI messaging into Lua modules. Its Svelte and TypeScript interface receives updates through a dedicated NUI bridge. This keeps framework-specific data handling separate from the presentation code.
The QBOX integration seeds player metadata when the player loads and listens for hunger and thirst changes. Values are checked and clamped before updating HUD state, which gives the interface a consistent range to display.
Controlling updates to the interface
The Lua-to-NUI bridge remembers the last payload for each action and skips a message when its data has not changed. When the interface reports that it is ready, the cache is cleared so the HUD can send fresh state after a reload.
Separate update intervals and selectable performance profiles control how frequently different HUD systems refresh. This allows status, vehicle information and other displays to use refresh settings appropriate to their role.
Loading screen and continued maintenance
The React loading screen responds to FiveM loading-progress and log events, bounds the progress value and keeps its event listeners within the component lifecycle. A development preview can simulate progress outside the game, making the interface easier to check during UI work.
The result is a server build with custom interfaces and continuing lead-development responsibility after around six months of work. The roleplay server remains TBA, with community updates through the TrafficRP Discord.
Scope of work
- Complete FiveM roleplay server built from scratch for Not License
- Lead developer responsibility across the server build
- QBOX server setup and Lua resource integration
- Custom HUD and loading screen interfaces
- Around six months of development work
- Ongoing development and server maintenance
Built with
Want something like this?
Tell me what you have in mind and I'll put together a tailored quote.
Start a project