I’m currently looking for new scripts and things to add to my servers. There are certain things that I like about QB-Core servers that aren’t supported by ESX and vice versa.
I’ve seen a bunch of ESX servers switching to QB-Core and I’m wondering if it’s worth it. I want to see if I can get some of your reviews and opinions.
Thanks!
The following is just my personal opinion from a developers point of view. I do not actually play anymore unless it involves testing purposes.
Tl’dr: Established by way too many servers to ignore it.
A lot more scripts to choose from than any other framework.
Not as easy out of the box if you never worked with FiveM. Lots of little quirks just through the sheer amount of versions out there.
Breaking backwards compatibility is annoying.
Tl’dr: One step ahead and many backwards imo
Feels easier for beginners.
Comes with a lot of better maintained resources out of the box.
Many functions are (or have been once) a straight up copy from ESX and just renamed.
Items and other essentials as Lua files? This makes no sense at all.
Oooh boy the documentation. Copy pasting source code is not documentation.
Too many old (and bad) habits in many scripts (not necessarily the framework itself). Be it performance or quality in general.
For me as a developer the last point for QB is simply a deal-breaker. I had high hopes at the beginning for QB but shortly after developing a resource that would support both ESX and QB I found out about the items being in a Lua file, I completely lost it. The script requires you to add ~150 additional items. For ESX I had a tiny piece of code that would craft a SQL query to add all of them to the database. For QB that is simply not possible and I would have to tell my customers “Oh yea, you have to do this by hand as I am not providing a file”. You never know when the layout in that lua file will change etc.
I hate both equally (okay, QB a little more) and I will always advise people to make their own framework. But since 99.9999% of them can’t, I’ll just recommend (staying with) ESX (for now).
There is an addItem function, might want to look into it. You can easily store items in the database and upon initialization of the script add the items to the core via additem function.
They barely maintain anything, all the competent team members left. Also,
Uses (or used) stolen/unauthorised code from paid resources and nopixel.
Refuses to use any sort of versioning.
Breaks backwards compatibility (paired with the lack of versioning, this is a nightmare).
Randomly forks resources, renames them (qb-), and claims full ownership/copyright.
Horrible code with countless exploits. qb-inventory is probably the biggest offender.
Performance leaves a lot to be desired, especially for server-database interactions.
The lack of versioning blows my mind along with their documentation being extremely incomplete with horrible examples - it’s almost not worth looking at.
So what other options are there? I have been on qb for almost a year now.
you can easily add them with a Function inside your own script!, or make a table and loop through it to register the items!.
but imo currently the best option is ESX + OX ( inventory )