Special ProjectsIn progressDeep Orange theme

WorldForge

WorldForge is a C++/Qt world-building workspace for authors, game designers and tabletop creators. It manages connected worlds, characters, places, events, powers and relationships instead of isolated notes. The existing architecture uses a SQLite-backed model, Qt Quick/QML interfaces and interactive visual graphs to keep fictional systems consistent as they grow.

C++Qt 6QMLSQLiteQt Quick
WOWorldForge
C++Main technology
229Tracked files*
83.h files
82.cpp files
01 · What it does

What the application does

Capabilities evidenced by project documentation and source structure; some behaviours require platform configuration.

01

Multiple isolated worlds with a shared navigation mo

Multiple isolated worlds with a shared navigation model. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02

Connected characters, relationships and visual chara

Connected characters, relationships and visual character graphs. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

03

Powers, ability sets, formulas, attribute scales and

Powers, ability sets, formulas, attribute scales and skill trees. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

04

Organisations, elements, places, events, maps and ti

Organisations, elements, places, events, maps and timelines. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

05

Writing-oriented stories and an integrated editor.

Writing-oriented stories and an integrated editor. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

06

Local SQLite persistence, search, backup and import/

Local SQLite persistence, search, backup and import/export workflows. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02 · Technical structure

How the system works

Technical architecture drawn from the repository and supplied documentation.

01

The Qt application bootstraps world and database managers.

02

SQLite repositories persist characters, powers, attributes, events and other structured data.

03

Qt Quick/QML editors and graph components visualise data relationships.

01 · Input or user action

The workflow starts with the corresponding user choice or data entry. Multiple isolated worlds with a shared navigation model. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02 · Application processing

The relevant component must interpret the input, apply the project rules and coordinate any necessary storage, network access or computation. The documentation below identifies where that responsibility appears in the source when it is evidenced.

03 · Result and feedback

The resulting screen, calculation or stored record should reflect the processed state. Powers, ability sets, formulas, attribute scales and skill trees. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

04 · Boundaries and verification

This page describes the documented behaviour, not an independently verified live deployment. Runtime configuration, permissions, test data or connected services may still be required.

PROJECT WALKTHROUGH

Modules & engineering details

How the major parts fit together and what each part contributes.

01

Worlds and data organisation

Each world acts as an independent context for entities, history and rules. This provides a consistent place to develop fictional universes without scattering facts across files.

02

Characters and relationships

Characters, social links and related attributes can be represented as linked records and visualised in graph-like interfaces, helping authors follow connections.

03

Powers and custom systems

Powers, properties, scales and ability rules can be maintained as structured information, making the tool relevant to games and complex fiction as well as prose.

04

Locations, events and chronology

Places and events connect the fictional geography to timelines. Cross-references reduce contradictions as a world evolves.

05

Desktop architecture

C++ manages application logic and database access, SQLite stores structured content, and Qt Quick/QML provides editors and graphical views.

Connected universe data model

WorldForge documents interconnected character, world and story systems rather than isolated editor screens. The relationships below can be explained using the existing local SQLite model.

01

World container and persistence

Each world groups its characters, maps, relationships, attributes, locations and story content. SQLite keeps the local dataset available offline; the documentation also describes JSON export, backups and recoverable restores.

02

Character Forest and relationship types

The graph editor supports moving nodes, zoom, panning, persistent positions, labels and relation types. Reciprocal and inverse relationships can express links that are more meaningful than a plain connecting line.

03

Powers, elements and skill trees

Powers, custom elements and attributes can connect a character profile to progression systems. A skill-tree view should explain prerequisites and dependencies, not only display nodes.

04

Stories, timelines and maps

Story and world geography can reference the same people and locations. Timeline events help connect world chronology to relationships and narrative content.

Documentation: GitHub repository / project specification. The content describes documented behaviour or plans; deployment readiness is not inferred.

03 · Explore

Project-specific preview

A fictional world modelIllustrative nodes · fictional data
World
Silver Horizon
Character
Lyra
Location
Ivory Coast

The actual desktop app uses interconnected SQLite records and QML visual graphs; this panel is only a website illustration.

Visual studies · project-specific

Interface and system concepts

Independent illustrative views of the documented or proposed workflows. They are not connected to a running backend, and their values are not actual measurements.

Planned world authoring · illustrative

World editor and environment layers

WorldsCharactersRegionsEvents

A scene graph and editor hierarchy would organize editable world elements, locations and saved configurations in a clearer authoring workspace.

TerrainObjectsRegionsScene
Planned relationship map · illustrative

Character and faction network

World
Hero
Guild
City
Power

Linked records can be visualized as relationship graphs so an author can inspect social ties, affiliations and derived story connections.

CharacterFactionLocationPower
Planned illustration board · illustrative

Illustrations and reference gallery

Character concept
Location study
Emblem study

An illustration board could keep character sheets, location sketches and visual references beside the structured world data so creative assets remain easy to revisit.

IllustrationReferenceCharacter artGallery
04 · Source and design

Implementation examples and code walkthrough

The Qt application initializes the database-backed world managers

WorldForge/WorldForge/App/main.cppGitHub code excerpt
C++
WorldForge::App::Application application;
if (!application.initialize()) {
    qCritical() << "WorldForge initialization failed:" << application.lastError();
    return -1;
}
const QSqlDatabase database = application.database().database();
WorldForge::App::WorldManager worldManager(database);
WorldForge::App::CharacterManager characterManager(database);

Managing skill-tree entities

C++

Domain objects retain their universe identity separately from UI display labels.

WorldForge/WorldForge/Graphs/SkillTree/SkillTree.cppSelected source excerpt
SkillTree::SkillTree(const Common::Id& universeId, const QString& name)
    : m_id(), m_universeId(universeId), m_name(name.trimmed()) {}

const Common::Id& SkillTree::universeId() const noexcept { return m_universeId; }
void SkillTree::setName(const QString& name) { m_name = name.trimmed(); }

Timeline relationships

C++

The manager delegates mutations to a repository and refreshes the UI model afterwards.

WorldForge/WorldForge/App/TimelineManager.cppSelected source excerpt
bool TimelineManager::deleteConnection(const QString&id)
{
    if(!m_connectionsRepo.remove(Common::Id::fromString(id))) {
        setLastError(m_connectionsRepo.lastError());
        return false;
    }
    refresh();
    return true;
}

Code samples are excerpts or documented illustrations; surrounding project files, configuration and dependencies may be required to compile or run them.

06 · Technology

Programming languages & stack

C++
Qt 6
Qt Quick
QML
Qt SQL
Qt Widgets
SQLite
MSVC
Visual Studio

Core technologies and integrations used or planned for this project.

File types identified: 83 .h, 82 .cpp, 52 .qml

07 · Reality check

Status, evidence & limitations

The project status is based on repository sources and supplied documentation. It may be updated as the project evolves. A published case study is not a certification of production readiness.
  • The portfolio documents code and README structure; it does not certify a complete Windows release or large-scale performance.
08 · Resources

Downloads & project resources

Installers appear only after a verified release is added to the public download directory. Unavailable builds are marked clearly.

↓Windows EXEComing soon↓Android APKComing soon
Source and platform support may change. An installer is not implied by the existence of source files. Desktop and Android package placeholders are shown until verified releases are published.