Setup

#Dependencies

Install oxmysql, zyke_lib, and zyke_bollards_assets. Configure the framework and inventory providers in zyke_lib. See Dependencies.

#Resource & Items

Place the resource in your server's resources folder as zyke_bollards.

Items are only needed for item access and access cards. Copy the matching definitions from zyke_bollards/extras/items/ox_inventory.txt or zyke_bollards/extras/items/qb-core.txt into your configured inventory. Copy the icons from extras/items/images/256/ into the inventory's image directory. The bundled definitions include bollard_keycard and bollard_access_card.

Keep bollard_access_card non-stackable/unique so each card retains the terminal it was issued at.

For the motor sound, copy extras/sounds/bollards into zyke_sounds/nui/sounds/ and restart zyke_sounds.

#Configuration

Edit shared/unlocked/config.lua. Review the admin permission, terminal PIN rules, and traffic settings. Use the Config reference for current defaults.

Bollard groups are created in game from the Admin Menu, not in the config.

Custom access restrictions, such as duty status or gangs, belong in server/unlocked/access.lua.

#Start Order

Start your configured providers and their dependencies before Bollards:

cfg
ensure oxmysql
ensure zyke_lib
ensure zyke_bollards_assets
ensure zyke_bollards

The zyke_bollards_groups table is created on first start.

#Verify Gameplay

Open /bollards, add a group, place a row and a terminal, and save. Aim at the terminal, press E, and raise the bollards. Use /bollardtraffic to send AI cars at the row and confirm they stop.