LWK Development + CDE CAD - Native FiveM Compatibility
CDE CAD runs alongside LWK Development scripts without conflicts. Both read from the same FiveM framework data, so plates, identities, warrants, and licenses stay in sync between LWK's in-game UIs and CDE CAD's web-based CAD/MDT.
How the integration works
- LWK Development resources run in-game; CDE CAD runs on the web. They share a framework data layer (ESX, QBCore, Qbox, vRP).
- Vehicle data and warrants stay consistent between LWK resources and CDE CAD's DMV bureau.
- Character data and licenses surface in both the LWK in-game UIs and the CDE CAD civilian portal.
- LWK resources can push dispatch events to CDE CAD via the REST API and WebSocket events.
LWK Development + CDE CAD FAQ
Does CDE CAD work with LWK Development scripts?
Yes. CDE CAD is fully compatible with LWK Development resources. Both read from the same framework data layer, so there are no conflicts and no duplicate data entry.
Do I need to remove my LWK scripts?
No. The two systems are designed to coexist. LWK resources provide in-game UIs; CDE CAD provides web-based dispatch, MDT, judicial, records, FTO, and disciplinary workflows.
Can LWK scripts push dispatch events to CDE CAD?
Yes. LWK resources can call the REST API or push WebSocket events to broadcast 911 calls, BOLOs, and unit status into the CDE CAD dispatch board.
Is there any performance hit?
No measurable impact. CDE CAD runs as cloud SaaS; LWK runs client-side in-game.