# FlatRedBall: a C# 2D engine with an editor built around designer productivity > FlatRedBall is a .NET 2D game engine whose selling point is not the runtime but the workflow. A visual editor, a content pipeline, and a code generation step sit on top of a runtime that has been refined for over two decades, and the same project can be launched from the editor or straight from Visual Studio. **vchelaru/FlatRedBall** — Cross-platform 2D game engine focused on ultimate productivity built in .NET - Repository: https://github.com/vchelaru/FlatRedBall - Website: http://flatredball.com - Stars: 580 · Forks: 73 - Language: C# - License: MIT - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/vchelaru-flatredball ## The engine's pitch is productivity, not rendering tricks The FlatRedBall Game Engine is designed to boost your productivity as a game developer, with a particular focus on building 2D games of any genre, and it provides a powerful editor to help you organize your projects. At runtime, the engine provides efficiency, stability, and features which have been refined for over two decades. That last phrase is the one to weigh. The engine descends from the XNA era, which the repository topics confirm with tags for xna, nes, snes, monogame, and dotnet, and that history shows in the shape of the product. What is being sold is a workflow in which content is authored in an editor, exported, and turned into C# that the developer then treats as ordinary code, rather than a runtime that does something a competitor's runtime cannot. The audience is a 2D game developer who is tired of wiring content by hand. ## It is plain .NET, so you can launch from the editor or from Visual Studio The FlatRedBall Engine utilizes the C# programming language, operating on the full version of .NET for uncompromised access to modern language features and all NuGet packages. That is a concrete architectural statement, not a slogan. Because the output is ordinary .NET, games can be launched via the FlatRedBall Editor or directly from Visual Studio, or any other IDE, which keeps the development loop short. The practical consequence is that there is no special runtime to install on a build machine, no separate scripting environment to learn, and no wall between the designer and the programmer. A programmer who prefers to live in an IDE is not exiled from the editor, and a designer working in the editor produces artefacts the programmer can read as source. The default branch is `NetStandard`, which tells you where the modern work is happening, and the repository root carries a `CLAUDE.md` alongside the usual project files. ## The editor, the content pipeline, and generated code are the product Based on the repository layout, the engine is split into a set of distinct pieces. `Engines/` holds the platform specific engine code, `FlatRedBall/` holds the core runtime, `FRBDK/` is the development kit, `Content/` is the content pipeline, `Tiled/` is a Tiled map importer, `Templates/` holds project templates, and `Samples/` holds the example projects. `Tests/` and `scripts/` are there for the obvious reasons, and `FullClean.ps1` is a housekeeping script. The `Samples` directory is the part worth studying, because it shows the shape of a real project. There is `Beefball`, the flagship sample, plus variants of it named `BeefballCodeOnly`, `BeefballKni`, and `BeefballWeb`, which tells you that the same project can be emitted as code only, with a different UI framework, or for the web. Other samples include `ChickenClicker`, `Platformer`, `Overworld`, `SimCity`, `FinalFantasy2`, `EditorTest1`, `FormsSampleProject`, `SkiaSampleProject`, `MonoGameExtendedParticles`, `AotAudioTest`, and a `StandardTileset.tsx` with a matching icon sheet, which shows that Tiled maps and tilesets are first class in the content pipeline. ## Downloads come as a daily build or from source The README points to the download documentation for both prebuilt and source builds, at the flatredball.com download pages and the docs site. It also gives a direct link to the FlatRedBall Editor itself, a zip under the DailyBuild path of the FRBDK templates: ```bash Direct link to FlatRedBall Editor: https://files.flatredball.com/content/FrbXnaTemplates/DailyBuild/FRBDK.zip ``` The release list shows how this project ships, and the pattern is unusual. Alongside dated releases such as `Release_August_10_2026` and `Release_August_07_2026` from August 2026, there is a `glue-daily` tag, a Glue Daily Build from 2026-10-14 published on 2026-10-16. A daily build tag alongside monthly release tags tells you that development is continuous and the project prefers to let you take the newest state rather than wait for a curated release. The README backs the claim, saying commits are being made almost daily and pointing to the commit history so you can check the activity yourself. The licence is MIT, with the LICENSE file at the root. ## Maturity here is a claim about runtime, not about the editor The README says FlatRedBall is mature and continually improving, and that reported issues are resolved or commented soon after they are created, and that the maintainers actively watch pull requests and keep them from piling up. Those are the right things for a project to say about itself, and the parts you can verify are the release cadence and the issue tracker, both of which the repository shows. The commercial record is the strongest evidence in the README, because the project lists the games built with it. The Incredible Baron, Cranky Chibi Cthulhu, Battlecrypt Bombers, WeeRPG, Deadvivors, Super Refresh Men on iOS and Android, Masteroid, KosmoSquad, King Randall's Party, A.R.E.S.: Extinction Agenda EX, and Fusion: Sentient for Windows Phone 7, which is a nice illustration of how far back the engine's reach goes. Dozens of commercial games is a real number of production hours on the runtime, and it is also a constraint: the editor and pipeline are shaped by the needs of the games that were shipped. ## Where FlatRedBall is the wrong choice The 2D focus is the obvious limit and the README is upfront that the focus is building 2D games of any genre. If you need 3D, this is not the engine, and the topic tags confirm the orientation with 2d-game-engine and pixel-art. The second limit is ecosystem. FlatRedBall is a self-contained engine with its own editor, its own content pipeline, and its own project structure, and the sample projects show how much of a project is engine-specific, from the generated code to the Tiled import setup. A studio whose members already know Unity or Godot will be learning a workflow rather than gaining one. The third is the daily build cadence as a stability trade-off. Taking the newest build means taking the newest bugs, and while the maintainers say issues are picked up quickly, the team behind it is a small group, which is the profile of most engines of this kind. ## Conclusion FlatRedBall fits a solo developer or small studio making 2D games who wants designers editing content in a visual editor while the code stays in plain C#, and who wants a pipeline that outputs real .NET projects rather than a proprietary runtime. It is the wrong choice for a team that needs 3D, a console-first workflow, or an engine with a large ecosystem of third party plugins. Before you commit, install the editor and open one of the Samples projects, since the editor workflow is the product and the code samples are the only honest way to judge it, and check the NetStandard branch, which is where the work is happening rather than on master. ## FAQ ### What is FlatRedBall and what language is it built in? It is a cross-platform 2D game engine focused on developer productivity, using the C# programming language and operating on the full version of .NET for access to modern language features and all NuGet packages. The repository describes it as refined over two decades, descending from the XNA era. ### How do I install the FlatRedBall editor? The README points to the download documentation for both prebuilt and source builds, and gives a direct link to the editor zip under the DailyBuild path of the FRBDK templates. The project also publishes a Glue daily build alongside its dated release tags. ### Can I run a FlatRedBall game from Visual Studio? Yes. The README states that games can be launched via the FlatRedBall Editor or directly from Visual Studio, or any other IDE, because the engine operates on the full version of .NET and generates ordinary C#. ### What is included in the FlatRedBall repository? The repository has an `Engines/` directory for platform specific engine code, `FlatRedBall/` for the core runtime, `FRBDK/` for the development kit, `Content/` for the content pipeline, `Tiled/` for Tiled map import, `Templates/` for project templates, and `Samples/` with example projects including Beefball and its code only, KNI, and web variants, plus Platformer, Overworld, SimCity, and ChickenClicker. ### Is FlatRedBall still being worked on? The README says commits are being made almost daily and points to the commit history so you can check the activity yourself. The release list includes dated releases from August 2026 and a Glue daily build tagged on 2026-10-14, and the last push was on 2026-10-18. The default branch is `NetStandard`. ## Sources - [License: MIT](https://github.com/vchelaru/FlatRedBall/blob/NetStandard/LICENSE) - [Project website](http://flatredball.com) - [README](https://github.com/vchelaru/FlatRedBall/blob/NetStandard/README.md) - [Releases](https://github.com/vchelaru/FlatRedBall/releases) - [vchelaru/FlatRedBall on GitHub](https://github.com/vchelaru/FlatRedBall) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/vchelaru-flatredball