Raycin Menu — Admin Features¶
The in-world Raycin Menu (rralan_nativemenu resource, F10 by default) is where
admins do day-to-day racing operations: host gates, server-wide whitelist mode,
runtime resource controls, and live diagnostics. Everything here is gated behind
an ACE check — non-admins see the Dev Tools section greyed out.
Getting in: how the admin check works¶
Every time you open the menu, your client asks the server: "is this player admin?" The server side runs through these ACEs in order and the first ALLOW wins:
| ACE checked | Granted by (typical) |
|---|---|
raycin_creator.access |
add_ace group.admin raycin_creator.access allow |
raycin_races.admin |
add_ace group.admin raycin_races.admin allow |
raycin_races.access |
add_ace group.admin raycin_races.access allow |
rralan_nativemenu |
Custom principal, optional |
If any one of these returns ALLOW, Dev Tools is unlocked. Most admin servers
already grant raycin_creator.access to group.admin, so adding your license to
group.admin is the path of least resistance:
See Quick Reference → Permissions for the full ACE / principal pattern.
Two diagnostic chat commands¶
If Dev Tools is greyed out and you think it shouldn't be, type these in chat
(press T then type, then Enter):
| Command | What it shows | Where the reply lands |
|---|---|---|
/raycin_check |
Your client-side _isAdmin state; also re-asks the server |
Chat box (yellow lines) + F8 client console |
/raycin_admin_check |
Your license + each ACE check result + final verdict + the rule that matched | Chat box (~6-7 yellow lines) + server console (audit line) |
When dev tools is greyed but should not be
Run /raycin_admin_check. If every ACE shows DENY, check:
- Your license in chat matches the one in
server.cfg add_principal … add_ace group.admin raycin_creator.access allowis inserver.cfg- The
rralan_nativemenu/fxmanifest.lualineserver_script 'server.lua'is NOT commented out (this exact issue silently blocked admin status for a long time before being found — the server-side admin sync simply wasn't running).
🏆 Player Hub — everyday tools for every player¶
Open Raycin Menu → Racing Lobby → 🏆 Player Hub. This submenu is available to every player (no admin check) and collects the things you reach for between races. It was previously called My Stats — same place, broader contents.
| Item | What it does |
|---|---|
| My Race Points | Fetches your personal RP total from the server and prints it to chat. |
| Top 10 Leaderboard | Pulls the global RP leaderboard (top 10 by points) into chat. |
| My Vehicles | Opens your personal garage showroom — save builds, customise, delete. Same as the /my_vehicles command. Also still available under Quickish Race Sessions for muscle-memory. |
| 🚩 Set My Flag | Submenu of country flags (GB / US / DE / FR / ES / IT / BR / AU / JP / NL / PT / SE / BE / ZA / NO). Pick one to set the flag shown next to your name on the in-race HUD and scoreboard. Wraps the /setflag <code> command. |
For admins¶
There is nothing admin-only inside Player Hub — admins see exactly the same items as players. Admin-only operations live in Dev Tools, Hosting Permissions, and Whitelist Mode (covered below). The garage / RP / leaderboard / flag items work identically whether you're admin or not, so admins can use Player Hub for their own pre-race prep the same way players do.
Dev Tools — quick admin productivity shortcuts¶
Open Raycin Menu → Racing Lobby → 🔬 Dev Tools. Every item below is gated by your admin check.
📋 Show My License¶
Prints all of your FiveM identifiers (license:, fivem:, discord:, license2:)
to your chat box. Saves the "join the server then dig through the console log"
dance when you need to grant ACE permissions to a new admin.
🔄 Restart raycin_races (2-click confirm)¶
Hot-restarts the raycin_races resource. First click arms (item flashes ⚠
"Click again to confirm"). Second click within 3 seconds fires the restart.
Server console logs [raycin_races] /restart triggered by <admin name>.
Players in an active race
A restart drops them back to freemode and ends the current race. Use during quiet windows or when you genuinely need to push a Lua fix.
🧹 Force-unstick everyone (2-click confirm)¶
Broadcasts a closeNUI message to every connected player. Hides any stuck
v3 NUI screen (showroom, race-creation, leaderboard, etc.) and tells Lua to
release NUI focus.
Useful when a player reports "I'm stuck on the menu/garage and can't move" — hit this and their state clears in seconds, no disconnect/reconnect needed.
📊 List active rooms¶
Opens a sub-menu populated by a server callback. Shows every open race room:
🏁 <track name> · 4 👥 · racing
Host: KernowGlyn | Mode: face_to_face | Vehicle: track_class | Cat: F2F
Display-only for now (no click-to-spectate or click-to-end actions yet — those are candidate features for a future round).
🔐 Hosting Permissions — who can host races¶
The first sub-menu in Dev Tools. Controls who is allowed to host a race on your server (separate from who can connect — that's the Whitelist Mode).
| Mode | Effect | When to use |
|---|---|---|
| 🟢 Whitelist (role-gated) | Approved whitelist roles (admin/staff/crew/drivers/vip/temp) + ACE admins can host |
Default for community servers |
| 🌐 Open to everyone | Anyone connected can host | Casual/community days, public events |
| 🔧 ACE-only (lockdown) | Only players with the raycin_races.access ACE |
Events; tournaments where only staff host |
| 🔒 Strict (whitelist roles only) | Whitelist roles only — even ACE admins are denied | Maximum control |
The currently active mode shows a ✓ tick badge + "ACTIVE" right-side label.
Clicking another mode fires immediately; the server updates Config.Whitelist.*
in memory, persists the choice to data/hosting_mode.json, and the change
survives restart raycin_races and full server restarts.
Only one mode is active at a time — Open beats everything
The four modes are mutually exclusive, not a stack of toggles. Every
time you click a mode, applyMode() first clears the previous flags then
writes the new mode's combination of UseRaycinWhitelist / UseAce /
AllowCooldownFallback / AllowAnyone. So picking 🌐 Open doesn't
"add to" Whitelist — it overwrites it completely.
Priority order used to detect the current mode (highest wins):
AllowAnyone == true→ Open (short-circuits the entire permission callback inmain_server.lua— no other check runs)UseRaycinWhitelist && !UseAce→ StrictUseRaycinWhitelist && UseAce→ Whitelist (roles)!UseRaycinWhitelist && UseAce && !AllowCooldownFallback→ ACE-only
Open is the strongest signal. If you ever set it, every player can host until you flip back to another mode — there's no role check, no ACE check, no cooldown trap. That's the whole point.
How the mode is restored at start
On raycin_races resource start, server/admin_overrides.lua reads
data/hosting_mode.json. If a previous admin set a mode, that mode is
re-applied. If the file is missing, Config.Whitelist.* defaults from
config_server.lua apply untouched.
🛡 Whitelist Mode — who can connect to the server¶
The second sub-menu in Dev Tools. Controls who is allowed to connect to the
FiveM server itself. Mirrors raycin-whitelist's /setmode command.
The 5 modes¶
| Mode | Allowed roles | Common use |
|---|---|---|
| 🌐 Everyone | No role check | Default for public servers |
| 🏎 Drivers + above | drivers, crew, staff, admin |
Casual race nights — keeps out probation/temp |
| 👥 Crew + above | crew, staff, admin |
Crew-only events |
| 🛡 Staff + admin | staff, admin |
Maintenance windows |
| 🔒 Admin only | admin |
Emergency lockdown |
Delayed (default) vs Instant¶
The submenu has a ⚡ Instant change checkbox at the top:
| Toggle | Behaviour |
|---|---|
| OFF (default) | 60-second grace + chat announce + Discord log. Players see "RAYCIN NOTICE — switching to X in 60 seconds". At T+60s the mode actually flips, ineligible players are kicked, and a "✅ RAYCIN ACTIVE" announce confirms. Polite. |
| ON | Mode flips on the next tick. Non-matching players are kicked immediately. The pre-announce is skipped (only the final announce + kick run). Use for emergency lockdown. |
What players see¶
- Pre-announce (delayed only, T+0): styled RAYCIN NOTICE chat + QBCore notification
- Final announce (T+delay): styled RAYCIN ACTIVE chat + QBCore notification
- Discord audit log: Two embeds for delayed (Scheduled orange + Changed green) or one for instant (INSTANT orange)
- Ineligible players: dropped via
DropPlayer(src, reason)with the rejection reason visible on their FiveM disconnect screen
Real-time badge updates¶
Whenever the mode actually flips on the server:
- All connected admins get a yellow chat line:
[raycin] 🛡 Whitelist Mode is now: staff_only (by KernowGlyn) - The ✓ ACTIVE badge in any open Whitelist Mode submenu repaints to the new mode in real time
- Non-admins see only the standard raycin-whitelist styled broadcast (no extra noise)
Safety nets¶
- Rate limit: Spamming mode changes hits
Config.RateLimit.setmodeand the request is rejected withFAIL: rate-limited - Pending lock: Only one mode change can be in-flight at a time. Clicking a second mode during the 60s grace returns
FAIL: a mode change is already pending - DB persistence: The mode survives server restarts (read from
raycin_whitelist_modetable latest row on boot)
Instant mode kicks are immediate
There is no grace window with Instant ON. If you switch to Admin only instantly, every non-admin currently connected is kicked in less than a second. Useful for stopping abuse mid-incident; harmful for routine flips. Leave Instant OFF unless you specifically need it.
Access scenarios — what each gate actually does¶
Two independent gates control what a player can do. Knowing which gate blocks what is the key to diagnosing any "I can't…" report quickly.
The two gates do NOT affect each other — they fire at different moments
Whitelist Mode runs once at the connection screen (before the player loads in). Hosting Permissions runs every time a player clicks open the race menu (after they're already on the server). Different code paths, different events, different decisions — neither reads the other's state.
Think of it as a front door + an internal door:
- Whitelist Mode = the front door. If it kicks you, you never reach the lobby — Hosting Permissions is irrelevant for you.
- Hosting Permissions = an internal door that only opens when you click Create Race. Whitelist Mode is irrelevant here — you're inside.
So you can mix-and-match freely (see the Quick decision table below).
The only indirect link: if you set Hosting = 🟢 Whitelist (roles) or
🔒 Strict, the host check reads the player's role from the same
raycin_whitelist DB table the connection check uses. A player with no
row fails both — for different reasons in different places. Set Hosting
to 🌐 Open or 🔧 ACE-only and even that indirect link disappears.
| Gate | Controlled by | What it decides |
|---|---|---|
| Whitelist Mode | Raycin Menu → 🛡 Whitelist Mode (or /setmode) |
Whether the player can connect to the server at all. Checked once at the connection screen. |
| Hosting Permissions | Raycin Menu → 🔬 Dev Tools → 🔐 Hosting Permissions | Whether a player (who is already on the server) can click Create Race. Checked every time they open the race menu. |
My Vehicles is not gated by either (since Config.AllowPersonalVehiclesForAll = true)
— any connected player can save / customise personal builds.
Quick decision table¶
This is the master reference. Read across a row: "if I want Trench to do X, what do I set?"
| Goal for the player | Whitelist Mode setting | Hosting Permissions setting | What the player can do |
|---|---|---|---|
| Public party — anyone can do everything | 🌍 Everyone |
🌐 Open to everyone |
✅ Connect · ✅ Host · ✅ Join · ✅ My Vehicles |
| Public connect, but only trusted hosts | 🌍 Everyone |
🟢 Whitelist (roles) |
✅ Connect · ❌ Host (unless approved + correct role) · ✅ Join · ✅ My Vehicles |
| Members club — only whitelisted in, anyone in can host | 🚗 Drivers Only (or higher) |
🌐 Open to everyone |
✅ Connect (if has role) · ✅ Host (everyone who got in) · ✅ Join · ✅ My Vehicles |
| Locked club — only trusted in, only trusted host (recommended for events) | 🚗 Drivers Only (or higher) |
🟢 Whitelist (roles) |
✅ Connect (if has role) · ✅ Host (same role check) · ✅ Join · ✅ My Vehicles |
| Total lockdown — admins only | 👑 Admin Only |
🔧 ACE-only |
✅ Connect (admins) · ✅ Host (admins) · ❌ Everyone else kicked at connect |
| Strict whitelist, no admin ACE escape hatch | 🚗 Drivers Only (or higher) |
🔒 Strict |
✅ Connect (if has role) · ✅ Host (only role-matched players) · admins must also have a whitelist row |
Hosting vs My Vehicles — side-by-side compare¶
My Vehicles has its own config flag (Config.AllowPersonalVehiclesForAll in
config/config_client.lua). That flag — combined with your Hosting Permissions
choice — decides who can open the garage. Two scenarios:
Default setup (AllowPersonalVehiclesForAll = true) — what ships now:
| Player situation | Hosting Permissions | Can HOST a race? | Can open MY VEHICLES? |
|---|---|---|---|
| Admin (ACE allowed) | Any setting | ✅ Yes | ✅ Yes |
| Whitelisted (correct role) | 🌐 Open · 🟢 Whitelist · 🔒 Strict | ✅ Yes | ✅ Yes |
| Whitelisted (wrong role) | 🟢 Whitelist · 🔒 Strict | ❌ Denied | ✅ Yes |
| Whitelisted (wrong role) | 🌐 Open to everyone | ✅ Yes | ✅ Yes |
| Not whitelisted (random player) | 🌐 Open to everyone | ✅ Yes | ✅ Yes |
| Not whitelisted (random player) | 🟢 Whitelist · 🔧 ACE-only · 🔒 Strict | ❌ Denied | ✅ Yes |
Locked-down setup (AllowPersonalVehiclesForAll = false) — flip this in
config/config_client.lua if you want the garage gated like hosting:
| Player situation | Hosting Permissions | Can HOST a race? | Can open MY VEHICLES? |
|---|---|---|---|
| Admin (ACE allowed) | Any setting | ✅ Yes | ✅ Yes |
| Whitelisted (correct role) | 🌐 Open · 🟢 Whitelist · 🔒 Strict | ✅ Yes | ✅ Yes |
| Whitelisted (wrong role) | 🟢 Whitelist · 🔒 Strict | ❌ Denied | ❌ Denied |
| Whitelisted (wrong role) | 🌐 Open to everyone | ✅ Yes | ✅ Yes |
| Not whitelisted (random player) | 🌐 Open to everyone | ✅ Yes | ✅ Yes |
| Not whitelisted (random player) | 🟢 Whitelist · 🔧 ACE-only · 🔒 Strict | ❌ Denied | ❌ Denied |
Key takeaway: with the default flag, My Vehicles is always available to any connected player (because it's a personal feature — saved builds don't affect anyone else). With the locked-down flag, My Vehicles follows the exact same rules as hosting.
To change the flag:
-- config/config_client.lua
Config.AllowPersonalVehiclesForAll = true -- default: anyone can open the garage
-- Config.AllowPersonalVehiclesForAll = false -- locked: garage uses hosting permissions
restart raycin_races.
Scenario walkthroughs — step by step¶
Scenario A — "I want my test player Trench to be able to host"¶
- Open Raycin Menu → 🔬 Dev Tools → 🔐 Hosting Permissions.
- Pick 🌐 Open to everyone.
- (That's it.) Trench can now click Create Race without applying for whitelist.
Scenario B — "I want Trench whitelisted as a normal driver, not an admin"¶
- Open Raycin Menu → 🔬 Dev Tools → 👤 Set Player Role.
- Find Trench in the list, scroll the role to drivers, press Enter to apply.
- Open Raycin Menu → 🔬 Dev Tools → 🔐 Hosting Permissions → 🟢 Whitelist (roles).
- Trench can now connect, host races, and join. They get no admin tools.
Scenario C — "I want to run a private members-only race night"¶
- Pre-event: assign Crew / Drivers roles via 👤 Set Player Role (or web Apply).
- Open 🛡 Whitelist Mode → pick 🚗 Drivers Only. Currently-connected non-drivers get a 30-second warning then get kicked.
- Open 🔐 Hosting Permissions → leave at 🟢 Whitelist (roles) so only your approved members can host.
- After the event: 🛡 Whitelist Mode → 🌍 Everyone to reopen the server.
Scenario D — "I'm closing the server for maintenance, only I should be in"¶
- Open 🛡 Whitelist Mode → 👑 Admin Only.
- Open 🔐 Hosting Permissions → 🔧 ACE-only.
- All non-admins get kicked at the connection screen; nobody else can host.
- Don't forget to flip both back when you reopen.
Scenario E — "A friend joined and says 'You don't have permission to host'"¶
- Check Raycin Menu → 🔐 Hosting Permissions: is it on Whitelist / ACE-only / Strict?
- If Whitelist (roles): have they been approved? Use 👤 Set Player Role to give them a role from the allowed list (admin / staff / crew / drivers / vip / temp).
- If ACE-only: only ACE-allowed players can host — easiest fix is switch Hosting Permissions to 🟢 Whitelist (roles) and give them a role, or 🌐 Open to everyone for casual play.
- Watch the server console for the diagnostic line: That tells you immediately which gate denied them.
Scenario F — "A friend can't even connect to the server"¶
- Check Raycin Menu → 🛡 Whitelist Mode. If it's anything other than 🌍 Everyone, they need a whitelist row.
- Use 👤 Set Player Role to give them an appropriate role — they need to reconnect after you do this.
- Or switch Whitelist Mode → 🌍 Everyone if you want unrestricted joining.
- Check the FiveM server console — the rejection reason is logged
(
Whitelist mode: Drivers Onlyetc.).
Mental model — read this once and remember¶
Whitelist Mode = the door of the club (can they walk in?)
Hosting Permissions = the DJ booth (once they're in, can they pick the track?)
My Vehicles = your locker (once in, always yours — no one gates it)
Fake Drivers, Lock/Unlock Race¶
Existing Dev Tools items that pre-date this round:
- Fake Drivers — Toggle on/off ghost drivers that appear in the HUD bar (visual only, for solo race testing). No resource restart required.
- 🔒 Lock Race / 🔓 Unlock Race — Prevent or allow new players joining the race room.
Where the code lives¶
For server owners or maintainers debugging:
| Feature | File |
|---|---|
| Admin check (server) | rralan_nativemenu/server.lua (must be registered in fxmanifest.lua — was previously a commented-out line) |
| Admin client state | rralan_nativemenu/client.lua (_isAdmin var, adminResult event) |
| Hosting Permissions toggle | raycin_races/server/admin_overrides.lua (escrow_ignore) |
| Show License / Restart / Force-unstick / List rooms | raycin_races/server/admin_overrides.lua + raycin_races/client/admin_helpers.lua |
| Whitelist Mode wrapper | raycin-whitelist/server.lua (AdminSetMode export) |
/raycin_check |
rralan_nativemenu/client.lua |
/raycin_admin_check |
rralan_nativemenu/server.lua |
All four raycin_races admin files are listed in fxmanifest.lua's
escrow_ignore block, meaning they stay readable for live operations and
survive re-escrow.
Quick test checklist when adding a new admin¶
- Add their license to
group.admininserver.cfg(or grantraycin_creator.accessdirectly) - They join — open chat (
T) →/raycin_admin_check— confirm verdict isALLOW - They open Raycin Menu (
F10) → Racing Lobby → Dev Tools should NOT be greyed - Each Dev Tools item works (Show License, Restart, Force-unstick, List rooms, Hosting Permissions, Whitelist Mode)
- Discord audit channel logs the join + any mode changes they make