> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rathforge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> FORGE is a reusable, server-authoritative RP framework for HELIX (Unreal Engine / UnLua).

<Frame>
  <img src="https://mintcdn.com/rathforge/d3EZVTK1JP03qv6C/logo/01.png?fit=max&auto=format&n=d3EZVTK1JP03qv6C&q=85&s=48b58b3dffb43b4dffe39d5af5149d0e" alt="FORGE" width="240" height="240" style={{ margin: "0 auto", display: "block" }} data-path="logo/01.png" />
</Frame>

FORGE is the **base you fork** to build a fantasy or roleplay server on [HELIX](https://helixgame.com). It ships characters, attributes,
inventory, equipment, abilities, combat, loot, crafting, economy, quests, factions, instancing,
admin, and dev tooling, every system server-authoritative and written in pure Lua.

**The framework is the product, not a running server.** You fork FORGE, drop in your own content,
and ship your server.

<Note>
  A fresh fork boots a coherent **neutral baseline** with no theme attached, create a character, get
  starter items, craft a bandage, eat bread for a buff, equip an item and watch a stat change. You
  replace that baseline with your own world.
</Note>

## Why FORGE

<CardGroup cols={2}>
  <Card title="Forkable" icon="code-branch">
    21 isolated Lua packages you own and edit. Fork, reskin, extend, nothing is locked.
  </Card>

  <Card title="Server-authoritative" icon="shield-check">
    Every mutation is validated server-side. Clients render; the server decides.
  </Card>

  <Card title="Batteries included, removable" icon="battery-full">
    Each package ships a small neutral default set you can keep, edit, or switch off.
  </Card>

  <Card title="Tested" icon="vial">
    625 unit + 153 smoke tests run in-editor on every boot.
  </Card>
</CardGroup>

## How it fits together

FORGE is a stack of small packages, each isolated in its own `lua_State`, talking only through
**exports** (function calls) and **events**. You enable the packages you want in `config.json`, tune
them in their `Config`, and register your content through their public APIs.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Fork, boot, and walk the neutral baseline in a few minutes.
  </Card>

  <Card title="Architecture" icon="diagram-project" href="/concepts/architecture">
    Isolated states, exports, events, and the Result contract.
  </Card>

  <Card title="Content model" icon="layer-group" href="/concepts/content-model">
    The two-tier system: neutral defaults plus your themed content.
  </Card>

  <Card title="Packages" icon="cubes" href="/packages/overview">
    The 23 packages and what each one owns.
  </Card>
</CardGroup>

## Status

FORGE is at **v0.2**: all 23 packages are built and tested (646 unit + 146 smoke green), with a
working end-to-end vertical slice. v0.2 adopted HELIX native health, adding `forge-health` and
`forge-gameplay-rules` and reworking `forge-combat` onto the native provider. The launch-readiness
target is **November 2026**. Expect APIs to be stable within the 0.x line but still evolving toward v1.0.