A TypeScript RPG framework that works with your renderer.

RPG systems, without a monolithic engine singleton.

A renderer solves cameras, materials, meshes, and frames. An RPG also needs long-lived state, content schemas, objectives, rewards, saves, input arbitration, networking, and UI projections. Putting all of that inside React components or scene objects makes those rules difficult to test and impossible to reuse on a server.

Overworld separates serializable content, headless state machines, and rendering adapters. Your application remains the composition root. There is no global engine object that has to own the render loop, routing, or product-specific game rules.

Connect a scene event to a complete gameplay flow.

Scene code emits a typed fact. The quest engine advances matching objectives, runs a registered reward, and emits completion. React UI subscribes to stores or events. No system needs to import the others.

import { gameEvents } from '@overworld-engine/core'
import { createQuestEngine } from '@overworld-engine/quest'

const quests = createQuestEngine({
  quests: QUESTS,
  conditions,
  effects,
  events: gameEvents,
})

// Called from an R3F controller, Three.js system, or server simulation:
gameEvents.emit('player:moved', { position, distance: 1.4 })

// quest objective → reward effect → quest:completed → React UI

This boundary also makes automated tests cheap: inject an event bus, storage adapter, clock, and random source; drive the system with events; assert against plain state.

Choose the systems your game needs now.

Start from the problem, not the package list

If rendering and game state are becoming entangled, begin with the React Three Fiber RPG architecture guide. If quest logic imports the wallet, inventory, combat, and UI directly, use the headless TypeScript quest system guide.

Build one renderer-independent system at a time.

Each guide follows a real vertical slice from serializable content or validated input through runtime state, events, UI, persistence, and server boundaries.

Choose an architecture, then ship a complete slice.