When comparing Queen vs Wave, the Slant community recommends Wave for most people. In the question“What are the best 2D game engines?” Wave is ranked 36th while Queen is ranked 41st. The most important reason people chose Wave is:
In addition to online [API documentation](http://waveengine.net/Engine/Documentation), the Wave Engine team provides [tutorials](http://www.indiedb.com/engines/wave-engine/tutorials) via IndieDB, plus [sample projects](https://github.com/WaveEngine/Samples) and "[QuickStarters](https://github.com/WaveEngine/QuickStarters)" via GitHub.
Ranked in these QuestionsQuestion Ranking
Easy to learn, based on Entities and Components, the later being class-like objects that entities inherit.
Has open function binding systems, allowing easy creation of custom components.
Pro Supports coding in C#, F# and Visual Basic
Wave Engine explicitly supports all three core .Net Platform languages.
Pro Oculus Rift support
The Wave Engine team provides an official, open-source Oculus Rift extension via GitHub.
Con No IDE
If you like having some huge GUI akin to Gamemaker, Unreal, Unity, etc, Crafty is not for you.
Con Not many tutorials available
Con Mandatory splash screen
Games and applications made with Wave Engine must display a splash screen advertising it. No splash-free license option is available.
Con Outdated UI
The UI looks like it is from Windows XP days. A refresh is much needed.