Lore for game teams

Understand the large-asset engine behind ForgeLore

Lore is built for large binary-heavy projects. This knowledge base explains sparse workspaces, chunked storage, version-control concepts, scaling behavior, and adoption tradeoffs.

Accurate by design

Technical claims stay grounded in official Lore, Epic Games, or GitHub sources.

Markdown files under docs/lore are canonical.

Technical claims should cite official Lore, Epic Games, or GitHub sources.

Analysis should be labeled separately from documented behavior.

This route is an index, not a Markdown renderer.

Reading order

Use these deeper references when evaluating Lore for a production team.

9 files

Lore Knowledge Base

Entry point, reading order, source policy, and architecture mind map.

docs/lore/README.md

Overview and Purpose

What Lore is, target workloads, maturity, license, and UEFN relationship.

docs/lore/01-overview-and-purpose.md

Architecture Mental Model

Immutable/mutable stores, partitions, contexts, and API-first design.

docs/lore/02-architecture-mental-model.md

Storage and Chunking

BLAKE3, fragments, packfiles, FastCDC, sparse reads, and compression.

docs/lore/03-storage-and-chunking.md

Version Control Model

Revisions, trees, branches, staging, push/sync/merge, and metadata.

docs/lore/04-version-control-model.md

Scale, Security, and Deployment

Centralized/offline behavior, multi-tenancy, backends, edge caches, and consistency.

docs/lore/05-scale-security-and-deployment.md

Comparison and Analysis

Git, Perforce, Mercurial, Sapling, tradeoffs, and adoption risks.

docs/lore/06-comparison-and-critical-analysis.md

Roadmap and Adoption

Pre-1.0 caveats, roadmap themes, and practical adoption checks.

docs/lore/07-roadmap-and-adoption.md

Sources

Official references used by the knowledge base.

docs/lore/sources.md

Back to ForgeLore docs

Use the architecture and operations docs for ForgeLore-specific hosting and release guidance.

Docs hub