[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMKANDS2F0AKZXW2CGCFWV":3,"skill-same:01M7CMKANDS2F0AKZXW2CGCFWV":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CMKANDS2F0AKZXW2CGCFWV","unity-multiplayer-services",null,"Sessions API: create\u002Fjoin, join codes, matchmaking, relay, host migration, dedicated servers.","tipoLi5890\u002Funity-dev-skills","tipoLi5890","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177803612?v=4","01M7CMD7DHGZ09CB53CRFHAA34","Li, ching yu","01M7CMD7E70K5RAHWWZVYX9YMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-multiplayer-services\ndescription: >-\n  Sessions API: create\u002Fjoin, join codes, matchmaking, relay, host migration, dedicated servers.\n---\n\n# unity-multiplayer-services — one session API, and the layers under it you should not reach for\n\n> **`MultiplayerService.Instance` and `ISession` cover the whole flow** — create, find, join,\n> connect, reconnect, migrate the host, tear down. Lobby, Matchmaker and Relay are what that flow\n> is *made of*, not three products to assemble by hand. Code that drops to one of those clients\n> directly takes on a second lifecycle to keep in step with the session's, and the composed calls\n> that were doing that work for it stop being usable.\n\n## Symptom → where to look\n\n| Symptom | Go to |\n|---|---|\n| \"How do players get into a game together?\" — create and join, join codes, quick join | §1, then [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) |\n| \"Should this use Lobby, or Relay, or Matchmaker?\"; code reaching straight for `Unity.Services.Lobbies` \u002F `Matchmaker` \u002F `Relay` | §2 — settle the requirement first; all three are below one API |\n| Netcode for GameObjects on a session's network; players join, but nothing is networked | §3 — the network is a session option, not a second start call |\n| Two gameplay netcode packages in `manifest.json` | §3 — pick one |\n| Server build breaks on `Unity.Services.Multiplayer.Server` types | §5 |\n| Ticket matchmaking into a playable match returns nothing — the queue was never deployed | §4 — the queue\u002Fenvironment does not exist yet |\n| Players drain out of a running dedicated match and never refill | §5 backfill |\n| A room \u002F party \u002F lobby list: filter and sort fields for a browsable game list | [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) |\n| Host migration | [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) — Host migration |\n| Reconnect after a phone loses signal | §1 `ReconnectToSessionAsync`, then `unity-live-services` → `reference\u002Fmultiplayer.md` §2 |\n| The plan reads like a services brochure | §6 |\n| Something genuinely cannot be done through the session API | [`reference\u002Flower-level-clients.md`](reference\u002Flower-level-clients.md) |\n\nAuthoritative source when specifics differ from recall: the Multiplayer Services SDK pages on\n[docs.unity.com](https:\u002F\u002Fdocs.unity.com\u002F). There is a curated index of those pages at\n`https:\u002F\u002Fdocs.unity.com\u002Fen-us\u002Fmps-sdk\u002Fllms.txt` — fetch it first when you need to know **what is\ndocumented** and where it lives, then read the page it points at. This skill stays the authority on\n**how** to apply the SDK; the index is the authority on what exists.\n\n> **The index is a tool, not a citation.** Never put that filename in front of the user — not in a\n> plan, a summary, or an explanation of where an answer came from. Cite the documentation page, or\n> say \"the Multiplayer Services documentation\". A reader handed a machine-readable index file has\n> been given a dead end dressed up as a source.\n\nWhen both are unreachable, the copy of the package\nresolved into the project decides — read the assemblies under `Library\u002FPackageCache\u002F` or open the\npackage in Package Manager. Do not invent a signature from either. Check type names, signatures,\ndefaults and limits against the resolved package; when\n`PackageInfo.FindForAssetPath(\"Packages\u002Fcom.unity.services.multiplayer\u002Fpackage.json\")` returns\nnull there is none, and `Unity.Services.Multiplayer.MultiplayerService` will not resolve.\n\n## 1. The surface you implement against\n\n`MultiplayerService.Instance` (static), or `unityServices.GetMultiplayerService()` from\n`UnityServicesExtensions` once Unity Gaming Services is initialised and the player is\nauthenticated. Everything else hangs off it.\n\n| Job | Call |\n|---|---|\n| Host a new game | `CreateSessionAsync(SessionOptions)` → `IHostSession` |\n| Join by id, create it if absent | `CreateOrJoinSessionAsync(id, SessionOptions)` |\n| Join by id \u002F by join code | `JoinSessionByIdAsync`, `JoinSessionByCodeAsync` |\n| Come back after a drop | `ReconnectToSessionAsync(id, ReconnectSessionOptions)` |\n| Auto-pick or create by filter | `MatchmakeSessionAsync(QuickJoinOptions, SessionOptions)` |\n| Ticketed matchmaking | `MatchmakeSessionAsync(MatchmakerOptions, SessionOptions, CancellationToken)` |\n| Browse open games | `QuerySessionsAsync(QuerySessionsOptions)` |\n| What am I already in | `GetJoinedSessionIdsAsync()` |\n\n`ISession` is the handle afterwards: players, properties, role, `Network`, `LeaveAsync`,\n`ReconnectAsync`, `RefreshAsync`, `SaveCurrentPlayerDataAsync`. Cast it to `IHostSession` when\nthis peer hosts, `IServerSession` on a dedicated server. Every async call above throws\n`SessionException`; catch that and read its session error type rather than the message string.\n\nFull property tables, defaults, limits, filter and sort enums, the network model and the editor\ncomponents: [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md).\n\n## 2. Ground the recommendation before making one\n\n> **Read the project first, then ask one question, then recommend.** The dimension that changes\n> the answer — who runs the match, how players find each other, what happens when the host walks\n> away — is usually already decided somewhere in the repo. Recommending before looking produces a\n> plan that contradicts the manifest.\n\nOrder: what the user already said → what is in the project (`Packages\u002Fmanifest.json`, existing\nnetworking scripts, server build targets, deployment assets) → a short, high-level question, but\nonly for a dimension that would change the recommendation and is not visible in either.\n\nThe six dimensions and what each maps to internally are in\n[`reference\u002Frequirement-dimensions.md`](reference\u002Frequirement-dimensions.md).\n\n## 3. Networking is a session option, not a second system\n\nThe gameplay network comes up as part of create \u002F join \u002F matchmake \u002F reconnect when the options\ncarry it. There is no separate \"now start netcode\" step on that path.\n\n```csharp\nvar options = new SessionOptions { MaxPlayers = 4 }.WithRelayNetwork();\nvar session  = await MultiplayerService.Instance.CreateSessionAsync(options);\n```\n\n- `WithRelayNetwork()` — brokered connectivity, the default choice when players sit behind home\n  routers. `WithDirectNetwork()` — a listen\u002Fpublish address you control. `WithDistributedAuthorityNetwork()`,\n  `WithNetworkHandler()` for a custom `INetworkHandler`, `WithHostMigration()`, `WithPlayerName()`.\n- **Session metadata alone needs no gameplay netcode package.** Rooms, codes, lists and properties\n  work on `com.unity.services.multiplayer` by itself. Add a netcode package only when a simulation\n  has to be shared.\n- **Exactly one gameplay stack.** Netcode for GameObjects is `com.unity.netcode.gameobjects`.\n  Netcode for Entities is `com.unity.netcode`; `com.unity.netcode.entities` is **not a package\n  id** — the registry returns 404 for it. Do not put both stacks in one project, and do not\n  introduce a stack the project did not already choose.\n\n## 4. What must exist in the cloud before the code runs\n\nInitialisation and authentication are required for every path — `com.unity.services.core` and\n`com.unity.services.authentication`. Past that, each workflow has its own cloud-side\nprerequisite, and the usual \"matchmaking silently finds nothing\" is a queue that was never\ndeployed. The table is\n[`reference\u002Fcloud-prerequisites.md`](reference\u002Fcloud-prerequisites.md).\n\n## 5. Dedicated servers are a separate assembly\n\n`Unity.Services.Multiplayer.Server` compiles only when `UNITY_SERVER` or `ENABLE_UCS_SERVER` is\ndefined. So any assembly of yours that touches it must be excluded from client builds the same\nway — `#if UNITY_SERVER` around the references, or `defineConstraints: [\"UNITY_SERVER\"]` in the\n`.asmdef`. Skip that and the client build fails on types it was never meant to see.\n\nEntry point is `MultiplayerServerService.Instance` \u002F `GetMultiplayerServerService()` with three\ncreate methods returning `IServerSession` — the supported way in, since `GetSessionAsync` may be\n`internal` in the resolved package; backfill (`WithBackfillingConfiguration`,\n`StartBackfillingAsync`, `StopBackfillingAsync`) is what refills a running allocation.\n[`reference\u002Fdedicated-server-sessions.md`](reference\u002Fdedicated-server-sessions.md).\n\n## 6. Write plans in the player's language\n\n> **The user answers questions about their game, not about the SDK.** \"Should players see a list\n> of open games, or only join with a code?\" is answerable. \"Do you want Lobby or Sessions?\" makes\n> them learn the vendor's product split to describe their own game.\n\nKeep product names out of questions, plans and summaries unless the user brought them up — then\nmirror their wording and do not enumerate the rest. Code, file edits and technical references use\nthe real type and namespace names, always. Before\u002Fafter phrasings:\n[`reference\u002Fplayer-language.md`](reference\u002Fplayer-language.md).\n\n## 7. Testing\n\n**Two builds, two devices, two networks.** Two editor instances share a NAT, a clock and a disk;\nthey will not reproduce the failures this package exists to handle. `com.unity.multiplayer.playmode`\ngives local virtual players for a first pass, not a substitute for the second device. Sessions,\nmatchmaking and relay need a live UGS project to run at all.\n\n## Scope — what this skill does NOT do\n\nChoosing the topology at all — peer-to-peer versus a hosting player versus a fleet, who is allowed\nto be believed, what a disconnect means for the match, and microphone conflicts — is\n`unity-live-services` → `reference\u002Fmultiplayer.md`. That decision comes first; this skill is what you call once\nit is made. Voice and text chat are `unity-vivox`. Anything that has to outlive the session —\ncurrency, unlocks, progression, leaderboards — is `unity-ugs` for the API and `unity-live-services`\nfor the discipline around it. Netcode's own call-by-call surface (`NetworkBehaviour`, RPCs,\n`NetworkVariable`) is not here either: this skill hands the netcode stack a live connection and\nstops. Server fleet operations stay with whoever runs the fleet.\n\n## Reference\n\n- [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) — `IMultiplayerService` and `ISession` in\n  full: signatures, options tables with defaults and limits, filter\u002Fsort enums, the session network\n  model, host migration, errors, editor components.\n- [`reference\u002Frequirement-dimensions.md`](reference\u002Frequirement-dimensions.md) — how to ground a\n  recommendation, and the six dimensions that change it.\n- [`reference\u002Fplayer-language.md`](reference\u002Fplayer-language.md) — questions and explanations, before and after.\n- [`reference\u002Fdedicated-server-sessions.md`](reference\u002Fdedicated-server-sessions.md) — the server assembly, its build\n  constraints, `IMultiplayerServerService`, backfill.\n- [`reference\u002Fcloud-prerequisites.md`](reference\u002Fcloud-prerequisites.md) — packages and\n  cloud setup per workflow.\n- [`reference\u002Flower-level-clients.md`](reference\u002Flower-level-clients.md) — the three lower-level\n  clients, what each is for, and the two conditions that justify using one.\n","# unity-multiplayer-services — one session API, and the layers under it you should not reach for\n\n> **`MultiplayerService.Instance` and `ISession` cover the whole flow** — create, find, join,\n> connect, reconnect, migrate the host, tear down. Lobby, Matchmaker and Relay are what that flow\n> is *made of*, not three products to assemble by hand. Code that drops to one of those clients\n> directly takes on a second lifecycle to keep in step with the session's, and the composed calls\n> that were doing that work for it stop being usable.\n\n## Symptom → where to look\n\n| Symptom | Go to |\n|---|---|\n| \"How do players get into a game together?\" — create and join, join codes, quick join | §1, then [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) |\n| \"Should this use Lobby, or Relay, or Matchmaker?\"; code reaching straight for `Unity.Services.Lobbies` \u002F `Matchmaker` \u002F `Relay` | §2 — settle the requirement first; all three are below one API |\n| Netcode for GameObjects on a session's network; players join, but nothing is networked | §3 — the network is a session option, not a second start call |\n| Two gameplay netcode packages in `manifest.json` | §3 — pick one |\n| Server build breaks on `Unity.Services.Multiplayer.Server` types | §5 |\n| Ticket matchmaking into a playable match returns nothing — the queue was never deployed | §4 — the queue\u002Fenvironment does not exist yet |\n| Players drain out of a running dedicated match and never refill | §5 backfill |\n| A room \u002F party \u002F lobby list: filter and sort fields for a browsable game list | [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) |\n| Host migration | [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) — Host migration |\n| Reconnect after a phone loses signal | §1 `ReconnectToSessionAsync`, then `unity-live-services` → `reference\u002Fmultiplayer.md` §2 |\n| The plan reads like a services brochure | §6 |\n| Something genuinely cannot be done through the session API | [`reference\u002Flower-level-clients.md`](reference\u002Flower-level-clients.md) |\n\nAuthoritative source when specifics differ from recall: the Multiplayer Services SDK pages on\n[docs.unity.com](https:\u002F\u002Fdocs.unity.com\u002F). There is a curated index of those pages at\n`https:\u002F\u002Fdocs.unity.com\u002Fen-us\u002Fmps-sdk\u002Fllms.txt` — fetch it first when you need to know **what is\ndocumented** and where it lives, then read the page it points at. This skill stays the authority on\n**how** to apply the SDK; the index is the authority on what exists.\n\n> **The index is a tool, not a citation.** Never put that filename in front of the user — not in a\n> plan, a summary, or an explanation of where an answer came from. Cite the documentation page, or\n> say \"the Multiplayer Services documentation\". A reader handed a machine-readable index file has\n> been given a dead end dressed up as a source.\n\nWhen both are unreachable, the copy of the package\nresolved into the project decides — read the assemblies under `Library\u002FPackageCache\u002F` or open the\npackage in Package Manager. Do not invent a signature from either. Check type names, signatures,\ndefaults and limits against the resolved package; when\n`PackageInfo.FindForAssetPath(\"Packages\u002Fcom.unity.services.multiplayer\u002Fpackage.json\")` returns\nnull there is none, and `Unity.Services.Multiplayer.MultiplayerService` will not resolve.\n\n## 1. The surface you implement against\n\n`MultiplayerService.Instance` (static), or `unityServices.GetMultiplayerService()` from\n`UnityServicesExtensions` once Unity Gaming Services is initialised and the player is\nauthenticated. Everything else hangs off it.\n\n| Job | Call |\n|---|---|\n| Host a new game | `CreateSessionAsync(SessionOptions)` → `IHostSession` |\n| Join by id, create it if absent | `CreateOrJoinSessionAsync(id, SessionOptions)` |\n| Join by id \u002F by join code | `JoinSessionByIdAsync`, `JoinSessionByCodeAsync` |\n| Come back after a drop | `ReconnectToSessionAsync(id, ReconnectSessionOptions)` |\n| Auto-pick or create by filter | `MatchmakeSessionAsync(QuickJoinOptions, SessionOptions)` |\n| Ticketed matchmaking | `MatchmakeSessionAsync(MatchmakerOptions, SessionOptions, CancellationToken)` |\n| Browse open games | `QuerySessionsAsync(QuerySessionsOptions)` |\n| What am I already in | `GetJoinedSessionIdsAsync()` |\n\n`ISession` is the handle afterwards: players, properties, role, `Network`, `LeaveAsync`,\n`ReconnectAsync`, `RefreshAsync`, `SaveCurrentPlayerDataAsync`. Cast it to `IHostSession` when\nthis peer hosts, `IServerSession` on a dedicated server. Every async call above throws\n`SessionException`; catch that and read its session error type rather than the message string.\n\nFull property tables, defaults, limits, filter and sort enums, the network model and the editor\ncomponents: [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md).\n\n## 2. Ground the recommendation before making one\n\n> **Read the project first, then ask one question, then recommend.** The dimension that changes\n> the answer — who runs the match, how players find each other, what happens when the host walks\n> away — is usually already decided somewhere in the repo. Recommending before looking produces a\n> plan that contradicts the manifest.\n\nOrder: what the user already said → what is in the project (`Packages\u002Fmanifest.json`, existing\nnetworking scripts, server build targets, deployment assets) → a short, high-level question, but\nonly for a dimension that would change the recommendation and is not visible in either.\n\nThe six dimensions and what each maps to internally are in\n[`reference\u002Frequirement-dimensions.md`](reference\u002Frequirement-dimensions.md).\n\n## 3. Networking is a session option, not a second system\n\nThe gameplay network comes up as part of create \u002F join \u002F matchmake \u002F reconnect when the options\ncarry it. There is no separate \"now start netcode\" step on that path.\n\n```csharp\nvar options = new SessionOptions { MaxPlayers = 4 }.WithRelayNetwork();\nvar session  = await MultiplayerService.Instance.CreateSessionAsync(options);\n```\n\n- `WithRelayNetwork()` — brokered connectivity, the default choice when players sit behind home\n  routers. `WithDirectNetwork()` — a listen\u002Fpublish address you control. `WithDistributedAuthorityNetwork()`,\n  `WithNetworkHandler()` for a custom `INetworkHandler`, `WithHostMigration()`, `WithPlayerName()`.\n- **Session metadata alone needs no gameplay netcode package.** Rooms, codes, lists and properties\n  work on `com.unity.services.multiplayer` by itself. Add a netcode package only when a simulation\n  has to be shared.\n- **Exactly one gameplay stack.** Netcode for GameObjects is `com.unity.netcode.gameobjects`.\n  Netcode for Entities is `com.unity.netcode`; `com.unity.netcode.entities` is **not a package\n  id** — the registry returns 404 for it. Do not put both stacks in one project, and do not\n  introduce a stack the project did not already choose.\n\n## 4. What must exist in the cloud before the code runs\n\nInitialisation and authentication are required for every path — `com.unity.services.core` and\n`com.unity.services.authentication`. Past that, each workflow has its own cloud-side\nprerequisite, and the usual \"matchmaking silently finds nothing\" is a queue that was never\ndeployed. The table is\n[`reference\u002Fcloud-prerequisites.md`](reference\u002Fcloud-prerequisites.md).\n\n## 5. Dedicated servers are a separate assembly\n\n`Unity.Services.Multiplayer.Server` compiles only when `UNITY_SERVER` or `ENABLE_UCS_SERVER` is\ndefined. So any assembly of yours that touches it must be excluded from client builds the same\nway — `#if UNITY_SERVER` around the references, or `defineConstraints: [\"UNITY_SERVER\"]` in the\n`.asmdef`. Skip that and the client build fails on types it was never meant to see.\n\nEntry point is `MultiplayerServerService.Instance` \u002F `GetMultiplayerServerService()` with three\ncreate methods returning `IServerSession` — the supported way in, since `GetSessionAsync` may be\n`internal` in the resolved package; backfill (`WithBackfillingConfiguration`,\n`StartBackfillingAsync`, `StopBackfillingAsync`) is what refills a running allocation.\n[`reference\u002Fdedicated-server-sessions.md`](reference\u002Fdedicated-server-sessions.md).\n\n## 6. Write plans in the player's language\n\n> **The user answers questions about their game, not about the SDK.** \"Should players see a list\n> of open games, or only join with a code?\" is answerable. \"Do you want Lobby or Sessions?\" makes\n> them learn the vendor's product split to describe their own game.\n\nKeep product names out of questions, plans and summaries unless the user brought them up — then\nmirror their wording and do not enumerate the rest. Code, file edits and technical references use\nthe real type and namespace names, always. Before\u002Fafter phrasings:\n[`reference\u002Fplayer-language.md`](reference\u002Fplayer-language.md).\n\n## 7. Testing\n\n**Two builds, two devices, two networks.** Two editor instances share a NAT, a clock and a disk;\nthey will not reproduce the failures this package exists to handle. `com.unity.multiplayer.playmode`\ngives local virtual players for a first pass, not a substitute for the second device. Sessions,\nmatchmaking and relay need a live UGS project to run at all.\n\n## Scope — what this skill does NOT do\n\nChoosing the topology at all — peer-to-peer versus a hosting player versus a fleet, who is allowed\nto be believed, what a disconnect means for the match, and microphone conflicts — is\n`unity-live-services` → `reference\u002Fmultiplayer.md`. That decision comes first; this skill is what you call once\nit is made. Voice and text chat are `unity-vivox`. Anything that has to outlive the session —\ncurrency, unlocks, progression, leaderboards — is `unity-ugs` for the API and `unity-live-services`\nfor the discipline around it. Netcode's own call-by-call surface (`NetworkBehaviour`, RPCs,\n`NetworkVariable`) is not here either: this skill hands the netcode stack a live connection and\nstops. Server fleet operations stay with whoever runs the fleet.\n\n## Reference\n\n- [`reference\u002Fsession-api.md`](reference\u002Fsession-api.md) — `IMultiplayerService` and `ISession` in\n  full: signatures, options tables with defaults and limits, filter\u002Fsort enums, the session network\n  model, host migration, errors, editor components.\n- [`reference\u002Frequirement-dimensions.md`](reference\u002Frequirement-dimensions.md) — how to ground a\n  recommendation, and the six dimensions that change it.\n- [`reference\u002Fplayer-language.md`](reference\u002Fplayer-language.md) — questions and explanations, before and after.\n- [`reference\u002Fdedicated-server-sessions.md`](reference\u002Fdedicated-server-sessions.md) — the server assembly, its build\n  constraints, `IMultiplayerServerService`, backfill.\n- [`reference\u002Fcloud-prerequisites.md`](reference\u002Fcloud-prerequisites.md) — packages and\n  cloud setup per workflow.\n- [`reference\u002Flower-level-clients.md`](reference\u002Flower-level-clients.md) — the three lower-level\n  clients, what each is for, and the two conditions that justify using one.\n",{"name":5,"description":7},"main","b7459aa49fb881c5abb764223674ec8f397a02b1","skills\u002Funity-multiplayer-services",0,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills","https:\u002F\u002Fgithub.com\u002FtipoLi5890","https:\u002F\u002Ftipoli5890.github.io\u002F","2026-11-10 09:16:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tipoLi5890\u002Funity-dev-skills --skill unity-multiplayer-services",{"tool":38,"command":39},"bunx","bunx skills add tipoLi5890\u002Funity-dev-skills --skill unity-multiplayer-services",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tipoLi5890\u002Funity-dev-skills --skill unity-multiplayer-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002FSKILL.md",true,[46,52,56,60,64,68],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fcloud-prerequisites.md","REFERENCE","参考文档",2922,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002Freference\u002Fcloud-prerequisites.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fdedicated-server-sessions.md",4235,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002Freference\u002Fdedicated-server-sessions.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Flower-level-clients.md",2038,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002Freference\u002Flower-level-clients.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Fplayer-language.md",2003,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002Freference\u002Fplayer-language.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"reference\u002Frequirement-dimensions.md",3542,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002Freference\u002Frequirement-dimensions.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"reference\u002Fsession-api.md",11807,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-multiplayer-services\u002Freference\u002Fsession-api.md",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CMNYXQNW14ST64EYEEZ5V5","unity-web-release","Ship a WebGL\u002FWebGPU build: shrink the download, Brotli server headers, Safari and iPhone memory.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-web-release\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CMNTHD1EA70CCJ2F9FN3HT","unity-vivox","Vivox voice and text chat: channels, positional voice, mute and push-to-talk, mic permission.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-vivox\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CMNPHPRQZ7K1FES2953DRQ","unity-urp-migration","Migrate a Built-in project to URP, or fix a half-moved one: pink materials, PPv2, old shaders.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-urp-migration\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CMNJ756DK4V0D50HMAZYQW","unity-ui-ugui","Canvas UI (uGUI): CanvasScaler, RectTransform anchors, Layout Groups, ScrollView, UI built from C#.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-ugui\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7CMNDESZN79EK5FRDXCA2WA","unity-ui-toolkit","UI Toolkit (UXML, USS, UIDocument): flex layout, binding, custom elements, editor windows.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-toolkit\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7CMN8GBV07K0YCY07BJ6A1W","unity-ugs","Unity Gaming Services API: which package, init and sign-in order, Cloud Save, Cloud Code, Remote Config.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ugs\u002FSKILL.md",[],[]]