Prop Manager

Features

• One command, one menu (/propmanager): every edit in one list with search, filters (all / removed / moved / placed) and sorting (nearest / newest). Shows who made each edit, when, and how far away it is.
• Place new props: pick from quick picks or type any prop model name, position it with the move keys and save. Placed props are saved and shown to every player like any other edit.
• Teleport to an edit's original spot or to its new position, straight from the manager.
• Name your edits ("Bench blocking the PD door") so staff know why a prop was changed.
• Edit position of a moved prop from the manager: it teleports you there and opens move mode.
• Restore one edit (or delete a placed prop), or select several and undo them all at once.
• Copy model, positions and ids with one click.
• Aim editor (started from the menu): the prop you aim at is outlined with its type, model and distance. Press E for a panel with every option: remove, move, copy details, open in the manager.
• Move mode panel with live position and rotation, plus Tab to type exact values. Snap to ground, reset tilt, fast / slow movement, all 3 rotation axes.
• Edited-prop markers: removed and moved props leave a marker at their original spot. Aim at it and press H to restore it, teleport or open it in the manager.
• Works on MLO props: interiors keep re-creating their props, so edits are re-applied automatically.
• Safe: props spawned by other scripts are locked, so you can't break another resource's objects.
• Edits apply for everyone and survive restarts. They only stream in near players, so far-away edits cost nothing.
• Works on any server: ESX, QBCore, Qbox or standalone. Only ox_lib is required. No SQL.
• Permissions by ace or framework admin group.
• Discord logs for removes, moves, placed props and restores.
• Fully configurable UI colors, fonts, keys and fully translatable.

Requirements

Files

orynt_propmanager/
├── config.lua            Settings, keys, UI colors (editable)
├── fxmanifest.lua
├── README.md             This file
├── LICENSE.md            Terms of use
├── locales/
│   └── en.lua            All text (editable, copy to translate)
├── shared/
│   └── text.lua          Loads the language
├── client/
│   └── main.lua          Editor, move mode, applying edits
├── server/
│   ├── sv_config.lua     Discord and console logs (editable, server only)
│   ├── logs.lua          Discord webhook sender
│   └── main.lua          Saving edits, permissions
└── html/                 Prop Manager and editor panels (UI)

Files marked editable stay readable when the resource is escrowed.

Installation

1. Put the orynt_propmanager folder in your resources folder.

   Don't rename the folder. Saved edits are stored under the resource name. A renamed folder starts empty.

2. In server.cfg, after ox_lib: cfg ensure ox_lib ensure orynt_bridge ensure orynt_propmanager
3. Permissions: admins in your framework's admin, superadmin or god group can already use it. To give access by ace instead (or as well, and on standalone servers): cfg add_ace group.admin orynt_propmanager.admin allow
4. Restart the server, or type refresh and then ensure orynt_propmanager. You should see: [Orynt Prop Manager] Loaded 0 prop edit(s)

Coming from CarrotPropRemover or an older version? Copy your old data/props.json into orynt_propmanager/data/props.json before the first start. The edits are imported once, then you can delete the file.

Prop Manager (/propmanager)

/propmanager is the only command. Everything else is done from this menu.

• Counts of removed, moved and placed props.
• Search by name, model, edit id or staff name. Sort: Nearest / Newest.
• Filter: All / Removed / Moved / Placed.
• Tick the boxes to select several edits, then Restore them all at once (with a confirmation). Placed props in the selection are deleted.

Top buttons - Place prop opens the place view (see Placing props). - Start editor closes the window and turns on the aim editor (press Backspace there to come back).

Pick an edit to see: - Name: type a name (max 40 characters) and press Save name. Everyone with access sees it. - Details: model, distance, original position, new position and rotation (moved props), MLO room, edit id. The copy buttons copy a value to your clipboard. - Actions: - Teleport to original spot / Teleport to new position (placed props: Teleport to prop) - Edit position (moved and placed props): teleports you there and opens move mode, then brings you back here - Remove instead (moved props): turns the move into a remove - Restore original: the map prop comes back for every player (with a confirmation) - Delete prop (placed props): removes it for every player (with a confirmation)

Press Esc or the close button to close the window. The list updates live when other staff make changes.

Placing props

1. In the Prop Manager, click Place prop.
2. Click one of the quick picks, or type any prop model name (e.g. prop_bench_01a) or hash and press Place. Typing also filters the quick picks.
3. The prop appears on the ground in front of you, in move mode. Position it (see Move mode) and press Enter to save, or Backspace to cancel.
4. You're taken back to the Prop Manager with the new prop selected, so you can name it.

