RPG Saga Engine manual
Every system, setting and node, written for people who build games, not only for programmers. 33 chapters, about 312,000 words, searchable.
Getting started
1. Introduction
In short: RPG Saga Engine is a framework for role-playing games in Unreal Engine 5.8: battles in several modes, characters, abilities, items, exploration, dialog, quests, saves and an enemy AI, all driven by data you aut
6 sections · 1,675 words2. Installation and your first project
In short: Install the plugin (from Fab or by hand), enable it, and either open the Starter project or run Set up the project in RPG Saga Studio. In about 45 minutes you will have a playable slice, a character of your own
9 sections · 2,902 words3. Core concepts
In short: A handful of ideas explain how the whole plugin works: content is data, rules are settings, state is plain serializable data, logic is separate from presentation, and everything is checked by validation. Learn
9 sections · 3,027 words4. Game foundation and archetypes
In short: The Game Foundation is the rule book of your game: what you call things, which stats and resources exist, how damage is computed, which elements and equipment slots there are, which battle modes you use, and ho
9 sections · 4,224 wordsCharacters and systems
5. Characters and party
In short: A class (URSEClassData) defines stat growth, abilities by level and allowed equipment. A character (URSECharacterData) is a specific hero, recruit or enemy with a fixed class plus personal traits. The party (UR
9 sections · 3,793 words6. Progression
In short: Progression is how your heroes grow. Every game has levels (stats from the class, abilities at their unlock levels). On top you choose one of three systems: Classic (levels only), Classic + Points (the player s
9 sections · 3,995 words7. Abilities and statuses
In short: An ability is anything a unit can do in battle: a sword strike, a spell, a heal, a thrown bomb. A status is a lasting effect on a unit: poison, haste, a shield, charm. Both are data assets. One ability works in
9 sections · 3,700 words8. Items, inventory and economy
In short: One item system serves every battle mode and exploration. Items are data assets in four kinds (consumables, equipment, key items, documents). The party carries them in a shared grid or in per-character bags, an
9 sections · 2,788 words19. Weapons
In short: every attack with a weapon shows that weapon in every battle mode: guns aim and fire, bows release arrows, blades swing with a trail, staves glow. The look is a Weapon Presentation data asset, and how the weapo
10 sections · 3,685 words18. Character visuals and animation
In short: a character's looks are data. A look (appearance) names a body, optional modular parts, a thin Anim Blueprint and an animation set, and the battle systems play animations and effects from that data. You can bri
9 sections · 2,726 wordsBattles
9. Battle fundamentals
In short: Every fight in the plugin is an encounter: a data asset that names the battle mode, the enemies, the rules, the objectives and the rewards. The modes (grid Tactics, Free Tactics, ATB, turn-based, Action) share
9 sections · 3,605 words10. Grid Tactics
In short: Grid Tactics is turn-based combat on a square grid laid over your live level. Tiles have height and terrain, units face a direction, and position matters: flanking, high ground, cover, line of sight. Turn order
9 sections · 2,988 words11. ATB and turn-based
In short: The classic battle modes are menu-driven fights on a stage where two sides face each other in rows. ATB gives every unit a time bar that fills until the unit can act. Turn-based drops the bar: one unit acts at
9 sections · 3,214 words12. Free Tactics (Live)
In short: Free Tactics is a turn-based battle mode that is fought right on the exploration map, with free movement in meters instead of grid tiles. There is no loading screen and no battle map: enemies notice the party,
9 sections · 4,352 words13. Action battles
In short: Action battles are fought live. The player swings a sword, rolls, guards, parries, aims a gun or casts a spell, and the enemies do the same, all on the party, classes, abilities, items and statuses you already
9 sections · 3,220 words14. Enemy AI and adaptive difficulty
In short: Every enemy (and every companion nobody plays) fights with an AI profile: a small data asset that says what the unit goes after. One utility AI serves every battle mode. A single number per mode, the intelligen
9 sections · 4,048 words20. Camera and battle presentation
In short: one camera framing system keeps every camera (exploration, each battle mode, cinematic shots) out of rocks and walls, and the battle presentation system turns the results the rules already computed into a show:
9 sections · 2,744 wordsWorld and story
15. Story, dialog and quests
In short: One small language tells the whole story. Conditions ask a question ("does the party carry the key? is the flag set?") and effects change the world ("give an item, start a battle, recruit a character"). Dialogs
9 sections · 3,812 words16. Exploration
In short: Exploration is everything the party does between battles: examining and talking, opening locks, solving puzzles, walking through zone exits, saving at save points, meeting enemies on the map (random or visible)
9 sections · 4,628 words17. World building
In short: a handful of editor tools turn an empty stretch of your map into playable content: a battle site, a populated zone, buildings you can walk into, interiors built from your own asset packs. Test rooms prove the f
11 sections · 4,304 words21. User interface
In short: every built-in screen (menus, party menu, options, dialog, shops, HUDs) takes its look from one UI Style asset, and its arrangement from small layout classes. Ten styles ship in the plugin; change one field and
9 sections · 3,410 words22. Save and load
In short: the whole game state (party, inventory, story, quests, world, time and more) is saved in slots, from save points in the world, from a consumable save item that works almost anywhere, and by autosave at save poi
9 sections · 2,508 words25. Localization
In short: RPG Saga Engine ships in English only. Every text goes through Unreal's localization system, so any language can be added. The Translate with AI tool exports the texts for an AI assistant, checks what comes bac
9 sections · 2,534 wordsOnline, platforms, tools
23. Co-op and online
In short: RPG Saga Engine lets two to four players play one game together: one player hosts, friends find or are invited to the session, and everyone explores, talks and fights in the host's world. You do not write netwo
9 sections · 4,534 words24. Platforms and performance
In short: RPG Saga Engine is built and tested on Windows (Win64) and plays on the Steam Deck. It has a low-end fallback path with no Lumen, Nanite or Virtual Shadow Maps, a Steam Deck device profile, a scripted benchmark
9 sections · 3,576 words26. Editor tools
In short: you build a game with RPG Saga Engine in the editor, not in code. RPG Saga Studio is the front door, the Configurator holds every setting, the Create New wizards and visual editors make content, Content Import
9 sections · 4,199 words27. Extending the plugin
In short: most extensions need no C++. Conditions, effects, ability effects, AI scorers, interactable objects, menu entries, screens and command handlers can all be written in Blueprint and show up in the editor's lists.
9 sections · 3,395 words28. Troubleshooting and FAQ
In short: most problems show up in Validate All Data and in the Output Log. This chapter collects the common symptoms with their causes and fixes, answers the questions people ask first, and lists the logs and debug cons
10 sections · 3,222 words29. Glossary
In short: the words used in RPG Saga Engine, its editor tools and this manual, in plain language. Terms in italics inside an explanation have their own entry. Each group ends with the chapter that explains it in depth.
7 sections · 2,793 wordsReferences
Appendix A. Blueprint node reference
Generated from the plugin's reflection data (RSE.Docs.ExportReference). 2247 nodes, events and overridable functions in 287 classes. Kind: function is a callable node, pure has no execution pin, event is an assignable ev
287 sections · 67,742 wordsAppendix B. Settings reference
Generated from the plugin's developer settings classes. 151 settings classes with 4465 properties. Open Project Settings, then the category and section shown in each heading. Defaults are the values the class holds when
151 sections · 103,433 wordsAppendix C. Console variables and commands
Generated from the console manager: every variable and command whose name starts with RSE.. 356 entries. Type the name in the editor or game console; a variable without a value shows its current value.
0 sections · 6,579 wordsAppendix D. Data asset types
Generated from the plugin's data asset classes (UDataAsset and UPrimaryDataAsset subclasses). 127 types. Only properties you can edit on the asset are listed; inherited ones are listed under the parent class.
127 sections · 34,200 words