At first, thanks for all the feedback!
Sounds good. Take all the time you need. We'd be delighted to chat about any questions and concerns you may be having!
In the meantime, I'd like to respond to a couple of things that were mentioned in this thread.
I read this a couple of times before, so it seems like a pretty important aspect. It's true that MTA got something like a "custom engine you can mod". I personally don't think it's a restriction though. In the end, nobody forces anyone to create something that looks totally different from SA - it's the server's decision. Also, I think you inevitably end up with something like this if you add more and more features.
Just a rough and spontaneous idea to address this issue: Perhaps it would help to introduce a server tagging system that allows for better filtering (e.g. "SA credibility").
(1) MTA depends on a few third-party libraries that are known to cause problems on Wine (e.g. CEF). We invested some time a few months ago to make these components optional. This should have improved Wine support. Also, I know of a couple of people who actively use MTA on Linux.
(2) It's true though that some servers block Wine. The reason is that essential anticheat components do not work on Wine and therefore simplify cheating a lot. So we decided to go for a trade-off that allows servers to block Wine. At the same time, we added scripting features that can be used for per-player whitelisting.
(3) Technically, it's possible, but the demand for it was pretty low in the past.
In my humble opinion, Lua is a very nice multi-paradigm language that supports imperative, object-orientated and even some functional programming approaches. Unlike other languages, it was also implemented with focus on embedding in other applications - that's a big advantage, especially when it comes to securely using it for clientside scripting.
Apart from that, let me mention an interesting project that was created by the MTA community recently: https://mta-slipe.com/. It essentially transpiles C# to Lua.
That's not what I was suggesting. We're talking about a compatibility layer that would allow you to run your SA:MP gamemodes (written in Pawn) without modifications directly on MTA. Like open.mp wants to implement additional languages, we'd add Pawn as an additional language to MTA (incl. SA:MP's scripting API).
(2019-04-26, 10:01 PM)JustMichael Wrote: We will comment officially, when we have fully discussed this.
Sounds good. Take all the time you need. We'd be delighted to chat about any questions and concerns you may be having!
In the meantime, I'd like to respond to a couple of things that were mentioned in this thread.
(2019-04-25, 07:53 PM)BloodMaster Wrote: SA-MP is a mod that's supposed to keep the credibility and looks of San Andreas, while MTA is a custom engine you can mod, and that's the main difference why many more players are better appealed by SA:MP
I read this a couple of times before, so it seems like a pretty important aspect. It's true that MTA got something like a "custom engine you can mod". I personally don't think it's a restriction though. In the end, nobody forces anyone to create something that looks totally different from SA - it's the server's decision. Also, I think you inevitably end up with something like this if you add more and more features.
Just a rough and spontaneous idea to address this issue: Perhaps it would help to introduce a server tagging system that allows for better filtering (e.g. "SA credibility").
(2019-04-25, 08:27 PM)ohmios Wrote: 1) MTA client is famous for being a pain in the ass?to make?run on linux with wine, to be fair it seems easy now using the latest wine, but I can see that being broken again with more MTA updates.
While samp client on linux just works? and hopefully open.mp client will too when it gets released many moons ahead.
2)?One?MTA?server didn't let me join, the error message from the server literally said it was because I was running wine.?
3) AFAIK?MTA server doesn't support ARM while open.mp will.
(1) MTA depends on a few third-party libraries that are known to cause problems on Wine (e.g. CEF). We invested some time a few months ago to make these components optional. This should have improved Wine support. Also, I know of a couple of people who actively use MTA on Linux.
(2) It's true though that some servers block Wine. The reason is that essential anticheat components do not work on Wine and therefore simplify cheating a lot. So we decided to go for a trade-off that allows servers to block Wine. At the same time, we added scripting features that can be used for per-player whitelisting.
(3) Technically, it's possible, but the demand for it was pretty low in the past.
(2019-04-25, 10:47 PM)iReal Worlds Wrote: Lua... Srsly?
In my humble opinion, Lua is a very nice multi-paradigm language that supports imperative, object-orientated and even some functional programming approaches. Unlike other languages, it was also implemented with focus on embedding in other applications - that's a big advantage, especially when it comes to securely using it for clientside scripting.
Apart from that, let me mention an interesting project that was created by the MTA community recently: https://mta-slipe.com/. It essentially transpiles C# to Lua.
(2019-04-26, 06:29 AM)michael@belgium Wrote: imagine everyone switching to lua...
That's not what I was suggesting. We're talking about a compatibility layer that would allow you to run your SA:MP gamemodes (written in Pawn) without modifications directly on MTA. Like open.mp wants to implement additional languages, we'd add Pawn as an additional language to MTA (incl. SA:MP's scripting API).