Placed props show amber in the list. Change the quick picks in Config.PlaceProps. A model that doesn't exist (or a vehicle) shows "That prop model doesn't exist". Placed props are local objects that every player spawns for themselves, so they cost no network entities.

Aim editor

In the Prop Manager, press Start editor. Press Backspace to go back to the Prop Manager. A crosshair appears, and a bar at the top shows the prop you aim at with its type, model and distance.

The prop panel (E) shows the model and position (with copy buttons) and the options: - Map prop: Remove or Move. - Moved prop (one you moved earlier): Remove, Move again, Open in manager, Restore original. - Placed prop: Move again, Open in manager, Delete prop. - Script prop (locked): spawned by another resource. Change it in that resource instead.

Edited-prop markers: removed props can't be aimed at, so every edit within Config.RestoreDistance shows a marker at its original spot (red = removed, blue = moved). Aim at it and press H to teleport to its original spot, open it in the manager or restore it.

Move mode

Opens from the prop panel (Move), the manager (Edit position) or when placing a prop. A panel shows the live position and rotation.

Exact values: press Tab and the mouse is freed. Click X / Y / Z / Pitch / Roll / Yaw, type a number and the prop jumps there. The Snap to ground, Reset tilt, Save and Cancel buttons work too.

Configuration (config.lua)

1. Commands and permissions

2. Editor

3. Applying edits

4. Keys

Config.Keys: every editor and move-mode key (control ids). Config.KeyLabels: how each key is shown in the UI. If you change a key, change its label too.

5. Language, notifications and UI

Server configuration (server/sv_config.lua)

Never sent to players, so webhook links stay private.

Discord logs

1. In Discord: Server Settings → Integrations → Webhooks → New Webhook, pick the channel, Copy Webhook URL.
2. In server/sv_config.lua, paste it into SvConfig.Logs.webhook and set enabled = true.
3. Optional: a webhook per channel in webhooks (remove, move, place, restore).
4. ensure orynt_propmanager.

Each log shows who did it, the prop model, the edit id and the positions. Keep webhook links private.

Translating

All text, including the whole UI, is in locales/en.lua. Copy it to e.g. locales/de.lua, change Locales['en'] to Locales['de'], translate it (keep the words in {braces}), set Config.Locale = 'de', then refresh and ensure orynt_propmanager. Anything left out falls back to English.

Saved data

Edits are saved in the server's resource storage (KVP), not in a database: one entry per edit. They survive restarts and updates.

• Saved data belongs to the resource name orynt_propmanager: don't rename the folder.
• To undo everything, open the Prop Manager, select the edits and restore them.

Other resources can read the edits with exports.orynt_propmanager:GetEdits().

Updating

Replace the resource folder with the new version and start it (refresh, then ensure orynt_propmanager, or restart the server). Nothing to copy over:

• Your settings come back by themselves. Every start, config.lua, server/sv_config.lua and your own translation are copied to the server (its KVP, outside the resource folder). When the new version starts with the files from the download, yours are put back and the resource restarts once to load them.
• New options your config doesn't have yet use their defaults, and the console lists them once (the changelog below says what they do).
• Your prop edits are saved on the server, not in the resource folder: they stay.
• Keep the resource's name (orynt_propmanager): the saved settings belong to it.

To let it restart itself after putting your settings back, add this to server.cfg (without it, the console asks you to type ensure orynt_propmanager once):

add_ace resource.orynt_propmanager command.ensure allow

To go back to the default settings on purpose: type orynt_propmanager:resetsettings in the server console, put the files from the download back and restart the resource.

Updating from a version before 1.1.0: those don't save your settings yet, so this one time keep a copy of your config.lua, server/sv_config.lua and language files, and put them back after replacing the folder. From 1.1.0 on, updates keep them by themselves.

Changelog

• 1.2.0: now runs on orynt_bridge, the free Orynt resource that handles your framework (admin groups) for every Orynt script. Install it once (see Installation); your settings and data stay.
• 1.1.0: the new Orynt look: purple theme, Orbitron titles, the new Orynt logo and wordmark, purple checkboxes and dropdowns, purple outline, crosshair and restore markers in the editor, purple Discord logs. Updates keep your settings now: replace the folder and your config comes back by itself (see Updating).

Troubleshooting

Escrow and license

When escrowed, config.lua, server/sv_config.lua and locales/ stay readable so you can configure and translate it. See LICENSE.md for the terms of use. In short: use it on your own servers; don't resell, share or leak it; keep the Orynt Development branding.

© Orynt Development