FzD Scripts

Welcome to the official documentation for FzD Scripts. We create FiveM resources with a simple goal: make scripts that are useful, polished and comfortable to use in a real server environment. We care about how a resource works just as much as how it looks, so our focus is not only on adding features, but on making those features feel considered and dependable for both server owners and players. Our resources are built around practical configuration, sensible defaults and clear documentation. Where a script needs to integrate with a framework or another resource, we aim to make that integration straightforward without turning the resource into a collection of unnecessary dependencies.

​

What we prioritise

​

Functionality first

A script should solve a real problem and do it well. We prioritise useful features, predictable behaviour and configuration that gives server owners control without making setup unnecessarily complicated. That means we would rather build a smaller feature properly than add something simply to make a feature list longer.

​

Controller-friendly by design

Controller support is an important part of FzD Scripts. FiveM resources are often designed around keyboard and mouse first, with controller support considered later — or not at all. When a resource involves menus, player input, NUI or interactive controls, we aim to consider controller users from the beginning of the design process. Where the FiveM environment allows it, we look at things such as:

• controller navigation and focus behaviour
• sensible confirm and back controls
• avoiding unnecessary mouse-only interactions
• clear on-screen input prompts
• key mapping and remapping where appropriate
• keeping keyboard, mouse and controller behaviour consistent

Not every FiveM integration can provide identical behaviour across every input method, but controller support is something we actively design for rather than treating as an optional extra.

​

Qbox and framework integration

We aim to keep our resources as standalone and self-contained as practical, while still integrating properly with the frameworks that FiveM servers actually use. Qbox is one of the ecosystems we prioritise when a resource benefits from framework integration. Where appropriate, we also support environments such as QBCore, ESX and standalone servers. Framework support is handled on a resource-by-resource basis. We do not add a framework dependency simply for the sake of having one; if a feature can work cleanly without a framework, we prefer to keep it independent.

​

Polished user experience

Functionality is only one half of a good resource. Interfaces should also be clear, responsive and consistent. We put attention into menu behaviour, visual hierarchy, interaction flow and the small details that make a resource feel like a finished product rather than something that has simply been made to work.

​

Straightforward integration for developers

When a resource exposes exports, events or other integration points, the goal is to make them easy to understand and predictable to use. The documentation for each resource includes the setup information, configuration options and developer reference needed to integrate it into your own server resources without having to dig through the source code to understand the basics.

​

Resources

Each FzD Scripts resource has its own expandable section under Resources in the navigation. This keeps the documentation organised as the catalogue grows while allowing each script to have its own installation guides, configuration, examples, API reference and troubleshooting pages.

​

Learn more about FzD Scripts

​

Need help?

If you run into an issue, use the support section for the relevant resource first. Resource-specific troubleshooting pages cover common setup, configuration and compatibility problems, while the main support page explains what information to include if you need further help.