Umka Scripting Layer for Games and C/C++ Hosts

I design and deliver scripting layers written in the Umka language, a statically-typed embeddable scripting language with a Go-like syntax and automatic memory management. If you are building a game engine, a simulation tool, or any native application that needs safe, fast, hot-reloadable logic without dragging in a heavyweight runtime, this is exactly the work I do. My typical deliverable is a clean integration of the Umka language into your C or C++ host: I wire up the interpreter, expose your engine functions to scripts, marshal structs and slices across the boundary, and set up call-in and call-out paths so designers can drive gameplay without recompiling. Because the Umka language is statically typed, I catch whole classes of errors at compile time that dynamic scripting would leak into runtime, and the automatic memory management keeps gameplay code free of manual bookkeeping. I also use the Umka language for structured configuration and data-driven content, where its Go-like syntax reads clearly for non-C teammates. Over several projects I have written binding generators, module loaders, sandboxing rules, and error-reporting bridges that surface script stack traces back into the host log. Every job ships with documented APIs, example scripts, a small test harness, and build notes so your team can extend the system on its own. Tell me about your host application, your target platform, and how you want scripts to hook into the update loop, and I will propose a concrete architecture and timeline.