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.

Thanks for the feedback. That's a good point.

I'm one of the core developers. I think we improved a lot in this release. No more textile but instead Markdown with a WYSIWYG editor for instance.

I'd love to live in a city like this. I spent a couple of days in Dublin and it was just crazy how loud, crowded and congested with cars and buses the city is. Was not really pleasant walking through the city.

I'm the other dev AMA