#ox_inventory dont work
1 messages · Page 1 of 1 (latest)
What inventory version do you have ?
Yes I understand but you need to make the bridge file for the framework. Because ox does not support qb out of the box
Or someone here can share you theirs
ox_inventory
Use version 2.41.0
Above 2.41.0, it doesn't support qbcore
Once you've downloaded it, please mention me and I'll tell you what to do next
@ornate reef
I can't find that video anymore I can teach you how to install it
Are you currently installing version 2.41.0?
If so, please add config.cfg to the ox_inventory folder
did
i already did it
it work
@terse mica
ima try it
i dont see the error no more
am i able to update the client and server.lua that overextended updated or do i have to keep it old version
You can try
I haven't updated so I can't give you an answer
I suggest you keep the old version
Bro
ok
1.31.1
If you need it, I can send you the one I use
Do you need it, I'm going to sleep if I don't need it, because I have a time difference with you here@terse mica
Ty
My inventory don’t want to open
I’m not geting any errors
I’m geting that one error again
I have the qb bridge
ok
wait a min
I'll send it to you when I wake up
Because I'm so sleepy, bro
I'll send you the version I used
Ok
Hey make sure you added sql files into your database
Because you have a lot of errors that tables in your db don’t exists
what sql
there is no sql
if it hasnt been said, lastest ox inventory no longer works for qbcore anymore
version 2.41 still supports it but to make certain items usable or function youll need to write in some client events in the items lua table, there are some other support threads that are related that you may find useful, we can only provide support fully for qb inventory since thats the inventory we provide in the build.
I have 2.41
are you using the convars?
?
https://overextended.dev/ox_inventory look in the documents
Documentation for Overextended's resources for FiveM/RedM
where it says this
setr inventory:framework "esx"``` just put qb right there
add the whole convar to your server config
i did that
okay mmm
wait
is this supposed to be in my server cfg or can it be in the config.cfg i made for ox inventory
no
needs to be in you server config, unless youve done exec ox in your server config, may work but works to have it in your server config, thats how ive done it
i did exec@ox_inventory/config.cfg
that wont work, just throw it in your server config
its already in there
no i meant the entire convar like it is in the docs i linked you to
is that what you have?
no im not saying have it like that
like this
i meant literally put that whole convar out and PUT it in your server config
no..
pull al that and throw it in your main server config files where all your resource are ensured etc etc.
put that at the very bottom of it for now and reorganize it later
from top to bottom, paste it into your regular server config
It still dont work
dont see how it doesnt work for you but has for me
can you show me how your putting this into your server config
just show the section where you added it
can i send you mg cfg
use old ox inventory the support for qb stopped on latest ox inventory
'2.41.0'
try it
you can execute sql again of inventory related scripts . if you cannot get into server check db name
I told him to do that
``` CREATE TABLE IF NOT EXISTS gloveboxitems (
id int NOT NULL AUTO_INCREMENT,
plate varchar(255) DEFAULT NULL,
items json DEFAULT NULL,
PRIMARY KEY (id),
KEY plate (plate)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
CREATE TABLE IF NOT EXISTS stashitems (
id int NOT NULL AUTO_INCREMENT,
stash varchar(255) DEFAULT NULL,
items json DEFAULT NULL,
PRIMARY KEY (id),
KEY stash (stash)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
CREATE TABLE IF NOT EXISTS trunkitems (
id int NOT NULL AUTO_INCREMENT,
plate varchar(255) DEFAULT NULL,
items json DEFAULT NULL,
PRIMARY KEY (id),
KEY plate (plate)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; ```
My inventory dont want to open
You have to be more specific when troubleshooting
"It won't open" is not enough
Try monitoring the possible errors you receive client side and server side
I fixed it