[machisuji]

I was always ruling out Unreal as an option due to C++ because I'm no good with C++ and it seems scary.

But in the end I got so frustrated with Unity that we did do the switch to Unreal. So far I actually had to do a lot less coding in Unreal than in Unity. There's almost nothing you can't do in blueprints.

The only thing I had to write C++ for is some JSON parsing because the existing JSON blueprint libraries (from the marketplace) are terribly slow. What little C++ I had to write is fairly simple. Just using core APIs form Unreal itself (FJsonObject). It's just creating structs and calling APIs. Easy enough even for me.

Everything else we implement in Blueprints. No C++ required.

[username90]

How much C++ you need depends on what kind of game you are making. You probably wont make a game like Civilization in blueprints.

[TeMPOraL]

Which Civilization?

I'd say a lot depends on how much stuff you're doing every frame. From what I've seen, Epic is emphasizing you should avoid running blueprints every tick, and instead use event-driven programming heavily (or "steal" ticks from input handling), and then flip appropriate switches to remove anything that doesn't need updating every frame from even being issued a tick by the engine.