Godot 入門：VS Code と Codex 拡張で 2D ゲームを作る開発フロー

1
2
3
4

エディタ
→ エディタ設定
→ テキストエディタ
→ 外部

1

外部エディタを使用

1

where code.cmd

1

C:\Users\あなたのユーザー名\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd

1

{project} --goto {file}:{line}:{col}

1
2
3
4
5

エディタ設定
→ テキストエディタ
→ 動作
→ ファイル
→ Auto Reload Scripts on External Change

1
2
3
4
5
6
7

my_game/
├─ project.godot
├─ AGENTS.md
├─ scenes/
├─ scripts/
├─ assets/
└─ .vscode/

1
2

cd D:\GodotProjects\my_game
code .

1

.vscode/launch.json

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Godot プロジェクトを実行",
            "type": "godot",
            "request": "launch",
            "project": "${workspaceFolder}",
            "debugServer": 6006
        }
    ]
}

1

godotTools.editorPath.godot4

1

D:\Programs\Godot\Godot_v4.7-stable_win64.exe

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

# Godot Project Instructions

This is a Godot 4.x project using GDScript.

## Coding Rules

- Use only Godot 4.x APIs.
- Do not use old Godot 3.x syntax.
- Prefer static typing in GDScript.
- Use snake_case for variables and functions.
- Use PascalCase for class_name.
- Prefer @onready for node references.
- Use @export for configurable parameters.
- Do not rename existing nodes casually.
- Do not create an overly complex Manager architecture.
- Implement only one independently testable feature at a time.

## File Responsibilities

- scenes/ stores .tscn scenes.
- scripts/ stores .gd scripts.
- assets/ stores images, fonts, and sounds.
- ui/ stores UI scenes and UI scripts.

## Scene Modification Rules

- Before editing .tscn files, read and understand the existing node structure.
- Do not guess node names or NodePath values.
- For complex scenes, prefer telling the user to create nodes manually in the Godot editor.
- Unless the task explicitly asks for it, do not rewrite .tscn files broadly.

## Verification Rules

After finishing a task:

1. Check GDScript syntax.
2. Check resource paths and node paths.
3. List modified files.
4. Explain how to test in Godot.
5. Do not claim it ran successfully unless you actually verified it.

1

git init

1
2
3
4
5

.godot/
.vscode/*.log
*.tmp
export/
build/

1
2

git add .
git commit -m "初始化 Godot 项目"

1

2D 見下ろし型シューティングのプロトタイプ

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16

my_game/
├─ project.godot
├─ AGENTS.md
├─ scenes/
│  ├─ main.tscn
│  ├─ player.tscn
│  ├─ bullet.tscn
│  └─ enemy.tscn
├─ scripts/
│  ├─ main.gd
│  ├─ player.gd
│  ├─ bullet.gd
│  └─ enemy.gd
├─ ui/
│  └─ hud.tscn
└─ assets/

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17

This is a new Godot 4.x GDScript project.

I want to build a minimal 2D top-down shooter.

Do not modify files yet.

First complete the following:

1. Read project.godot and the current directory structure.
2. Check whether the project already has a main scene configured.
3. Design the minimum viable version.
4. Break the work into small tasks that can each be run and verified independently.
5. Clarify which nodes I should create manually in the Godot editor.
6. Clarify which scripts are suitable for you to write.
7. Use only Godot 4.x APIs.
8. Do not generate the whole game at once.
9. Do not directly write complex .tscn files.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21

Now implement only player movement.

Scene structure:

Player: CharacterBody2D
├─ Sprite2D
└─ CollisionShape2D

Script path:
scripts/player.gd

Requirements:

- Use Input.get_vector
- Use move_and_slide
- Use static typing
- Use @export for movement speed
- Do not rename scene nodes
- Do not implement shooting, health, or animation
- After editing, tell me which Input Map actions I need to configure
- Provide test steps

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

Godot でノードを作る
        ↓
VS Code で Codex にスクリプトを書かせる
        ↓
Git diff を確認する
        ↓
F5 で実行する
        ↓
完全なエラーを Codex に渡す
        ↓
最小修正を依頼する
        ↓
動いたら Git commit

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

The following runtime error occurred:

Paste the full error message

Please identify the root cause first.

Requirements:
- Check the actual node structure and NodePath values;
- Make only the smallest change;
- Do not refactor unrelated code;
- Do not modify features that already work;
- After editing, explain why the error happened.