Installation
Five minutes. No SQL file, no framework setting — one permission and a restart.
Before you start
Section titled “Before you start”| You need | Why |
|---|---|
| ESX, QBCore or QBox | Usable items, jobs, notifications and status come from the framework |
| oxmysql | Item configurations are saved in a table called mic_itemcreator |
| An inventory that runs framework usable items | That is how using the item reaches this resource |
| ox_lib, ox_target / qb-target, screenshot-basic | Optional; see Customization |
1. Put the folder in place
Section titled “1. Put the folder in place”Download mic_itemcreator from your Cfx.re granted assets and drop the folder into your resources, for example resources/[mic]/mic_itemcreator.
2. Start it after the things it leans on
Section titled “2. Start it after the things it leans on”In server.cfg, ensure mic_itemcreator goes below oxmysql, your framework (es_extended, qb-core or qbx_core) and your inventory.
The framework is found by looking for a started es_extended or qb-core, so the order matters: start it too early and it finds neither. QBox is found through its QBCore compatibility — qbx_core provides qb-core — so there is nothing to set.
3. The database — nothing to do
Section titled “3. The database — nothing to do”On its first start the resource creates the table mic_itemcreator (one row per configured item), and adds any column an older version did not have. There is no SQL file to import.
It worked when the table mic_itemcreator is in your database after the first start.
4. Items
Section titled “4. Items”The Item Creator does not add items to your inventory — it gives items you already have something to do. Each item you configure must exist in your inventory first.
No item definitions or images ship with it. For new items, the menu’s Registry Tool writes the definition for you: choose OX, QBCORE or ESX SQL, fill in the fields, and copy the result into ox_inventory/data/items.lua, qb-core/shared/items.lua, or your ESX items table. Pictures go in your inventory’s own image folder, named after the item.
5. Give yourself the menu
Section titled “5. Give yourself the menu”The menu is locked behind the ACE permission mic_itemcreator.open. Grant it in server.cfg with an add_ace line — to one person, for example add_ace identifier.discord:YOUR_DISCORD_ID mic_itemcreator.open allow, or to a group, for example add_ace group.admin mic_itemcreator.open allow.
The permission is checked when you join. Granted it while you were already connected? Reconnect.
It worked when /itemcreator opens the menu on the dashboard. Without the permission you get the “no permission” notification.
6. First test
Section titled “6. First test”/itemcreator→ Usable Items, and pick an item that exists in your inventory, for examplewater.- Add a Notification feature with a message, and a Food/Thirst feature with some thirst.
- Open the item’s settings, turn on Remove on Use with
1, and save. - Give yourself the item (the menu has a button for it, one at a time) and use it from your inventory.
It worked when the notification appears, your thirst goes up, and one of the item is gone.
Before you open your city
Section titled “Before you open your city”- Only the right people have
mic_itemcreator.open. It can make any item do anything, including spawn cars, run commands and grant superpowers. - Every configured item exists in your inventory, with the same name.
- Check
Config.ImageInventoryPathpoints at your inventory’s image folder, or the menu shows no pictures. - Tell your players about the cancel key — X by default — which stops animations, scenarios, walking styles, speed, superpowers and props started by an item.