[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79QJMS5XJPPJTEWR23PNAXY":3,"skill-same:01M79QJMS5XJPPJTEWR23PNAXY":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79QJMS5XJPPJTEWR23PNAXY","unreal-packaging",null,"Package and ship an Unreal Engine 5 project: the Platforms menu Package Project flow, build configurations (Development vs Shipping), cooking content, packaging settings and the Game Default Map, and command-line builds with RunUAT BuildCookRun. Use when packaging a build, making a shipping build, cooking content, configuring packaging settings, or when the user mentions package Unreal, cook content, shipping build, or BuildCookRun.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Funreal-packaging\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unreal-packaging\ndescription: >\n  Package and ship an Unreal Engine 5 project: the Platforms menu Package Project flow, build\n  configurations (Development vs Shipping), cooking content, packaging settings and the Game\n  Default Map, and command-line builds with RunUAT BuildCookRun. Use when packaging a build,\n  making a shipping build, cooking content, configuring packaging settings, or when the user\n  mentions package Unreal, cook content, shipping build, or BuildCookRun.\n---\n\n# Unreal Packaging & Cooking\n\nTurn a UE5 project into a runnable, distributable build: choose the right build configuration,\ncook content, set the launch map, and package — from the editor or the command line. Targets\n**UE 5.8**.\n\n## When to use\n\n- Use when producing a build (test or release), choosing Development vs Shipping, cooking\n  content, configuring Packaging \u002F Maps & Modes settings, or automating builds with\n  `RunUAT BuildCookRun` for CI.\n- Use when the project has a `*.uproject` and `Config\u002FDefault*.ini`, and the goal is a packaged\n  player rather than running in-editor.\n\n**When *not* to use:** storefront submission\u002Frelease process → `steam-publish` \u002F `itch-publish`.\nEditor-time gameplay\u002Fiteration is not packaging.\n\n## Core workflow\n\n1. **Set the launch map.** Project Settings → **Maps & Modes** → **Game Default Map** is what a\n   packaged build loads first. Wrong\u002Fempty here is the most common \"packaged game is black\"\n   cause.\n2. **Pick the build configuration:** **Development** (default; optimized but keeps logging\u002F\n   stats\u002Fconsole for testing) vs **Shipping** (all optimizations, debugging tools stripped — for\n   release). `DebugGame`\u002F`Debug` are for debugging engine\u002Fgame code and aren't for distribution;\n   `DebugGame` isn't available for Blueprint-only projects.\n3. **Understand cook vs package.** **Cooking** converts assets to the target platform's format.\n   **Staging\u002Fpackaging** copies the compiled executable + cooked content into a standalone,\n   distributable folder, with content in container files (`.pak`, plus `.utoc`\u002F`.ucas` when\n   **Use Io Store** is on, which is the default). Packaging runs a cook as part of it.\n4. **Package from the editor:** the **Platforms** menu → choose the platform (e.g. Windows) →\n   set the Binary Configuration → **Package Project** → pick an output folder.\n5. **Or build from the command line** with the Unreal Automation Tool (`RunUAT BuildCookRun`)\n   for repeatable\u002FCI builds. The **Project Launcher** (Platforms → Project Launcher) saves the\n   same build\u002Fcook\u002Fstage\u002Fdeploy choices as reusable launch profiles.\n6. **Tune Packaging settings** (Project Settings → **Packaging**): which maps\u002Fdirectories to\n   cook, full-rebuild, compression, and whether to build all maps.\n7. **Validate assets before packaging when UnrealEditor-Cmd is available.** Run\n   `UnrealEditor-Cmd \u003CProject>.uproject -run=DataValidation` (`UnrealEditor-Cmd.exe` on\n   Windows) and fix every reported validation error before cooking.\n8. **Verify** by *running the packaged build*, not just by a successful cook — launch the\n   executable and confirm it loads the right map and runs.\n\n## Patterns\n\n### 1. Editor packaging (the menu path)\n\n```text\nPlatforms (toolbar)\n  -> Windows\n     -> Binary Configuration -> Development | Shipping\n     -> Content Management -> Package Project\n  -> choose\u002Fconfirm the staging output folder\n```\n\n### 2. Command-line build with UAT (CI-friendly)\n\n```bash\n# Cook + build + stage + pak + archive a Shipping Windows build.\nRunUAT BuildCookRun \\\n  -project=\"C:\u002FPath\u002FMyGame.uproject\" \\\n  -noP4 -platform=Win64 -clientconfig=Shipping \\\n  -cook -allmaps -build -stage -pak -archive \\\n  -archivedirectory=\"C:\u002FBuilds\u002FMyGame\"\n```\n\n`RunUAT` lives in `Engine\u002FBuild\u002FBatchFiles\u002F` (`RunUAT.bat` on Windows, `RunUAT.sh` on\nmacOS\u002FLinux). Drop `-allmaps` and pass `-map=Map1+Map2` to cook a subset. UE 5.8 adds\nexperimental Windows on Arm game builds: `-clientarchitecture=arm64` (or `arm64+x64` for both\nexecutables side by side); the editor itself is not supported on Arm64 in 5.8.\n\n### 3. Cook only (no packaging), e.g. to refresh content\n\n```bash\nRunUAT BuildCookRun -project=\"C:\u002FPath\u002FMyGame.uproject\" -noP4 \\\n  -platform=Win64 -clientconfig=Development -cook -skipstage\n```\n\n## Pitfalls\n\n- **Packaged build loads a black\u002Fempty level** — Game Default Map isn't set (or that map wasn't\n  cooked). Set it in Maps & Modes and ensure it's included in the cook.\n- **Shipping a Development build** — Development keeps logging\u002Fconsole\u002Fstats and is slower; ship\n  **Shipping**. Conversely, Shipping strips `UE_LOG`\u002Fconsole, so debugging a Shipping-only issue\n  needs Development or `Test`. A Shipping build has no console `quit`, so the game needs its own\n  exit option.\n- **A referenced map\u002Fasset is missing at runtime** — it wasn't cooked. Add it to the Packaging\n  settings' maps\u002Fdirectories to cook, or cook all maps.\n- **Build fails on the platform** — the platform SDK\u002Ftoolchain isn't installed or is too old.\n  For UE 5.8 on Windows that means Visual Studio 2022 17.14+ (2026 recommended), MSVC 14.38+\n  and Windows SDK 10.0.22621.0+; macOS needs Xcode 15.2+. Check the release notes' Platform SDK\n  table for other targets. Console packaging also requires a source build of the engine, not\n  the Launcher build.\n- **`Saved\u002FCooked\u002F\u003CPlatform>` has no `.uasset`\u002F`.uexp` files** — in UE 5.8 Zen Server is the\n  cooked output store by default (unless the project turned it off in Packaging settings). The\n  folder only holds a small `ue.projectstore` marker and the data lives in the Zen data\n  directory. Staging still writes `.pak`\u002F`.utoc`\u002F`.ucas` to the staging folder; ship that\n  folder, not `Saved\u002FCooked`. For team and CI machines Epic recommends\n  `LimitProcessLifetime=false` under `[Zen.AutoLaunch]` in `DefaultEngine.ini` so `zenserver`\n  is not started and stopped on every step; make sure your build automation tolerates that\n  long-running process.\n- **Expecting Blueprint Nativization** — it was **removed in UE5**; don't rely on it for\n  performance. Profile and move hot logic to C++ (`unreal-cpp-gameplay`) instead.\n- **First cook is very slow** — shaders and all assets cook from scratch; subsequent cooks are\n  incremental. Don't mistake a slow first cook for a hang.\n\n## References\n\n- Primary docs: \"Packaging Your Project\"\n  (`https:\u002F\u002Fdev.epicgames.com\u002Fdocumentation\u002Fen-us\u002Funreal-engine\u002Fpackaging-your-project`), the\n  Build Configurations \u002F `BuildCookRun` references, \"Zenserver as Cooked Output Store\"\n  (`https:\u002F\u002Fdev.epicgames.com\u002Fdocumentation\u002Fen-us\u002Funreal-engine\u002Fusing-zen-storage-server-as-cooked-output-store-for-unreal-engine`)\n  and the Platform SDK table in the UE 5.8 release notes\n  (`https:\u002F\u002Fdev.epicgames.com\u002Fdocumentation\u002Fen-us\u002Funreal-engine\u002Funreal-engine-5-8-release-notes`).\n\n## Related skills\n\n- `steam-publish` \u002F `itch-publish` — distributing the packaged build to a storefront.\n- `unreal-cpp-gameplay` — moving hot logic to C++ now that BP nativization is gone.\n","# Unreal Packaging & Cooking\n\nTurn a UE5 project into a runnable, distributable build: choose the right build configuration,\ncook content, set the launch map, and package — from the editor or the command line. Targets\n**UE 5.8**.\n\n## When to use\n\n- Use when producing a build (test or release), choosing Development vs Shipping, cooking\n  content, configuring Packaging \u002F Maps & Modes settings, or automating builds with\n  `RunUAT BuildCookRun` for CI.\n- Use when the project has a `*.uproject` and `Config\u002FDefault*.ini`, and the goal is a packaged\n  player rather than running in-editor.\n\n**When *not* to use:** storefront submission\u002Frelease process → `steam-publish` \u002F `itch-publish`.\nEditor-time gameplay\u002Fiteration is not packaging.\n\n## Core workflow\n\n1. **Set the launch map.** Project Settings → **Maps & Modes** → **Game Default Map** is what a\n   packaged build loads first. Wrong\u002Fempty here is the most common \"packaged game is black\"\n   cause.\n2. **Pick the build configuration:** **Development** (default; optimized but keeps logging\u002F\n   stats\u002Fconsole for testing) vs **Shipping** (all optimizations, debugging tools stripped — for\n   release). `DebugGame`\u002F`Debug` are for debugging engine\u002Fgame code and aren't for distribution;\n   `DebugGame` isn't available for Blueprint-only projects.\n3. **Understand cook vs package.** **Cooking** converts assets to the target platform's format.\n   **Staging\u002Fpackaging** copies the compiled executable + cooked content into a standalone,\n   distributable folder, with content in container files (`.pak`, plus `.utoc`\u002F`.ucas` when\n   **Use Io Store** is on, which is the default). Packaging runs a cook as part of it.\n4. **Package from the editor:** the **Platforms** menu → choose the platform (e.g. Windows) →\n   set the Binary Configuration → **Package Project** → pick an output folder.\n5. **Or build from the command line** with the Unreal Automation Tool (`RunUAT BuildCookRun`)\n   for repeatable\u002FCI builds. The **Project Launcher** (Platforms → Project Launcher) saves the\n   same build\u002Fcook\u002Fstage\u002Fdeploy choices as reusable launch profiles.\n6. **Tune Packaging settings** (Project Settings → **Packaging**): which maps\u002Fdirectories to\n   cook, full-rebuild, compression, and whether to build all maps.\n7. **Validate assets before packaging when UnrealEditor-Cmd is available.** Run\n   `UnrealEditor-Cmd \u003CProject>.uproject -run=DataValidation` (`UnrealEditor-Cmd.exe` on\n   Windows) and fix every reported validation error before cooking.\n8. **Verify** by *running the packaged build*, not just by a successful cook — launch the\n   executable and confirm it loads the right map and runs.\n\n## Patterns\n\n### 1. Editor packaging (the menu path)\n\n```text\nPlatforms (toolbar)\n  -> Windows\n     -> Binary Configuration -> Development | Shipping\n     -> Content Management -> Package Project\n  -> choose\u002Fconfirm the staging output folder\n```\n\n### 2. Command-line build with UAT (CI-friendly)\n\n```bash\n# Cook + build + stage + pak + archive a Shipping Windows build.\nRunUAT BuildCookRun \\\n  -project=\"C:\u002FPath\u002FMyGame.uproject\" \\\n  -noP4 -platform=Win64 -clientconfig=Shipping \\\n  -cook -allmaps -build -stage -pak -archive \\\n  -archivedirectory=\"C:\u002FBuilds\u002FMyGame\"\n```\n\n`RunUAT` lives in `Engine\u002FBuild\u002FBatchFiles\u002F` (`RunUAT.bat` on Windows, `RunUAT.sh` on\nmacOS\u002FLinux). Drop `-allmaps` and pass `-map=Map1+Map2` to cook a subset. UE 5.8 adds\nexperimental Windows on Arm game builds: `-clientarchitecture=arm64` (or `arm64+x64` for both\nexecutables side by side); the editor itself is not supported on Arm64 in 5.8.\n\n### 3. Cook only (no packaging), e.g. to refresh content\n\n```bash\nRunUAT BuildCookRun -project=\"C:\u002FPath\u002FMyGame.uproject\" -noP4 \\\n  -platform=Win64 -clientconfig=Development -cook -skipstage\n```\n\n## Pitfalls\n\n- **Packaged build loads a black\u002Fempty level** — Game Default Map isn't set (or that map wasn't\n  cooked). Set it in Maps & Modes and ensure it's included in the cook.\n- **Shipping a Development build** — Development keeps logging\u002Fconsole\u002Fstats and is slower; ship\n  **Shipping**. Conversely, Shipping strips `UE_LOG`\u002Fconsole, so debugging a Shipping-only issue\n  needs Development or `Test`. A Shipping build has no console `quit`, so the game needs its own\n  exit option.\n- **A referenced map\u002Fasset is missing at runtime** — it wasn't cooked. Add it to the Packaging\n  settings' maps\u002Fdirectories to cook, or cook all maps.\n- **Build fails on the platform** — the platform SDK\u002Ftoolchain isn't installed or is too old.\n  For UE 5.8 on Windows that means Visual Studio 2022 17.14+ (2026 recommended), MSVC 14.38+\n  and Windows SDK 10.0.22621.0+; macOS needs Xcode 15.2+. Check the release notes' Platform SDK\n  table for other targets. Console packaging also requires a source build of the engine, not\n  the Launcher build.\n- **`Saved\u002FCooked\u002F\u003CPlatform>` has no `.uasset`\u002F`.uexp` files** — in UE 5.8 Zen Server is the\n  cooked output store by default (unless the project turned it off in Packaging settings). The\n  folder only holds a small `ue.projectstore` marker and the data lives in the Zen data\n  directory. Staging still writes `.pak`\u002F`.utoc`\u002F`.ucas` to the staging folder; ship that\n  folder, not `Saved\u002FCooked`. For team and CI machines Epic recommends\n  `LimitProcessLifetime=false` under `[Zen.AutoLaunch]` in `DefaultEngine.ini` so `zenserver`\n  is not started and stopped on every step; make sure your build automation tolerates that\n  long-running process.\n- **Expecting Blueprint Nativization** — it was **removed in UE5**; don't rely on it for\n  performance. Profile and move hot logic to C++ (`unreal-cpp-gameplay`) instead.\n- **First cook is very slow** — shaders and all assets cook from scratch; subsequent cooks are\n  incremental. Don't mistake a slow first cook for a hang.\n\n## References\n\n- Primary docs: \"Packaging Your Project\"\n  (`https:\u002F\u002Fdev.epicgames.com\u002Fdocumentation\u002Fen-us\u002Funreal-engine\u002Fpackaging-your-project`), the\n  Build Configurations \u002F `BuildCookRun` references, \"Zenserver as Cooked Output Store\"\n  (`https:\u002F\u002Fdev.epicgames.com\u002Fdocumentation\u002Fen-us\u002Funreal-engine\u002Fusing-zen-storage-server-as-cooked-output-store-for-unreal-engine`)\n  and the Platform SDK table in the UE 5.8 release notes\n  (`https:\u002F\u002Fdev.epicgames.com\u002Fdocumentation\u002Fen-us\u002Funreal-engine\u002Funreal-engine-5-8-release-notes`).\n\n## Related skills\n\n- `steam-publish` \u002F `itch-publish` — distributing the packaged build to a storefront.\n- `unreal-cpp-gameplay` — moving hot logic to C++ now that BP nativization is gone.\n",{"name":5,"description":7},"main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Funreal-packaging","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill unreal-packaging",{"tool":37,"command":38},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill unreal-packaging",{"tool":40,"command":41},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill unreal-packaging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Funreal-packaging\u002FSKILL.md",true,[],[46,52,58,64,70,76],{"skillNo":47,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]