How to install props?

  1. After completing your order, download the ZIP file from your CFX portal account.
  2. Extract the ZIP and add it to your server in the resources folder.
  3. Start the resource in server.cfg.
  4. Restart your entire server.

After restarting the server, you can use the props on your server in the same way as GTA props. All scripts on your server can use them. In configurations and code, you can use either the prop names or their hashes.

How to find the spawn name?

The spawn name is always the same as the prop name. For example: bzzz_prop.ydr = spawn name is bzzz_prop. For faster browsing of props, you can use my wiki.

If you want to use props, for example in your inventory (e.g. ox_inventory), it is not necessary to move the files (ydr, ytyp, ytd...) into your ox_inventory resource. The props can be streamed from their original folder. Once your server has loaded the models, it can use them for all your scripts.

Important: Some of our assets are also under escrow, so you cannot modify them in any way. If you don't know what you're doing, don't touch it at all. It works as it is.

How to get a hash?

To obtain a hash, you can use several tools. These can be in-game tools, CodeWalker, or you can use this Pleb Master tool.

By entering the prop name into the input field and selecting the required criteria, you can get the hash. For example, the hash for bzzz_prop is the HEX hash 0x54563C09.

For which framework can props be used?

All 3D models, whether props, vehicles, MLOs, clothing, or animations, are always standalone. You can use them on any GTA5 server, regardless of which framework you use.

However, it is important to note that, unlike MLOs - which usually have no dependencies - props need "something to use them." This means you must have a script, inventory, or prop spawner that determines what the prop does.

Please be aware that correctly setting up the scripts or code you use is your responsibility, not ours. You must follow the documentation of the scripts you use or have the necessary programming knowledge. We do not have the time capacity to create configurations or custom scripts for you.

Problem: Props are not working. What now?

  1. Check resource is added correctly
    Check that you have actually added the resource to your server, included it in server.cfg, and when starting the server, monitor the server console to see if the resource started correctly and shows no errors.
  2. Check for duplicate resources
    Check that our resource is present on your server only once. It often happens that a server has multiple developers, and each of them adds our asset to a different folder. Some of our assets may also be included in other scripts. You need to perform a files check, because if the asset exists on the server multiple times, it may cause it not to work.
  3. Anti-cheat configuration
    If your server has an anti-cheat or any other protections against cheaters, you will likely need to add the prop names to the script's configuration in order to use the props in-game.
  4. Check script settings
    Check the settings of the script you are using. You may have entered the wrong prop name, or you might have forgotten to add/remove a bracket or comma somewhere. (If you are using food props, we have prepared configurations for some scripts.) Check whether your script shows any errors in the server/client console. If it does, revert the changes and configure the props correctly. Try restarting the script in-game (/ensure script_name); it's possible that the error only appears after a server restart.
  5. OneSync Infinity
    Please note: Some scripts require OneSync Infinity to be enabled in order to function correctly.
  6. Test in different script
    Have you tried using the props in a different script? If not, give it a try.
  7. Test with ymap file
    Some of our packages (usually newer ones) include a ymap file in the data folder for testing props. If the package you have includes this file, move it to the stream folder. Restart the server and teleport to the coordinates listed in the folder. Do you see the props at these coordinates?
  8. Restore original files
    Have you made any edits to the resource? Moved any files? Delete them and install our original files. It works as it is.

Warning: The files are interconnected, and even simply renaming files or images can break the entire resource. Don't do anything if you don't know exactly what you're doing. Do not make any edits in the stream folder or in the fxmanifest.lua file. You can delete the data and images folders.

These steps should resolve your issue.

If not, contact us on our Discord - communication is faster there. If you don't use Discord, you can reach us via the email provided in your order confirmation. Please include your purchase ID (tbx-XXX) or CFX name.

Is it possible to merge props into a single resource?

Merge Props Example 1

The first thing you should know is that merging 10 resources into a single resource is not an optimization. For "hoarders," it's more like a folder where no one will ever find anything again. It makes sense to merge into a single resource if our package contains only one or two props, but please use folders in the stream and don't throw everything into one large stream folder.

Merge Props Example 2

If you do it in a "hoarder" way, it will still work, but we do not recommend it. Later, if you want to find, edit, or remove something, searching through the files can be time-consuming and exhausting.

Warning: You should also know that having a single resource that includes several props and totals several GB can cause crashes and other issues in the future.

Important: If you are merging, don't forget to load the ytyp files in the fxmanifest. You cannot merge packages that are in escrow!!!

The easiest way to start all packages without breaking anything is to create a folder in square brackets, for example [props], add the resources to this folder, and ensure [props] in server.cfg.

server-data/
└── resources/
    └── [props]/           <-- Create this folder
        ├── bzzz_food/     <-- Your prop packages
        ├── bzzz_weapons/
        └── bzzz_items/

# In server.cfg:
ensure [props]

Need More Help?

If you're still having issues, join our Discord server for support. Our community and team are always happy to help!

Join our Discord