// the take
PuerTS lets you write Unity or Unreal game logic in TypeScript, Lua, or Python instead of (or alongside) C#, with reflection-based or statically generated C#/C++ bridging. It's for game teams who want scripting flexibility for hot-reloadable logic, modding, or letting non-C# devs contribute, without replacing C# entirely for engine-level code.
Three interchangeable JS backends (V8, QuickJS, Node.js) let you trade performance against binary size and debuggability per platform, including a genuinely clever move to the browser's native JS VM for WebGL/H5 builds. The TypeScript declaration generator gives you compile-time checked access to the actual C# API surface instead of hand-written bindings. It's been in production long enough to have real CI across both engines (Unity and Unreal workflows, nuget builds) and ships prebuilt packages via nuget/UPM rather than requiring you to build the native layer yourself.
Lua and Python backends are Unity-only — Unreal users are stuck with JS/TS regardless of what the rest of the team prefers, so the 'pick your language' pitch doesn't hold across engines. The Python backend has no mobile support at all (desktop only), and the Node.js JS backend disables OpenSSL-dependent APIs on Unreal mobile, so 'full Node API' comes with asterisks exactly where mobile games live. Running three distinct language runtimes embedded in your game is real operational surface area — three sets of bugs, three debugging stories, three things to keep updated — and the new Puerts.AI/agent framework (editor assistant, MCP server, runtime NPC agents) is a recent, Unity-only addition that's unproven compared to the core scripting bridge and adds LLM API dependencies to a codebase that didn't need them before.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →