| # Provisional progress toward the complete game |
|
|
| Assessment date: **2026-10-19**, after the57312 movement analysis batch. **Estimated overall completion: approximately5–10%. Playable Rust rewrite completion:0%.** This is a low-confidence engineering estimate against the full [G1–G9 goals](GOALS.md), including every required game feature/content path, Bevy/Solari, native macOS/Linux operation and release qualification. It is not a measured percentage of recovered behavior, a calendar forecast or a claim that90–95% of a fixed number of hours remains. |
|
|
| The project has a substantial static research and extraction foundation. The implementation and integration work required for a playable replacement has not started in this checkout. The strongest observable fact is that the repository has **no Cargo.toml and no Rust source files**. There is no demonstrated Rust client, dedicated server, Bevy application, Solari scene or native platform gameplay result. |
|
|
| ## Evidence available now |
|
|
| | Evidence | Current state | What it establishes | |
| | --- | --- | --- | |
| | Reference inventory |39 installation files;23 PK3 archives | A pinned initial scope and original-file identities; see [inventory](inventory/README.md). | |
| | Extraction |9835 verified file occurrences,10578 central-directory entries, including743 directory records | Source variants and provenance are preserved; see [extraction](extraction/README.md). This is unpacking, not a complete runtime conversion pipeline. | |
| | Analysis tools |178 Python files, including85 test modules | Reproducible inspection/evaluation infrastructure, including this batch. | |
| | Verification |687 passing tests | Analyzer/parser/storage and bounded synthetic behavior regression checks. This is not687 original-runtime or Rust gameplay conformance tests. | |
| | Canonical RE checklist |248 checked,292 open after this batch | Completed scoped research deliverables. These540 tasks are uneven in size, and new bounded tasks have been added over time.248/540 must not be read as46% of the game being complete. | |
| | Asset pipeline checklist |4 checked,129 open | Extraction has verified steps; content schemas, complete dependency resolution, conversion, runtime packaging and QA remain open. Partial work on unchecked items is described in the checklist. | |
| | Rewrite checklist |0 checked,173 open | No validated runtime deliverable yet. | |
| | Runtime and platform evidence |No Rust/Cargo project; no demonstrated Solari or macOS/Linux game execution | No playable or release gate can currently be credited. | |
|
|
| Counts describe this repository snapshot, not all possible work. The [research ledger](RESEARCH_LEDGER.md) records what was verified and which inputs/effects remain supplied. Static QVM decoding and bounded synthetic instruction evaluation are valuable specifications, but they do not establish complete game logic, native collision consistency, scheduler fidelity, networking interoperability or end-to-end gameplay. |
|
|
| ## Basis for the5–10% estimate |
|
|
| These are deliberately coarse judgments of remaining engineering effort. Weights are planning assumptions, not measurements. The categories cover the full requested game and overlap only through integration work assigned to the relevant runtime/presentation/release category. |
|
|
| | Work category | Assumed share of total effort | Estimated completion within category | Evidence and gap | |
| | --- | ---: | ---: | --- | |
| | Reference research and behavioral specification |25% |15–25% | Broad static binary/format/ABI analysis and many bounded helper fixtures exist. Original execution/reference traces, complete modules/engine/service behavior and exhaustive semantic coverage remain. | |
| | Production content pipeline |15% |10–20% | Inventory/extraction/variant preservation exist. Complete conversion, material/animation/collision/navigation runtime contracts, dependency resolution and content-wide QA remain. | |
| | Shared Rust simulation, collision, gameplay and server |25% |0% | No Rust runtime. Movement, weapons, damage, all modes, entities and authoritative scheduling must be implemented and compared. | |
| | Multiplayer, bots, demos, audio, UI and services |15% |0% | No demonstrated replacement systems. Research evidence does not count as their runtime implementation. | |
| | Bevy/Solari presentation and platform integration |15% |0% | Required native hardware capability, animated content/material pipeline, rendering/performance and application integration have no passing prototype evidence. | |
| | Packaging, integration QA and release qualification |5% |0% | Storage/tooling checks exist, but no game build can pass native installation, multiplayer, fidelity, performance or full-content release tests yet. | |
|
|
| These assumptions produce approximately5.25–9.25% overall; rounding to5–10% avoids implying precision the evidence does not support. Plausible discovery or implementation surprises can move this estimate substantially. The0% playable-runtime assessment is much firmer than the overall effort estimate. No completion date is defensible from the current evidence. |
|
|
| ## Milestone status |
|
|
| Using the existing [milestone exit criteria](VALIDATION_AND_MILESTONES.md), **no complete milestone is credited as passed** by this assessment. This does not discard partial work: |
|
|
| - M0 research baseline: strong inventory/extraction/tooling progress; the executable reference-observation/harness requirement remains open. |
| - M1 platform feasibility: no passing Bevy/Solari prototype and declared native GPU/OS test matrix. |
| - M2 engine/content contracts: meaningful partial static/ABI/format/helper evidence; complete controlled runtime contracts remain open. |
| - M3 complete initial asset pipeline: extraction works; required runtime conversion, dependencies and content validation remain open. |
| - M4–M8 playable movement/combat/rules/presentation/bots-services: no working Rust integration demonstrated. |
| - M9 exhaustive coverage: inventory coverage is not exhaustive semantic analysis or validated runtime content. |
| - M10–M11 platform qualification/entire-game completion: pending the runtime and full-content gates. |
|
|
| ## Highest-value next completion evidence |
|
|
| 1. Prove M1 with a pinned Rust/Bevy/Solari application on actual target macOS/Linux hardware and record capabilities, failures and measured frame behavior. Do not infer Solari feasibility from a planned raster fallback or static documentation. |
| 2. Establish an original reference execution harness and capture real movement/collision/event traces for the recovered paths. Keep synthetic cases separately identified. |
| 3. Build the first Rust vertical slice: load one converted map, share collision/movement with a headless server, and validate camera/input/step/ground/query behavior against those traces. |
| 4. Add a single complete weapon and two-client controlled match, then expand authoritative rules, content and presentation using measured integration results. |
| 5. Re-estimate after the prototype and first match. Those milestones will reveal constraints and a delivery rate that repeated small static research batches cannot currently quantify. |
|
|
| This assessment does not change the requested all-file/all-feature scope or close any unmet task. Continue the detailed [RE](REVERSE_ENGINEERING_TODO.md), [asset](ASSET_PIPELINE_TODO.md), [rewrite](RUST_BEVY_SOLARI_TODO.md) and [provisional](PROVISIONAL_TODO.md) checklists, with completed deliverables linked to testable evidence. |
|
|
