← ExekiteCONTENT HISTORY
WHAT CHANGED
Update to Exekite
Snapshot Nov 17, 2026 · 12:11 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Exekite and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "For Exekite-hosted Godot games only. Godot 3 → 4 migration cheat sheet. Use when written or encountered GDScript shows a Godot-3 idiom — `KinematicBody2D`, string-based 4-arg `connect()`, `yield(...)`, `OS.get_ticks_msec`, `export var`, or a `Pool*Array`. Covers body renames, connect changes, exports, lifecycle, math/utility relocations.",
"included_files": [],
"name": "godot-4-syntax-vs-3",
"skill_md_contents": "---\nname: godot-4-syntax-vs-3\ndescription: \"For Exekite-hosted Godot games only. Godot 3 → 4 migration cheat sheet. Use when written or encountered GDScript shows a Godot-3 idiom — `KinematicBody2D`, string-based 4-arg `connect()`, `yield(...)`, `OS.get_ticks_msec`, `export var`, or a `Pool*Array`. Covers body renames, connect changes, exports, lifecycle, math/utility relocations.\"\n---\n\n# Godot 3 → 4 syntax migration\n\nMost LLM training data leans Godot 3, so this is the failure mode to defeat first. The tables below give the Godot-4 form for each; `start_check` with the parse profile catches what slips through.\n\n## Physics bodies — the renames you must memorize\n\n| Godot 3 | Godot 4 |\n|---|---|\n| `KinematicBody2D` / `KinematicBody` | `CharacterBody2D` / `CharacterBody3D` |\n| `RigidBody2D` (kinematic mode) | `RigidBody2D` with `freeze = true` and `freeze_mode = FREEZE_MODE_KINEMATIC` |\n| `move_and_slide(velocity, Vector2.UP)` | set `velocity` as a property, then call `move_and_slide()` (no args) |\n| `is_on_floor()` after `move_and_slide` | identical, but only valid AFTER the call |\n| `Transform` (3D) | `Transform3D` |\n\n```gdscript\n# WRONG (Godot 3)\nextends KinematicBody2D\nvar velocity := Vector2.ZERO\nfunc _physics_process(delta):\n velocity = move_and_slide(velocity, Vector2.UP)\n\n# RIGHT (Godot 4)\nextends CharacterBody2D\nfunc _physics_process(delta: float) -> void:\n velocity.y += 980.0 * delta\n move_and_slide()\n```\n\n## Signals — the connect form changed\n\n```gdscript\n# WRONG (Godot 3 string-based connect)\nbutton.connect(\"pressed\", self, \"_on_button_pressed\")\n\n# RIGHT (Godot 4 — pass the Callable directly)\nbutton.pressed.connect(_on_button_pressed)\n\n# disconnect:\nbutton.pressed.disconnect(_on_button_pressed)\n```\n\nSignal declaration in the script body:\n```gdscript\nsignal hit(damage: int) # typed args supported in 4\nhit.emit(10) # Godot 3 used `emit_signal(\"hit\", 10)`\n```\n\n## Exports\n\n```gdscript\n# WRONG\nexport var speed := 100.0\nexport(int, 1, 10) var difficulty := 1\n\n# RIGHT\n@export var speed: float = 100.0\n@export_range(1, 10) var difficulty: int = 1\n@export_group(\"Movement\") # groups in the Inspector\n@export_range(0.0, 1.0, 0.05) var jump_cutoff: float = 0.4\n```\n\n**Give `@export_range` an explicit step when increments matter.**\n`@export_range(0.0, 10.0, 0.25)` retains the 0.25 increment in its property\nhint. Omitting the step still exports a range: integers default to 1, while\nfloat increments depend on the Inspector's default-float-step setting.\nThe two-argument form is valid; it does not force float values to integers.\n\n`@onready` is unchanged in spirit; the syntax is the same `@onready var sprite: Sprite2D = $Sprite2D`.\n\n## Lifecycle and types\n\n```gdscript\n# WRONG\nfunc _ready():\n pass\n\n# RIGHT — always type the return, even when it's void\nfunc _ready() -> void:\n pass\n```\n\n`_process(delta)` and `_physics_process(delta)` both take `delta: float`. The class declarations:\n\n```gdscript\nclass_name PlayerStats\nextends Resource\n```\n\n## Function and global utility moves\n\n| Godot 3 | Godot 4 |\n|---|---|\n| `OS.get_ticks_msec()` | `Time.get_ticks_msec()` |\n| `OS.get_unix_time()` | `Time.get_unix_time_from_system()` |\n| `yield(timer, \"timeout\")` | `await timer.timeout` (or `await get_tree().create_timer(0.5).timeout`) |\n| `Sprite` | `Sprite2D` |\n| `AnimatedSprite` | `AnimatedSprite2D` (or 3D) |\n| `Tween` (node) | call `create_tween()` per-tween; no Tween node |\n| `Reference` | `RefCounted` |\n| `PoolByteArray` | `PackedByteArray` (and similar `Pool*Array` → `Packed*Array`) |\n| `range(0, 5, 1)` | unchanged |\n\n## `await` everywhere `yield` lived\n\n```gdscript\n# WRONG (3): yield(get_tree().create_timer(1.0), \"timeout\")\n# RIGHT (4):\nawait get_tree().create_timer(1.0).timeout\n\n# Wait for a signal:\nawait tween.finished\nawait body_entered # current node's signal\n```\n\nForgetting `await` is the most common subtle bug — the next line runs immediately, the timer fires later, and behavior splits.\n\n## Tween — node → builder\n\n```gdscript\n# Godot 3: had a Tween node; you'd call interpolate_property\n# Godot 4: per-call builder, returned by create_tween()\nvar t := create_tween().set_trans(Tween.TRANS_SINE).set_ease(Tween.EASE_OUT)\nt.tween_property(sprite, \"position:y\", -10.0, 0.3)\nt.tween_property(sprite, \"position:y\", 0.0, 0.3)\nawait t.finished\n```\n\nFor looping tweens, `create_tween().set_loops()`. Don't reuse a tween across calls — make a new one.\n\n## Inputs are unchanged in spirit\n\n`Input.is_action_just_pressed(\"ui_accept\")` still works. `Input.get_axis(\"ui_left\", \"ui_right\")` returns a float in [-1, 1] and is the idiomatic way to get a horizontal direction. Only the harness's pre-bound actions exist: ui_left/ui_right/ui_up/ui_down (WASD + arrows), ui_accept, ui_cancel, pause, fire (left mouse), interact (E).\n\n## Resources — same idea, simpler typing\n\n```gdscript\n# Define a typed Resource\nclass_name PlayerStats\nextends Resource\n@export_range(50.0, 400.0, 5.0) var speed: float = 130.0\n\n# Use it from a script\n@export var stats: PlayerStats # slot in the Inspector\n```\n\nThe `.tres` saves the values; the script provides the schema. Some Exekite games pair `<id>_stats.gd` with a `stats.tres` — match that shape where the game you are editing already uses it.\n\n## Anti-patterns — a checklist before claiming done\n\n- [ ] No `KinematicBody*`, no `Sprite` (2D), no `AnimatedSprite` (2D).\n- [ ] All `connect()` calls are the callable form: `signal.connect(method)`.\n- [ ] No `yield(...)` — `await` only.\n- [ ] No `OS.get_ticks_msec()` — `Time.*`.\n- [ ] All `func`s have a return type (or `-> void`).\n- [ ] No 4-arg `move_and_slide` — set velocity, call no-arg.\n- [ ] All `export` annotations use `@export` form.\n"
}SHA-256 of public snapshot: 69f552807529d1cd06a53fd2c1ea2c0ff83504c627f076351ca26119b95657c9