OZY STUDIO Documents

Documentation

OZY STUDIO Resources Document

OZY STUDIO Documentation

Welcome to the official documentation for OZY STUDIO resources.

Find installation guides, requirements, settings, door lists, replaced files and performance numbers for all of our products.

Browse Resources

Need Help?

Maps · OZY STUDIO Documents

Golden Dragon – Chinese Restaurant MLO

Resource

ozystudio-chinese

Version

2.6.3

Size

24 MB

Location

Little Seoul, Los Santos
vector3(-663.77, -1217.96, 11.81) (side entrance)

Requirements

• No scripts, no dependencies. Works with any framework (QBX, QBCore, ESX, standalone).
• OneSync is not required.
• Protected with Cfx.re Asset Escrow.
• Game build: works on the default build. Tested on build 3407.

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-chinese folder in your resources folder.
3. Add this line to your server.cfg:

   ensure ozystudio-chinese

4. Fully restart the server. restart ozystudio-chinese or refresh is not enough, because the game keeps the old interior in memory until the server restarts.

Layout

All rooms use the base-game V_Solomons timecycle, so no extra timecycle file is needed.

Doors

The restaurant has 18 door leaves. They swing open when you push them and are not locked.

Replaced base-game files

The map edits the original S.HO building to remove the old signs, doors and invisible walls. Any other resource that streams one of these files will conflict:

• kt1_15_rest_01.ydr – building shell (old signs, door leaves, window panels removed)
• kt1_15_detail_01.ydr – fence piece that went through the tea room wall
• kt1_15_0.ybn, hi@kt1_15_0.ybn – collision (solid blocks that caused invisible walls)
• hei_kt1_occl_00.ymap – occluders inside the building (stops the interior from popping in and out when you look through the windows)

Performance

• 5 rooms, 14 portals. Rooms you can't see are not rendered.
• 612 entities: 435 custom models, 177 base-game props.
• Room meshes are 41k–101k triangles each. The total for all custom models, props and the facade together is about 366k.
• One shared texture dictionary of 10.7 MB (mostly 512² and 1024², one 2048²).

Maps · OZY STUDIO Documents

Sugar Bloom – Bakery & Café MLO

Resource

ozystudio-sugarbloom

Version

1.4.3

Size

27.8 MB

Location

Vespucci Canals, Los Santos
vector3(-784.34, -1255.16, 5.70)

Requirements

• No scripts, no dependencies. Works with any framework.
• OneSync is not required.
• Protected with Cfx.re Asset Escrow.
• Game build 2545 or newer. The café uses props from The Contract update. Add this line to your server.cfg (use a higher number if you already run one):

  sv_enforceGameBuild 2545

  Tested on build 3407.

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-sugarbloom folder in your resources folder.
3. Add this line to your server.cfg:

   ensure ozystudio-sugarbloom

4. Fully restart the server. A resource restart is not enough.

Layout

The salon uses the included ozy_sugarbloom timecycle (bright and warm); the kitchen, storage and restroom use ozy_sugarbloom_back. Both are loaded from ozystudio_cafe_timecycle.xml, so you don't need to do anything.

Doors

The café has 11 door leaves. They swing open when you push them and are not locked.

Replaced base-game files

Any other resource that streams one of these files will conflict:

• vb_38_build01.ydr – building shell (old door leaves and green awnings removed)
• vb_38_build01_em.ydr – night-time window glow of the old shop
• vb_38_2.ybn, hi@vb_38_2.ybn – collision (blocks that closed the doorways)
• vb_38_strm_1.ymap, vb_38_strm_2.ymap and their hei_ versions – base-game terrace props removed to make room for the new terrace
• vb_occl_01.ymap – occluders inside the building

Performance

• 2 rooms, 5 portals.
• 231 entities: 62 custom models, 169 base-game props.
• Front salon about 99k triangles, back area about 180k. The total for all custom models, props and the facade together is about 334k.
• One shared texture dictionary of 7.8 MB (mostly 256² and 512², one 2048²).

Maps · OZY STUDIO Documents

Mariner Coffee – Pier Café MLO

