gdquest-demos/godot-open-rpg

Learn to create turn-based combat with this Open Source RPG demo ⚔

View on GitHub ↗Jump to charts ↓Open shareable report →

gdquest-demos/godot-open-rpg has 3k+ stars and 350+ forks on GitHub, is written in GDScript, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 48 minutes ago
Added to GitGenius on October 5th, 2026
Created on October 20th, 2018
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 368
Total Stargazers: 3,013 (+0)
Total Subscribers: 62 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 days
Mean response time: 25.4 days
90th percentile: 101.7 days
Tracked items: 11

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 451 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 2
Events in 7 days: 3

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Godot Open RPG is a demo project that teaches how to create a turn-based RPG in Godot 4.

The project addresses the challenge of structuring code for a 2D RPG by providing a concrete, educational example rather than a framework. It demonstrates how to build turn-based combat, inventory systems, character progression, grid-based movement, dialogues, map transitions, and multi-menu user interfaces. The codebase prioritizes modern GDScript 4 practices and accessibility for developers with solid programming foundations, following established GDScript guidelines.

This project suits developers learning RPG architecture in Godot who want a reference implementation they can study and adapt. It is explicitly positioned as a teaching resource rather than a reusable framework, making it most valuable for those seeking to understand design patterns and code organization rather than a plug-and-play solution. The project is a work-in-progress and requires a specific engine version to open.

The project maintains an active contribution process with documented guidelines and open issues for community involvement. Development emphasizes educational value alongside practical implementation, with the team focused on demonstrating solid practices rather than building comprehensive tooling.