giving people unriddled access to the runtime is a terrible idea for security
giving people unriddled access to the runtime is a terrible idea for security
Lthey could just start dumping files to a server or download viruses
Lwith a Lua sandbox you control p much everything they have access to
HHmmmmm
His there alternatives that is statically typed though?
Hi tried lua scripting in C++ before
Lthere probably is, but Lua is the most mature ive seen, and generally i havent run into issues with lua's non-type safety
Las long as you structure things right, it should be fine, just provide docs to the API and let people go wild with lua
Hi see
SI used TypeScriptToLua to workaround type safety
Ha transpiller then?
DI use the Roslyn compiler in one of my apps. works pretty good.
Hare there no licensing problem?
CIt is a standard MIT license.
CVery easy to do the compliance dance for that.
Hoh?
Hi didnt know that
SCC0 
Rmight want to look at angelscript
Rthough you might have to do a lot of work if your engine is in C#
Hhmm yea
Hthe biggest advantage of using C# to me is that it's maturity
Hmeanings there's already tons of libraries out there
Rhonestly I would just use C#, if you can figure out a way to blacklist and whitelist parts of the C# library, and mostly prevent just prevent reflection you should be fine, and you might be able to implement moonsharp if you want a LUA inerpreter
Rwhich is "Safer" Ultimately when it comes to modding just dont be safe, it's inherently NOT safe
RYou can make it safer
Rbut someone will find a way to break out of the sandbox as some point, or find something malicious they can do WITHIN the sandbox
RJust give a fair warning that modding is unsafe
RUltimately by allowing for modding of any sort you run that risk, he should disable the ability to enter official/unmodded/different mod configuration servers while modded, give a fair warning to the user explaining the potential problems with mods, and disable modding support by default
RProviding a safe and secure place to download scripts is a better idea IMO
RUltimately you cannot and should not be responsible for third party content
Ralso happy birthday
HYes i'm very aware of those. I'm currently doing this to make a new open source game engine that i would personally use but also let others use if they want
Rthen even more so, dont be safe
Hyes
Heven unity games are so easily hacked
Hand can be turned back to source
RLOL yeah just the nature of the beast
HIL2Cpp is another thing tho, it's preventing turning back to source
Hbut hacking is still possible
Hjust no more reselling the game source
Rbut its turning into into C++
Hyeah
HImplementing something like that would take ages xD
RYeah'
Rthats why you dont
Hyeah
SDon't trust anyone.
SThat's how you should implement multiplayer
SNot set his position to whatever he said (typical scp:sl game)
Pyou shouldn't care about your game being turned back to source. anyone passionate enough will be able to read the assembly itself and lift it up to usable code no matter what the language or obfuscation.