Installation
Ten minutes. The one step people skip is fmLib — the resource will not start without it.
Before you start
Section titled “Before you start”| You need | Why |
|---|---|
| ESX, QBCore or QBox | Callbacks, notifications and player data come from the framework |
| fmLib | Required. Money, items, jobs and vehicle keys go through it. The resource’s own guide points to fmLib v2.0.2 |
| oxmysql | Every quest, event and player’s progress is stored in your database |
| ox_target or qb-target | Optional. ox_target is the default; switch to 3D text if you run neither |
| screenshot-basic | Optional, only for screenshots on the webhook node |
1. Put the folder in place
Section titled “1. Put the folder in place”Download mic_questcreator from your Cfx.re granted assets and drop the folder into your resources, for example resources/[mic]/mic_questcreator. Put fmLib in your resources too if it is not there already.
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_questcreator goes below oxmysql, your framework (es_extended, qb-core or qbx_core), fmLib and your target resource. The manifest declares fmLib and oxmysql as dependencies, so if either one is missing or starts later, FiveM refuses to start the quest creator and says which one it could not find.
It worked when the console prints [QuestCreator] FMLIB Initialized successfully. when the resource starts. A red CRITICAL ERROR: FMLIB NOT FOUND!, ESX NOT FOUND! or QBCore NOT FOUND! means the start order is wrong or Config.Framework names the wrong framework.
3. The database
Section titled “3. The database”Import install.sql from the resource folder once, with HeidiSQL, phpMyAdmin or whatever you use. The resource does not create its tables itself.
It creates eight tables, all starting with mic_questcreator_:
| Table | What it holds |
|---|---|
mic_questcreator_list | The quests |
mic_questcreator_locations | Where each quest giver stands, and its model |
mic_questcreator_dialogs | The question-and-answer options, and their cooldowns |
mic_questcreator_personalization | Welcome message, title and subtitle of each quest |
mic_questcreator_events | The events you draw in the node editor |
mic_questcreator_progress | Where each player is in a quest |
mic_questcreator_cooldowns | When each player may use a dialog option again |
mic_questcreator_unlocks | Which events each player has unlocked |
It worked when those eight tables are in your database. Deleting a quest removes its locations, dialogs and personalization with it.
4. Items
Section titled “4. Items”None. The resource ships no items of its own. The items a quest gives, takes or checks for are whatever you type into the nodes, so they must already exist in your inventory.
5. Framework and target
Section titled “5. Framework and target”Open config.lua and check two lines:
| Option | Set it to |
|---|---|
Config.Framework | 'esx' (the default) or 'qbcore'. It is not detected on its own. On QBox, use 'qbcore' — QBox runs QBCore resources through its compatibility layer |
Config.InteractionType | 'ox_target' (the default), 'qb-target' or 'drawtext' |
If you run neither target resource, set 'drawtext': players then walk up to the NPC and press E.
6. Give yourself the editor
Section titled “6. Give yourself the editor”The editor is locked behind the ACE permission mic_questcreator.open. Grant it in server.cfg (or your permissions file) with an add_ace line: to a single person by identifier, for example add_ace identifier.discord:YOUR_DISCORD_ID mic_questcreator.open allow, or to a whole group, for example add_ace group.admin mic_questcreator.open allow.
It worked when /questcreator opens the Quest & Event Creator. Without the permission the server answers “You do not have permission to access the Quest Creator.”
7. First test
Section titled “7. First test”- In the Events tab, create an event, open it in the node editor, and wire Start → Notification → Give Money → End. Save.
- In the Quests tab, create a quest. Add a location: pick a ped model, press Set Position, walk to a spot, and confirm with E.
- Add a dialog with a question and an answer, and pick your event under Trigger Event. Save the quest.
It worked when the NPC is standing where you placed it, talking to it opens the dialog window, and choosing your option shows the notification and pays you.
Before you open your city
Section titled “Before you open your city”- Only the right people have
mic_questcreator.open. Anyone with it can create and delete every quest on the server. - Check
Config.FrameworkandConfig.InteractionTypematch what your server actually runs. - Decide on
/cancelquest. It is on by default;Config.EnableCancelQuestswitches it off. - Test a quest with a reward on a normal character, not only on your admin one, so you see the same permissions and inventory your players will.