1Click Maker
Get 1Click Maker

One HUD, Many Bodies ​

The same dress rigged for Legacy, Maitreya, Reborn, Kupra… You want one HUD and one project. Two features make it possible: link names and target synchronization.

The rule ​

Every body version must have the same link names.

Not the same link numbers, not the same link count. Names. If the Legacy dress has skirt, top, belt, the Reborn dress must have skirt, top, belt too. Extra parts with other names are fine; they just do not receive actions aimed at the three.

Steps ​

  1. Name the parts identically in every version. Do it once in your 3D tool before export, or in-world with Edit linked.

  2. Set up the first version (say Legacy) as a normal target: *TARGETS → NEW. Build the HUD against it, test everything.

  3. Rez the other versions within 5 m of the Legacy one.

  4. Drop *TARGETS into each and choose SYNC, then pick the Legacy dress from the list.

  5. Done. Every version listens to the same channel; the HUD needs no change.

What if a version lacks a part? ​

Say the Kupra version has no belt. Actions aimed at belt simply do nothing on Kupra; everything else works. No errors.

Testing ​

Wear the HUD and one version at a time; each should react identically. Wearing two versions at once (for a screenshot) also works: both react.

Selling ​

Box every version with the same HUD. Customers wear the version for their body plus the HUD. If you later fix the HUD, all versions benefit without re-syncing, because the HUD is what changed.

  • A demo of the multi-body set: clone the project and Bulk Edit to a demo target, then sync the demo versions to it. See Demo Version.