ecks (pronounced "ex") is a fully data-driven RPG framework created by ReD AKA unauthorizedlogin for Godot Engine.
ecks is a Godot RPG framework focused on turning complex gameplay systems into flexible, data-driven tools. Instead of hard-coding gameplay logic, ecks focuses on creating flexible foundations where quests, dialogue, combat, inventory, progression, and world systems can be authored through data-driven resources.
ecks focuses on reducing the amount of custom code required when building RPGs by providing interconnected systems for quests, dialogue, combat, inventory, progression, localization, and world management.
The framework is developed alongside a full Adventure RPG project, where every system is tested through real gameplay requirements before being expanded into reusable tools.
This repository contains project documentation only. All source code is maintained in a separate private repository and is not publicly available.
ecks is designed to provide developers with a reusable foundation for creating RPGs in Godot.
The goal is to transform common RPG systems into modular, data-driven tools that can be extended, customized, and reused across multiple projects.
Follow the development of ecks and the Adventure RPG project:
-
🎥 YouTube: unauthorizedlogin
-
💬 Discord: ecks Community
-
🎮 itch.io: ecks on itch.io
-
🕹️ gamedev: Game Development
-
💡 Discussions: ecks Discussions
-
🐛 Issues: Bug Reports & Feature Requests
-
🔒 Security Advisories: Private Vulnerability Reporting
Development updates, system breakdowns, and framework progress are shared through regular devlogs and community discussions.
- Status: ecks is currently in active development.
- Stage: pre-alpha
- Version: 0.52.206
- Date: 7/28/2026
- Changelog
- Godot Engine
- GDScript
- Godot Resources
- Data-driven architecture
ecks is built around a creator-first, data-driven architecture designed to separate gameplay systems from the content those systems manage.
The framework follows a simple principle:
Systems define the rules. Data defines the structure. Content defines the experience.
This separation allows creators to expand RPG content without constantly modifying core gameplay code.
ecks separates framework responsibilities into three layers:
- 🏗️ Systems Layer
- 📚 Data Layer
- 🎮 Content Layer
For a detailed breakdown of each Layer & and its role, documentation can be found here:
ecks is designed to support both framework developers and content creators.
A creator is able to define:
- An NPC's role
- A quest's objectives
- Dialogue states
- Rewards
- Item properties
- Progression rules
through data and configuration rather than rewriting gameplay systems.
The framework is built to turn complex RPG development into an organized authoring process while keeping the underlying architecture flexible for expansion.
ecks is designed around Godot's Inspector workflow, giving creators a powerful editor-facing configuration layer without requiring constant script modification.
While gameplay systems are driven through resources, databases, and configurable definitions, framework scenes and components expose their creator-facing options directly through exported Inspector properties.
This includes more than simple visual adjustments. ecks uses the Inspector to configure presentation, behavior, and localized content choices throughout the framework.
Examples include:
- UI fonts, colors, outlines, spacing, alignment, and layout settings
- Menu and panel presentation options
- HUD and display configuration
- Resource and scene references
- Gameplay component properties
- Numeric ranges and limits
- Creator-facing dropdown selections
- Localized label and title options
ecks also provides enum-driven Inspector workflows for common text selections. Instead of requiring creators to manually enter localization keys or modify scripts, predefined options can be selected directly from dropdown menus.
For example, vendor configuration can expose options such as:
- Shop titles
- Inventory section labels
- Buyback labels
- Item information headings
These selections automatically map to the framework's localization pipeline while keeping the Inspector clean and creator-friendly.
Custom override fields are available when a project needs unique wording, allowing creators to use framework defaults while still supporting complete customization.
The result is a workflow where creators can configure and customize the majority of framework systems directly through Godot's editor, while still retaining the ability to extend or replace systems with custom code when desired.
ecks is built with localization as a core framework feature rather than an afterthought.
Every player-facing text field throughout the framework is already wrapped with tr(), including UI, menus, dialogue, quests, objectives, items, events, combat messages, notifications, and gameplay systems. Localization is explicitly authored and does not rely on automatic machine translation at runtime.
The framework includes a production-tested CSV → PO generation pipeline that has been battle-tested throughout development and is designed to scale alongside the project.
Features include:
- Framework-wide
tr()integration for all player-visible text - Data-driven localization pipeline
- Battle-tested CSV → PO generator workflow
- Generator-based translation management
- Over 14,000 unique localization keys
- Translation infrastructure configured for 23 languages.
- Approximately 322,000 translated strings (14,000+ keys × 23 languages)
- At an average of 7 words per string, the framework currently manages over 2.25 million localized words
- Localization-ready resources, menus, systems, and templates
For details on the localization architecture, translation workflow, and CSV → PO generator, see the Localization and PO Generator documentation.
The ecks Framework includes a collection of editor-based creator tools designed to accelerate content production while maintaining framework standards.
These tools extend the Godot editor workflow by allowing developers to create framework-compatible content through dedicated interfaces rather than manually configuring every resource and scene.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
ecks is a modular, data-driven ARPG framework built around reusable gameplay systems rather than one-off implementations.
Every major feature—from entities and combat to quests, world streaming, localization, and creator tooling—is designed to work together through a shared architecture while remaining independently extensible.
This allows creators to build, customize, and scale projects without rewriting core framework systems.
Currently Existing Systems:
The Economy System provides the framework's complete commerce and currency architecture.
It is responsible for managing player wealth, merchant interactions, buying and selling, item distribution, and transaction processing through a collection of specialized managers.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
The Engine Systems layer provides the foundational runtime infrastructure that powers the Ecks Framework.
The engine layer provides the foundation that all gameplay systems build upon.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
The Entity Systems layer provides the framework foundation for all gameplay entities within ecks.
This layer contains the systems responsible for defining, controlling, and modifying any entity that exists in the game world.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
- ⚡ Ability System
- 🐾 Behaviors
- 🧍 Actor Controllers
- 🧬 Class System
- ⚔️ Combat System
- 🎚️ Difficulty System
- ✨ Effect System
- 👤 NPC System
- 📊 Stats System
- 📈 XP System
The Launch Flow System provides the complete startup pipeline responsible for transitioning the framework from application launch into an active gameplay session.
The Launch Flow separates application startup from gameplay execution, ensuring all required systems are prepared before the player enters the world.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
The Loot System provides the centralized item framework responsible for item definitions, ownership, storage, equipment handling, and world-based loot interactions.
The Loot System does not rely on a single universal inventory pipeline. Instead, item categories are handled through dedicated managers responsible for their own routing, behavior, and serialization.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
The Progression System provides the framework responsible for player progression through dialogue, quests, and narrative-driven gameplay.
Dialogue and quests remain independent systems while integrating through shared runtime managers and data resources.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
The UI System provides the centralized framework responsible for managing the game's user interface, coordinating menu interactions, HUD visibility, and communication between gameplay systems and the player.
At the center of the system is the UI Manager, which acts as the global authority for UI registration, menu lifecycle management, input routing, and player movement locking while interfaces are active.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
- 🎬 Credits Scene
- 📋 Event Viewer
- 💀 Game Over
- ⏸️ Pause Menu
- ⚙️ Settings Menu
- 📊 Stats Menu
- 🖥️ UI Manager
The World Systems framework provides the foundation for managing world loading, map structure, environmental presentation, interactive objects, and player navigation.
World systems are responsible for managing the game world state while remaining independent from gameplay systems such as quests, combat, and progression.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
- 🔊 Audio System
- 🧩 Chunk Loader
- 🗺️ Chunk Manager
- 💥 Destroyables
- 🌿 Environment System
- 🗺️ Maps
The Database Framework provides centralized runtime access to dialogue resources through the engine's standard database architecture.
This architecture provides fast, scalable resource access while maintaining a creator-friendly workflow.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
- ⚡ Ability Database
- 🧬 Class Database
- 💬 Dialogue Database
- ⚖️ Difficulty Database
- ✨ Effect Database
- 📦 Item Database
- 🗺️ Map Database
- 📜 Quest Database
- 🧮 Stat Formula Database
The Generator System provides a data-driven content creation pipeline for converting structured creator data into runtime-ready engine resources.
The framework uses generators to create content without requiring manual resource creation or direct code modification.
For an overview of the system check out the README:
Or, if you'd prefer a specific topic you can access them directly here:
- ⚡ Ability Generator
- 🧬 Class Generator
- 🏷️ Class Rules Generator
- 🎬 Credits Generator
- 💬 Dialogue Generators
- ⚖️ Difficulty Generators
- ✨ Effect Generator
- 📦 Item Generator
- 🗺️ Map Generator
- 👤 NPC Generator
- 🌐 .po Generator
- 📜 Quest Generator
- 🧮 Stat Formula Generator
- 📈 XP Generator
The ecks RPG Framework is developed by UnauthorizedLogin.
This repository is the official home of the framework and its public documentation.
Because search engines often associate similar RPG projects, creators, and discussions together, the following clarifications are provided to avoid confusion.
ecks is not associated or affiliated with:
- Godot RPG Framework by Grandro
- RPG in a Box
- Godot A-RPG or its associated repositories.
- ORK Framework.
- Godot open RPG by GDQuest or projects maintained by newold3.
- Skelerealms by SlashScreen.
- Community forks, template repositories, or unrelated GitHub projects using similar RPG terminology.
- Reddit posts, community discussions, or third-party examples. UnauthorizedLogin does not maintain an active Reddit presence, and Reddit content should not be considered an official source of information about Ecks.
- Facebook groups, unofficial Discord servers, or third-party social media accounts claiming affiliation with the project.
- Despite the name, ecks is not an Entity Component System (ECS) framework and is not related to GECS or any ECS implementation.
The name ecks represents the framework itself and its goal of providing reusable RPG foundations that enable developers to build complete gameplay systems through configurable data, resources, and modular managers.
Official Sources:
For accurate information about the framework, use only official ecks resources, including:
This GitHub repository Official documentation published with the project Content published by UnauthorizedLogin
Anything outside of those sources should be treated as unofficial unless explicitly linked from the project.