Zloma HUD [FREE][ESX][QBCORE][QBOX]

FiveM Releases
,
1

3bbad6d6-2033-4d3d-a3cb-6d0292860d52
3bbad6d6-2033-4d3d-a3cb-6d0292860d521672Ă—941 455 KB

Links

Modern HUD System for FiveM Roleplay Servers

Zloma HUD is a complete heads-up display resource designed for FiveM roleplay servers.

The resource focuses on clean UI, useful player information, vehicle HUD elements, server customization, and stable performance. It is built to provide players with a modern and readable interface while keeping the server-side configuration flexible for different server styles.

This resource is sold through Tebex and protected by FiveM Asset Escrow.
Configuration files and customization files remain editable for server-side setup, while the rest of the resource is escrow protected.

Features

Player HUD

  • Health display
  • Armor display
  • Hunger display
  • Thirst display
  • Stress support
  • Player ID display
  • Cash and bank display
  • Job information display
  • Clean and responsive UI layout

20260617052138_1
20260617052138_11920Ă—1080 480 KB

Vehicle HUD

  • Speedometer
  • Fuel display
  • Engine health display
  • Seatbelt status
  • Cruise control status
  • Vehicle lock status
  • Gear/RPM display
  • Vehicle indicator support
  • Vehicle-specific HUD visibility handling

20260617060040_1
20260617060040_11920Ă—1080 448 KB

Voice and Radio

  • Voice range display
  • Talking status
  • Radio status support
  • Configurable voice integration support

20260617052205_1
20260617052205_11920Ă—1080 478 KB

Minimap and Compass

  • Minimap handling
  • Compass display
  • Street name display
  • Zone/location display
  • Optional visibility controls

20260617054646_1
20260617054646_11920Ă—1080 610 KB

Customization

  • Configurable HUD elements
  • Configurable colors
  • Configurable status visibility
  • Server-side default settings
  • Easy integration with existing server resources
  • Editable configuration files for server-specific changes

20260617054356_1
20260617054356_12560Ă—1440 459 KB

20260617054358_1
20260617054358_12560Ă—1440 456 KB

20260617054400_1
20260617054400_12560Ă—1440 462 KB

20260617054402_1
20260617054402_12560Ă—1440 456 KB

Integrated Systems

  • Integrated stress system
  • Configurable stress gain and reduction logic
  • Vehicle mileage system
  • Mileage tracking for owned and driven vehicles
  • Mileage display support inside the HUD

Framework Support

  • ESX Legacy support
  • QBCore support
  • QBox support
  • ox_lib support

Optimization

  • Designed for low resource usage
  • Stable client performance
  • Optimized NUI updates
  • No unnecessary heavy loops
  • Suitable for larger roleplay servers

Dependencies

Required:

  • oxmysql
  • ox_lib

Optional:

  • pma-voice
  • Framework status resources depending on your server setup

Performance

Resource monitor:

  • Idle: 0.05 ms
  • Active usage: up to 0.15 ms
  • Normal usage does not exceed 0.15 ms in tested scenarios

Links
Code is accessible No
Subscription-based No
Lines (approximately) 20,000+
Requirements & dependencies ox_lib,
Support Yes

Additional note:
This resource is protected with FiveM Asset Escrow.
Editable files include configuration files and customization files.

3 Likes
2

Please add a green option!

3

Added to list for new update! :slight_smile:

4

Hey, this HUD looks really well designed at first glance, so good work on that front.

I wanted to grab the free version through Tabex/CFX, but during authorization I noticed that it requests the Discord guilds.join scope. When I tried removing that scope manually, Tabex returned an error saying “Discord membership required,” meaning that joining the Discord server is apparently mandatory just to access the download.

Honestly, this raises some serious red flags for me. I’m not saying that you’re personally running a scam or that you have malicious intentions. I’m saying that the mechanism itself falls into what I would consider scam/malicious behavior from a security perspective.

The guilds.join scope is heavily controversial in the Discord developer community because it has been abused extensively by malicious services and scammers to automatically move users between servers. For example, if a server gets banned or shut down, a service with this permission could potentially move large numbers of users to another server without those users explicitly choosing to join it.

There’s also a more general trust issue here. By authorizing guilds.join, you’re giving an application permission to automatically add your account to a server. If you later leave that server, the authorization can potentially still allow the application to add you again. You then have to go through Discord’s authorized apps/connections and manually find and revoke the permission.

And that’s a lot of unnecessary risk and hassle for a free HUD.

I’m saying this as a developer myself, with quite a bit of experience running and participating in online communities, even though my experience isn’t specifically in the FiveM scene. I personally wouldn’t make guilds.join a requirement for my own users, and I wouldn’t consider forcing users to join a Discord server an appropriate requirement either.

If someone likes the product, they can always join the Discord voluntarily for support, updates, community interaction, etc. If there’s a paid version or a direct download available, that’s also a perfectly reasonable alternative. But forcing someone to authorize an application that can automatically join them to a Discord server just to obtain free content is, in my opinion, crossing a line.

There are creators in the Discord community who have discussed this exact permission extensively, including No Text To Speech, because of how frequently this functionality has been abused.

Again, I’m not accusing you personally of being a scammer. I genuinely think the HUD looks great. But when I see a mandatory guilds.join authorization combined with a mandatory server membership requirement, all my security alarm bells go off.

If the Discord membership were optional, this would be a completely different story. I’d strongly recommend removing the forced server join and making the Discord an optional way for users to support and interact with the project. I think that would actually improve trust in what otherwise looks like a really solid HUD.

5

I appreciate your input. I will review the guilds.join permissions issue along with the Cfx/Discord guidelines related to it and determine how we can better integrate with Discord.

6

Added in new Update!

7

Thanks for the response! Just to clarify, I actually wasn’t referring to official Cfx or Discord guidelines in my original message. My main concern is solely about how the broader Discord developer community views the guilds.join scope and the security implications involved.

Because scammers frequently abuse this specific permission to forcibly move users between servers, having it as a mandatory requirement sets off security alarms for many users. It’s really about user trust rather than whether it technically breaks any guidelines.

Since you are using Tebex for your store (as required by Cfx), there is actually a much safer built-in alternative. Tebex has native Discord integration that allows you to verify if a user is in your Discord server or has a specific role before they can claim a package.

By utilizing Tebex’s official Discord sync, you can enforce your server membership requirement securely without needing a custom application that asks for the controversial guilds.join scope. Alternatively, you could just request the basic, read-only guilds scope to check a user’s server list, or simply make the Discord join completely voluntary.

Hopefully, this makes sense! I’d love to try out the HUD once the authorization process feels a bit safer.