Requirements#
Optional:
- ox_inventory, for the
markeritem - qbx_core, only if you want the item registered through
CreateUseableItem - glitch-uiElements, for the live drawer editor. Without it the script falls back to an ox_lib dialog (no live preview).
Installation steps#
- Put the
glitch-scenesfolder in your resources and addensure glitch-scenesto server.cfg after ox_lib and oxmysql. - The
glitch_scenestable is created on first start.glitch_scenes.sqlholds the same statement if you would rather import it by hand. - Set the options in
config.lua. Fill inConfig.BlockedWordsbefore you open the server, it is empty by default and there is no other text filter. Example:Config.BlockedWords = { 'badword1', 'badword2' }.
Then run /scene (or use the item, radial menu or keybind if you turned them on). Aim the laser and press E to place a scene, G to delete the one under the laser, Backspace to cancel.
Marker item (ox_inventory)#
Add this to ox_inventory/data/items.lua:
['marker'] = {
label = 'Marker',
weight = 50,
stack = true,
close = true,
consume = 0,
description = 'Leave a message on a wall.',
server = { export = 'glitch-scenes.useMarker' },
},
consume = 0 matters. The script removes the item itself when the break chance rolls, so letting ox_inventory consume it as well would take it twice.
Set Config.Item = false to turn the item off. If you use qbx_core's CreateUseableItem instead, leave out the server line and the script registers the item itself.
Permissions#
Admin features (Config.AdminOnly, deleting other people's scenes, the never-expire option) check the ACE named in Config.AceGroup. The default is admin:
add_ace group.admin admin allow
Stuck on a step?Ask in the Discord →