UE4 Limitations?

keep it simple, pick your programming language first. Ue4 I do prefere over unity 5. but If I had to code as a first time coder I rather learn C# or JS because you can use both in unity. I do love UE4 But years down the road when I pick up C++ then I dump unity. At the end of the day it all depends on what your making, what Code your using, because blueprints is nice, But being able to write your own code for building a custom character

controller where your character moves in your game the way you want is priceless. Coming from a animation, Rigging back ground I have only one need and thats coding I can do most in a 3D pipeline. Just really strong in animating and rigging. I like Cry engine It’s got the best water and terrain in most engines with the help of world machine lol. But who doesn’t use world machine for there terrains.
And the marketplace, Because of Unity’s Marketplace it saves me alot of time. UE4 needs alot more content. Unity has some junk content there

but there are some real gems that are also on UE4’s marketplace like rifleanim pro.
If your new start off slow, If you have a team that knows UE4 use it. If your solo get Unity 5 personal and check out Marketplace theres a wealth of content. When you get better learn C++ and kill it in UE4. AAA titles better to use UE4 mobile better to use Unity. Other engines get lost in the rest.

Definitely go with blueprints first. Learning a new engine is a big enough task in itself without also having to learn the programming language its written in, and it doesn’t sound like you have a lot of programming experience full stop. Trying to do both in parallel will lead to frustration and eventually demotivation.

Once you have created a few prototypes with blueprints you can then start looking at some code, as you’ll at least have a point of reference rather than just looking at reams of code without knowing what it’s supposed to be doing.

I still recommend learning C++ away from UE4 though, as game engines are extremely complex and it would be like trying to learn basic mechanics by examining the engine of a lamborghini.

I would highly recommend you the Game Engine Architecture book by Jason Gregory - , no matter the engine you decide to go with. It presents a great overview of how the game engines work which you will find useful. Some of the sections, however, require a bit of C++ / Maths which you could skip for now and revisit later.