Resource

ozystudio-mariner

Version

1.8.4

Size

18.1 MB

Location

Del Perro Pier, Los Santos (former Out Of Towners building)
vector3(-1655.65, -999.59, 13.02)

Requirements

• No scripts, no dependencies. Works with any framework (QBX, QBCore, ESX, standalone).
• OneSync is not required.
• Protected with Cfx.re Asset Escrow.
• Game build 2802 or newer. The café uses props from the Los Santos Drug Wars update. Add this line to your server.cfg (use a higher number if you already run one):

  sv_enforceGameBuild 2802

  Tested on build 3407.

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-mariner folder in your resources folder.
3. Add this line to your server.cfg:

   ensure ozystudio-mariner

4. Fully restart the server. restart ozystudio-mariner or refresh is not enough, because the game keeps the old interior in memory until the server restarts.

Layout

The two floors are connected by an open staircase. All rooms use the included ozy_mariner_wh timecycle, a copy of the base-game WAREHOUSE timecycle. It is loaded from ozystudio_mariner_timecycle.xml, so you don't need to do anything.

Doors

The café has 16 door leaves. They swing open when you push them and are not locked.

Replaced base-game files

The map edits the original pier building to remove the old shop, signs, doors and invisible walls. Any other resource that streams one of these files will conflict:

• sm_22_build_01.ydr – building shell (window glass, door leaves, striped awnings and "Out Of Towners" signs removed)
• sm_22_emissive_1.ydr – night-time window glow of the old shop
• sm_22_oot_alpha.ydr, sm_22_oot_alpha_n.ydr – old neon signs in the windows
• sm_22_pier_railing3.ydr, sm_22_pier_section_006.ydr – pier railing and curb pieces that ran through the building
• sm_22_2.ybn, hei_sm_22_2.ybn, hi@sm_22_0.ybn, hi@hei_sm_22_0.ybn – collision (blocks that closed the doorways and filled the building)
• sm_22_strm_2.ymap, sm_22_strm_3.ymap and their hei_ versions – work barriers and traffic cones in front of the building
• sm_occl_00.ymap, hei_sm_occl_00.ymap – occluders inside the building (stops the outside from popping in and out when you look through the windows)

Performance

• 3 rooms, 21 portals (doors, windows, the staircase and 2 restroom mirrors). Rooms you can't see are not rendered.
• 284 entities: 21 custom models (room meshes and doors), 263 base-game props. Furniture, plants, cups and kitchen items are base-game props with their own LODs, so they add nothing to the download.
• Upper floor about 85k triangles, lower floor about 190k, staff annex about 5k. The total for all custom models and the facade together is about 302k.
• One shared texture dictionary of 8.9 MB (mostly 256² and 512², largest 2048×1024).

Maps · OZY STUDIO Documents

Dark Academia – Café · Library · Bar MLO

Resource

ozystudio-darkacademia

Version

1.4.3

Size

17 MB

Location

Del Perro Pier, Los Santos (former carousel building)
vector3(-1569.20, -958.85, 12.62) (building centre)

Requirements

• No scripts, no dependencies. Works with any framework (QBX, QBCore, ESX, standalone).
• OneSync is not required.
• Protected with Cfx.re Asset Escrow.
• Game build 2545 or newer. The club uses props from The Contract update. Add this line to your server.cfg (use a higher number if you already run one):

  sv_enforceGameBuild 2545

  Tested on build 3407.

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-darkacademia folder in your resources folder.
3. Add this line to your server.cfg:

   ensure ozystudio-darkacademia

4. Fully restart the server. restart ozystudio-darkacademia or refresh is not enough, because the game keeps the old interior in memory until the server restarts.

Layout

The rooms use the included ozy_darkacademia timecycle (a warm, dim club look); the cloakroom and lavatory use ozy_darkacademia_svc. Both are loaded from ozystudio_darkacademia_timecycle.xml, so you don't need to do anything.

Doors

The club has 7 door leaves. They swing open when you push them and are not locked.

Replaced base-game files

The map removes the old carousel building on the pier without editing its map file. Any other resource that streams one of these files will conflict (Mariner Coffee is the exception, see above):

