Files
aetherbound-guild/README.md
T

72 lines
3.1 KiB
Markdown

# Aetherbound Guild / 裂脉远征团
An original landscape 2D Japanese hand-drawn guild-expedition strategy game.
This repository is currently in **complete pre-production design**. Formal game
implementation, bulk final-asset production, packaging, and publishing are
forbidden until the owner approves the complete product, content, presentation,
balance, and interactive-design package.
## Current Product Boundary
- 30 named recruitable characters
- 12 base professions and 24 advanced professions
- 100 enemy combat identities across 8 chapters
- 320 equipment and item entries
- 25-35 hour first campaign, 60-80 hour build completion, roughly 100 hour
collection and high-difficulty completion target
- Landscape 16:9, premium cross-platform target, English and Simplified Chinese
- 2D Japanese hand-drawn presentation using layered rigs, equipment layers,
authored key poses, and unique portraits/illustrations
The game may learn structural lessons from authorized private reference
research, but its setting, characters, enemies, names, art, audio, UI,
progression, formulas, and expression must be original.
## Review The Design
The current owner-facing HTML in [`prototype/site/`](prototype/site/) is a
**coverage audit**, not a completed UI prototype. Owner review on 2026-08-10
proved that generic specification templates were not understandable as game
screens. Its page browser now distinguishes one dedicated page, 40 shared
family mockups, and 41 pages whose UI is still missing.
1. **Flow specification:** inspect the required 17-step title-to-restoration
order; do not treat it as a validated clickable experience.
2. **Eight chapters:** inspect route, battle, and restored-world direction for
every chapter.
3. **Page coverage:** inspect all 82 requirements and identify which screens
still need a dedicated composition.
4. **Content:** search all 30 characters, 36 professions, 100 enemies, 320
items, 48 achievements, and 20 collections.
5. **Production and readiness:** inspect the art/audio scope and the gates that
remain open before runtime development.
Run it locally from the repository root:
```bash
python3 -m http.server 8766 --directory prototype/site
```
Then open `http://127.0.0.1:8766`. The published Artifact Gallery link is a
disposable presentation copy; this repository remains the design authority.
Gallery publication must use the self-contained bundle because the Gallery
viewer intentionally sandboxes HTML and may not forward its access cookie to
relative CSS, JavaScript, JSON, or image requests:
```bash
python3 tools/build_gallery_bundle.py
```
## Evidence Boundary
The HTML is an interactive **design prototype**, not a playable build. Its four
AI-generated boards are concept direction only. The UI chrome and readable text
are authored in HTML; no concept board is a final background, sprite, item icon,
animation, integrated asset, runtime screenshot, or human-approved result.
See [`docs/README.md`](docs/README.md) for the complete authority map and
[`docs/reviews/PRE_DEVELOPMENT_READINESS_AUDIT.md`](docs/reviews/PRE_DEVELOPMENT_READINESS_AUDIT.md)
for the exact completed and open gates.