#How to fix qbx_vehiclekeys couldn't load

1 messages · Page 1 of 1 (latest)

atomic glacier
#

here the qbox docs, i used 12911 cz my server hosting required use it version for performance.

artifacts-8c6f7ca461759e47dbea1605876fff76.png
rigid fractal
#
  1. Image shown has nothing to do with whatever info you provided
  2. oxmysql requires 12913 or later. So 12911 isn't gonna work either way and your whole server won't work even if you could join without that error message
  3. It doesn't mean that 12911 is shown in that second image, that we recommend using that specific artifact. That image is purely for demonstration purposes only in the hopes that people just pick whatever is the latest artifact at the time
  4. Either the communication between you and the server isn't great and you got some packets lost or the manifest file of qbx_vehiclekeys itself is corrupted and that is why it couldn't load it properly
atomic glacier
#

i told them to use a newest artifact but they said the newest have a some performance issues

rigid fractal
#

Bro your server will literally NOT work if you are going to use 12911

#

oxmysql requires an artifact where they updated to have node22

#

If your SQL connection isn't gonna work how is anything else gonna work

rigid fractal
#

Artifact x vs artifact y isnt gonna do anything performance related even

#

It's all just about vulnerability fixes and features being added like the aforementioned node update

#

@atomic glacier name the hosting

atomic glacier
atomic glacier
rigid fractal
#

And why even use them? Because of the free server option?

#

Normally in fivem development you start configuring your server using your own pc

#

Aka localhost

atomic glacier
#

in first development all off the script is fine. bcz i used the latest artifact..

atomic glacier