-
-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script error #1838
Comments
que esta pasando con el ox_inventory para esx |
nothing |
esta dando un grave error nose por que |
SCRIPT ERROR: @ox_inventory/modules/bridge/esx/server.lua:20: ox_inventory requires Config.CustomInventory to be set to "ox" in the ESX Config este error |
im getting same issue |
ok |
This comment was marked as spam.
This comment was marked as spam.
Read it. It's in plain English and telling you what to do. This is not an issue with ox_inventory, nor does anything need to be changed in ox_inventory. Once again - read what that message is telling you to do. |
This comment was marked as spam.
This comment was marked as spam.
I am pleading for you to read and follow the instructions provided to you. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Why are you posting here still? I cannot do anything for you. There is no problem in this script. There is no problem in any script. The only problem is in your head. |
This comment was marked as spam.
This comment was marked as spam.
what these ppl don't get is we not slow u can change all u want it still shows up. bro its the script just ditch it. just get another something wrong with the code. Not ox but script u using |
This guy responded to one of the half a dozen duplicate issues about this topic, with exact instructions and screenshots to correctly configure ESX 1.11+ to support ox_inventory. The next user still failed to modify it. Spot the difference. |
SCRIPT ERROR: @ox_inventory/modules/bridge/esx/server.lua:22: ox_inventory requires a ESX Legacy v1.6.0 or above, refer to the documentation.
The text was updated successfully, but these errors were encountered: