Discord Moderators Pirulax Posted May 28, 2018 Discord Moderators Posted May 28, 2018 Is there any chance to see Lua 5.3 in MTA? Mostly because of new features in 5.3, like goto statement, bitwise operators, and new metatable events.
CrosRoad95 Posted May 29, 2018 Posted May 29, 2018 This topic was considered many times, mta team said that "this can break already existed scripts" but there can be option to change version of lua, by default: 5.1
Discord Moderators Pirulax Posted May 30, 2018 Author Discord Moderators Posted May 30, 2018 I dont thing that it would break anything, but alright.
Captain Cody Posted May 30, 2018 Posted May 30, 2018 (edited) The current lua system is heavily modified; adding in an updated system would require a rewrite of hundreds of thousands lines of code that have accumulated over years. MTA simply doesn't have a big enough development team left to accomplish stuff such as that. Edited May 30, 2018 by CodyJ(L)
CrosRoad95 Posted May 30, 2018 Posted May 30, 2018 Not change to lua 5.3, but trying copy stuff from lua 5.3
Captain Cody Posted May 30, 2018 Posted May 30, 2018 With the amount of core changes done that would likely not be plausible.
MTA Team qaisjp Posted June 1, 2018 MTA Team Posted June 1, 2018 On 30/05/2018 at 21:25, PolskiSebek12 said: Not change to lua 5.3, but trying copy stuff from lua 5.3 What kind of features, in particular, are you looking for?
CrosRoad95 Posted June 1, 2018 Posted June 1, 2018 bitwise operators goto statement more metamethods new function table.move new function string.pack new function string.unpack new function string.packsize this is only few 1
Jusonex Posted June 5, 2018 Posted June 5, 2018 Actually, it's not about code changes by MTA (there are a few changes, but those are easy to migrate). The real problem is that the bytecode changed which is why compiled scripts won't work any longer. Additionally, some features (like fenvs) were removed. The only way to get support for Lua 5.3 is to add a field to the meta.xml to switch between Lua versions. The question is though: Is the confusion and community fragmentation caused by this worth the few new features? 1
Jaysds1 Posted June 9, 2018 Posted June 9, 2018 In general I like upgrades but if there's nothing wrong with the current version and the whole community isn't invested into the upgrade then I would just say leave it. Create a poll if you really want the community decision.
MrBiG Posted August 21, 2018 Posted August 21, 2018 (edited) On 01/06/2018 at 18:48, PolskiSebek12 said: bitwise operators goto statement more metamethods new function table.move new function string.pack new function string.unpack new function string.packsize this is only few It's amazing More functions for package system Edited August 21, 2018 by Debo15
SugarD-x Posted October 12, 2018 Posted October 12, 2018 On 05/06/2018 at 13:25, Jusonex said: Actually, it's not about code changes by MTA (there are a few changes, but those are easy to migrate). The real problem is that the bytecode changed which is why compiled scripts won't work any longer. Additionally, some features (like fenvs) were removed. The only way to get support for Lua 5.3 is to add a field to the meta.xml to switch between Lua versions. The question is though: Is the confusion and community fragmentation caused by this worth the few new features? I hate to bump such an old topic, but theoretically could it be possible to have 5.1 be the "default" seen by MTA:SA unless manually changed by the user? Even as a long-term fix, that could be used to eventually promote users migrating over to newer versions, and eventually the default could be changed when the developers feel word has gotten around enough. (Kind of like the idea of how XP builds of MTA:SA still exist for those users while they are being encouraged to move over to a newer OS before XP support completely ceases in MTA:SA down the road).
Recommended Posts