How to Enable Cayo Perico in FiveM

To make Cayo Perico content available on a FiveM server, set the enforced game build at startup to build 2189 or any later supported build. Build 2189 is the Cayo Perico Heist build and can also be selected with the alias h4. Every later game build includes content from previous builds.

Confirm the target GTA edition before installing or exporting assets. Legacy packages are not automatically Enhanced-ready; follow the official Enhanced asset-conversion guidance when that is your target.

The configuration and code examples here target FiveM for GTA V Legacy. Enhanced has different runtime and compatibility rules; check Cfx.re’s Legacy-to-Enhanced changes before applying them to an Enhanced server.

Enable the Cayo Perico game build

1. Stop the server.
2. Open the configuration file that is executed at startup.
3. Add one of these lines:

   sv_enforceGameBuild 2189

   or

   sv_enforceGameBuild h4

4. Start the server again and confirm the selected build in the server console.

sv_enforceGameBuild can only be set at server startup. Entering it after the server has started will not switch the active game build.

Should you use build 2189 or a newer build?

Use 2189 when you need the oldest build that contains Cayo Perico. Use a later supported build when other resources require newer GTA Online content. Test your complete resource stack after changing builds because vehicles, maps and scripts may depend on a particular build.

Game build versus island loading

The game build makes Cayo Perico assets available. It does not guarantee that every server resource will load the island, route players there or configure collisions correctly. Some server stacks use a dedicated island/IPL resource or custom travel script. Follow the documentation for the exact maintained resource you install; do not download an old ZIP simply because a tutorial names it.

Verify Cayo Perico

• Restart the server fully rather than only restarting one resource.
• Join with a clean client session and travel to the island using your server's supported route.
• Check terrain, collisions, vegetation, doors and interiors.
• Review the server and F8 consoles for missing resources or map errors.
• Test with the same OneSync and routing-bucket behavior used in production.

Troubleshooting

The island is invisible or incomplete

Confirm the startup build first. Then verify that the island/IPL resource starts successfully and does not conflict with another map resource.

Players fall through the map

Check collisions and resource start order. Temporarily disable conflicting Cayo Perico map resources and retest one implementation at a time.

The server will not start after the change

Restore the previous build line, check the console error, and confirm that the build number or alias is listed in the current Cfx documentation.

Production checklist

1. Back up server.cfg and the affected resource configuration.
2. Test the chosen build and island resource on a staging copy.
3. Verify jobs, vehicles, inventories and maps—not only the island.
4. Deploy during a maintenance window with a documented rollback.

Official reference

The current build list and startup-only behavior are documented in the official Cfx server commands reference. For additional server resources, browse FiveM resources or the RPScripts shop.