• sm_22_build0x.ydr, sm_22_build_railing.ydr, sm_22_build_railing1.ydr, sm_22_emissive_2b.ydr, sm_22_alpha_01x.ydr, sm_22_extras_08.ydr, sm_22_sm1_22_glue_03.ydr – the old building, its railings, night glow and decals
• sm_22_slod1b_children.ydd, sm_22_emissive_slod_children.ydd, sm_lod_slod2_22_children.ydd, sm_lod_slod3_children.ydd, sm_lod_emissive_22_children.ydd, sm_lod_sm_emissive_slod_children.ydd – distant versions of the old building (stops it from appearing when you look from far away)
• sm_22_2.ybn, hei_sm_22_2.ybn, hi@sm_22_0.ybn, hi@hei_sm_22_0.ybn – pier collision
• sm_22_long_0.ymap, sm_22_strm_3.ymap and their hei_ versions – base-game props that stood on the plot
• sm_occl_02.ymap, hei_sm_occl_02.ymap – occluders of the old building (stops people and props outside from popping in and out)

Performance

• 7 rooms, 24 portals (doors, windows, arches and the lavatory mirror). Rooms you can't see are not rendered.
• 280 entities: 7 room meshes, 189 custom props, 77 base-game props and 7 doors.
• Room meshes are 2k–45k triangles each (about 140k together); the facade is about 35k.
• One shared texture dictionary of 5.7 MB.

Scripts · OZY STUDIO Documents

Vampire Village – Social Deduction Game

A social deduction game for 4 to 15 players on its own floating village: 21 roles, a night in which every player walks alone, a day vote at the stake, and bots that can fill empty seats.

Resources

ozystudio-villagegame (game) · v1.1.0 · 14 MB
ozystudio-vampirevillage (map) · v1.1.1 · 17 MB
ozystudio-jelly (characters) · v2.6.2 · 68 MB

Players

4 to 15 per game, several games at the same time

Open in game

/vampirevillage or /vv, or the marker at Legion Square
vector3(195.17, -933.77, 30.69)

Languages

English, German, French, Spanish, Portuguese (Brazil), Italian, Polish, Dutch, Turkish

Requirements

• Framework: Qbox, QBCore, ESX or none (standalone). A framework is only used for the player's name and the optional money reward; the game itself runs on plain FiveM.
• Works out of the box with: illenium-appearance, fivem-appearance, qb-clothing, esx_skin + skinchanger, ox_inventory, qb-weathersync, Renewed-Weathersync. For anything else (your HUD, another clothing script, an anticheat) see Your other scripts below.

Installation

1. Download the bundle from the Cfx.re Portal → Assets → Granted Assets.
2. Put the three folders in your resources folder. Do not rename them (or change Config.MapResource / Config.PedResource if you do).
3. Add these lines to your server.cfg, in this order:

   ensure ox_lib
   ensure pma-voice
   ensure ozystudio-vampirevillage
   ensure ozystudio-jelly
   ensure ozystudio-villagegame

4. Fully restart the server. The map and the characters are streamed assets, so ensure on a running server is not enough the first time.

Playing

1. /vampirevillage (or /vv), or E at the marker in the city, opens the main menu.
2. Create Lobby → pick a colour (your colour is your house) → invite players → Start Game. The host can fill empty seats with bots: they plan, act at night, talk and vote.
3. In a game: F6 opens the village board, ESC opens the game's own menu (role guide, leave).

The game asks every player once for the microphone (the box at the top right: F8 → Allow). It is used for the night voice changer only. Set Config.Night.voiceChanger.requireMic = false to let a game start without it.

One round, with the default timers:

At night nobody shares the street: every player outside walks a street of their own, looks like a grey stranger with a changed voice, and meets others only inside houses. A game ends in a draw after 12 days (Config.MaxDays).

Roles

21 roles in three teams. The host builds the role list in the lobby, or lets the game pick one for the number of players.

Every player can read the full guide for their own role in the game's menu (ESC).

Settings

Everything is in config.lua, with a comment on every line. The ones most servers change:

