# Pleb Masters Forge: find models for QBCore

[Pleb Masters: Forge](https://forge.plebmasters.de/) is a browser for GTA game data, including vehicle, pedestrian and object models. Use it to find the identifier you need, then check that identifier against your server's actual game assets. A catalog result alone does not prove that an asset is installed, usable or configured in QBCore.

This guide connects lookup, a small client-side diagnostic and the receiving configuration. It does not claim a sponsorship relationship with qbcore.net. The browser was reviewed on September 21, 2026; the example's FiveM acceptance checks remain manual staging work.

## Choose the right browser

| Task | Start in Forge | What to record | Continue with |
| --- | --- | --- | --- |
| Choose a car for a dealership or garage | Vehicles | Model identifier and asset entry | [Custom vehicles](/docs/guides/add-custom-vehicles) |
| Choose an NPC for an interaction | Peds | Ped model, not a character's displayed name | [qb-target](/docs/resources/qb-target) |
| Find a prop or door | Objects | Object model and matching asset entry | [qb-doorlock](/docs/resources/qb-doorlock) |
| Compare a model name and hash | JOAAT Converter | Input name and resulting hash | The receiving resource's expected value type |

Those browser categories are available on [Forge](https://forge.plebmasters.de/). Copy an identifier from the asset record rather than deriving it from a screenshot or marketing name. Record the resource you intend to edit alongside it.

## Model name, hash, item name or coordinates?

A **model name** identifies an asset, such as `adder`. A **model hash** is its numeric identifier; it is not a unique spawned vehicle, plate or owner. A **QBCore item name** is a key in shared item data. **Coordinates and heading** describe a placement in your installed map.

These values are not interchangeable. Finding a prop does not create an inventory item, image or use handler. Finding a door model does not identify one particular door: the same model can appear in several buildings.

Some APIs accept a hash, others expect a model string. Keep the representation required by the destination. The Cfx.re [Lua scripting introduction](https://docs.fivem.net/docs/scripting-manual/introduction/creating-your-first-script/) explains model checks and hash arguments; use the resource's own documented field shape for configuration.

## Check a vehicle model on your client

Before editing dealership prices or saved ownership, test whether the client recognizes the candidate as a vehicle. This original diagnostic **does not spawn entities, grant keys, modify inventory or write to the database**.

Create a staging-only resource at `resources/[local]/qbnet-modelcheck/` with these two files.

### fxmanifest.lua

```lua
fx_version 'cerulean'
game 'gta5'
client_script 'client.lua'
```

### client.lua

```lua
RegisterCommand('qbnet-modelcheck', function(_, args)
    local model = args[1]
    if type(model) ~= 'string' or #model > 80
        or not model:match('^[%w_]+$') then
        print('Usage: /qbnet-modelcheck <vehicle_model_name>')
        return
    end

    model = model:lower()
    local hash = GetHashKey(model)
    local registered = IsModelInCdimage(hash)
    local vehicle = IsModelAVehicle(hash)

    print(('[modelcheck] name=%s hash=%s registered=%s vehicle=%s'):format(
        model, tostring(hash), tostring(registered), tostring(vehicle)
    ))
end, false)
```

The native checks follow the [Cfx.re vehicle-validation example](https://docs.fivem.net/docs/scripting-manual/introduction/creating-your-first-script/). The resource structure follows the [manifest reference](https://docs.fivem.net/docs/scripting-reference/resource-manifest/). It needs no QBCore dependency because it only inspects local game data.

In the **server console**, discover and start the diagnostic:

```text
refresh
ensure qbnet-modelcheck
```

In **in-game chat**, run `/qbnet-modelcheck adder`, then open F8 to read the printed result. In F8 itself, enter `qbnet-modelcheck adder` without the slash. Repeat with the exact candidate from Forge.

| Output | Interpretation | Next check |
| --- | --- | --- |
| `registered=true vehicle=true` | Client recognizes a vehicle model | Test its gameplay integration separately |
| `registered=true vehicle=false` | Registered model is not a vehicle | Recheck the Forge category and destination |
| `registered=false` | Client does not recognize the supplied model | Spelling, selected build and streamed resource startup |
| Usage message | Argument failed the diagnostic's format check | Supply a model name, not a URL, label or hash |

These are expected interpretations, not captured runtime results. `adder` is a useful baseline from Cfx.re's tutorial. Recognition does not establish that a mod's textures, collision, handling or persistence work. Do not use the vehicle-specific result to reject a valid ped or prop.

After testing, stop `qbnet-modelcheck` and remove it from your staging startup configuration. There are no entities or database records to clean up.

## Workflow: add a vehicle to a QBCore configuration

First find and record the model in Forge. Distinguish a display label from the actual model identifier and establish whether the asset is built in, depends on the selected game build or is separately streamed. Run the diagnostic before changing QBCore's configuration.

Next follow [adding custom vehicles](/docs/guides/add-custom-vehicles) to connect the model to shared vehicle data and the intended dealership or job garage. Model lookup does not install an add-on resource or create saved ownership. Avoid adding a second entry for a model that is already configured.

Finally test spawn, entry, keys, storage, retrieval and reconnect on staging. Record the upstream resource commit and your configuration diff. When the vehicle appears but cannot be retrieved, investigate [vehicle state](/docs/troubleshooting/vehicle-state) rather than repeatedly changing the model name.

## Workflow: identify a door or target prop

Find a candidate in Objects, then inspect the actual entity in the loaded map. Record its model, coordinates and heading. An MLO replacement may change any of those values even when the room appears similar.

For [qb-doorlock](/docs/resources/qb-doorlock), distinguish a single leaf from two separately moving doors. For [qb-target](/docs/resources/qb-target), choose between an interaction on every entity of that model and a location-specific zone. A model-wide interaction is not a substitute for limiting an action to one shop counter.

Use the in-game door creation workflow to capture the installed entity instead of guessing coordinates from a catalog. Keep only one resource responsible for a given door's state.

## Troubleshooting

**The asset exists in Forge but not on my server:** inspect model spelling, category, game build and streamed resource errors. Do not change unrelated inventory fields.

**The model spawns but keys or garage storage fail:** asset recognition and ownership are separate. Check the vehicle integration and its server-side state.

**An item has no icon or use action:** a prop lookup supplies neither. Follow [usable-item creation](/docs/guides/item-use-effect) and [inventory configuration](/docs/resources/qb-inventory).

**The door prompt appears but the door does not move correctly:** inspect the actual entity, placement and second leaf, plus any competing door controller.

## Sources and next steps

Forge supplies the asset catalog and lookup categories. Cfx.re documents the resource format and model checks. The diagnostic and workflow here are independent examples; they are not tools published by Pleb Masters or the QBCore team.

Return to [QBCore tutorials](/docs/guides) for the implementation task or [resource references](/docs/resources) for its API. Keep lookup evidence, source revision and manual test outcomes together so another maintainer can reproduce your configuration.
