Vcore-cocaineproduction
Optional VCORE addon providing a complete persistent cocaine-production chain: dead-drop contacts, Cayo coca fields, guards, barrel soaking, staged lab processing, suppliers, reputation, dispatch alerts and VCORE Phone mail. 1. Import `sql/coke.sql`. The resource also creates missing tables at startup. 2. Configure locations, recipes, durations, items and integrations under `config/`. 3. Start `cocaineproduction` after `core`, `inventory` and `oxmysql`. `vcore_phone`, `dispatch`, `logs` and `ipl` are optional runtime integrations. The addon uses Core prompts, menus, progress, notifications, currency formatting and inventory APIs. It has no custom NUI and Base does not depend on it. All default item IDs map to the rebuilt Core shared registry and existing inventory
Introduction
Optional VCORE addon providing a complete persistent cocaine-production chain: dead-drop contacts, Cayo coca fields, guards, barrel soaking, staged lab processing, suppliers, reputation, dispatch alerts and VCORE Phone mail. 1. Import `sql/coke.sql`. The resource also creates missing tables at startup. 2. Configure locations, recipes, durations, items and integrations under `config/`. 3. Start `cocaineproduction` after `core`, `inventory` and `oxmysql`. `vcore_phone`, `dispatch`, `logs` and `ipl` are optional runtime integrations. The addon uses Core prompts, menus, progress, notifications, currency formatting and inventory APIs. It has no custom NUI and Base does not depend on it. All default item IDs map to the rebuilt Core shared registry and existing inventory
Version: 2.0.0Optional Resource9 Lua files1 SQL filesExports
Export available from this resource. Check the resource notes and expected parameters before integrating it.
Export available from this resource. Check the resource notes and expected parameters before integrating it.
Export available from this resource. Check the resource notes and expected parameters before integrating it.
Callbacks
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Callback available from this resource. Confirm parameters and return values before using it.
Registered network events
Registered event for this resource. Confirm the expected payload and intended scope before using it.
Registered event for this resource. Confirm the expected payload and intended scope before using it.
Registered event for this resource. Confirm the expected payload and intended scope before using it.
Registered event for this resource. Confirm the expected payload and intended scope before using it.
Commands
/assigncokefield(server)
Database / SQL
SQL files
sql/coke.sql
Detected tables
cocaineproduction_auditcocaineproduction_processingcocaineproduction_stockcoke_barrelscoke_daily_accesscoke_harvest_nodes
Troubleshooting
- Confirm every manifest dependency above is started first.
- Import the SQL where the resource includes database files.
- Use the exact resource folder name shown on this page unless you intentionally change both the folder and configuration.
- Do not copy internal event names into integrations without checking their implementation.

