// the take
LuaScriptCore is a native-to-Lua bridge for iOS/macOS, Android and Unity3D, letting native code call Lua functions and vice versa, with native classes exportable as Lua objects. It's aimed at mobile/game developers who want to embed a Lua scripting layer for hot-reloadable game logic without hand-rolling JNI or Objective-C glue.
The API is consistent across all three platforms (Java, Objective-C/Swift, C#) for the same operations: reading globals, calling Lua methods, registering native callbacks, and exporting native types as Lua-constructible objects. It handles the genuinely annoying plumbing itself — JNI array/byte[] marshaling, exception propagation from Lua into native exception handlers, and a LuaScriptController for forcibly interrupting a running script. It also supports running Lua calls on separate threads via LuaContext.runThread, which matters for game engines where you don't want script execution blocking the main thread.
No commits or releases since December 2020 — six years with no maintenance, so no support for newer Unity IL2CPP/scripting backend changes, Apple's current toolchain, or current Android NDK ABIs; treat this as effectively abandoned. The changelog itself admits a history of serious bridge bugs (JNI stack overflows on array arguments, memory leaks and deadlocks on thrown exceptions, crashes on repeated method calls on Android) — the kind of native-bridge bugs that are hard to fully trust even after being 'fixed' in a project with no ongoing fuzzing or CI. Documentation lives entirely in a Chinese-language wiki with no English translation, which will block adoption or debugging for non-Chinese-speaking teams. Prebuilt release binaries aren't checked into source — you have to manually fetch them from GitHub Releases to even run the sample projects, and since the project is dead those release artifacts won't track any future Lua or platform-SDK updates.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →