thedivergentai/game-design-agentic-skills

godot-version-migration

Full-history Godot version migration hub.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/thedivergentai/game-design-agentic-skills --skill godot-version-migration

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Godot Version Migration

Orchestrator for engine version upgrades from early Godot through the library target. Domain Skills document current APIs; this hub owns the upgrade path.

Library target: Godot 4.7+

Corpus: docs changelog · interactive changelog · download archive · GitHub releases · migrating index

NEVER Do

  • NEVER skip majors — route 1.x → 2.x → latest 3.x → 4.0 before any 4.x minor ladder.
  • NEVER skip 4.x hops — upgrade 4.0 → 4.1 → … → 4.7 one minor at a time; stabilize after each hop.
  • NEVER claim automatic 1.x→4.x conversion or bit-exact autopilot.
  • NEVER treat Domain Skill bodies as migration changelogs — load references/<topic>.md (mirrored from each skill’s references/migration-notes.md).
  • NEVER load all module notes at once — only subsystems present in the project.
  • NEVER mix server/client Godot minors for high-level multiplayer (especially across 4.2→4.3 SceneMultiplayer protocol changes).
  • NEVER choose Mesh “Restart & Upgrade” without VCS backup (4.1→4.2 mesh format).
  • NEVER run the 3→4 converter without a full backup (tool does not backup).

Version detect

  1. Read project.godot (config_version, config/features) or legacy engine.cfg.
  2. Ask the user if files are ambiguous.
  3. Map to an era in references/era-index.md.

Workflow router (MANDATORY)

Detected eraLoadDo NOT
1.x / early 2legacy/pre-2-context.mdInvent a 1→4 converter
2.xlegacy/2-to-3.md then stabilize on latest 3.xJump straight to 4.7 notes
3.xbridges/3-to-4.md + official 3→4 guideSkip latest-3.x stabilize gate
4.x < 4.7Official hop guide + hop-index.md module notes for touched systemsSkip minors
Already 4.7+godot-master / Domain SkillsTreat this hub as a coding tutorial

Steps (4.x minors)

  1. While current < 4.7, perform exactly one hop to current + 0.1.
  2. Open the official upgrading page for the destination version.
  3. From hop-index.md, open only module notes for subsystems present in the project.
  4. Apply fixes; open in the new editor; playtest; repeat.

Hop table

Majors / bridges

EraResource
1.x archaeologylegacy/pre-2-context.md
2.x → 3.xlegacy/2-to-3.md
3.x → 4.0bridges/3-to-4.md · official guide
Ladder overviewera-index.md

4.x minors

HopOfficial guide
4.0 → 4.1https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.1.html
4.1 → 4.2https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.2.html
4.2 → 4.3https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.3.html
4.3 → 4.4https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.4.html
4.4 → 4.5https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.5.html
4.5 → 4.6https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.6.html
4.6 → 4.7https://docs.godotengine.org/en/stable/tutorials/migrating/upgradingtogodot_4.7.html

Cross-skill checklist: references/hop-index.md

Module directory

Mirrored Domain Skill migration notes live at references/<topic>.md (e.g. references/2d-physics.md). Hub-native legacy/, bridges/, and era-index.md are not Domain Skill mirrors.

text
sync_godot_version_migration.py --all

Reference

Official docs

Related Skills

Master

  • godot-master — Library router for current Domain Skill modules after migration is complete.

Downstream / consumers

  • godot-analyst — Score architecture on the target APIs after hops land.
  • godot-auditor — Never-list / legacy-syntax verification after upgrades.
  • godot-builder — CI / headless bake against the new engine target after each hop.

Complements

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills