Propshot Tools

What it is

PropShot queues models from your catalog, teleports into a bundled greenscreen room, frames each prop, and saves raw screenshots. You then run a small Python script to cut the green and export transparent WebP files for catalog thumbnails.

Map Live Editor shows a Screenshots button in the top bar when cdev_propshot is started. That button closes the editor and calls exports['cdev_propshot']:Start().

How it works

1. Open from Map Live Editor or with /propshot

---

2. Permission and screenshot resource check

The server runs propshot:canStart: ACE cdev_propshot.use (or configured fallback), screenshot-basic / screencapture must be started, and a catalog source must resolve.

---

3. Queue builds, then capture in the greenscreen studio

PropShot scans which models still need shots (skips existing raw files when configured), shows progress (percent, ETA, current model, captured / skipped / failed), and can be cancelled (ESC or Cancel — finishes the current shot cleanly).

---

Do not move Capture.location unless you also move the bundled greenscreen map assets.

4. Raw files land under screenshots/raw

Default folders (PropShotConfig.Capture):

Folder	Purpose
screenshots/raw/	Camera output (jpg / png)
screenshots/props/	Transparent WebP after processing
screenshots/skipped_*.json	Skip reports

---

5. Run process_propshots.py for catalog WebPs

On a machine with Python + Pillow (NumPy recommended):

cd cdev_propshot
python tools/process_propshots.py

Useful flags: --watch, --quality, --size, --force, --raw, --out.

---

6. Bright/Glowing Items

Issue: Bright/Glowing Items

If items appear too bright in the image, please set your in-game time to 12:00 AM.

Video how to fix:

---

Installation

1

Dependencies

Required for capture

Resource	Purpose
screencapture or screenshot-basic	Takes the actual screenshot. One of them must be started.

Optional

Resource	Purpose
cdev_mapeditor	Preferred catalog source (props.json + CustomProps)
Framework / ox_lib	Admin and notify bridges

The greenscreen map is bundled inside cdev_propshot (stream/ + this_is_a_map). You do not install a separate greenscreen resource.

2

Install and ACE

Extract into resources/[cdev]/cdev_propshot (or your preferred folder).

add_ace group.admin cdev_propshot.use allow

ensure screenshot-basic
ensure cdev_propshot
# if you use the map editor catalog:
ensure cdev_mapeditor

Open with /propshot, or use Screenshots inside Map Live Editor.

How the catalog is chosen

1. If cdev_mapeditor is started: load cdev_mapeditor/public/data/props.json and merge exports['cdev_mapeditor']:GetCustomProps().

2. Otherwise: use cdev_propshot/public/data/props.json and PropShotConfig.CustomProps.

Paths are configurable under PropShotConfig.Catalog.

Configuration

File: public/shared/config.lua (PropShotConfig).

Section	Purpose
Debug	Extra console logs
Locale	en / pt / es
Bridge	Framework auto or forced
Permissions	ACE cdev_propshot.use, fallback, framework admin
Command	Default propshot
Capture	Studio location, camera, FOV, encoding (jpg/png), quality, output folders, size filters, cooldowns
Catalog	Map editor resource name and props.json paths
CustomProps	Extra models when using the local catalog

Commands and exports

Command	Permission	Description
/propshot	cdev_propshot.use	Start the capture UI / run

Client exports

exports['cdev_propshot']:Start()
exports['cdev_propshot']:Cancel()
local busy = exports['cdev_propshot']:IsActive()

Server exports

local ok = exports['cdev_propshot']:CanUse(source)

FAQs (PropShot)

Screenshots button missing in Map Live Editor

• Start cdev_propshot and reopen the editor (availability updates live when the resource starts/stops).

• Confirm ACE cdev_propshot.use if you also open via command.

Error about screenshot resource

Start screenshot-basic or screencapture before cdev_propshot. Restart after adding them.

Empty queue / wrong catalog

With Map Editor installed, ensure cdev_mapeditor is started so PropShot can read its props.json. Check PropShotConfig.Catalog paths.

Solid green or empty photos

Keep maxObjectDistance and studio location as shipped. Large props may need FOV / framing tweaks in Capture. Filter giants with maxModelSize.

Processed WebP missing

Run tools/process_propshots.py against the raw folder. Confirm Python packages and the --out path.