Hi lineupthesky, welcome to the fun house.
I want to answer your question in two different ways, so forgive me if the first part sounds a little preachy.
Although I started with C++ (it was the only language taught at the school I first programmed at, when I first programmed) I would never recommend it for a beginner. The problem with C++ is, at a very basic level, there are a whole lot of gotchas that the uninitiated will find themselves stumbling into. Things like memory management can also be a pain if you’re not familiar with it. With that being said I would also never say C++ isn’t worth learning. It’s a very dominant language in many industries (I think most people would agree it is definitely the dominant language in gaming, and has been for quite a while and thus probably will be for a while.) But don’t rush yourself, if you wait until you master C++ before you really start working on your game, well, it’s gonna be a while.
So my second answer to your question is, you don’t need to learn C++ at all. Don’t undersell Blueprints, it is very powerful and there are already a lot of tutorials. Check out the blueprint subforum, some of the really interesting threads like Edge Grabbing or some of the Map Generation threads. Blueprints is powerful, and if you have a basic understanding of most programming concepts - blueprints should be second nature for you, regardless of what language you’re coming from. If you ever run into something you can’t do in Blueprints, you can solve that problem in C++ without having to have your whole project in it. In fact, personally my workflow right now is basically prototyping the idea in blueprints, if I think it’s going to be a performance problem I might move it to C++, but honestly I haven’t run into that yet. I’ve been employed as a developer (a C++ developer coincidentally) for the majority of my professional life, and yet currently 100% of my project is blueprints. It’s that effective and easy.
So to sum it up and combine the two, I say disconnect the two goals (making a game and learning C++.) You can work on your game in Blueprints all day long, and when you take breaks or want to relax you can run through C++ tutorials or elearning at your own pace and completely separate of your work on your game(s). A lot of concepts in gaming (like 3d math, and working with things like directx) are a pain in the butt if you know what you’re doing, they’re not really conducive in my opinion to learning a language. You will do much better (again, obviously this is my opinion) if you don’t try to apply those things until after you already understand the language. Basically don’t try to learn too many things at once, you’ll move too fast and end up confusing yourself and getting bogged down or disappointed.
Finally, this is the best community for a game engine I’ve been a part of. It rivals Ogre3D back in the day, I like it more than Unity’s community, or CryEngines. You have so many resources available to you, the Epic tutorials, other tutorials by users in this forum (look around, again for example the blueprint section, or rendering or content - people post ‘tutorials’ of how they figured something out basically every day), the wiki, the UE AnswerHub. The community here is great, everyone wants to help you and everyone wants you to succeed. If this is what you want to do, you’ve already surrounded yourself with people who want you to achieve your goals too, it’s a healthy place to learn and move forward. Start today, if you get stuck ask for help - I could practically guarantee you someone will help, one of your peers here, one of the Epic devs - someone. The support here is unmatched in my experience.
Best of luck!