Devil May Cry 3 HD Collection · Evidence-first C++20 research

DMC3 .index Resource Family — DMC Rengine

Evidence-aware entry point for .index in Devil May Cry 3 HD. The page explains the known purpose, identifiers, current schema/product maturity and a practical route for inspecting the family without promoting unresolved semantics.

What .index is

The canonical registry places .index in the Metadata domain and records its purpose as: Extraction/display naming manifest and structural naming metadata for container children.
Known identifiers for this family are recorded as .index. The public page keeps those physical or logical identifiers separate instead of assuming that similarly named extensions, runtime objects or converted representations are interchangeable.
This page is generated from the canonical purpose registry rather than from filename intuition, so its description follows the currently promoted DMC Rengine evidence boundary for the index family.

Evidence and implementation status

Identity status is DATA_CONFIRMED, purpose status is DATA_CONFIRMED, schema status is TEXT, and current product status is recognized; these fields describe different proof dimensions and must not be collapsed into one generic supported/unsupported flag.
A TEXT schema status does not automatically authorize writing, conversion or original-game reintegration, while a recognized product status does not upgrade unresolved field semantics beyond the evidence recorded for this exact family.
When the registry says OPEN, RESEARCH_REQUIRED, runtime-only or capability-only, the site preserves that limitation visibly instead of filling the missing knowledge with presentation-layer guesses.

Practical tutorial path

First locate a real .index instance through the canonical GDSpaces/container path and preserve its provenance: numbered NBZ volume, container/member identity, slot position and original byte range should remain attached to the sample you inspect.
Next confirm identity using the evidence appropriate to .index: extension, magic, dispatcher, registry mapping or structural checks should be used only where the canonical research actually establishes them, and ambiguous .bin/.ukn-style naming must not be treated as semantic proof.
Then compare the sample with the canonical parser, tests and research notes for the index family. Promote a field from raw bytes to typed meaning only when executable, corpus or structural evidence reaches the project's required evidence level.

Current limitations and safe next steps

The current public status for .index is recognized with schema state TEXT; operations beyond that boundary require a separate implementation and validation receipt rather than an assumption that recognition implies editing support.
If a writer exists later, structural round-trip tests, preservation of unknown bytes, reintegration into the correct container lineage and original-game consumption are separate gates; none is implied merely by this encyclopedia page.
For deeper work, use the canonical source and Current Status links below, then follow the reverse-engineering workflow to turn remaining .index unknowns into bounded research targets instead of broad speculative format claims.

.index at a glance

Identifiers: .index
Domain: Metadata

Identity: DATA_CONFIRMEDPurpose: DATA_CONFIRMEDSchema: TEXTProduct: recognized

Canonical source

This page is a public discovery and readability layer. It does not replace the repository's current implementation, status, evidence or format-specific documentation.

Open canonical GitHub source

Evidence boundary

A parser is not automatically a writer. A successful writer is not automatically equivalent to Capcom's offline tools. Synthetic validation does not establish original-game behavioral equivalence.

Use the current status for promoted capabilities and open proof gates.