Lumberyard has been out for a little over a year and a half, and it has been experiencing steady development since then. Just recently, they published a blog post highlighting where they want the game engine to go. Pretty much none of this information is new if you’ve been following them, but it’s still interesting none-the-less.
From a high level, Amazon has been progressing their fork of CryEngine into more of a component-entity system. The concept is similar to Unity, in that you place objects in the level, then add components to them to give them the data and logic that you require. Currently, these components are mostly done in Lua and C++, but Amazon is working on a visual scripting system, like Blueprints from Unreal Engine 4, called Script Canvas. They technically inherited Flow Graph from Crytek, which I think is still technically in there, but they’ve been telling people to stop using it for a while now. I mean, this blog post explicitly states that they don’t intend to support migrating from Flow Graph to Script Canvas, so it’s a “don’t use it unless you need to ship real soon” sort of thing.
One of Lumberyard’s draws, however, is their license: free, but you can’t use this technology on any cloud hosting provider except AWS. So if you make an offline title, or you use your own servers, then you don’t need to pay Amazon a dime. That said, if you do something like leaderboards, persistent logins, or use cloud-hosted multiplayer, then you will need to do it through AWS, which, honestly, you were probably going to do anyway.
The current version is Lumberyard Beta 1.10. No release date has been set for 1.11, although they usually don’t say a word until it’s published.