Closed TankinTom closed 11 months ago
can u send me your script version ?
the best thing i could tell you to do is update your qbcore to the newest qbcore as old ones normally tend to start getting outdated you can change your qbcore version inside of txadmin or the github.
the best thing i could tell you to do is update your qbcore to the newest qbcore as old ones normally tend to start getting outdated you can change your qbcore version inside of txadmin or the github.
For it to work one day, but not the next, and we're on the most recent qb-core version, would mean it's something else.
My issue was that I had stuff outdated and was running updated qb-core and my stuff still broke
I'm having a similar issue …. I have already updated my artifacts and updated the qb-adminmenu script, yet still i cannot use my developer menu and vehicles don't show up in the vehicle menu, so I cant use it at all …. the last comment said they had something outdated, can someone help me figure out what I would need to update to try that solution -- I'm new to all this and have been learning as i go ... but have not had any issues with the admin menu until now, Please Help
@Tr1n14Lif3 same here, I'm pretty late but if you found a fix please lmk!
the best thing i could tell you to do is update your qbcore to the newest qbcore as old ones normally tend to start getting outdated you can change your qbcore version inside of txadmin or the github.
For it to work one day, but not the next, and we're on the most recent qb-core version, would mean it's something else.
Found a fix? Please tell me you have lol
This issue has had 60 days of inactivity & will close within 7 days
Describe the bug When pulling up the admin menu, and pulling up players, or vehicles, nothing appears, when reloading the menu, you get the following screenshot, and when re-installing, none of the developer options work, such as getting vectors, even the slash commands don't work
To Reproduce
Expected behavior Everything should work fine
Screenshots
Questions (please complete the following information):
qb-
to something custom? [e.g. yes/no] noAdditional context First noticed it last night, and then today it was still occurring.