Asset IDs

Asset IDs are unique identifiers that reference files across the entire MOD system. Whenever you attach a VRM model to a persona, play an animation, or open a WebView, you use an asset ID to tell the engine which file to load. The only hard requirement is that every asset ID is globally unique — duplicate IDs are logged as warnings and skipped.

Recommended Convention

The recommended convention is:

<mod-name>:<asset-name>

The engine treats asset IDs as opaque strings — it does not validate or parse this format. However, prefixing with the mod name prevents collisions between MODs and makes IDs self-documenting.

Part	Source	Example
mod-name	Derived from the name field in package.json	@hmcs/assets becomes assets
asset-name	The key in the homunculus.assets object	vrm, open, ui

The mod name is extracted from the package name by stripping the scope prefix. For example:

• @hmcs/assets -- mod name is assets
• @hmcs/settings -- mod name is settings
• my-character -- mod name is my-character (no scope to strip)

The asset name is whatever you chose as the key when declaring the asset in package.json.

Example

Given this package.json:

{
  "name": "my-character",
  "homunculus": {
    "assets": {
      "my-character:vrm": {
        "path": "assets/MyModel.vrm",
        "type": "vrm",
        "description": "Custom VRM character model"
      },
      "my-character:open": {
        "path": "assets/open.mp3",
        "type": "sound",
        "description": "Sound effect for opening action"
      }
    }
  }
}

The asset IDs are my-character:vrm and my-character:open. You use these strings anywhere the SDK or API expects an asset reference.

Built-in Assets

The @hmcs/assets MOD provides a set of default animations and sound effects that all MODs can use. These are available out of the box when @hmcs/assets is installed:

Asset ID	Type	Description
vrma:idle-maid	vrma	Maid-style standing idle with hands clasped in front
vrma:grabbed	vrma	Reactive pose while being dragged by the user
vrma:idle-sitting	vrma	Seated idle loop with legs together
se:open	sound	Sound effect for opening a HUD panel

ヒント

The built-in assets use the mod name vrma and se (from the @hmcs/assets package). You do not need to create your own idle animations unless you want custom ones.

Using Asset IDs in Code

The @hmcs/sdk accepts asset IDs as strings wherever an asset is needed.

Attaching a VRM character to a persona

import { persona } from "@hmcs/sdk";

const p = await persona.create({ id: "elmer" });
const vrm = await p.attachVrm("elmer:vrm");

Playing a VRMA animation

import { repeat } from "@hmcs/sdk";

await vrm.playVrma({
  asset: "vrma:idle-maid",
  repeat: repeat.forever(),
  transitionSecs: 0.5,
});

Opening a WebView

import { Webview, webviewSource } from "@hmcs/sdk";

await Webview.open({
  source: webviewSource.local("settings:ui"),
  size: [1, 0.9],
  viewportSize: [900, 700],
});

The webviewSource.local("settings:ui") source tells the engine to load the HTML file registered under the settings:ui asset ID.

Using Asset IDs in the HTTP API

Asset IDs appear in HTTP API request bodies as well. For example, to attach a VRM model to a persona via the API:

curl -X POST http://localhost:3100/personas/elmer/vrm \
  -H "Content-Type: application/json" \
  -d '{"assetId": "elmer:vrm"}'

The same asset ID string is used consistently across the SDK and the HTTP API.

Referencing Assets from Other MODs

A MOD can reference assets from any other installed MOD. For example, a MOD that creates a character commonly uses animations from @hmcs/assets:

// This MOD uses an animation from @hmcs/assets
await vrm.playVrma({
  asset: "vrma:idle-maid", // Defined in @hmcs/assets, not in this MOD
});

警告

If the MOD that owns the asset is not installed, the engine will return an error when you try to use its asset ID. Make sure the MOD that provides the asset is installed (hmcs mod install <mod-name>).