LUA

The language is small and easy to embed, which is why it ended up inside so many engines, level editors and build pipelines. Designers use it to script events, interfaces and gameplay logic; programmers use it to expose the right hooks.

It sits on top of an engine: C++ or C# underneath, Python for tooling, Git taken for granted. Lua work ranges from scripting positions to design roles where the scripting is the way a designer gets an idea into the build.

What it signals is a studio with its own tools: where everything happens inside a standard engine, the scripting layer is usually something else.

The language itself is quick to pick up, and that is part of the point. The harder part is the surrounding system: which objects are exposed to the script, what happens when one throws an error during a live session, and how a change gets from a script file into a build that players receive.