There’s a limit for a reason. Doing so could harm your game due to the sheer amount of information.
Just so you know, you don’t have to include the questions in your post, and please attempt to solve it yourself before posting.
He said he searched for a solution but didn’t find it,
if I called a recursion with wait() after calling the function again it would give a stack overflow, if I managed to bypass that I’d probably be travelling faster than time itself so yeah, the answer is no.
call the wait before calling the function basically, that should fix your stack overflow.
It’s a good question–If you use a tail call, that is commonly optimized to use goto–Not sure about
the version of Lua you are using, but some versions do indeed do tail call optimization.
Just so you know that what you said is completely false. The problem is regarding stack overflow, not script execution timeout. Stack overflow is caused when you exceed the size of the stack.
This code below would cause a stack overflow, since the function rec recursively calls it self over and over, creating more more than 16381 stack frames in the stack and thus causes a stack overflow.
local function rec()
rec()
end
rec()
Yielding will just cause the stack overflow to occur slightly after some time, that’s it.