> They didn't really build their own engine, they bought a re-licensable license to CryEngine, rebranded it to Lumberyard, and started their engine work from th

> They didn't really build their own engine, they bought a re-licensable license to CryEngine, rebranded it to Lumberyard, and started their engine work from that. If you start to dig in (source-code is one available source) What actually is clearly the story is they started building a game engine, some higher-up bought a license to CryEngine and told them "Here! Use this!" Then they packaged that up as a module in the Engine they started building initially, and spent the next 5 years slowly deleting bits of CryEngine and replacing it with the engine they wanted to build in the first place. Not that that's much better, but I think it clearly speaks to the politics at play in the environment. edit: To add links to the code: ly framework, clearly core engine systems unrelated to cryengine: https://github.com/aws/lumberyard/tree/6b8dd98ad0e59b1817a79f6aaf5b89afb41b1086/dev/Code/Framework https://github.com/aws/lumberyard/tree/6b8dd98ad0e59b1817a79... Gems, the non crytek plugin system: https://github.com/aws/lumberyard/tree/6b8dd98ad0e59b1817a79f6aaf5b89afb41b1086/dev/Gems https://github.com/aws/lumberyard/tree/6b8dd98ad0e59b1817a79... A big dump of cryengine: https://github.com/aws/lumberyard/tree/6b8dd98ad0e59b1817a79f6aaf5b89afb41b1086/dev/Code/CryEngine https://github.com/aws/lumberyard/tree/6b8dd98ad0e59b1817a79... Which we can see has been dramatically shrunken in the time since the initial commit: https://github.com/aws/lumberyard/tree/master/dev/Code/CryEngine https://github.com/aws/lumberyard/tree/master/dev/Code/CryEn...