How to Enable Cayo Perico on Your FiveM Server

Enabling Cayo Perico in your FiveM server can enhance the gameplay experience by adding a new island for your players to explore. Here’s a simple, step-by-step guide to get Cayo Perico up and running on your server.

Leveren:

• FiveM Server Build 3324 or Higher – Ensure your FiveM server is running the required build.nServer Configuration File (server.cfg) – The configuration file where you will add the necessary settings.nAccess to Server Files – You need the necessary permissions to modify server files and upload new scripts.

Gereedschap:

• Text Editor – For editing the server configuration files (server.cfg). Examples include Notepad++, Sublime Text, or Visual Studio Code.nFTP Client – For uploading files to your server if it’s hosted remotely. Examples include FileZilla or WinSCP.nServer Console Access – To run commands and restart the server.

Materialen: HeistIsland Script – The HeistIsland_island_load.lua script that enables Cayo Perico on your server. This can be downloaded from the GitHub repository.

Cayo Perico Script

Download the Script – Download the HeistIsland_island_load.lua script from the GitHub-repository:

local islandVec = vector3(4840.571, -5174.425, 2.0)
Citizen.CreateThread(function()
    while true do
	local pCoords = GetEntityCoords(GetPlayerPed(-1))		
		local distance1 = #(pCoords - islandVec)
		if distance1 < 2000.0 then
		Citizen.InvokeNative("0x9A9D1BA639675CF1", "HeistIsland", true)  -- load the map and removes the city
		Citizen.InvokeNative("0x5E1460624D194A38", true) -- load the minimap/pause map and removes the city minimap/pause map
		else
		Citizen.InvokeNative("0x9A9D1BA639675CF1", "HeistIsland", false)
		Citizen.InvokeNative("0x5E1460624D194A38", false)
		end
	Citizen.Wait(5000)
    end
end)

By following these steps, you should have Cayo Perico enabled on your FiveM server, providing your players with a new and exciting area to explore.

Practical checklist

Use this guide as a staging checklist before changing a live FiveM server. Confirm the current server artifact version, framework version, resource dependencies, database changes, and any client-side files before you apply the change.

• Back up the affected configuration files and database tables.
• Apply the change on a test server first.
• Watch the server console and client F8 console for errors.
• Check whether the change affects jobs, inventory, vehicles, maps, voice, permissions, or player data.
• Document the exact file, command, or setting you changed so it can be reverted quickly.

Testing before production

After the first test, join with a normal player account and repeat the flow from the player perspective. If the topic involves performance, measure before and after with the same player count, route, and resource set. If it involves admin tools or permissions, verify both allowed and denied users.

Common mistakes

Most FiveM issues come from missing dependencies, stale cache, wrong folder names, framework mismatch, or configuration copied from another server. Avoid changing multiple systems at once; make one change, test it, and then continue.

Related resources

For production-ready assets, compare paid resources in the FiveMX shop. For free resources, browse free FiveM scripts and test each resource before using it publicly.

Production rollout notes

Before using this guidance on a live FiveM server, define the exact outcome you expect from the change. For How to Enable Cayo Perico on Your FiveM Server, that means checking which resource, setting, command, or workflow is affected and confirming that the change fits your current framework, artifact version, and server rules. Keep the rollout small enough that you can reverse it quickly if players report errors.

Use a staging server with the same framework, database schema, resource order, and key dependencies as production. If the topic changes gameplay, permissions, visuals, voice, vehicles, maps, inventory, or economy behavior, test with at least one admin account and one normal player account. Watch server console output, client F8 logs, and resource timing while repeating the exact player flow that will happen on the live server.

Rollback checklist

• Save the previous configuration file, resource folder, and database state before changing anything.
• Record the resource version, commit, download page, or setting value you tested.
• Restart only the affected resource first when possible, then restart the full server if dependencies require it.
• If errors appear, revert the single changed resource or setting before testing another fix.

Maintenance guidance

Review this setup again after FiveM artifact updates, framework updates, or major resource changes. A configuration that works today can break after dependency updates, renamed exports, changed events, or database migrations. Keep notes with your server documentation so future admins understand what was changed, why it was changed, and how to verify it again.

Ongoing review

Recheck How to Enable Cayo Perico on Your FiveM Server after major FiveM artifact updates, framework changes, or resource migrations. Confirm that the advice still matches current server behavior, that any linked source remains available, and that installation steps still match the files a server owner will actually download or configure.

For public servers, keep a short changelog beside your server documentation. Note what was tested, what changed, which accounts were used for verification, and how to roll back. This makes future maintenance faster and prevents old setup notes from becoming unclear or unsafe for players.