About the service
I am a Lua developer, and Lua for me is not a side skill but a language in which I have invested years and know it in depth. I write game scripts and mods for engines that embed Lua, create embedded scripting layers that let non-programmers safely customize behavior, and design request processing logic for Nginx and OpenResty. If you have a host application in C, C++ or any runtime with Lua bindings, I'll write scripts that live inside it, carefully expose the API your designers or operators actually need, and make the system predictable under load.
My niche differs from both generalists in Unity, Unreal, Godot and from regular backend developers. I care about details that show up precisely where Lua acts as a binding layer: coroutine threads, careful memory management and garbage collection, sandboxing for untrusted user scripts, metatables and clean module boundaries, and the real cost of each call across the C boundary. On the OpenResty side I write handlers for access, rewrite and content phases, gateway logic and API plugins, request rate limiting, authorization checks and caching via shared dictionary that stays correct when thousands of requests arrive simultaneously.
In practice this means I'll extend an existing mod system, give your team a documented scripting API, bring a tangle of legacy Lua into readable modules or spin up an OpenResty gateway with proper routing and request formation instead of hard-coded rules. Every result comes with tests where the runtime allows, clear comments and notes on extending it. Tell me what engine, host or gateway you're working with and what the scripts need to do, and I'll be honest about what fits.
— Game scripts and mods for engines with embedded Lua
— Embedded scripting layers and customizable behavior for host applications
— Nginx/OpenResty handlers for access, rewrite, content phases
— API gateway plugins and request logic, rate limiting, authorization
— Sandboxing and safe execution of untrusted scripts
— Refactoring legacy Lua into clean documented modules
My niche differs from both generalists in Unity, Unreal, Godot and from regular backend developers. I care about details that show up precisely where Lua acts as a binding layer: coroutine threads, careful memory management and garbage collection, sandboxing for untrusted user scripts, metatables and clean module boundaries, and the real cost of each call across the C boundary. On the OpenResty side I write handlers for access, rewrite and content phases, gateway logic and API plugins, request rate limiting, authorization checks and caching via shared dictionary that stays correct when thousands of requests arrive simultaneously.
In practice this means I'll extend an existing mod system, give your team a documented scripting API, bring a tangle of legacy Lua into readable modules or spin up an OpenResty gateway with proper routing and request formation instead of hard-coded rules. Every result comes with tests where the runtime allows, clear comments and notes on extending it. Tell me what engine, host or gateway you're working with and what the scripts need to do, and I'll be honest about what fits.
— Game scripts and mods for engines with embedded Lua
— Embedded scripting layers and customizable behavior for host applications
— Nginx/OpenResty handlers for access, rewrite, content phases
— API gateway plugins and request logic, rate limiting, authorization
— Sandboxing and safe execution of untrusted scripts
— Refactoring legacy Lua into clean documented modules
