Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWave vs LITIENGINE
When comparing Wave vs LITIENGINE, the Slant community recommends Wave for most people. In the question“What are the best 2D game engines?” Wave is ranked 33rd while LITIENGINE is ranked 87th. 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.
Specs
Question Ranking
Pros
Pro Extensive learning material
In addition to online API documentation, the Wave Engine team provides tutorials via IndieDB, plus sample projects and "QuickStarters" via GitHub.
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.
Pro Many components are open source
Several core components and official extensions of the Wave Engine are publicly hosted on GitHub.
Pro Easy to use
Clean and well-designed API that is easily discoverable. Comes with a simple tool (utiLITI) for editing levels based on .tmx maps.
Pro Free an open-source
The engine is published under the MIT license and is entirely free to use.
Pro they are developing a beta for mac and linux
Pro Active and helpful community
Has an active forum and discord channel to discuss topics about the engine.
Cons
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 Not many tutorials available
Con Outdated UI
The UI looks like it is from Windows XP days. A refresh is much needed.
Con Limited to Desktop
Games made with the engine only run on Windows, Linux and MacOS. There is no support for Android or HTML, yet.
