Game Master Core

GMCore is an RPG framework for Godot 4 built on traditional tabletop-RPG principles.

It attempts to merge modern software design patterns with classic pen-and-paper concepts, such as the role of the Game Master and the action adjudication loop, to provide an extensible base for building RPGs and roguelikes.

Features

• Tabletop Metaphor: Rules and action resolution are handled by a central GameMaster router.
• Action Handling: Each RpgAction is a self-contained rule that can be executed by the GameMaster. Intercept and modify RpgAction data synchronously via signals before execution.
• Systems Oriented: signals are used extensively to provide hooks for your own custom systems and managers. You can extend the optional RpgSystem nodes to skip basic signal boilerplate too.
• Data-Driven: Entities, worlds, and stats are represented with extensible and composable RpgComponent resources.

Note that GMCore does not provide a ready to use game template. It focuses instead on eliminating boilerplate and offering an opinionated architectural structure for RPG and roguelike games.

Usage

Building a game with GMCore tries to mirror running a tabletop session, from rules setup to action adjudication:

1. The Core Rules: Add the GameMaster node to your main scene. It manages your world state, entity lists, and game mechanics.
2. Define the Mechanics: Extend RpgComponent to store data (like a section in a character sheet) and RpgAction to handle specific rule logic (like casting a spell or attacking).
3. Populate the Adventure: Use GameMaster.entities to register game objects and attach their initial components. If your game tracks layout or positioning, you can implement a custom GameWorld resource and add it to the GM here.
4. Setup the Game Systems: Build your observers (like turn managers or combat controllers) to listen to the session's events. You can connect directly to GameMaster signals or extend the RpgSystem node class to handle hooks automatically.
5. Run the Game: Pass player choices or AI behaviors into GameMaster.attempt(action). The GM checks requirements, runs your preview interceptors, executes the action, and broadcasts the final outcome.

More

Check the Github page for details and examples.