Sections marked TIED TO THE MAP in config.lua are measurements of the village and the characters. Leave them as they are.

Adding a language: copy locales/en.json to locales/<code>.json, translate it and set Config.Locale = '<code>'. Anything missing from a language is shown in English.

Voice

• Night voice changer: a stranger's voice is pitch-shifted for the others in the house, with a new pitch every night. Players without the microphone permission get a radio filter instead.
• Pack and ghosts (needs pma-voice): the living vampires hear each other at night, the dead hear each other all game. Config.Night.packVoice, ghostVoice.
• Ranges: houseVoiceRange (14 m) makes a whole room hear each other at night. squareVoiceRange is 0 by default, which leaves your server's own proximity setting alone by day; set it to e.g. 40 to let everyone on the square hear everyone.

Your other scripts

A player in a game is moved to the village (far out over the sea, 800 m up), gets another character model, is made invincible and is put in a routing bucket of the game.

• State bag: LocalPlayer.state.vampirevillage is true while a player is in a game. On the server: Player(src).state.vampirevillage.
• Server exports:

  exports['ozystudio-villagegame']:IsInGame(src)
  exports['ozystudio-villagegame']:IsInLobby(src)

• Config.Hooks (client side, at the end of config.lua): your own code when a player enters or leaves a game, and to give the player their look back with a clothing script the game does not know.

  Config.Hooks = {
      onEnter = function() exports['my-hud']:hide() end,
      onLeave = function() exports['my-hud']:show() end,
      restoreAppearance = function() TriggerEvent('my-clothing:reloadSkin') return true end,
  }

