It doesnt matter if it does work fine with legacy. I reskined it as the original one wasnt looking to good. I didnt realloy go dibth with the code as i didnt want to rewrite the whole thing and just tweaked it
Nope its disabled. Again this is a reskin of scrpit and not a script that been wrote from scratch. So my main goal was a good design not to make it compatible with every other scripts…
its a reskin of a script from 4 years ago, ESX multicharacter is an official part of ESX Legacy.
The backend is just completely messed and literally not compatible with any esx code made within the last 2 years.
I will glady PR a fixed backend if you want, but claiming ESX 1.1 code will work straight away with legacy when its using functions that were removed years ago is just not right
Again, it doesnt matter even if its 1000 years old. The idea is to reskin a script that was working perfectly on my server. So i dont need to look at code or really do anything with it except adding a nickname. Again if i did test it on esx 1.1 i would have mentioned it but i literally got my esx server few days ago.
Bro, you don’t get it, people won’t be able to use this in their legacy servers, it might work in your server but it won’t work in most legacy servers,
The entire backend of the script is using functions that haven’t existed in esx since 1.1
I will PR an updated backend for you tomorrow, but, do check what version a resource is coded for before saying