Kneeshaw Developments
0
← Back

The Codex · in development

Ten topic groups · the questions players ask most

Questions of the age,answered as plainly as possible.

Ten topic groups cover what players ask most: about the game, combat and systems, platforms and technical, release and business model, saves and data, the sister games in the universe, modding and community, accessibility and comfort, developer-side curiosities, and the wiki itself. If your question isn't here, the long answer is almost certainly somewhere else in the wiki.

10topic groupsalwaysplain answerswhere usefullinks to long versionsIdlesister wiki

Plain answers · links to the long versions

ABOUT THE GAMECOMBAT & SYSTEMSPLATFORMSRELEASE · BIZSAVES & DATAOTHER GAMESMODDINGACCESSIBILITYDEVELOPER-SIDEABOUT THIS WIKI?

Ten topic constellations · one wiki anchor at the centre

About the game
Combat & systems
Platforms
Release · biz
Saves & data
Other games
Modding
Accessibility
Developer-side
About this wiki

10

Categories

44

Questions answered

PC

Windows · macOS · Linux

Single-player

No live service

Jump to a section

About the game

The shape of Titan Saga — genre, vibe, scale, what makes it different from other RPGs.

What kind of game is Titan Saga?

An open-world fantasy simulation with real-time action combat. Every NPC is an autonomous agent with needs and goals, every city runs its own economy, and ten major factions pursue their own agendas. You step in as a cultivator — bonding essence, climbing thirteen ranks from Unbound to Monarch, and shaping a world that never pauses for you. See the overview for the long pitch.

What does “2.5HD” mean?

Hand-painted, high-detail 2D environments and characters composited with 3D camera depth and lighting. Every frame reads like illustration; every fight still feels physical and spatial. The trade-off is deliberate — full 3D loses the painterly tone the world is written in.

What's the scope?

Around 850,000 simulated agents running concurrently across the continent. Every agent has a profession, needs, goals, memory, and relationships. Ten major factions, dozens of named cities, four cultivation realms, 153 bondable essences, 584 source abilities. The simulation page explains how the engine runs that without melting.

Is this a chosen-one story?

No. The opening explicitly frames you as a survivor — heir to a small noble house whose city has just been burned in an orchestrated raid. You are not destined; you have information no one else has and a few people who didn't sell you out, and that is your entire advantage. Choices ripple through a world that does not wait for the protagonist.

Combat & systems

How play actually works once you're in the world.

How does combat work?

Real-time action with weak / strong attacks, combos, dash cancels, lock-on targeting, and four energy pools — Mana, Stamina, Rage, and Segment — that your active essence decides between. Each archetype runs two of the four concurrently. Enemy tells are readable (lunges, roars, volleys). The battle system page covers attack patterns, energy economy, and AI selection in detail.

How does cultivation work?

You bond up to five essences, run two active at any time, and earn attribute points by ranking each one up. Thirteen ranks across four realms, 83 attribute points at maximum, a 10,368× power gap from Unbound to Monarch. Active essences modify every ability through aspect filters (Destructive, Restorative, Swift, etc.). See the essence system and ranks for the full breakdown.

Is the simulation a gimmick?

No. The C++ World Engine runs cities, factions, traders, and monsters whether or not the player is looking. Famines propagate as price waves. Faction relations actually decay. Quest hooks spawn from real systemic imbalances via the WorldEventGenerator. The simulation tier system (FULL / LITE / DORMANT) is how it stays affordable.

How many quests, monsters, items, essences?

Most quests are procedural — 11 quest categories generated from world state, plus hand-authored Story Arcs on top. 13 monster power tiers across 5 origin families. 153 bondable essences, 14 weapon types, 6 armor types, 18 equipment slots, 7 rarity levels. See the quest system, bestiary, items & gear for the full counts.

Can I play a non-combat build?

Yes. The 32 professions split across 10 categories — gathering, crafting, trading, support, espionage, infrastructure, alchemy, enchanting — alongside combat professions. A pure-Merchant or pure-Cartographer run is mechanically viable; you'll trade through crisis routes and map regions other parties paid to find. See the professions page for the full set.

