We, homo sapiens, are all quite unique, especially in how we think and learn. I've studied programming as a youngster and now at university, and I remember some of what it felt like to begin scripting long ago - frustration when things didn't work for a long time and then exhilaration when they did. Perhaps, in hindsight, I can offer some structure.

First, I'll comment on some of your observations:

"no one really cares to teach or explain how to do anything"

It is often the case with technical concepts that those who know how to manipulate them proficiently are not very apt at explaining them. Albert Einstein himself said:

"If you can't explain it simply, you don't understand it well enough."

Explaining things is always a good exercise, but it takes time and effort, and engineers just want results. Many programmers on ROBLOX are happy learning something well enough to be good at using it, but don't practice explaining. Thankfully, we have a community here of people who do just that: try to explain things.

Journalists are often people who have a special talent for explaining rich ideas in a simple way, and many scientific institutions have special departments for publishing public resources to explain intricate research. There are many knowledgeable programmers on ROBLOX, but many are driven by an insatiable creativity that can't be interrupted to answer small questions on websites like this. There is a somewhat secluded group called RBXDev, which is managed officially by ROBLOX themselves and requires an application form to get in, but that is where the deep technical discussion on cutting edge updates takes place.

There are a handful of people actively writing tutorials (the blog posts on this site), producing video content on YouTube, and answering questions on forums (here and on the ROBLOX forums). I agree, though, that often they aren't actually good at explaining things. This is partly because you and I come from different programming backgrounds, and there's no way to write an article that appeals perfectly to everyone.

I understand your frustration about things not being explained, but I say these things just to highlight that explaining things is actually quite difficult and time consuming!

Structured Learning

I can't say for sure, but there are some abstractions (ways of thinking about things) which have really helped me to understand how to learn programming more effectively.

I'm going to suggest 4 different compartments to think about on your scripting journey which I think would have helped me a lot.

1. Language
2. Data structures
3. Algorithms
4. ROBLOX API

Language

The language is Lua. You need to know what it can do and how to write it. I would set aside some time to read the official Lua 5.1 Reference Manual. It tells you everything there is to know about the language.

There's also a tutorial-like book online for free called Programming in Lua.

These are good reference materials, which means that you can look up a specific concept in them if you forget some of the details (which I often do). You already know about loops and a bit about objects, and you probably know about other control structures like conditionals (if this then that) - these are all parts of the language.

Data Structures

Data structures are ways to store and retrieve information in a program. You'll be familiar with arrays from Java - an ordered list of things accessed by numbers (where they are in the array). Data structures are distinct from language because any data structure that you can imagine (there are a lot of them!) can be implemented (written) in Lua. Lua, the language, provides ways for programmers to make more interesting ones. You'll learn all about tables in the Lua programming book and reference manual - they are an essential ingredient in any script.

There is a chapter in the Programming in Lua book about data structures.

Algorithms

Algorithms are well-defined steps which take some input data and generate some output. You don't need to focus on this specifically, because you will be thinking about algorithms automatically once you get into the flow of programming. How do I choose 5 random players from the players connected to a server? How do I find the nearest zombie to a player? How do I find the top 3 players in a round? Etc.. all these questions are asking how to calculate something based on some data.

Lots of people ask questions on this forum like "How do I clone a monster in front of a player when they click a button?" or "How do I award a player points when a timer runs out?" But these aren't about algorithms, they are about the ROBLOX programming interface - aghem, that is, the actions and data which ROBLOX provide to us.

I mention algorithms as a separate category because often the best programmers are not the ones who know everything about the language, but they can put what they do know together to make efficient and robust algorithms. For example, I can write excellent algorithms for searching lists, sorting lists, generating terrain, and making many games without ever using metatables or closures (advanced features of Lua).

ROBLOX API

API means Application Programming Interface. This means everything that ROBLOX has added as extras to Lua which you can use in your scripts. Most of the ROBLOX wiki is about the ROBLOX API, rather than about Lua itself (though there are some basic tutorials). I think the reason why it seems to go from 0-100 in difficulty is that they don't often explain the language before explaining how ROBLOX fits on top of it.

I know how to make basic loops and change brick properties, but that's about it.

This is a brilliant start. Honestly. You've understood one of the fundamental aspects of the ROBLOX API: properties.

Every ROBLOX object has properties, and you can find all of those properties by looking at the page for an object on the ROBLOX wiki. For example, have a look at Accessory, ParticleEmitter, and Part. Can you see all the properties on each of these? The trick to effectively learning and mastering programming in ROBLOX, once you know the basics of Lua, is to know how to read these API pages. These pages tell you almost everything you would need to know. With the more complicated objects (like Welds, CFrame, and BodyMovers) there are specific tutorials to elaborate on them.

As well as properties, each object has some functions and some events. Functions are actions which the object will do when they are triggered. Events provide a way to detect when special things happen in the ROBLOX game engine. For example, Touched is an event on every Part object which happens whenever something touches that Part. ROBLOX provides a way to connect your own code to these events so that you can make things happen when specific changes happen in the ROBLOX world. Once you understand properties, functions, and events, the whole ROBLOX API is opened up to you.

Summary

I know I've waffled a bit here - long answers aren't very common on this forum. Your heartfelt story struck a chord with me, and this is the best advice I could come up with. As I said in the beginning, being good at scripting doesn't make it easy to explain it to others, and we all learn in different ways. I read programming books when I was younger and that really helped.

Knowing that the language is separate from the ROBLOX API is the key distinction for me. When I know what I want to do, like when I already have an algorithm and a data structure in my head, but I don't know how to do it, then I look in two places: I either look at the Official ROBLOX API or the Lua Reference manual. Together, they answer all my questions about what the language does and what things ROBLOX provides, then the rest (data and algorithms) is up to your own imagination and design!

Wow, I had the same question now I'm gonna use the resources mentioned thx also great explanations.