Haven Game Engine List 
This is a list of game engines, and whether or not they are “compatible” with Haven, and the reasons for incompatibility.
To put it short, typically the main reason for a game engine not being supported is either due to it lacking support to export to a browser, or the fact that it does not store projects as usable files on a computer and lacks suitable support for Git Version Control.
If your game engine is not on this list, that does not directly mean it is not supported. (If the site is missing any game engine, please submit an Issue or Pull Request to the site’s repository on GitHub: https://github.com/sometgirldotonline/haven-ge-list/)
How to know if your game engine is supported
- Saves on your computer: It saves the project files directly to your computer's hard drive.
- Uses a Git-compatible project format: Your project can be reasonably stored and versioned using Git. Projects do not necessarily need separate files for every asset; text-based single-file projects can still be compatible.
- Plays in a browser: It lets you export your game to run on a website (look for options like "Web", "HTML5", "WebGL", or "WASM").
A note on Block based game engines (IE: Scratch, MakeCode Blocks, etc)
Any game engines that use blocks for code are explicitly banned by Haven. This is not negotiable.
If the game engine can be written in text-based code, the text mode may be used. For example you are permitted to use Gamemaker's GML Script but not GML Visual mode.
| Game Engine / Tool | Web Export | Git Compatibility |
|---|---|---|
| Godot | Web Export Supported |
Yes Uses a Git-friendly project structure with text-based project and scene files. |
| Unity | Web Export Supported |
Yes Supports text-based project serialization, allowing project files to be tracked with Git. |
| Unreal Engine (5+) |
No Web Export
Note 📝Built-in HTML5 export was removed from Unreal Engine. Third-party/community solutions exist, but there is no official built-in web target. |
Yes Project files can be tracked using Git and Unreal provides source-control support. |
| GameMaker | Web Export Supported |
Yes Uses a Git-compatible project structure and supports source control workflows. |
| GDevelop | Web Export Supported |
Yes Projects can be stored locally as files and tracked using Git. |
| Defold | Web Export Supported |
Yes Uses text-based project and game files designed to work well with version control. |
| Ren'Py | Web Export Supported |
Yes Uses standard text files for scripts and project data, making Git version control straightforward. |
| RPG Maker (MV / MZ) | Web Export Supported |
No Although many project files use text-based formats, important project data is stored in large database files that are not practical for the Git workflow required by Haven. |
| RPG Maker (VX Ace / XP / older) | No Web Export |
No Uses proprietary project and data formats that are not practical for the Git workflow required by Haven. |
| CryEngine | No Web Export |
Yes Project and source files can be stored and tracked using Git. Large binary assets may require additional Git storage considerations. |
| Flax Engine | Web Export Supported |
Yes Project, scene, and script files can be stored and tracked using Git. |
| Stride Engine | No Web Export |
Yes Uses a standard project folder structure with project and source files that can be tracked using Git. |
| PICO-8 | Web Export Supported |
Yes PICO-8 cartridges can be saved as text-based .p8 files. Although code, graphics, maps, and music are created within PICO-8, the resulting source file can be meaningfully tracked with Git.
|
| Twine | Web Export Supported |
Yes Twine projects can be stored in text-based formats such as Twee, allowing them to be tracked using Git. |
| Bitsy | Web Export Supported |
Yes Bitsy game data can be stored as text and tracked using Git, even though the game is authored within the Bitsy editor. |
| Phaser | Web Export Supported |
Yes Uses standard web development files and folder structures that work naturally with Git. |
| PlayCanvas | Web Export Supported |
Yes Supports version control workflows and provides tools for working with project files outside of the online editor. |
| Babylon.js / Three.js | Web Export Supported |
Yes Uses standard web development files and folder structures that can be tracked using Git. |
| TIC-80 | Web Export Supported |
Yes Supports text-based cartridge files that can be stored and tracked using Git. |
| PuzzleScript | Web Export Supported |
Yes Games are represented as plain-text PuzzleScript source files, making them straightforward to track with Git. |
| ct.js | Web Export Supported |
Yes Projects are stored locally in a folder structure that can be tracked using Git. |
| LÖVE (Love2D) |
Web Export Supported
Note 📝Requires using a web port such as love.js to run LÖVE games in a browser. |
Yes Uses normal source code and asset files that can be stored and tracked with Git. |
| libGDX | Web Export Supported |
Yes Uses a standard source-code and asset folder structure suitable for Git. |
| Bevy Engine | Web Export Supported |
Yes Uses a standard Rust/Cargo project structure that works naturally with Git. |
| PixiJS | Web Export Supported |
Yes Uses standard JavaScript/TypeScript project files and folder structures. |
| DragonRuby GTK | Web Export Supported |
Yes Uses source files and project assets that can be tracked using Git. |
| AGS (Adventure Game Studio) |
Web Export Supported
Note 📝Requires using the WebAGS community port to export for web browsers. |
Yes Project and source files can be stored and tracked using Git. Binary art and sound assets can also be tracked, although they cannot be meaningfully merged. |
| TyranoBuilder | Web Export Supported |
Yes Projects are stored locally and contain source and project files that can be tracked using Git. |
| Cocos Creator | Web Export Supported |
Yes Uses a standard local project folder structure designed to work with version control systems. |
| Macroquad / Raylib | Web Export Supported |
Yes Code-based projects use standard source files and assets that can be tracked directly with Git. |
| Narrat | Web Export Supported |
Yes Uses standard source, configuration, and asset files that can be tracked using Git. |
| Clickteam Fusion 2.5 |
Web Export Supported
Note 📝Requires the separate HTML5 Exporter. |
No Uses a proprietary project format that is not practical for the Git workflow required by Haven. |
| Excalibur.js | Web Export Supported |
Yes Uses standard JavaScript/TypeScript source files and web assets that can be tracked using Git. |
| bipsi / binksi | Web Export Supported |
Yes Project data can be represented as text and stored in Git, even though the game is authored within the editor. |