Leaderboard

Temporary bans can't be appealed. Bans on MTA forks are generally longer because they cheater-infested due to their weak anticheat, and thus there needs to be a stronger deterrant. So, once you get unbanned, don't do it again.. lesson learned.

When lights turn on, the GTA renderer culls backfaces of polygons - essentially making polygons draw only 1 side being the direction that the normal is facing. I believe this is an issue with both opaque and transparent materials, but it's usually not visible with GTA vehicles as they have fabric on the inside which covers the vehicle metallic surface from the inside. If you don't plan on doing this, something you could do is duplicate the metallic surface polygons and flip their normals. I don't recall if this works for transparent materials.

1) Yes. By completely implementing the Lua 5.1 language this approach can speed up any 10+ years old Lua resource/gamemode. Don't get me wrong, I want to implement the entirety including garbage collection, luac binaries and the API layer for applications like MTA. But there will be limits where security is at risk, mainly the luac binaries that use sequences of opcodes that cannot be generated by the reference Lua 5.1 bytecode compiler (call opcode with stackframe intersection, exploits, etc). 2) Great care will be taken that the execution order of all statements does perfectly match the order of the Lua 5.1 reference compiler. I will go into the old source code if I must make things clear, and I have already studied the internal workings of it in great detail. Thus NO, there will be no misinterpreting long/complex operations. The compiler will be created with great scientific effort and documentation. 3) Yes. My goal is to optimize the code as much as possible. I will post about any optimization technique that will be implemented in great detail in this thread once I get to them. Removing unused and redundant code is an important optimization I want to make. An example situation is: if there is code which does not call C functions and whose effects can be isolated to have no influence on code which otherwise would call C API, then the code can be removed. This is possible by inspecting the dependencies of language constructs (arrows in the calculation graph). I plan to improve the error messages of script compilation and provide warnings where code does not perform well, for example if by static analysis the compiler finds that two booleans would be added together. In Lua 5.1 this code is allowed to compile but once that code is to be executed, the language throws a runtime error. This situation will not change due to compatibility, but a warning will be put out to help devs. ?