Documentation
Update the Camera script from version 1.x to 2.0 on your FiveM server: what changes, what keeps working, the new items and tables, and moving your Fivemanage key.
Camera 2.0 replaces Camera 1.x in place. The resource is still called qs-camera, and the four items you already have — camera, broken_camera, camera_module and photo — keep their names. What changes is everything around them: a second resource for the models, database tables, seven new items and an in-game settings panel in place of the config file.
In 1.x
In 2.0 |
|---|
|
|
| Detected from what is running. |
|
|
No database | Five tables from |
One resource | Two: |
| A durability that wears with every shot, plus a failure chance that grows with wear. |
| Wear on every supported inventory, kept on the camera item itself. |
No film | Rolls of |
Photos taken with 1.x keep their picture and the place they were taken. Players can show them and store them in albums like any new photo.
Cameras keep their condition — the old value becomes the new durability — and get a serial number the first time they are used. They start with an empty roll, so give players camera_film, or switch on New bodies come loaded (Wear, repair & film) before they pick their cameras up again.
Broken cameras and camera modules work as before: use the module to bring the camera back.
Your upload key — the same Fivemanage token or webhook goes into the new file.
1.x stored nothing in the database, so there is nothing to migrate or clean up there.
Export your database with HeidiSQL, phpMyAdmin or your host's panel, and move the old qs-camera folder somewhere outside resources.
Open the old server/custom/webhook.lua and copy the value of DEFAULT_WEBHOOK.
Write down anything you changed in the old config/config.lua — the break chance, the spark damage, the wear rate. You set them again in game.
Copy qs-camera and qs-camera-props, add both to server.cfg — props first — and import sql.sql. Installation has the details.
Into the new qs-camera/server/webhook.lua. A Discord webhook must now end in ?wait=true.
photo_album, camera_film, instant_camera, instant_film, instant_photo, instant_album and cork_board — see Inventory Items. On ox_inventory, also add the server = { export = 'qs-camera.useItem' } line to the four items you already had.
Restart, open /cameraconfig and set what you wrote down under Wear, repair & film — Sudden failures and Base failure chance replace the old break chance.
In 1.x | In 2.0 |
|---|---|
Use the camera and shoot. | Use the camera to see its condition and film, then press Take photos. Zoom, filters, a grid and a self-timer in the viewfinder. |
Use a photo to look at it. | Use a photo to show it to the people around you, or to store it in a photo album. |
Every photo the same. | Every photo graded from Masterpiece to Damaged by how it was taken. |
A broken camera is repaired with a module. | The same — and a worn camera can be topped up before it breaks. |
— | The instant camera, printed cards, wall frames, cork boards and card albums. |
The console shows qs-camera v2.0.0 started with your framework and inventory, and no red line about the webhook or screenshot-basic.
An old camera opens its panel with a serial and its old condition.
An old photo opens with Show it and Store in an album, and its picture loads.
/cameraconfig opens for your staff.
