I think this should work with LuaRocks

make require allow get lua files outside mta folder which is defined, example /var/mta on linux
this could be useful for hostings, could decrease amount of files and speed up scripting

hostings can control mtaserver.conf file and keep this path always in place, don't let user to change it
for security, mta while running could checking this path and if contain file like mta.txt with content allow this folder for require, if not, then this folder will not work for require

I made some tests, serverside ( shared code, i don't think there are difference between client and server ).

Checks for incorrect behaviour

1. simply require("module")
   i think, should show only path from mta root directory
   

2. while require myself filename = "s.lua" and require "s". I don't think this is issue, but could information you can't require myself
   

3. I created 3 files text.lua in each of possible according to pattern:
   print("test in ", "D:/mtasa require test/InstallFiles/server/mods/deathmatch/resources/t")
   where second argument is current pattern ( from screenshot above ) and properly loaded only first occur

longText = string.rep("a",2^24)
require(longText) -- just spam in console, and a bit lag

require("../../../../../asdf")

i was suprised when i discovered this

require("ŕşôíŠ%v=Ü6ÇŘ˙˙śeDL×�`�­��ëGF–±Öş|5ľxuóľ�") -- https://pastebin.com/eA1xHZQr

when you trying require this monster, windows produce this sound:
https://www.youtube.com/watch?v=qlUFWSiOXpM

setTimer(function()
  for k=1,100 do
    randomString = {}
    for i=1,40 do
    randomString[#randomString + 1] = string.char ( math.random(255) )
    end
    randomString = table.concat(randomString)
    require(randomString)
  end
end,50,0)

nothing special, just make server logs spam
i ran this for few minutes, crash doesn't appear, server working normally after stopping resource

8. Test while required script has error
   

9. Creating elements in required resource working. I restarted resource many times, and always print same thing

test.lua

a = createElement("test")
return a

rrr = require "test"

iprint(rrr, getElementsByType("test"))

Tests in practice usage

rrr = require "test"

iprint(rrr, rrr.func(2,2))

where test is

randomModule = {}

randomModule.int = 1
randomModule.float = math.pi
randomModule.string = "hi"
randomModule.table = {a = 3, [1] = 9, asdf = "asdf"}
randomModule.func = function(a,b) return a+b end

return randomModule

2. Traceback working

test.lua

function traceback ()
  local level = 1
  while true do
    local info = debug.getinfo(level, "Sl")
    if not info then break end
    if info.what == "C" then   -- is a C function?
      print(level, "C function")
    else   -- a Lua function
      print(string.format("[%s]:%d",
                          info.short_src, info.currentline))
    end
    level = level + 1
  end
end

return traceback

t.lua

rrr = require "test"

iprint(rrr())

Bugs, issues

1. Infinity loop wrong source information

s.lua

print ("blabla")

rrr = require "test" -- contain infinity loop

print("bla bla")

2. require myself should be disabled.

3. While incorrect file is passed, only path from server root should be showned Improved warnings for lua-package #683

any plans to marge?

@patrikjuvonen — I have investigated requiring the same file.

Test code:

s = io.read("*l")
if s == "yes" then
    print("YUP")
    require("test")
end
print(s, s:len())

• Lua 5.1 (MTA's Lua, but not tested in MTA) errors out after the second time you enter "yes" (so this file is run a total of two files, once on initial load, and once after the first require)
• Lua 5.3.5 simply repeatedly says "YUP" (after entering "yes")

I think we should just do the latter.

• ll_require in Lua 5.1
• ll_require in Lua 5.3.5

Here is the commit in Lua that removes this error message.

The Lua specification also does not define what should happen if require requires itself.

Also, this is how 5.3.5 behaves for infinite loops:

➜ cat test.lua
require "test"
print "hello"

➜ lua test.lua
lua: C stack overflow
stack traceback:
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	...
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	./test.lua:1: in main chunk
	[C]: in function 'require'
	test.lua:1: in main chunk
	[C]: in ?

Right now requiring the same file crashes the server.

Since the development of this PR has halted (has it?), I think it helps if there is an up-to-date todolist of what has to be done in order to complete this PR.
To-dos so far:

• More detailed error messages for Pure lua packages (?)
• Extensive testing
• Infinite loop error should output some more useful trace

A new PR should be created by someone who wants to author this enhancement to the end. Remember to link to this, gather necessary information from here and elsewhere to the new PR.