6 product images available.
Limited-time price
Save $4.00 (16% off)
Secure Checkout
Card, Klarna and supported wallets via Stripe. More local methods may appear when available for your region.
Description
### Requirements
- ESX
- esx_vehicleshop
- esx_mechanicjob
- xSound (free on github / [https://github.com/Xogy/xsound])
### Installation
1) Drag & drop the complete_carplay into your `resources` server folder.
2) Configure the config file.
3) Import the SQL file into your database.
4) Install and ensure the requirements.
5) Add export on gcphone (see below)
6) Add `start complete_carplay` to your server config.
### GCPhone export
1) Open gcphone folder
2) Open `fxmanifest.lua`
3) Add at the bottom of the file: `export {'sendMessage'}`
### Showcase
- https://youtu.be/BE69t2cHunQ
Installation notes
Install details not published
Detailed install notes are not published yet. Review the product description and ask before buying if your server uses custom framework, inventory, or database changes.
Buy this when it saves setup time
Use this checklist to decide quickly whether the resource fits your current server build, framework, and support expectations.
Server-owner payoff
Complete Carplay (ESX) is positioned to reduce Scripts instead of making you rebuild the same system from scratch.
Compatibility
Works with esx. Check the requirements block before adding it to a live stack.
Purchase confidence
Instant download, Stripe checkout, support access, and refund policy context are shown before payment.
Decision assets
installation details: Not published separately, Preview video
Product fit, setup, and proof at a glance
Use the published facts on this page to confirm whether Complete Carplay (ESX) matches your server before checkout.
Compatibility
- Frameworks
- ESX
- Category
- Scripts
Setup & requirements
- Install flow
- Download → resources folder → ensure in server.cfg
- Requirements
- Not published separately
Proof & buyer questions
- Reviews
- No reviews — be the first
- Sales
- 7
Only the facts published on this page should be treated as confirmed. If you need more detail, review the description, requirements, changelog, reviews, and product Q&A before checkout.
