ResMgr is the client's resource-manager bridge for virtual resource paths and section-like data. It helps prove that a resource can be opened; it does not prove that a GUI route, model owner, battle entity, or generated accessor is ready.

Primary ownershipVirtual resource system and package lookup
Typical objectDataSection-style tree or resource handle
Version sensitivityVerify call sites and signatures per client build

What ResMgr proves

  • A virtual resource path can be resolved through the current package/resource lookup layer.
  • A section-like resource can expose child keys, values, or structured data to Python.
  • A file or section may exist even when the higher-level system that consumes it is not ready.
  • Path success is evidence for resource availability, not evidence for UI lifecycle, service ownership, or gameplay synchronization.

Path taxonomy

Path or identifier Meaning Do not confuse with
Filesystem path Where a developer sees a file on disk or inside an extracted tree. The virtual path used by the running client.
Archive/package path Where a file lives inside a package such as a mod archive. The source path in your project or extraction workspace.
Virtual resource path The path the client resolves through package and resource lookup. Generated accessors, Gameface coui:// URLs, or localization keys.
DataSection child path A structured node below an opened section. A standalone file or guaranteed gameplay object.
Generated resource ID or accessor A build-generated contract that points to a resource or identifier. The underlying file path or the runtime object that consumes it.

Read by topic

Choose a focused chapter. Complete examples and reference details are preserved on their topic pages.