> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/docs/battlefield-3d.md).

# Battlefield 3D Historical Archive

## Status

This file is historical. It describes the removed pre-2D Three.js battlefield that existed before the 2026-05-28 asset-driven 2D migration.

Current product behavior is documented in `docs/battlefield.md`. Current runtime code does not import Three.js, mount a WebGL canvas, use raycasting, or load 3D battlefield assets.

## Historical Scope

The removed implementation used:

* `three` and `@types/three` in `apps/web`
* a procedural scene in `apps/web/src/components/battlefield/Battlefield.tsx`
* a Three.js particle celebration manager in `apps/web/src/components/battlefield/achievementCelebration.ts`
* a separate inline Three.js mirror in `public-demo/index.html`
* primitive geometry for terrain, faction keeps, hero silhouettes, rings, and achievement particles
* raycaster hit testing for hero selection and empty-field clearing

Those details are retained only as migration context. They are not current implementation guidance.

## Replacement

The current battlefield uses generated 2D art, DOM hero buttons, CSS rings and glows, DOM/CSS achievement bursts, and browser-tested fallbacks for missing assets. Runtime assets are tracked under:

* `apps/web/public/battlefield/`
* `public-demo/assets/battlefield/`
* `assets/battlefield-2d/reference/`

The related Phase 04 matrix row is `M04-026`. Historical 3D models, textures, trees, rocks, and animation files remain deferred quarantine evidence and are not promotable runtime media.

The current replacement and generated asset records are:

* `docs/battlefield.md`
* `docs/media/media-assets.md`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/docs/battlefield-3d.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.