Platforms & technical

What you'll need to run it, and on what.

What platforms will it run on?

PC-first: Windows, macOS, Linux via Steam at launch. Steam Deck and console parity are being evaluated but not promised yet.

Will it run on my computer?

Hardware requirements aren't finalised. The simulation backend is CPU-heavy by design — multi-core meaningfully helps. GPU requirements are modest (the 2.5HD art is cheaper to render than full 3D). Final spec ranges drop with the alpha invite waves.

Controller support?

Yes, planned for launch. The combat is built around input primitives that map cleanly to gamepad — light/heavy, dash, lock-on, ability rotation. Keyboard-and-mouse remains the default for menu-heavy workflows (the market, crafting UI, party management).

Will there be a Steam Deck verified rating?

That's the goal. Steam Deck is a target for the PC launch. Whether it ships with the verified badge depends on Valve's certification queue and the final UI scaling work.

Release & business model

When you can play it and what it costs.

When does it release?

In active development. No public release date yet. Wishlist the game on Steam for alpha invites, closed playtest keys, and the launch announcement.

Will there be an early access?

Likely. Alpha and closed-beta phases are planned to seed invites to Steam wishlisters first. The exact early-access structure depends on how the alpha shakes out.

How is it monetised?

One-time purchase. No live services, no season passes, no always-online, no microtransactions. The mobile sister games (Idle, Dungeons) are free-to-play; Titan Saga is premium.

Is it single-player?

Yes. Titan Saga is a single-player simulation — the multiplayer fantasy comes from the fact that the world is full of autonomous agents who act like other players. No multiplayer is planned. No always-online requirement.

Will there be DLC?

Possibly, post-launch. The simulation engine is structured so new regions, factions, and storylines can plug in without invalidating existing saves. Concrete DLC plans wait until launch ships.

Saves & data

How your progress is stored, persisted, and (sometimes) restored.

What format are saves?

XML. One file per save slot. The format is intentionally human-readable — debugging, modding, and data-archaeology all benefit. A single file captures the world seed, every committed decision, every faction relation, every active quest, and every NPC's current state.

What does a save actually capture?

The world seed + every committed choice + the current world clock + a snapshot of all major systems' state at the save instant. Restoring is exact — including the trader who was halfway through a long-haul convoy when you saved. The simulation determinism section covers the model in depth.

Will my choices stick?

Yes. Cities remember player actions; faction relations adjust permanently; world state changes do not reset. Failed Story Arcs stay failed; abandoned arcs stay abandoned. There is no checkpoint-revert mechanic in the simulation; a reload doesn't restore world state to a point — it replays the simulation deterministically to the saved tick.

How many save slots?

Multiple slots planned, each independent. Cross-save between PC platforms (Steam Cloud) is the working assumption. Cross-game saves between Titan Saga and the sister mobile games is not supported — different worlds, different rules.

Can I edit my save?

The format is XML and not encrypted, so yes — at your own risk. Editing saves is officially unsupported but not actively prevented. The community modding scene traditionally builds save editors first.

Other games in the universe

How Titan Saga relates to its mobile sister games.

What's Titan Saga: Idle?

A free-to-play mobile idle / management RPG set earlier in the world's chronicle, when mortals first bound themselves to fallen titans. Same universe, different slice. It has its own wiki at /titan-saga-idle/wiki.

What's Titan Saga: Dungeons?

A mobile deckbuilding dungeon-crawler set in the world of Titan Saga. Lore cross-references with the flagship; saves do not transfer. Built for shorter play sessions than the main game.

Do they share saves or progression?

No. Each game is its own product with its own save format. Lore is consistent; mechanics are not transferable. Playing one doesn't unlock the others.

Should I play them in order?

No required order. Idle is set earliest in the chronicle (the Champion Era), Dungeons sits roughly contemporary with the flagship, Titan Saga itself is set in Year 8,955 — five years after the Imperial Unity Law and the discovery of the Paragon. Any can be a first entry point.

