Add northern pursuit scenario
This commit is contained in:
@@ -1,15 +1,16 @@
|
||||
# Godot 4.6 Migration
|
||||
|
||||
This project targets Godot 4 and is being moved toward Godot 4.6 as the active editor baseline.
|
||||
This project targets Godot 4.6 as the active editor baseline.
|
||||
|
||||
## Current Risk Profile
|
||||
|
||||
- The project is a simple Godot 4 `Node2D` application with data-driven JSON content.
|
||||
- There are no addons, imported art assets, shaders, TileMaps, 3D physics scenes, or export presets yet.
|
||||
- The current renderer is explicitly set to `gl_compatibility`, so new-project rendering defaults in Godot 4.6 should not silently change the existing project renderer.
|
||||
- `project.godot` still advertises `config/features=PackedStringArray("4.2")`; let the Godot 4.6 editor update project files instead of editing generated scene/resource formats by hand.
|
||||
- `project.godot` advertises `config/features=PackedStringArray("4.6")`.
|
||||
- Godot 4.6 script UID sidecar files (`*.gd.uid`) are part of the migrated project metadata and should stay versioned.
|
||||
|
||||
## Before Opening In 4.6
|
||||
## Before Opening In 4.6 From An Older Checkout
|
||||
|
||||
1. Create a backup or initialize version control before the editor writes migration changes.
|
||||
2. Run the data/readiness check:
|
||||
@@ -24,7 +25,7 @@ powershell -NoProfile -ExecutionPolicy Bypass -File tools\check_godot46_readines
|
||||
$env:GODOT_BIN = "C:\Path\To\Godot_v4.6-stable_win64.exe"
|
||||
```
|
||||
|
||||
## Editor Migration Steps
|
||||
## Editor Migration Steps From An Older Checkout
|
||||
|
||||
1. Open the project folder in Godot 4.6.
|
||||
2. Let the editor import the project and accept any project-file migration prompt.
|
||||
|
||||
Reference in New Issue
Block a user