A portable, data-driven 2D game engine focused on ease of use and powerful features.
Orx is a portable, data-driven 2D game engine designed to simplify game development with a focus on ease of use and powerful features. It provides a comprehensive set of tools for rendering, animation, physics, input, and sound, all driven by a flexible configuration system. The engine solves the problem of rapid iteration and cross-platform deployment by allowing developers to define game logic and assets through data rather than hardcoded logic.
Game developers and hobbyists creating 2D games who value a data-driven workflow and need cross-platform support for Windows, Linux, macOS, Web, Android, and iOS.
Developers choose Orx for its heavily data-driven design, which enables fast iteration with hotloading and config-driven scripting, combined with a rich feature set and permissive zlib license for commercial use.
ORX: Portable Game Engine
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Hotloading of config files and resources enables real-time tweaking without restarting the game, drastically shortening development cycles as highlighted in the README.
Compiles natively for Windows, Linux, macOS, Web, Android, and iOS with abstracted inputs and consistent APIs, ensuring broad deployment options.
Includes hardware-accelerated rendering with MRT, animation chaining graphs, LiquidFun-based physics, and a full sound system with spatialization, covering most 2D game needs.
Zlib license allows free commercial and non-commercial use without royalties or mandatory attribution, making it business-friendly.
Mandatory setup script must be run to download dependencies and generate project files before first compilation, adding complexity and potential for errors.
Smaller user base compared to mainstream engines like Unity or Godot results in fewer tutorials, examples, and community-contributed assets or plugins.
Heavy reliance on configuration files for game logic and behavior can be unintuitive for developers accustomed to code-centric or visual scripting workflows.