• Escrow: the code is protected with Cfx.re Asset Escrow. Open files: config.lua, bridge/client.lua, bridge/server.lua and locales/*.json are not encrypted. The framework, clothing, inventory and weather calls are all in the two bridge files.

Testing alone

• Set Config.Debug = true: one player can start a game, the lobby gets an Add Bot button, and F10 (or /vvtest) opens the test panel (roles, phases, scenes).
• Keep it off on a live server. With it on, the night log shows everyone's role in the F8 console.
• Admins can open the test panel with Debug off:

  add_ace group.admin vampirevillage.debug allow

The map and the characters

• ozystudio-vampirevillage: a cartoon village floating in the sky, map only. 15 houses in a circle around the square, their doors facing it; all 15 interiors are the same and only the door colour and the number above the door differ. There is an invisible wall around the edges, so nobody falls off the island.
• ozystudio-jelly: 17 ped models, 16 colours and the grey, faceless night stranger (listed in models.txt). They are built on the human skeleton, so every human animation works on them. The mouth moves when a player talks on voice, and hats, glasses, clothes and expressions are ped components set from the game's wardrobe menu.
• You can try a character outside the game with your server's "set my ped model" command, e.g. ozystudio_jelly_mavi.

Troubleshooting

Sounds and music are CC0 recordings (ui/sounds/CREDITS.txt); the fonts are under the SIL Open Font License (ui/fonts).

Scripts · OZY STUDIO Documents

Bowling Alley – MLO + Bowling & 8-Ball Pool Script

A neon bowling alley in the Burton mall and a script that makes it playable: turn based bowling with real 10-frame scoring, team matches and live scoreboards on the lane monitors, plus 8-ball pool on every vanilla pool table, against players or the computer.

Resources

ozystudio-bowlingalley (map) · v4.4.3 · 9.8 MB
ozystudio-bowling (script) · v1.5.0 · 0.5 MB

Size

10.3 MB

Location

Burton, Los Santos (east side of the mall)
vector3(-138.42, -250.91, 43.06) (entrance)

Players

8 lanes, up to 6 players per lane · pool 1 vs 1 or against the computer

Languages

English, German, French, Spanish, Portuguese (Brazil), Polish, Dutch, Italian, Czech, Romanian, Swedish, Danish, Arabic, Turkish

Requirements

• Game build 2060 or newer for the map (the arcade cabinets): set sv_enforceGameBuild 2060 or higher.
• The pool part works on its own too, on any map that uses the vanilla pool tables.

Installation

1. Download the bundle from the Cfx.re Portal → Assets → Granted Assets.
2. Put ozystudio-bowlingalley and ozystudio-bowling in your resources folder.
3. Add these lines to your server.cfg, after ox_lib and your framework:

   ensure ozystudio-bowlingalley
   ensure ozystudio-bowling

4. Fully restart the server the first time. The interior is loaded at server start, so ensure on a running server is not enough.

The lanes of the map are already set in config.lua. Nothing else to configure.

Playing bowling

1. Walk to a lane, press E and choose Open Table: pick 5 or 10 frames, then Solo or Team Match.
2. Other players walk to the lane and choose Join Table (up to 6). In team matches players are split automatically.
3. The host chooses Start Game; the line-up is locked and turns begin.
4. On your turn take a ball from the ball return next to your lane (E), walk to the foul line and press E again.
5. ENTER locks the aim, ENTER locks the power, ENTER throws with hook. BACKSPACE cancels; you keep the ball.

Everyone sees the throw and the camera follows the ball. Scores, the next player and the standing pins are on the lane's monitor; at the end it shows the podium. Leaving before the game starts refunds your fee; if the host closes the table everyone is refunded.

Playing 8-ball pool

Works on every vanilla pool table in the game (prop_pooltable_3b and prop_pooltable_02). Walk up, press E, choose Play vs Player or Play vs Computer (easy, normal, hard).

Standard 8-ball rules: break, open table, solids and stripes, fouls give the opponent ball in hand, pot your group and then the 8. The computer plays with its own character at the table.

Placing pool tables

Put a pool table anywhere in the world from inside the game. Give the permission in your server.cfg:

add_ace group.admin ozystudio_bowling.pooltable allow

Placed tables are saved in data/pool_tables.json, survive restarts and play exactly like the tables of the map. Each player's game creates them only within Config.Pool.placement.drawDistance. If your admin group is not group.admin (for example superadmin), use that group's name in the line above.

Settings

Everything is in ozystudio-bowling/config.lua, commented. The ones most servers change:

• Escrow: the code is protected with Cfx.re Asset Escrow. Open files: config.lua, bridge/client.lua, bridge/server.lua, locales/*.json and data/lanes.json are not encrypted. Money, player names and character switching are only in the two bridge files.
• Adding a language: copy locales/en.json to locales/<code>.json, translate it and set Config.Locale = '<code>'. Anything missing is shown in English.

The map

The interior uses the base-game AP1_01_B_IntRefRange timecycle, so no extra timecycle file is needed. The two entrance door leaves (ozystudio_bowling_door) swing open when you push them and are not locked.

Replaced base-game files

The map opens the mall's facade for the entrance. Any other resource that streams one of these files will conflict:

• bt1_04_shop3.ydr, bt1_04_mall02.ydr – facade pieces cut where the entrance is
• bt1_04_0.ybn – collision (the solid blocks in front of the entrance)
• apa_ss1_occl_00.ymap – occluders around the building (stops the interior from popping in and out)

Performance

• 1 room. 312 entities inside: the hall, our own models (doors, balls, sign, pool lamps) and base-game props.
• The hall model is about 146k triangles in 46 parts. Total stream size 9.8 MB.

Other maps

The script works without our map. Set Config.Screen.mode = 'floating' (each scoreboard floats above its lane) and save the lanes in game:

/bowlingpoint <lane> stand   -- middle of the foul line
/bowlingpoint <lane> pin     -- where the head pin stands
/bowlingpoint clear <lane|all>

They are written to data/lanes.json; then restart ozystudio-bowling. The command needs add_ace group.admin command.bowlingpoint allow.

Troubleshooting

The game state lives on the server (turns, pins, scores, pool physics and rules), so results cannot be faked from a client.

Scripts · OZY STUDIO Documents

Photo Booth – Walk-In Photo Booth Script

A walk-in photo booth: up to three players squeeze inside, pick a pose for every shot, put on accessories and get a printed photo strip with the real in-game photos. The strip slides out of the machine and ends up in everyone's inventory.

Resources

ozystudio-photobooth · v1.1.1

Size

3.0 MB (2.1 MB streamed: booth, curtain, strips, 9 accessories)

Players

Up to 3 per photo · as many booths as you like

Frameworks

ESX, QBCore, Qbox or standalone (detected automatically)

Languages

English, German, French, Spanish, Portuguese (Brazil), Polish, Italian, Dutch, Russian, Turkish

Requirements

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-photobooth folder in your resources folder. Don't rename the folder: the ox_inventory item calls the export ozystudio-photobooth.useStrip.
3. Add these lines to your server.cfg, after screenshot-basic, your framework and your inventory:

   ensure screenshot-basic
   ensure ozystudio-photobooth

4. Add the item. The definitions are in install/:
   • ox_inventory: install/ox_inventory_item_en.lua → ox_inventory/data/items.lua
   • qb-inventory / ps / lj: install/qb_items_en.lua → qb-core/shared/items.lua
   • qs-inventory: install/qs_inventory_item_en.lua → qs-inventory/shared/items.lua
   • Copy install/ozystudio_photostrip.png into your inventory's image folder.
5. Restart the server and reconnect.

The ox_inventory item looks like this:

['ozystudio_photostrip'] = {
    label = 'Photo Strip',
    weight = 10,
    stack = false,
    close = true,
    description = 'A photo strip from the photo booth.',
    client = { export = 'ozystudio-photobooth.useStrip' },
},

Placing booths

The two booths in config.lua (Legion Square and Del Perro Pier) are examples. To place your own, stand in game where the centre of the booth should be, face the direction the door should face and type pbpos in the F8 console. Paste the printed line into Config.Booths:

Config.Booths = {
    { coords = vector4(188.27, -936.02, 30.69, 145.0) },   -- Legion Square
}

Add as many booths as you like. A booth needs about 2.2 m width × 1.8 m depth × 3.1 m height. Booths are local props, spawned when a player gets close (Config.SpawnDistance), so they add no network load.

Taking photos

1. In front of the booth press E: the velvet curtain opens (everyone sees it) and closes by itself a few seconds after you step in. It never closes on someone standing in the doorway.
2. Inside, press E for the menu. Pick Sitting or Standing and a filter.
3. Pick a pose for each of the 4 shots. Female and male characters have their own poses; the others inside pick theirs at the same time (20 seconds, random if they don't).
4. Optionally pick up to 3 accessories, one per spot (hat, eyes, face, hair clip).
5. The curtain closes, a 3-2-1 countdown and a flash for every shot. Automatic framing fits everyone in the picture.
6. The strip prints out of the slot on the front of the booth and everyone in the photo receives a Photo Strip item.

Using the item opens the photo; the character holds the strip and nearby players see the photo in their hand. Show to nearby player sends it to the closest player.

Settings

Everything is in config.lua, commented. The ones most servers change:

• Escrow: the code is protected with Cfx.re Asset Escrow. Open files: config.lua, bridge/client.lua, bridge/server.lua and locales/*.lua are not encrypted. Money, player names and the photo strip item are only in bridge/server.lua; to support another inventory change Bridge.AddItem, Bridge.HasPhoto and the usable item at the bottom of that file.
• Adding a language: copy locales/en.lua, rename it (for example cs.lua), change Config.Locales.en to Config.Locales.cs, translate it and set Config.Locale = 'cs'. Anything missing is shown in English.

Photos

Strips are saved in photos/ inside the resource, one file per strip (about 300-500 KB). No paid image host is needed. Keep this folder when updating: old photo items can't be opened without it. A player can only open photos that are in their own inventory.

Updating

1. Back up the photos folder.
2. Delete the old folder and put the new one in its place (no old files left in stream).
3. Restart the server and reconnect. restart ozystudio-photobooth alone keeps the old models in the game's memory.

Troubleshooting

Scripts · OZY STUDIO Documents

Vending Machines – Drink & Food Vending Script

Glass-front drink and food vending machines with no menu: walk up, press E and type the code on the machine's own keypad. The item is pushed off the shelf, falls behind the glass, and your character takes it from the tray. Drinking and eating restore thirst and hunger.

Resources

ozystudio-vending · v1.0.0

Size

2.0 MB (1.6 MB streamed: 2 machines, tray flap, screen digits, snack packs)

Machines

Cold Drinks + Snacks & Food · as many as you like, placed in game

Frameworks

Qbox, QBCore, ESX, ox_core or standalone (detected automatically)

Languages

English, Turkish, German, French, Spanish, Portuguese (Brazil), Italian, Dutch, Polish, Russian, Czech, Danish, Swedish, Romanian, Arabic

Requirements

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-vending folder in your resources folder. Don't rename the folder: the ox_inventory items call the export ozystudio-vending.useDrink.
3. Add this line to your server.cfg, after your framework and inventory:

   ensure ox_inventory
   ensure ozystudio-vending

4. Add the items (names must match item in config.lua). The definitions are in install/:
   • ox_inventory (ESX, Qbox, ox_core): install/ox_inventory_items.lua → ox_inventory/data/items.lua, images install/images → ox_inventory/web/images
   • qb-inventory / ps / lj: install/qb_items.lua → qb-core/shared/items.lua, images → qb-inventory/html/images
   • qs-inventory: install/qs_inventory_items.lua → qs-inventory/shared/items.lua, images → qs-inventory/html/images
   • ESX inventory: run install/esx_items.sql
   A missing item is reported in the server console at start.
5. Give admins the placement permission:

   add_ace group.admin ozystudio-vending.admin allow

   Framework groups in Config.Admin.groups (admin, god, superadmin) are allowed too.
6. Restart the server and reconnect.

One of the ox_inventory items looks like this:

['ecola'] = {
    label = 'eCola',
    weight = 330,
    stack = true,
    close = true,
    description = 'Ice cold eCola. Deliciously Infectious!',
    client = { image = 'ecola.png', export = 'ozystudio-vending.useDrink' },
},

Placing machines

Type /vending in game. A ghost machine follows where you aim:

/vending remove deletes the placed machine you stand next to. Placed machines are saved in data/machines.json and appear for everyone immediately. Machines can also be written in Config.Machines; /vendingpos prints a config line for the spot in front of you. A machine can sell only some products (products = { 'cola', 'water' }); the other codes show SOLD OUT.

Using a machine

1. In front of the machine press E. The camera moves to the keypad.
2. Type the code shown under the product (10-29) with the mouse or the keyboard and press OK, or tap the card reader.
3. The server checks the price, your money, the distance and your inventory space. The item is pushed off the shelf, falls behind the glass, and your character bends down, opens the tray flap and takes it.
4. Use the item from your inventory to drink or eat it. X stops, and the item is not used up.

Products

Prices and values are in Config.Products. Only the server's price is used; the client never sends a price.

Settings

Everything is in config.lua, commented. The ones most servers change:

• Escrow: the code is protected with Cfx.re Asset Escrow. Open files: config.lua, bridge/*.lua, locales/*.lua and install/*.lua are not encrypted. Money, items and thirst / hunger are only in bridge/server.lua.
• Languages and the GTA font: texts drawn with the game's own font (the E prompt, the placement help, the machine's screen) avoid letters the font does not have. In Arabic they stay in English; on the Russian machine screen they stay in English.

Performance

• Machines, flaps and shelf products are local objects, created only near the player and deleted when you leave. Loading runs in its own thread, so the E prompt never stalls.
• The main loop runs once a second when far away, every 300 ms near a machine, and every frame only within E distance or on the keypad.
• Drink machine: 15.6k triangles, 571 KB. Food machine: 13.4k triangles, 669 KB.

Updating

1. Back up data/machines.json (your placed machines).
2. Delete the old folder and put the new one in its place, then copy data/machines.json back.
3. Restart the server and reconnect. If the old look remains, clear the FiveM cache (FiveM Application Data\data\cache\priv).

Troubleshooting

Scripts · OZY STUDIO Documents

Taco Truck – Walk-In Food Truck Job Script

A walk-in taco truck job. Buy or rent your own truck at the dealer, stock it up, park it on any corner and open the shop. You walk into the truck, cook every taco yourself on the griddle and hand it out of the window to NPC customers and to players who order on the truck's tablet. The money goes into your truck's till.

Resources

ozystudio-tacotruck · v1.0.1

Size

4.5 MB (4.1 MB streamed: the walk-in truck, kitchen screens and 13 food props)

Frameworks

Qbox, QBCore, ESX, ox_core or standalone (detected automatically)

Interaction

ox_target, qb-target or the E key (detected automatically)

Languages

English, Turkish, German, French, Spanish, Portuguese (Brazil), Italian, Dutch, Polish, Russian, Czech, Danish, Swedish, Romanian, Arabic, Japanese

Requirements

No inventory items are needed: the stock lives in the truck.

Installation

1. Download the resource from the Cfx.re Portal → Assets → Granted Assets.
2. Put the ozystudio-tacotruck folder in your resources folder and keep the folder name.
3. Add it to your server.cfg, after ox_lib and your framework:

   ensure ox_lib
   ensure qbx_core
   ensure ozystudio-tacotruck

4. Admin commands (optional):

   add_ace group.admin command.tacotruck allow

   Framework groups in Config.Admin.groups (admin, god) are allowed too.
5. Restart the server and reconnect.

How it works

1. Dealer (blip "Taco Truck Dealer"): buy a truck, or rent one for Config.Truck.rent.minutes. Take it out: it waits on the street next to the dealer, with keys and a full tank.
2. Supplies: at the dealer, pick how many packs of tortillas, meat, onion & cilantro, salsa, limes and baskets you want. You get a box in your hands; carry it to your truck and press E next to it to load it. A dropped box waits at the dealer.
3. Open the shop: park, get out and open the shop at the back of the truck. The rear doors open, the steps fold down and the serving hatch opens; the truck is frozen while it is open. Another open truck may not stand closer than Config.Truck.openMinDistance.
4. Cook: step to the griddle and choose Cook. The order ticket on the left lists every step.
5. Serve: carry the basket to the window (G), then E to hand it out. The result card shows the score (0-100), the price and the tip.
6. Player orders: players order 1-3 tacos on the tablet outside the window. The server holds the money and pays it when you serve; not served within Config.Menu.playerOrderMinutes, or the shop closes, the player is refunded.
7. Till & menu (inside, by the window): set the truck name, the taco price and the screen colour, and take the money.
8. Close the shop from inside: you are put outside behind the truck and the customers leave.

The truck goes back to the dealer (stock and till are kept) when its owner logs out or stays farther than Config.Truck.returnWhenAway.distance from it for minutes. A rented truck goes back when the rent runs out.

Cooking controls

Raw meat cooks on the griddle in Config.Cook.meatSeconds if you stir it; without stirring for longer than stirEvery seconds the bottom starts to burn. A tortilla needs tortillaSeconds on each side. One tray of meat gives scoopsPerTray scoops.

Admin commands

Settings

Everything is in config.lua, commented. The ones most servers change:

• Escrow: the code is protected with Cfx.re Asset Escrow. Open files: config.lua, bridge/*.lua and locales/*.json are not encrypted. Money, hunger, keys and fuel are only in bridge.
• Saved data: truck records (owner, stock, till, menu) are in data/trucks.json.
• Languages and the GTA font: the dealer's map blip is drawn with the game's own font, which has no Arabic or Japanese letters; in those two it stays in English.

Performance

• One shared loop runs everything that needs every frame, and only while you are near a truck or cooking. Far from every truck and the dealer the script only checks once a second.
• The kitchen props and screens exist only within Config.Truck.propsDistance of a truck. Only the screens on your side of the truck are drawn: the kitchen display and the till inside, the menu board and the tablet outside.
• NPC customers are shown only within Config.Customers.showDistance.

Updating

1. Back up data/trucks.json (players' trucks).
2. Delete the old folder and put the new one in its place, then copy data/trucks.json back.
3. Restart the server and reconnect. If the old look remains, clear the FiveM cache (FiveM Application Data\data\cache\priv).

Troubleshooting