# Flare Engine: A GPL-Licensed 2D Action RPG Engine for Indie Game Development

> Flare (Free Libre Action Roleplaying Engine) is a C++ game engine built specifically for single-player 2D action RPGs. It uses INI-style config files for game data, supports Tiled for map creation, and separates engine code from game content, with the official Flare game living in a separate repository. The engine and its default mod are released under GPL-3.0.

**flareteam/flare-engine** — Free/Libre Action Roleplaying Engine (engine only). Flare Flare (Free Libre Action Roleplaying Engine) is a simple game engine built to handle a very specific kind of game: single-player 2D action RPGs.

- Repository: https://github.com/flareteam/flare-engine
- Website: http://flarerpg.org/
- Stars: 1,299 · Forks: 231
- Language: C++
- License: GPL-3.0
- Published: 2026-08-08 · Updated: 2026-08-18 · Language: en
- Canonical page: https://hysenlabs.com/projects/flareteam-flare-engine

## What Flare Is and What It Is Not

The Flare README is direct about the engine's scope: it is built to handle a very specific kind of game, the single-player 2D action RPG. It is not an abstract, general-purpose game engine. The design philosophy, stated in the README, is to build several real games and harvest an engine from the common, reusable code. The result is an engine that does one genre well rather than offering broad genre support at the cost of added complexity.

Flare is not a reimplementation of any existing engine or game. The README describes it as a tribute to and exploration of the action RPG genre. The official Flare game, the Empyrean Campaign, was originally part of the engine repository but was moved to the separate flare-game repository around September 2012. This separation means the engine repository contains only the runtime; all game content lives elsewhere.

The engine is written in C++ and is purely a runtime. It does not include a visual editor for game logic or item data; those are handled by editing INI-style config files directly. For map creation, Flare supports the Tiled map editor through the Flare Tiled Tools plugin, which is hosted at a separate repository.

## How the Engine Is Structured: Mods, Config Files, and the Runtime

Flare uses a mod system to organize game content. Game data, including maps, items, enemies, and configuration, lives in mod directories. The engine loads mods at runtime, and the README notes that there is a mods directory in the user data location that can override system-wide mods. This layering means a mod can replace individual files from the base game without copying the entire content set.

All game data is in INI-style config files with open formats. Images use PNG and audio uses OGG. The README states a preference for open formats explicitly. This makes game data human-readable and editable with a text editor, which lowers the barrier to content creation but means there is no graphical content editor included with the engine.

The engine binary accepts command-line flags for common operations. Selected flags from the README include:

```bash
flare --data-path /path/to/game/data
flare --renderer sdl
flare --no-audio
```

The --renderer flag selects between sdl_hardware (the default, using GPU acceleration) and sdl (a software renderer). The --mods flag starts the engine with only specified mods enabled. The --load-slot flag loads a save slot by index without showing the menu. The --debug-event flag enables verbose hardware input logging, which is useful when diagnosing controller or input issues. The --safe-video flag launches with minimum video settings and is useful as a recovery option when a settings change causes display problems at startup.

Settings files are written on first run and are stored in platform-specific locations. On Linux and macOS the default is $XDG_CONFIG_HOME/flare/ or $HOME/.config/flare/. On Windows, settings go to %APPDATA%\flare\config\. The engine also supports a portable mode by running with --portable or by placing a portable.ini file next to the binary.

## Building and Running Flare from Source

Flare uses SDL2 as its primary dependency, plus SDL2_image, SDL2_mixer, and SDL2_ttf. The build system is CMake. The README directs readers to INSTALL.engine.md in the repository for the full build instructions.

On Linux, the engine is also available via Ubuntu PPA and Fedora RPM packages, which handle dependencies through the system package manager. On macOS, the engine can be built from source or obtained via the distribution files in the repository's distribution folder. An Android project lives in flare-android-project and an iOS project in flare-ios-project, indicating that mobile targets are supported, though the README does not document the mobile build process in the main README.

The engine homepage at flarerpg.org lists additional distribution options and links to the community forum. The F-Droid badge in the README confirms that a Flare package is available on F-Droid for Android, making the engine accessible on mobile without requiring a custom build.

For developers who want to build the engine without game data, the engine repository includes a default mod in the mods folder that contains engine translations. The official Empyrean Campaign game data must be obtained from the flare-game repository separately.

## Translation Coverage and Localization

The Flare engine ships with translation support for more than thirty languages. The README lists current completion percentages for each language. As of the repository's current state:

