Originally from lua.org

You may use This manual on the official LUA home to learn LUA, or use This one to gain some knowledge about it. There are many resources around you can use. You can obtain the latest source from Here and build it yourself (Requires Ansi C compiler such as GCC), or grab a binary Here. There is also an IDE you'll find in Tutorialspoint introduced, which I doubt if is accessible.
As for LUA in action, I once herd a dude producing Telegram Bots with LUA code. Though I'm not sure if one could create audio games with it.
Edit:
Mushclient seems to be using LUA under the hood now that I remember.

@2 thank you.
@3 as well as Lua, are there any, besides obvious ones like python and c languages, that you would recommend? Maybe ruby or unity? Any others you think would be a good fallback for when bgt dies haha.

Lua is a pain in the ass. It does shit in a weird way that just leaves me shaking my head.

Wow.

First, to be clear, I'm not writing this as a particularly big Lua fan. I'm writing it as a senior software developer who has done work in probably close to a dozen languages over the past 2 decades.

You absolutely can write audio games in Lua. See https://love2d.org for a fairly complete basic game engine with audio, graphics, physics, etc. It's like a souped-up Pygame. I have most of an audio Asteroids game written in Lua, including an accessible real GUI (I.e. not just arrow menus with lists and a counter, but visual buttons with their focus-handlers augmented to speak button text, etc.) You can write audio games in just about any language, and though it may have its warts, Lua isn't a particularly bad choice for them.

Also, OOP is far from a holy grail or silver bullet. It's a tool, sure, but so are Entity Component Systems, for which objects and classes get in the way. And the Lua language is flexible enough that there are several class systems implemented. They're just not core to the language. But completely dismissing Lua because it doesn't support OOP is like throwing out a toolbox because it doesn't have a set of hex wrenches. Sure, they're useful to have, but their absence doesn't justify throwing out the entire box. For my part, objects and classes are far from the first tool I look to when solving a problem. I find them pretty limiting, actually. Give me an ECS, or something ECS-like where I have many systems iterating over a large quantity of has-a relationships and I'll be very happy.

That said, Lua has its rough edges. If you're used to traditional class-based OOP, the power of something like metatables and prototypes may not be immediately obvious. 1-based indices also routinely throw me, as do some of the operator choices. It isn't my favorite language by a long shot. But build software long enough and the language isn't an end, but a means. Can you use an existing ecosystem and work with a community to do cool, meaningful things with it? If so, then spend some time getting to know it, and see how good of a fit it is for you. If not, then don't. But don't just dismiss it out of hand because it doesn't use the paradigm that you're familiar with. Hell, I've seen enough BASIC threads here that I'm thinking of giving it a shot for nostalgia's sake. Played with a bunch of BASIC dialects when I was younger and kind of miss that simplicity.