At this point, QBUS is ESX Legacy lol. Someone just took esx_menu_default and pasted it for qbus. Why don’t anyone just make ESX better? Merge the community rather then taking ESX and renaming it? It gets harder and harder to choose between two frameworks.
People are buying random scripts here and there. And I see Qbcore GitHub getting awfully similar to ESX Legacy.
Why not someone from top of the chain take ESX and make it better? I have bought about 1000$ worth of different scripts and now I am in a middle ground to choose to go to qbus or stay with ESX.
Why have two of same frameworks with different name? Why not merge and make either one of them better?
Just keep this thread on the positive side. Don’t want to spark any riots from Qbcore Community (I see they are VERY active and can take any level of fights.)
Personally, I don’t use any of the “popular frameworks”. I like to make stuff myself. But having a choice is a good thing. You don’t need to have “one framework to rule them all”.
That’s just gonna make every single server feel the same. And will lead to new players thinking that every server should feel the same. Hell, that’s already happening in some parts of this community (Shout out to the guy that told me that my “K menu” doesn’t work, whatever that means).
I mean that’s also my argument. If you check the source code of ESX Legacy V1 and Qbus, you won’t find a difference lol. That’s like even worse to make a clone of framework with just differnet name and then 100’s of servers following two chains.
Maintainers of respective frameworks. They should talk it out and maybe just clear it out. Creators have to do double work of selling both versions, when technically both of them are same.
Look at this dude making a help guide for Qbus>ESX conversions lol
I mean that is true the QBCore community is very active because we strongly believe in this Project and the road that awaits us. I wouldnt say we take “can take any level of fights” tho, those people that do give QBCore a bad name
But ESX isnt really the same as QBCore, yes its easy to convert some scripts to QBCore but that dosent mean its the same.
also as ChatDisabled said QBUS was the server the QBCore the framework originated from.
I am happy to chat more about this like normal people if you have any questions.
You are referring to it as qbus which was the original rp server, the framework has been released under the name QBCore as that fits better and does not resemble all the leaks that are under the name ‘qbus’
IDK if you have seen why are those 2 resource made for, they are made for a quick QBCore conversion of guille_doorlock, I do not encourage anyone to use them and didn´t made them for having QBCore looking like ESX, it was just because I was on a hurry to have ready the QBCore conversion and didn´t have any time to make a UI, or learn how to use another UI, so I quickly did it, it isn´t official, neither I made it for people to use them in their resources.
Also, in my understanding, you are saying that ESX is exactly like QBCore but QBCore is renamed?
Check the code of the OFFICIAL QBCore Framework, which doesnt look any similar, but if you see the leaked QBUS files (2 year old files), that is normal.
I hope you understood me. Greetings, correct me if I am wrong
This is what I was talking about. Same 5-6 people from Qbus Community herd over someone to prove themselves right. 2 hour ago this was posted. Suddenly admins/maintainers of qbcore run towards defending themselves at the same time.
As I said those select few cough ChatDisabled cough give QBCore a rough name. Most of the time its not bad, but we hear the same thing over and over “ESX is QBCore” and it gets tiring after a while because its just not true.
If someone wasnt speaking the whole truth wouldnt you want to try and clear thing up? I know I would. and no one that has responded is an admin or maintainer
Man, you took out of context 2 resources published on my github to attack the QBCore community, lets not start to have beef because we dont want timeouts
It’s a bit bold of you to assume QBCore is suddenly ESX Legacy, that’s also why some of the people in the community tell you that, it is not an exact comparison, you also probably haven’t looked at any of the code or only a small part which looks like that of ESX Legacy and then assumee it’s the same and you linked an unnofficial resource which I didn’t even know the repo existed.
