-
Notifications
You must be signed in to change notification settings - Fork 202
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
maxZ is nil on qb-target.lua #106
Comments
Make it NOT NIL? |
The scripts I use are codes developed by other people, such as ox_target. and a few lines of code were written in the package (as the folder name suggests) to make it compatible. The fact that there are some problems with the default packages that come with If you are considering making the handling situations in each package the responsibility of the user, there should not be a compatibility package here. Instead of telling me this, what if you wrote a few more lines of code? Because otherwise there is no point in choosing your package. It makes more sense to spend the time writing my own target than I would spend on handling. The code written does not fully fulfill its purpose. I wrote it for your information. Clean code isn't just about making code that works. good luck. |
Not my fault that QB can't even manage to use "their" resource correctly. It also isn't my responsibility to provide 100% compatibility for anything, let alone for a framework that steals code and removes copyright notices. qb-target compatibility is only there because somebody PR'd it. If something doesn't work, then PR a fix, because I frankly could not give any less shits about it. |
"there should not be a compatibility package here" -yankikucuk
Tell me you're brain dead without telling me you're brain dead |
Bruh, you are a drama turkish queen! |
Tell me you crave attention without telling me |
are you like brain dead or something bruhhhhhhh? wew there goes the qb-target support CONGRATS buddy |
in line 139 value returned nil with console error.
was fixed in #33
any solution for this?
The text was updated successfully, but these errors were encountered: