KRUIGER LABS DOCUMENTATION Find it. Set it up.
Get back in-game.
Detailed FiveM server guides, product setup, troubleshooting, Vanta documentation, and practical answers — all in one searchable knowledge base.
Everything has a home.
Start with a category or search across every article.
Learning Paths
FiveM Servers
Free Scripts
Paid Scripts
Bots
Reference
Error Encyclopedia
Troubleshooting
Checklists
Recommended Services
Documentation
Frequently asked questions.
One page. Tap a section, then open the question you need.
FAQ SECTIONFiveM Installation FAQCommon FiveM installation, folder, ensure, dependency and restart questions.+
FiveM Installation FAQ
Where exactly does a resource go?
Put the complete resource folder under resources or a bracket category. The resource's fxmanifest.lua should be directly inside that resource folder.
Can I rename a resource?
Only when its documentation says that is supported. Exports, dependencies and code can refer to the original resource name.
Why does it work after I manually restart it?
That commonly points to start order or a dependency that was not ready during the cold boot.
Should I ensure every resource separately?
You can ensure individual resources or bracket categories. Explicit lines are easier to reason about when start order matters.
Why is FiveM saying the manifest is missing?
Check for an extra nested folder and confirm fxmanifest.lua is inside the actual resource directory.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONFrequently Asked QuestionsQuick answers for Kruiger Labs products, FiveM guides, Git, updates, and support.+
Frequently Asked Questions
Do I need a framework for every Kruiger free script?
No. Several Kruiger utilities are designed to be standalone. Always check the specific product page for the version you are installing.
Can I put resources inside bracket folders?
Yes. Bracket folders such as [kruiger] are commonly used to organize complete resource folders.
Should all permissions stay in server.cfg?
They can, but a large server is often easier to manage with a dedicated permissions.cfg loaded by exec permissions.cfg.
Can I manage my FiveM server through GitHub or GitLab?
Yes. Git is useful for versioned configuration and code you are allowed to store. Keep credentials out of the repository and use restricted deployment credentials for private repositories.
Should my server automatically deploy every commit?
Not necessarily. Production servers are usually safer with a review/test step before the live server pulls a change.
Where do I get support?
Work through the relevant troubleshooting page first. If the issue remains, join discord.gg/kruigerlabs and provide the product/version, relevant error, and steps already tried.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONPermissions FAQAnswers about ACE permissions, principals, groups, setup commands and role hierarchy.+
Permissions FAQ
What is an ACE?
An ACE is a permission rule. Resources can check named ACE objects to decide whether a principal is allowed to perform an action.
Why does an admin command say permission denied?
Verify the exact ACE object, the user's principal/group inheritance, and that the permissions file executes before the resource needs it.
Can I put ACEs in permissions.cfg?
Yes. Load it from server.cfg with exec permissions.cfg.
Should I grant wildcards to everyone?
No. Prefer the narrowest permission needed for the role.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONKruiger Paid Products FAQQuestions about installation, updates, configs, conflicts, the Ultimate Suite and support.+
Kruiger Paid Products FAQ
Can I install the Ultimate Suite over similar resources?
Plan the replacement first. Back up the server and disable conflicting HUD/chat/priority/headtag systems only when the Kruiger replacements are configured and ready.
Why should department IDs match?
Duty, HUD, Headtags and Chat integrations can refer to the same department. Stable internal identifiers prevent one component from referring to a department differently from another.
Can I share my paid resource files?
Follow the product license and delivery terms. Do not upload paid files to a public repository merely to deploy them.
Should I overwrite my old config during an update?
No. Back it up and compare the new default/config schema with your existing settings.
Why do the docs say to use my installed version's exact ACE?
Granular permission names can change between releases. The documentation avoids inventing a suffix that may not exist in your version.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONVanta FAQCommon questions about Vanta commands, dashboard, modules, verification, profiles, tickets and music.+
Vanta FAQ
Where is /commands?
Vanta's established help/command navigation uses /help.
Why does Vanta say a module is disabled?
The guild has that module disabled. A server manager can enable it in the dashboard.
Why can Vanta not assign my Verified role?
Check Manage Roles and move Vanta's bot role above the role it must manage.
How long does a verification link last?
The established web verification links expire after 5 minutes and are account-bound.
Are private profiles shown globally?
They should not be. The global directory is for public profiles.
Does a music failure mean Vanta is offline?
No. An individual provider or track can be unavailable while Vanta remains online.
Can I disable only one command?
Yes. Vanta's guild settings support module and individual command switches.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONHosting & Security FAQQuestions about CloudNord, bot hosting, Git deployment, VPNs, password managers, secrets and backups.+
Hosting & Security FAQ
Which FiveM host does Kruiger Labs recommend?
Kruiger Labs' preferred FiveM hosting recommendation in these docs is CloudNord. The recommendation page includes an affiliate disclosure.
Which bot host does Kruiger Labs recommend?
The preferred bot-hosting recommendation is Sparked Host, with an affiliate disclosure.
Is NordPass a VPN?
No. NordPass is a password manager. NordVPN is the VPN product.
Can a VPN replace server security?
No. A VPN does not replace MFA, unique passwords, least privilege, backups or server hardening.
Can I commit a private repository token because the repo is private?
No. Repository visibility does not make committed credentials safe.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONFiveM Beginner FAQA practical step-by-step Kruiger Labs guide to fivem beginner faq.+
FiveM Beginner FAQ
This guide walks through FiveM Beginner FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Short answer
FiveM Beginner FAQ is covered by the relevant Kruiger Labs guides; use the answer below as the quick operational rule.
What to do
Start from a known-good backup, follow the exact guide for the component/version, make one change at a time, and verify it before moving on.
What not to do
Do not publish secrets, blindly copy old configs, mix multiple competing resources, or use destructive reset commands merely to make an error disappear.
When to ask for help
If the documented test still fails, send Kruiger Labs Support the exact error, version, reproduction steps and sanitized configuration.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONNew Server Owner FAQA practical step-by-step Kruiger Labs guide to new server owner faq.+
New Server Owner FAQ
This guide walks through New Server Owner FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Preparation
Use the current recommended FXServer artifact and keep server binaries separate from server data. txAdmin is bundled with FXServer; you do not need to install it as a separate resource.
Initial setup
Run FXServer, open/link txAdmin, authenticate with Cfx, create the server profile, select the appropriate recipe, supply the server registration key, deploy, then save and run.
Configuration discipline
Keep server.cfg readable. Put related settings into clearly labeled sections or exec files. Never publish license keys, database credentials, webhooks or API secrets.
Operational test
Perform a full stop/start, connect from FiveM, verify txAdmin access, inspect the console, and test the server from a normal player's perspective.
Maintenance
Back up server-data, important txData/profile data and databases before major changes. Change one layer at a time: artifact, framework, then resources.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONFiveM Developer FAQA practical step-by-step Kruiger Labs guide to fivem developer faq.+
FiveM Developer FAQ
This guide walks through FiveM Developer FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Short answer
FiveM Developer FAQ is covered by the relevant Kruiger Labs guides; use the answer below as the quick operational rule.
What to do
Start from a known-good backup, follow the exact guide for the component/version, make one change at a time, and verify it before moving on.
What not to do
Do not publish secrets, blindly copy old configs, mix multiple competing resources, or use destructive reset commands merely to make an error disappear.
When to ask for help
If the documented test still fails, send Kruiger Labs Support the exact error, version, reproduction steps and sanitized configuration.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONResource Installation FAQA practical step-by-step Kruiger Labs guide to resource installation faq.+
Resource Installation FAQ
This guide walks through Resource Installation FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Create the resource
Use a dedicated folder under resources/[local] or another category. The resource root needs fxmanifest.lua; keep client and server responsibilities separate.
Manifest starter
fx_version 'cerulean'
game 'gta5'
author 'YourName'
description 'Resource description'
version '1.0.0'
client_script 'client.lua'
server_script 'server.lua'
Develop in small steps
Start with one observable behavior. Run refresh after adding a new resource, ensure ResourceName to start it, and restart ResourceName after edits. Watch both server console and F8.
Security boundary
Clients are not authoritative. Validate permissions, amounts, target IDs and state-changing requests server-side. Use local events when networking is unnecessary.
Release-quality check
Cold boot, reconnect, test two players, test allowed/denied permissions, inspect performance, remove debug spam, document config/dependencies, and tag a version.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONtxAdmin FAQA practical step-by-step Kruiger Labs guide to txadmin faq.+
txAdmin FAQ
This guide walks through txAdmin FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Preparation
Use the current recommended FXServer artifact and keep server binaries separate from server data. txAdmin is bundled with FXServer; you do not need to install it as a separate resource.
Initial setup
Run FXServer, open/link txAdmin, authenticate with Cfx, create the server profile, select the appropriate recipe, supply the server registration key, deploy, then save and run.
Configuration discipline
Keep server.cfg readable. Put related settings into clearly labeled sections or exec files. Never publish license keys, database credentials, webhooks or API secrets.
Operational test
Perform a full stop/start, connect from FiveM, verify txAdmin access, inspect the console, and test the server from a normal player's perspective.
Maintenance
Back up server-data, important txData/profile data and databases before major changes. Change one layer at a time: artifact, framework, then resources.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONDatabase FAQA practical step-by-step Kruiger Labs guide to database faq.+
Database FAQ
This guide walks through Database FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Plan the database
Know which database engine/version the resource supports. Create a dedicated database/user where possible, use a strong unique password, and restrict network exposure to what the application actually needs.
Connection configuration
Keep the connection string server-side. Never place it in client/shared Lua, NUI JavaScript, screenshots, public GitHub, or support posts. Verify hostname, port, database, username and TLS requirements.
Schema/imports
Back up first. Read SQL migrations before running them. Import only the schema/data required by your installed resource version and do not repeatedly import a destructive migration.
Test
Start the database adapter before resources that depend on it. Watch for authentication, DNS, timeout, missing-table and duplicate-column errors. Then perform an actual create/read/update path in-game.
Backup and rollback
Take a database dump before upgrades. A file rollback is not enough when an update also changed schema; document which code version matches which schema.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONGit & GitHub FAQA practical step-by-step Kruiger Labs guide to git & github faq.+
Git & GitHub FAQ
This guide walks through Git & GitHub FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Before you change anything
Confirm the repository, branch, destination folder and whether the server has terminal/SSH access. Back up local edits. Never place PATs, SSH private keys, .env files or production credentials in the repository.
First-time setup
Install Git if the host supports it. Clone into the intended parent directory, inspect the resulting folder, and confirm the resource/application entry files exist. For a private repository use a narrowly scoped credential or deploy key supported by your host.
Normal update workflow
Run git status first. If clean, fetch/pull the intended branch. Review the changed files, install dependencies only when lockfiles/package requirements changed, then restart only the required service/resource. Finish with a cold-boot test.
When git pull refuses
Do not use git reset --hard until you know what would be lost. Inspect git status and git diff. Preserve intentional server-only changes, reconcile conflicts, and keep secrets outside tracked files.
Verification
Record the commit hash deployed, confirm the application/resource reports the expected version, test its primary function, then inspect logs for errors.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONServer Security FAQA practical step-by-step Kruiger Labs guide to server security faq.+
Server Security FAQ
This guide walks through Server Security FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Short answer
Server Security FAQ is covered by the relevant Kruiger Labs guides; use the answer below as the quick operational rule.
What to do
Start from a known-good backup, follow the exact guide for the component/version, make one change at a time, and verify it before moving on.
What not to do
Do not publish secrets, blindly copy old configs, mix multiple competing resources, or use destructive reset commands merely to make an error disappear.
When to ask for help
If the documented test still fails, send Kruiger Labs Support the exact error, version, reproduction steps and sanitized configuration.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONPerformance FAQA practical step-by-step Kruiger Labs guide to performance faq.+
Performance FAQ
This guide walks through Performance FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Measure first
Do not optimize from guesses. Reproduce the problem with a stable player count/scenario and record server/client symptoms.
Isolate
Use resource monitoring/profiling tools and logs to identify the resource or operation consuming time. Compare idle and active behavior.
Common causes
Look for tight loops without appropriate waits, repeated database queries, oversized payloads, excessive entity creation, unnecessary NUI updates and log/event spam.
Change one variable
Optimize one hotspot, restart/retest under the same scenario, and compare measurements. Keep the previous version available for rollback.
Production validation
A change is not proven by one developer client. Test reconnects, multiple players, peak-use features and a full cold boot.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONMaps & Vehicles FAQA practical step-by-step Kruiger Labs guide to maps & vehicles faq.+
Maps & Vehicles FAQ
This guide walks through Maps & Vehicles FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Inspect the download
Extract it locally and identify the real resource root (fxmanifest.lua). Read its install notes and dependencies before uploading. Keep a backup of any resource it replaces.
Install
Place the resource under a logical bracket folder such as [vehicles], [maps], [eup] or [scripts]. Preserve the expected folder name unless the author says renaming is safe.
Manifest and data files
Check that streamed files and any required data/meta files are declared correctly by the supplied manifest. Do not invent manifest entries when the resource already ships a working manifest.
Start and test
Run refresh, then ensure ResourceName. Read the console before joining. Test the asset in multiple relevant locations/vehicles/outfits and then cold boot the whole server.
Typical failures
Missing assets often mean a nested folder, bad path/case, missing dependency, incorrect manifest/data declaration, or a conflict with another resource providing the same content.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONACE Permissions FAQA practical step-by-step Kruiger Labs guide to ace permissions faq.+
ACE Permissions FAQ
This guide walks through ACE Permissions FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Mental model
ACE is FiveM's permission system. An ACE grants or denies a named capability to a principal. Principals can inherit from groups, so design groups first instead of copying permissions onto every player.
Basic pattern
add_ace group.admin command allow
add_ace group.admin command.quit deny
add_principal identifier.fivem:YOUR_ID group.admin
Use real identifiers only in your private server configuration.
Split permissions cleanly
Keep larger permission sets in permissions.cfg, then load them from server.cfg with:
exec permissions.cfg
Place resource-specific ACEs before the resource starts when that resource reads permissions during initialization.
Test correctly
Test once as an authorized user and once as a normal user. If both succeed, your permission is probably too broad; if both fail, inspect the exact ACE object and principal inheritance.
Debug checklist
Confirm spelling/case, the actual player identifier, file execution order, inherited groups, explicit denies, and the exact permission object expected by the resource.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONNUI FAQA practical step-by-step Kruiger Labs guide to nui faq.+
NUI FAQ
This guide walks through NUI FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
How NUI fits together
A typical NUI resource has an fxmanifest.lua, client/server code where needed, and web assets such as HTML/CSS/JS. The manifest declares ui_page and the files clients need.
Minimal manifest shape
fx_version 'cerulean'
game 'gta5'
ui_page 'web/index.html'
files { 'web/index.html', 'web/style.css', 'web/app.js' }
client_script 'client.lua'
Opening and closing
Your Lua/JS client code controls focus and messages. Always provide a reliable close path; a stuck focus state can make the player appear frozen.
Callbacks
Treat data coming from the browser UI as untrusted input. If a callback ultimately changes authoritative game/server state, validate the action again on the server.
Debugging
Use the FiveM/client console and NUI developer tooling where available. Check file paths, manifest files, browser-console errors, callback names and focus state.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONVanta Setup FAQA practical step-by-step Kruiger Labs guide to vanta setup faq.+
Vanta Setup FAQ
This guide walks through Vanta Setup FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Short answer
Vanta Setup FAQ is covered by the relevant Kruiger Labs guides; use the answer below as the quick operational rule.
What to do
Start from a known-good backup, follow the exact guide for the component/version, make one change at a time, and verify it before moving on.
What not to do
Do not publish secrets, blindly copy old configs, mix multiple competing resources, or use destructive reset commands merely to make an error disappear.
When to ask for help
If the documented test still fails, send Kruiger Labs Support the exact error, version, reproduction steps and sanitized configuration.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONPaid Products FAQA practical step-by-step Kruiger Labs guide to paid products faq.+
Paid Products FAQ
This guide walks through Paid Products FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Short answer
Paid Products FAQ is covered by the relevant Kruiger Labs guides; use the answer below as the quick operational rule.
What to do
Start from a known-good backup, follow the exact guide for the component/version, make one change at a time, and verify it before moving on.
What not to do
Do not publish secrets, blindly copy old configs, mix multiple competing resources, or use destructive reset commands merely to make an error disappear.
When to ask for help
If the documented test still fails, send Kruiger Labs Support the exact error, version, reproduction steps and sanitized configuration.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
FAQ SECTIONKruiger Labs Support FAQA practical step-by-step Kruiger Labs guide to kruiger labs support faq.+
Kruiger Labs Support FAQ
This guide walks through Kruiger Labs Support FAQ from preparation through verification, with a rollback path and the checks that matter in a real faq environment.
Short answer
Kruiger Labs Support FAQ is covered by the relevant Kruiger Labs guides; use the answer below as the quick operational rule.
What to do
Start from a known-good backup, follow the exact guide for the component/version, make one change at a time, and verify it before moving on.
What not to do
Do not publish secrets, blindly copy old configs, mix multiple competing resources, or use destructive reset commands merely to make an error disappear.
When to ask for help
If the documented test still fails, send Kruiger Labs Support the exact error, version, reproduction steps and sanitized configuration.
Document status
Last reviewed: September 2026
Version note: Use the instructions that match your installed product/resource version. When behavior differs from your release, check its release notes before changing production configuration.
Troubleshoot first. We're here after.
Each product includes detailed troubleshooting. If you've worked through it and still need help, bring the error and what you've tried to Kruiger Labs Support.