- Chinese (zh) and German (de) and Russian (ru) are at 100%
- Portuguese (Brazil) (pt_BR) is at 96%
- Finnish (fi) and Gaelic (Scottish) (gd) are at 90% and 88% respectively
- Spanish (es), Swedish (sv), Italian (it), Korean (ko), and Indonesian (id) are between 87% and 88%
- Norwegian Bokmål (nb) is at 83%
- French (fr), Belarusian (be), and Ukrainian (uk) are in the range of 70% to 76%
- Turkish (tr) and Basque (eu) are at 0%

Translations cover engine strings, not game-specific content. The game content in flare-game has its own translation status separate from the engine. The translation system uses Tiled format or similar INI strings, and contributions to incomplete languages go through the project's Transifex configuration, which is referenced in the .tx/ folder in the repository.

## Flare vs. Godot for a 2D Action RPG

The most relevant comparison for a developer choosing between Flare and another engine for a 2D action RPG is Godot. Godot is a general-purpose 2D and 3D game engine with a visual editor, a scripting language (GDScript), and the MIT license. Godot supports action RPG mechanics but requires building those systems yourself or using community plugins, because it is a general engine rather than one designed around that genre.

Flare's advantage over Godot for this specific genre is that the core architecture, including the mod system, INI-based item and enemy data, and the isometric map support, is built in and reflects years of decisions made for this exact kind of game. A developer who wants isometric 2D combat with a Diablo-style inventory system gets a running reference implementation in flare-game rather than starting from scratch.

Flare's disadvantage is the GPL-3.0 license. Godot uses the MIT license, which means modifications to the engine can be kept private in commercial projects. With Flare, any distributed binary that includes modified engine code must make those modifications available under GPL-3.0. For an indie developer releasing a free game, this is not a problem. For a commercial developer, it may be.

Flare also does not have a visual editor for game content; all item, enemy, and quest data is authored in text files. Godot's editor is a substantial advantage for teams that prefer visual workflows or want to onboard non-programmer contributors.

## Mods, Community Games, and the Ecosystem

The Flare community has produced additional games and mods beyond the official Empyrean Campaign. The README points to a Mods page on the flarerpg.org website for the community collection. The mod system makes it practical to create a new game by layering new content over the engine's base mod.

The engine's save file location on Linux and macOS is $XDG_DATA_HOME/flare/ or $HOME/.local/share/flare/. The engine saves automatically on exit when file permissions allow. The user data mods directory in the save location can be used to override system mods, which means a user can install personal mod overrides without affecting the system-wide installation.

The repository's RELEASE_NOTES.txt tracks version history. The last push to the repository was on 2026-09-24, four days before the review date. The project uses GitHub Actions for CI, with the workflow file at .github/workflows/. The GPL-3.0 engine source and the CC-BY-SA 3.0 default mod content are covered by separate licenses; the default mod content uses a Creative Commons license rather than GPL, with the Liberation Sans font under the SIL Open Font License 1.1.

## Conclusion

Flare suits indie developers who want to build a 2D action RPG in the mold of Diablo-style games and are comfortable with C++ and INI-based data editing. The GPL-3.0 license means any binary distribution of a modified engine must provide source code under the same license, which is a genuine constraint for commercial developers who want to keep engine modifications private. Developers looking for a broader genre scope, a visual editor, or a commercial-friendly license should look at alternatives like Godot. The engine has no GitHub releases; the last push was on 2026-09-24, and the project tracks development in RELEASE_NOTES.txt.

## FAQ

### How does Flare Engine compare to Corgi Engine for a 2D action RPG?

Flare Engine is a free, open-source C++ runtime specifically designed for the action RPG genre, with INI-based content authoring and a mod system. Corgi Engine is a Unity-based platformer and 2D game engine sold on the Unity Asset Store, targeting a different genre and requiring a Unity license. For a Diablo-style isometric action RPG with free tooling and GPL-compatible content, Flare is the purpose-built option.

### What license does Flare Engine use?

The engine source code is GPL-3.0, with later versions permitted. The default mod, which includes engine translations, is dual-licensed under GPL-3.0 and CC-BY-SA 3.0. Any binary distribution of modified engine code requires releasing those modifications under GPL-3.0.

### Does Flare Engine include a visual editor for game content?

No. Game data including items, enemies, and quests is authored as INI-style config files in text editors. For map creation, Flare supports the Tiled map editor through the Flare Tiled Tools plugin hosted in a separate repository.

## Sources

- [Official documentation](http://flarerpg.org/)
- [Official README](https://github.com/flareteam/flare-engine#readme)
- [Project repository](https://github.com/flareteam/flare-engine)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/flareteam-flare-engine