Name Badges

namebadges

00c9c11d01d20e59c7613fc3f169ad84cb3a969e_2_690x35

Fully optimized and synced name badge script that lets players display their character’s name, rank, or job title. Works with ESX, QB, QBOX and custom frameworks. Perfect for law enforcement, corporate jobs, and immersive professional roleplay.

675c9f7b52fa85d757fc779e47163fe88ed0c8fe_2_690x35

https://www.youtube.com/watch?v=WJaQG2_t2Zo

b108dd158e6dbdc7b8f07bab36a81b3b11a798cd_2_690x35

firstname

secondname

third

fourth

0127e37a1ff8c9bffaf6e343a6811db67fd8e512_2_690x35

  • Easy configuration
  • Easy localization
  • Job restrictation
  • Sync with other players
  • Placement Mode
  • Name and last positions saving SQL
  • Custom objects
  • Optimized

99b0dfe3e0a8ab1d3f21c5f0fb66d42c47a1c2e7_2_690x35

Buy via Tebex (29.99€)

Code is accessible No
Subscription-based No
Lines (approximately) 1000+
Requirements N/A
Support Yes
3 Likes

how does this handle networked prop limits?
IE: 60+ officers in 1 area, would props start disappearing?

Natively, theres a prop limit in a given area before either they sync out or cause overload.

I am also wondering this, or is this based on runtime textures?

I feel like we need some info on the backend here! :smiley:

look nice, but how add custom place settings ? like use gizmo to change place :33

Our script works within FiveM’s native prop limits and does not bypass engine restrictions. In high-density scenarios (such as the 60+ players you mentioned), props will not randomly disappear; however, as engine limits are approached, some entities may stream out or go out of scope, which is expected behavior in FiveM.

We minimize this by keeping props client-side where possible and reducing unnecessary network load.

We have tested the system with up to 30 players in the same area without any issues.
However, if you encounter any problems, please feel free to contact us, and we will be happy to assist you.

We have already provided the relevant details in our previous message. If you have any further or different questions, please feel free to contact us and we’ll be happy to assist you.

It’s not a full gizmo system, but we do provide a simple positioning tool as shown in the showcase video. You can use it to adjust placement in a practical way.

If there’s enough demand, we may consider adding a more advanced gizmo-based system in the future.

So in short, this spawns a individual prop per player with a nametag?

Turned out really good

1 Like

what’s the resmon when there’s 5-10 ppl around with this badge attached?

also what’s the performance of the fivem subchromium since using DUI?

Yes, exactly. Each player has their own individual prop with a nametag attached. These are handled client-side to minimize network load and avoid hitting limits.

With 5–10 players in the same area, resmon usage remains at ~0.00 ms, only briefly reaching ~0.01 ms during prop placement.

The DUI is based on a very simple HTML setup, so it does not introduce any measurable overhead to FiveM’s Chromium.