yes it is promised i will give you a feedback unfortunately my servers are updated at the end of the week, i must guarantee 100% access for 1000 people per server it is very complicated to manage. But don’t worry I would
you should use the new imports system and comment the getsharedobject
1.1/1.2 are so outdated, no reason to support them. if people want to stay on their outdated, vulnerable versions, they can do 5 seconds of work to adapt it to that.
i just want to say one thing people stay on an obsolete basis as you say because they worked hard on their server 3 years - 4 years and that would make too much work to update it on esx_legacy, and frankly say we are doing everything on legacy and the rest, we don’t care. It’s not very fairplay like behavior. We will see how you will do when you work like crazy on your legacy version and it will be obsolete in a few years and a little clown will come and say, we are doing everything for the new version and for esx_legacy we need to share nothing more for them. …
Well for a person with basic esx knowledge switching from a old esx to legacy shouldn’t be a problem lol since what change is really not that much when it comes to features, is more about cleaner code and more up to date coding.
That’s kinda it I’m using EXM for quite a while now I have my whole system implemented to it so kinda don’t want to move to Legacy just because something new came out