Skip to main content

Helper component settings

CompSpawnHelper​

FieldTypeDescription
Return Base GoGameObjectPickup-side child GameObject that enters the Return trigger
Moves after Spawn and has its position reset after Return
Move DelayfloatNumber of seconds to wait between spawning and moving
Default: 1

Add CompSpawnHelper to the parent root GameObject registered in VRCObjectPool. In Return Base Go, assign the Pickup-side child GameObject that enters the Return trigger.

If Return Base Go contains VRCObjectSync, the helper uses FlagDiscontinuity and synchronized movement. On Return, it resets the position with Respawn.

Without VRCObjectSync, the helper moves the Transform directly and restores the position and rotation saved at world startup on Return.

Return Base Go is also a search target for SpawnOffset or an ObonEasy TrayItem component on an item using this helper. See Adjust position and rotation when spawning for details.

HGSpawnHelper​

FieldTypeDescription
Supported versionSelectionSelect v7.x.x or v8.x.x to match the item
Default: v8.x.x
HG BaseGameObjectGameObject containing the corresponding Base script
For v8.x.x, the same GameObject must contain VRCObjectSync
HG SyncGameObjectGameObject containing the VRCObjectSync used for movement in v7.x.x
Leave unassigned for v8.x.x
Move DelayfloatNumber of seconds to wait between spawning and moving
Default: 1

Clicking AUTO SET at the top of the Inspector searches the root hierarchy and assigns HG Base. For v7.x.x, it also searches for HG Sync; for v8.x.x, it leaves HG Sync unassigned.

For movement, v8.x.x uses the VRCObjectSync on HG Base itself, while v7.x.x uses the VRCObjectSync on HG Sync. On Return, v8.x.x sends Respawn to ResetSwitchHelper on the same root as HGSpawnHelper, while v7.x.x sends State7_Reset to the Base script. Both events are sent to all clients.

HG Base is also a search target for SpawnOffset or an ObonEasy TrayItem component on an item using this helper. See Adjust position and rotation when spawning for details.

Ownership​

When a client obtains ownership of a helper component, it also obtains ownership of the GameObject configured as the movement target. In a multi-user world, test Spawn, Return, and respawning with two clients.

Component placement​

Add either helper component to the same root GameObject registered in VRCObjectPool. A configuration containing both helper components on one root is not supported.