返回提示词目录第 1326 页

制定游戏引擎版本升级方案

梳理引擎升级收益与兼容风险,制定分支备份、迁移步骤、试玩验证和失败回退计划。

完整提示词

<context>
A game developer wants to move {{engine}} from {{from_version}} to {{to_version}}. Engine upgrades are riskier than library upgrades: opening the project in the new editor rewrites scene, prefab and resource files in place, re-imports every asset (which can take hours and changes texture and audio settings), and may convert shaders or materials one way. Third-party plugins and store packages are often the real blocker. Rendering changes alter how the game looks even when nothing errors, and physics or timing changes alter how it feels. Upgrading close to a release date, on a console certification schedule, or mid-jam is usually the wrong call.
{{#project_notes}}
Project notes:
{{project_notes}}
{{/project_notes}}
</context>

<task>
1. Decide go or wait: is the jump supported directly or does it need intermediate versions; is the target a long-term support or stable release; what the upgrade buys (features, platform requirements, store or console requirements, bug fixes); and how close the next release is.
2. Preparation: commit everything, tag the last good build, create an upgrade branch, confirm version control handles the engine's large and binary files (LFS or equivalent) and ignores generated folders (for example `.godot/` or `Library/`), record a baseline (build size, load times, frame time on target hardware, a short gameplay capture of key scenes), and freeze content changes or plan how to merge them.
3. Inventory what will break, using the official upgrade or migration guide for every version crossed (ask the user to paste it if you cannot read it, and do not list changes from memory as fact):
   - Scripting API renames and removals, and any automatic conversion tool the engine provides plus what it misses.
   - Rendering: pipeline or renderer changes, lighting, post-processing, colour space, shader language changes and custom shaders that need rewriting.
   - Assets: re-import settings, compression formats per platform, animation and import pipeline changes.
   - Physics, input, UI, audio and networking changes that alter feel or behaviour.
   - Plugins and packages: support status for the target version for each one, with a replacement or removal decision.
   - Build and platform: SDK and toolchain versions, export templates, signing, console or store requirements.
4. Write the upgrade steps in order: plugins first (update or remove), run the engine's converter on the branch, fix compile errors, then warnings, then rendering, then feel.
5. Write a playtest checklist that compares against the baseline: every scene loads, save files from the old version load, input on each device type, audio, UI scaling, performance on minimum-spec hardware, and a full build on each target platform.
6. Define rollback: the tag to return to and the rule for abandoning the branch.
</task>

<constraints>
- Never suggest opening the main project in the new editor without a backup branch or tag first.
- Do not invent API names, version numbers or plugin compatibility; say what to check and where (official migration guide, release notes, plugin page).
- If the exact versions, platforms or plugin list are missing and they change the plan, ask, and mark assumptions as [X].
- Players' existing save files must keep working, or the plan must say how they are migrated.
{{> output/uncertainty}}
</constraints>

<output_format>
## Go or wait
Recommendation in one line, then the reasons.

## Preparation
Checklist.

## What will break
Table: area | change | where it hits this project | fix or decision | source to check.

## Upgrade steps
Numbered steps.

## Playtest checklist
Checklist grouped by scene, platform and system, each compared with the baseline.

## Rollback
The tag, and when to abandon.

## Open questions
Bullets.
</output_format>

可替换内容

  • {{engine}}
  • {{from_version}}
  • {{to_version}}
  • {{#project_notes}}
  • {{project_notes}}
  • {{/project_notes}}
  • {{> output/uncertainty}}
  • [X]

分类与标签

编程开发、引擎升级、兼容性检查、迁移计划、版本回退

前往 AI 图片创作