unity-yooasset-design

Clarify correct YooAsset v2.3.18 API usage patterns for initialization, patch flow, and asset loading.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/YiDuandtdt/Bone-Throne --skill unity-yooasset-design-yiduandtdt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-yooasset-design
Source: https://github.com/YiDuandtdt/Bone-Throne/tree/main/.agents/skills/unity-skills/skills/yooasset-design
Command: npx skills add https://github.com/YiDuandtdt/Bone-Throne --skill unity-yooasset-design-yiduandtdt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This set of design rules provides a canonical guide to safely implementing YooAsset APIs and avoiding common misconfigurations, aligning development with v2.3.18.

Core Features & Use Cases

  • Canonical mapping between EPlayMode InitializeParameters and the corresponding behavior, preventing miswired file-system topologies.
  • Documented lifecycle and patch-flow requirements to prevent resource leaks, stale manifests, and loader conflicts.
  • References to official files (BUILD.md, FILESYSTEM.md, PLAYMODE.md, UPDATE.md, LOADING.md) for deeper guidance and reproducible patterns.

Quick Start

Review these rules before coding YooAsset initialization, asset loading, or patch flow to avoid common misconfigurations.

Frequently Asked Questions about unity-yooasset-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize YooAsset to avoid resource leaks and loader conflicts?

To initialize YooAsset safely, follow the canonical lifecycle order and parameter classes for your specific play mode. This prevents resource leaks, stale manifests, and loader conflicts during the setup process.

What is the correct patch flow for updating manifests in YooAsset?

The correct patch flow requires a specific lifecycle sequence to update manifests and download resources safely. Following these documented patch-flow requirements prevents stale manifests and ensures proper resource unloading.

Does YooAsset initialization behavior change across different play modes?

Yes, YooAsset initialization behavior changes across play modes. There is a canonical mapping between EPlayMode InitializeParameters and file-system topologies, ensuring you configure the correct parameter classes for each mode.

How do I configure file systems in YooAsset without miswiring the topology?

To configure file systems without miswiring the topology, use the canonical mapping between EPlayMode InitializeParameters and the corresponding file system behavior. This ensures correct parameter classes are applied.

What are common anti-patterns when loading assets with YooAsset?

Common anti-patterns include ignoring proper initialization sequencing, using incorrect parameter classes, and failing to follow lifecycle requirements for resource unloading. These misconfigurations lead to loader conflicts and stale manifests.

Are there specific design rules for YooAsset v2.3.18 APIs?

Yes, there are specific design rules to safely implement YooAsset v2.3.18 APIs. These rules standardize correct parameter classes, lifecycle order, and anti-patterns for initialization, patch flow, and asset loading.