Game Development

No prob! Hope it works well for you ^^

Tonnes of games use Lua. Lua is pretty much designed to be a scripting interface for a compiled engine.

Every language makes choices and tradeoffs, I'm not a fan of 1-indexing but that shouldn't actually get in the way of anyone worth their salt. Plenty of other languages used every day use 1-indexing including the perennial Fortran and the enterprise eternal (much to my chagrin) Matlab.

As an aside, the 1-indexing is enforced by array functions, but Lua as a language and syntax doesn't care. There are no true arrays in Lua, only tables (associative containers). If you have cause for it and are careful about your assumptions, you can have an array start at 1, 0, 4, -8 or even "cinnamon"

I've personally never seen that sentiment toward Lua. It's also used in Pico-8, and that's quite well regarded.

Unreal 2.5 is so old, your perception of engines is probably way outdated. Things are so much easier and more cohesive now, you'll definitely enjoy modern gamedev tools. Since you're already an experienced programmer you should be up and running with Godot in only an hour, there's a tutorial in the official documentation that you can skim. You can probably look into a Godot crash course video on youtube too for a quick overview.

based on my anecdotal experience your comment sounds rather biased.

That's called an opinion. Usually, you can identify those when someone writes something like "I don't like it"

Godot's easy to use, that's its strength. Past that, it is riddled with issues. A lot of APIs are either poorly designed, half-implemented, or outright broken. The engine has terrible extensibility support due to a shitty build system, which is why you need to download a separate build of the engine if you want C# support. Third party native plugins like Spine also require a custom build of the engine to deal with this (want to use multiple third party "plugins"? Start learning C++ and scons so you can glue them together yourself). The internal organization of the code is sloppy, and while understandable due to it initially being a one-man project, the situation has not improved despite the massive increase in volunteers and money it has had over the years. There's a lot of bike shedding that goes on, and leadership doesn't seem to have a clear vision of where to take the engine.

GDScript sucks. The events system sucks. The hierarchical entity design sucks (although the nestable scenes helps smooth that over). Godot physics sucks. Jolt physics is better, but the integration sucks (Try making joints. The only reliable one is the 6DOF joint, but that requires you to fiddle with dozens of parameters to try and achieve what you want). A lot of the rendering features suck and/or are broken, even basic things like static lighting and shadowmaps fall apart with basic geometry. Everything is buggy as hell, and that's something you just need to accept if you're going to make games with it.

I don't hate Godot, and I do use it because of its main strength: ease of use. It's my go-to for game jams and prototyping, and I have used it a lot. But if I'm going to invest serious time/effort into a project, I'm not going to disadvantage myself right out the gate by choosing Godot.

I haven't used it that much (never even done a jam with it). The weird licensing of the editor rubs me the wrong way, and IIRC it even has some telemetry enabled by default. That's kind of a red flag when you consider the engine came from King, a mobile game developer. I don't think I want to trust them, but other people might not care.

But I do like the design of the engine. Message passing is actually a great pattern in general, and it's used by other engines like O3DE to great effect. It does take some getting used to though, and I personally never was a fan of Lua. If you've ever done any Objective C or Swift, it'll be familiar. It provides a way to build decoupled systems effortlessly, and long-term keeps your codebase flexible and maintainable, which is exactly what you want for a game that needs to constantly evolve its design throughout development.