Advanced Pole Dancing — Script for FiveM
Rhythm-based pole-dance script for FiveM. QTE minigame, audience tipping, 6 venue presets, in-game editor. ESX/QBCore/QBox/ox_core/standalone.
Overview
Overview
Advanced Pole Dancing is a rhythm-driven, rewards-based pole performance script for FiveM. Players walk up to a pole, trigger the prompt, and step into a QTE mini-game where Perfect, Good, and Miss hits build a streak that unlocks new animations, ramps the difficulty curve, and scales per-hit payouts through a configurable multiplier. Anyone standing inside a marked spectator polygon becomes an audience member — either auto-paying per landed QTE or tipping through an on-screen wallet UI that plays GTA V’s “Make It Rain” emote in front of the venue. Ships with six bundled venue presets, an in-game level editor for new poles and zones, a SQL-backed leaderboard, 13 auto-detected languages, and the entire economy is server-authoritative against 1.x-era exploits.
What’s inside
The QTE minigame. Each performance is a rhythm sequence with Perfect / Good / Miss judgement on every input. Streaks build per consecutive Perfect or Good hit, with animation tier unlocks at 50 and 100 streak, automatic difficulty escalation from easy → medium → hard, and particle effects that flare at milestone hits. Per-hit payouts scale with a streak multiplier on top of flat completion bonuses. Personal-best tracking is on by default and feeds the persistent leaderboard.
The spectator system. Every venue includes one or more spectator polygons — arbitrary 2D shapes drawn around the pole. Anyone standing inside is auto-enrolled as audience. Two economic modes:
- Auto-pay mode — spectators pay per QTE the dancer lands. Settles server-side; clients never compute reward amounts.
- Donation-only mode — spectators tip through an on-screen wallet UI. Each tip triggers the “Make It Rain” emote with a cash-pile prop and money-rain particles, visible to nearby players. A genuine social loop.
Venue presets, ready to install. Six bundled presets cover the venues your players are most likely to be using already: Fiv3Devs Vanilla Unicorn MLO, stock GTA V Vanilla Unicorn, Gabz Vanilla Unicorn, Gabz + Fiv3Devs Bahama Mamas combo, Molo LUX, and Fiv3Devs Galaxy Nightclub. Together that’s 17+ poles and 20+ spectator polygons out of the box. One install command per preset and you’re live.
In-game level editor. No JSON editing. /setpolecoords drops a new pole
at your current position; /createspectatorzone draws a polygon vertex by
vertex around it. Both persist immediately to poles.json and
spectator_zones.json — no server restart. Visualisation overlays show
you exactly what your players will see.
What makes it different
Framework-agnostic with real auto-detection. Most pole scripts on the market either lock you into ESX or require manual bridge configuration. Advanced Pole Dancing detects ESX, QBCore, QBox, and ox_core automatically on first boot — notifications, money operations, admin gating, and job restrictions all wire up without you touching a config file. If none of those are present, it falls back to a fully working standalone mode.
Server-authoritative money against 1.x exploits. The 2.x line was a ground-up rewrite focused on the security model. Every reward — per-hit QTE payout, completion bonus, spectator auto-pay, donation — settles on the server. Clients never compute amounts. Rate limiting closes the event-spam vectors that affected the original release. This is the single biggest reason to be on 2.2.5+.
13 languages auto-picked per client. Players on a French GTA client see French; German clients see German; Italian clients see Italian. No per-server configuration, no “pick your language” menu — the script reads each client’s GTA language setting and serves the matching strings.
0.00 ms idle resmon. The QTE thread, the spectator polygon thread, and the animation thread are all gated on actual dance activity. With nobody on a pole, the script is parked. With one active dancer, it costs a fraction of a millisecond per audience member running the audience-side loop.
Framework support
Ships with first-party support for ESX, QBCore, QBox, and ox_core, with a standalone fallback for custom frameworks. Notifications, money handling, admin command gating, and job-restriction enforcement all use each framework’s native API directly. Job restriction lets you lock pole dancing to a specific job (e.g. only employees of the venue), and a Free Mode toggle pauses earnings without nuking the streak — useful for practice, tutorials, or events where the economy shouldn’t be active.
Installation
Drop the folder into resources/, add ensure fiv3devs_polescript to
server.cfg, and restart. The script size is ~837 KB on disk; streaming
memory is 0 MB because no game assets are streamed — the venue
geometry comes from whichever MLO you’re using. Detailed installation
notes, including the SQL schema for the leaderboard table and the
venue-preset import commands, ship with the resource README.
Technical specifications
| Category | Scripts |
|---|---|
| Framework support | ESX · QBCore · QBox · ox_core · standalone · standalone |
| Resource name | fiv3devs_polescript |
| License | Escrowed · single-server Tebex license |
| Current version | v2.2.6 |
Installation
Drop the folder into resources/, add the ensure line to
server.cfg, and restart. No database migrations, no dependency chains.
# server.cfg
ensure fiv3devs_polescript Changelog
- Added PlayFailAnimation = true/false, for those who don't want failing animations
- Cleaned `poles.json` and `spectator_zones.json` for fresh installs.
- Complete script overhaul.
- More secure — server-authoritative money handling and rate limiting close known 1.x exploit vectors.
- Cleaned, deduplicated, and reorganised internals.
- Bug fixes across the QTE, spectator, and animation threads.
- New features — see product page for the full list.
Frequently asked questions
01 Which frameworks does Advanced Pole Dancing support?
Auto-detects ESX, QBCore, QBox, and ox_core out of the box, with a standalone fallback for servers running custom frameworks. Bridge wiring covers notifications, money handling, admin gating, and job restrictions on all four supported frameworks. FiveM Enhanced is not supported yet.
02 Do I need to edit JSON files to place poles or spectator zones?
No. The script ships with `/setpolecoords` to drop a new pole at your current position and `/createspectatorzone` to draw an arbitrary polygon around it. Both persist to `poles.json` and `spectator_zones.json` immediately — no server restart needed — and the in-game editor visualises everything in real time.
03 How does the money system actually work?
Two modes. In `auto-pay` mode, every QTE the dancer lands triggers a per-hit payout that scales with a configurable streak multiplier, on top of flat completion bonuses. Spectators standing inside the polygon are auto-enrolled as the audience and pay per hit. In `donation-only` mode, spectators tip through an on-screen wallet UI that plays GTA V's "Make It Rain" emote with cash-pile prop and money-rain particles, visible to nearby players.
04 Is the money handling safe from common script exploits?
Yes. All money operations run server-authoritative with rate limiting — no client trust, no client-side reward calculation. This is the main difference between 2.x and 1.x; we audited every payout path during the 2.2.5 overhaul to close the exploit vectors seen on the older line.
05 What's the performance footprint?
0.00 ms resmon at idle. The QTE, spectator polygon, and animation threads are all gated on actual dance activity, so they stay parked until someone walks up to a pole and triggers the prompt. Active dancing adds a fraction of a millisecond per client running the QTE loop.
06 Which venue presets are included?
Six. Fiv3Devs Vanilla Unicorn MLO, stock GTA V Vanilla Unicorn, Gabz Vanilla Unicorn, Gabz + Fiv3Devs Bahama Mamas combo, Molo LUX, and Fiv3Devs Galaxy Nightclub — covering 17+ poles and 20+ spectator polygons out of the box. Install a preset with a single command and you're live.
07 Does it require any specific MLO to work?
No. The script is MLO-agnostic — no coordinates are baked into config. Use one of the bundled presets if your venue matches, or use `/setpolecoords` and `/createspectatorzone` to wire it up to literally any interior.
08 Can I restrict pole dancing to a specific job?
Yes. Job restriction is configurable and uses your framework's job system directly (ESX `getJob`, QBCore `PlayerData.job`, QBox equivalents). There's also a Free Mode toggle that pauses earnings without nuking the streak — useful for practice, tutorials, or events where you don't want the economy active.
09 What languages does it support?
13 included translations, auto-picked from each client's GTA language setting. Players on a French client see French prompts, German clients see German, etc., with no per-server configuration required.
Ship Advanced Pole Dancing to your server today.
One license. Lifetime updates. Discord support from the people who built it.