Modding & community

What you can change, share, and build on top of.

Will there be modding support?

Yes — design intent. The core data is JSON and the save format is XML, both intentionally human-readable. Tooling and Steam Workshop integration are post-launch goals. Expect community tools earlier than official ones.

Can I run a custom world seed?

At new-game time, yes — the world seed is part of the new game initialisation. Mid-game seed swaps are not supported (the simulation determinism model relies on a fixed seed from the first tick).

Can I share my world?

Save files are portable. Sharing a save with another player lets them step into your exact world-state at the saved tick. Cross-platform sharing works as long as both platforms run the same game version.

Is there an official community?

A Discord server and Steam community hub are planned. Pre- launch communications run primarily through the Steam store page and the developer's website. We will not be building a separate launcher or account system.

Accessibility & comfort

Player comfort, accessibility features, and difficulty options.

Is there a difficulty setting?

Yes. The simulation runs the same at every difficulty — what changes is monster damage, monster density, and the tolerance for player mistakes (forgiving healing, slower stamina drain, etc.). Hardcore difficulty disables save scumming for the players who want that.

Colourblind support?

Planned. Combat tells and status effects use shape+colour channels together, not colour alone. Settings will allow full palette substitution for the major colourblind profiles.

Text size and readability?

Adjustable text scale, UI scale, and high-contrast theme are part of the accessibility settings target. The wiki's in-game equivalent (the Codex) is keyboard-navigable.

Motion / visual comfort?

prefers-reduced-motion is respected in the UI (the same way this wiki respects it). Combat camera shake and screen-flash effects can be disabled in settings.

Developer-side & curious-people questions

The less-glamorous questions about how the game is built.

What engine?

Two layers. The presentation layer is Godot 4.6. The simulation runs in a separate C++ World Engine compiled as a GDExtension. The split means the engine can run headless for tests, on a server for tooling, or for future mod-friendly automation without dragging the renderer along.

Is the C++ engine open source?

Not at this time. The World Engine is a proprietary simulation library developed alongside the game. The engine's interfaces and architecture documentation may be released post-launch; the source itself is unlikely.

How big is the team?

Small. Communicated as a solo development with assistance from a network of contractors and AI tooling. The simulation-over-scripting design is partly a response to this — a small team can author the world's rules and let the engine generate the content.

Why so much AI in development?

Used as a productivity multiplier — drafting design documents, generating placeholder art, writing test scaffolds, surfacing inconsistencies between docs. Authoritative decisions (game design, lore, system tuning) remain human. The world isn't AI-generated; the productivity tooling around making it is.

Where can I report a bug or send feedback?

Pre-launch: through the Steam community hub and the developer's contact form. Post-launch: a dedicated bug reporter accessible from the in-game pause menu, plus the same Steam community channels.

About this wiki

Meta questions about the wiki you're reading.

Is this an official wiki?

Yes. Run by the developer (Kneeshaw Developments). The sister game Titan Saga: Idle has its own wiki at the same domain. Both ship in waves and update as the games evolve.

Where does the lore come from?

From the design docs (the Vault). Each page cites its source files at the bottom — the lore page references TITAN_SAGA_LORE; the geography page references TITAN_SAGA_GEOGRAPHY; and so on. The wiki is the human-readable layer on top of the canonical design documents.

What if I find an inconsistency?

Likely a real one — the design is iterating in real time. Report it through the Steam community hub or the developer contact form. The wiki gets updated when the underlying canon shifts.

Will deep-dive sub-pages happen?

Yes — per-Titan profiles, per-essence breakdowns, per-NPC character pages, per-region atlases, per-faction deep dives. The current pages establish the canon; the next wave widens each entry into its own page.

Where to read next

Source: TitanSaga design docs (TITAN_SAGA_DESIGN, ALPHA_EXECUTIVE_SUMMARY, USER_DATA_SAVE_GUIDE, XML_Serialization); landing-page FAQ as canonical reference for public-facing claims.