Configuration

Most of what makes up a hotel — entrances, rooms, prices, doors — lives in the database and is managed in-game with /hoteladmin. config.lua is just the global toggles.

The settings you’ll actually change

Option	What it does	Default
`Config.Framework`	`'qbox'`, `'qbcore'`, `'esx'`, or `'ox'` — must match your server.	`'qbox'`
`Config.AdminGroups`	Who can open `/hoteladmin`.	`{ 'admin' }`
`Config.Interact`	`'textui'` (press E) or `'target'` (eye-target with ox_target).	`'textui'`
`Config.PaymentAccount`	`'bank'` or `'cash'` — which one to charge first. The other is used as a fallback.	`'bank'`
`Config.Rent.MinDays`	Shortest rental allowed.	`1`
`Config.Rent.MaxDays`	Longest rental in a single transaction. Players can extend repeatedly.	`30`

Minibar stock

If a room has a minibar, this is what it sells:

Config.Minibar = {
    { name = 'water',    price = 10, count = 50 },
    { name = 'sandwich', price = 25, count = 50 },
}

name must match an item in your ox_inventory items list. Each room with a minibar gets its own private shop with this stock.

Where the hotel data lives

Entrances, exits, room prices, door props, blips, peds, elevator stops — all of it is set in the database via /hoteladmin (or by running a bundled import). There is no hotel list in config.lua. See Admin panel for the in-game workflow.

Get Started

Scripts

Changelog

The settings you’ll actually change

Minibar stock

Where the hotel data lives

​The settings you’ll actually change

​Minibar stock

​Where the hotel data lives

The settings you’ll actually change

Minibar stock

Where the hotel data lives