Skip to main content

Installation

RoadPark ships as 16 resources: the park map, the ticket booth, the entrance sign, six rides, the games and the food stands. Install them together — the map places every attraction into its slot as soon as that resource starts.
Do not use FileZilla. It can corrupt or skip hidden files during upload. We recommend WinSCP.
There is no SQL file and no transaction ID to enter. RoadPark keeps its data in JSON files and server KVP. The download comes from the cfx.re Portal.

📋 Prerequisites

OneSync

Required by every RoadPark resource.

Framework

Optional: ESX, QBCore or Qbox for payments and item prizes.

Inventory

Needed for Park Chips and prizes when you use a framework.

Target script

Optional: ox_target for the games row. Without it players press E.

🚀 Setup Instructions

1

Extract the resources

Put all 16 folders into one category folder. Keep the folder names exactly as they are — the map, the ticket booth and the rides find each other by resource name.
2

Start the resources

Start your framework and your inventory first, then RoadPark:
server.cfg
The order inside this block does not decide placement: a ride that starts after the map still receives its slot, and every ride registers its price with the ticket booth again when roadpark_tickets (re)starts.
3

Give your staff permissions

server.cfg
roadpark.editor unlocks the placement editors of the booths, games and most rides. roadpark.admin unlocks the Highlander editor. Players need no permission to ride, play or buy. Details: Permissions.
4

Register the inventory items

Park Chips and the prizes are real items. Add them to your inventory — see Inventory items below.
5

Join and check

Connect, follow the RoadPark blip to the entrance at Mirror Park and buy a chip at the ticket booth. The price board on the booth lists every ride that is running.Each resource with a bridge prints the framework and inventory it found in the server console, for example [Bridge] ESX + ox_inventory.

🎒 Inventory items

Pizza, gelato and drinks are held in the hand or consumed right away — they need no items.
data/items.lua
Qbox uses ox_inventory, so these definitions cover Qbox as well. The gingerbread heart needs no consume, usetime or export — using the item puts the heart on or takes it off.
The Lucky Ducks prize pictures ship in roadpark_ducks/web/img/ and can be copied into your inventory’s image folder.
You do not want an item prize at the Shooting Gallery? Set R.Prize.item = '' in roadpark_games/config/range.lua and the teddy item is no longer needed.

⚠️ Map compatibility

The roadpark resource replaces the original game files of the Mirror Park construction site and a few neighbouring LOD, road and collision files while it runs. Your GTA V installation is never modified.
Do not run another map that streams files with the same names — for example a different build on the Mirror Park construction site. Two maps replacing the same files overwrite each other, and you get holes or floating objects.
While the park runs, the roads inside the park area are closed for ambient traffic and the parked-car spawns there are removed. Both come back when you stop roadpark.

🔄 Updating

1

Keep your server-owned files

Copy the new files over the old ones, but keep:
  • every config.lua you changed (and roadpark_games/config/*.lua)
  • placement.json, managed_placement.json and their backups in the ride and booth folders
  • roadpark_games/scores.json (the leaderboards)
2

Restart

refresh, then restart the resources you updated. Copying files alone does not restart anything.
3

Reconnect

After an update with new streamed files (models, map, collision), reconnect your client so the new files load instead of the cached ones.

🗑️ Removing the park

Remove the ensure lines of roadpark and of every attraction you do not use elsewhere, restart the server and reconnect. The original construction site, its roads and its parked cars come back. Attractions can also live on without the park — see Placing attractions outside the park.