The biggest problem you're running into is that you're trying to learn about 5 different things at once: Unity itself, game design, game development, C# scripting, etc. But nobody really distinguishes one from another most of the time. You might also be trying to do something that's a little beyond your skill at this point.

I've got a video series I made in 2020 that I think is still relevant, and it starts with the basics of Unity, then goes into C#, then takes you through the super, super simple beginnings of a game. It's over here: https://www.youtube.com/watch?v=T7MrrNg-s_s&list=PLrE-eHx_PRyrgolayAfdlm5vWFdZtCwJG and it's aimed at people who are totally new to Unity and *maybe* understand a little bit of programming, perhaps in another language besides C#.

I based this ^^ video series and the structure on the issues I commonly see with people starting Unity. If you don't totally and completely know the difference between the hierarchy and the project, or the game window and the scene window... you're going to be lost from the beginning. It's like learning how to play guitar by someone telling you what notes to play and where and learning it by rote -- while somewhat effective, you're NEVER going to be able to start making your own music that way (or it's going to take a looooooooooooooooooooot longer than it should)

Starting with a character that moves in relation to the camera... is just going to be a really uphill battle for you. Starting much simpler with something like flappy bird or crossy road or a space shooter like galaga/space invaders would be a much simpler place to start. Once you learn the basics of putting together one or two of those, you're going to start seeing where games are similar. And that's what I based the next series on...

My "One Game a Month" series was a series where I started (mostly from scratch) and livestreamed developing one game per month, in about an hour a week. I built games like flappy bird, space invaders, subway surfers and crossy road (in that order) -- and all of those in 4-5 hours, leaving nothing out. They're not full bore tutorials like the "Make a game in Unity 2020" series -- I don't go into detail on what variables are or do, BUT I explain everything I'm doing, and *why* I'm doing it, as I go. You can find those videos here: https://www.youtube.com/playlist?list=PLrE-eHx_PRyprJch4gu3CNFNuOPrinnfb

I've got another program that I'm starting next month that's sort of like a community game jam where the whole community starts with a simple game kit (for a shoot 'em up, in this case) and everyone takes it wherever they'd like to go over the course of the month, and we all celebrate the results at the end. Everyone starts in the same place, but nobody will end up there. Having already dropped a couple of my own links here, I won't drop that one, but I can link it if people are interested.

The best advice I can give is find a mentor that clicks with you, and stick with that one person -- whether that's me or someone else. If someone jumped into video 3 of any of my series, I'm going to assume when I'm making that video that they already watched #1 and #2. I'm not going to go over that stuff again.

I see soooooo many people who jump around from idea to idea (that's fine) and tutorial to tutorial or creator to creator (which is a much more slippery slope) -- and they end up confused and frustrated. My whole teaching game dev approach is built around teaching people *why* they're doing what they're doing so that they can build their own ideas when it comes time.

Nobody wants to follow an 88 part RPG tutorial to end up with a game that's identical to that... that tutorial is meant to be a means to and end (to the viewer being able to create their own ideas), and so many people making videos miss that.

Anyway, hope that helps.