What causes the instance() vs instantiate() error after upgrading to Godot 4?

Godot 4 renamed PackedScene.instance() to instantiate() — any Godot 3 tutorial code or ported script calling the old name fails with a nonexistent-function error.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix “Function 'instance()' not found in base 'PackedScene'” in Godot 4

Q: How do you fix the instance() vs instantiate() error after upgrading to Godot 4?

Replace scene.instance() with scene.instantiate() project-wide, and watch for the handful of sibling renames (yield→await, export→@export) that travel with old code.

Quick answer: Replace scene.instance() with scene.instantiate() project-wide, and watch for the handful of sibling renames (yield→await, export→@export) that travel with old code.

This one-line rename bites everyone following Godot 3 tutorials in Godot 4. The fix is trivial; the value is knowing the related renames so you fix them in one pass. Here they are.

How to fix it

1. Do the project-wide replace

Search for .instance() and replace with .instantiate() — in scripts only; check matches so you do not touch unrelated identifiers.

2. Fix the travel companions

Godot 3 code also carries yield( (now await), export var (now @export var), onready (now @onready), and KinematicBody2D (now CharacterBody2D).

3. Re-check the tutorial's engine version

When following guides, match their Godot major version or translate as you go — the 3-to-4 API gap is wide enough that mixed code fails constantly.

4. Lean on the editor's hints

The script editor's autocomplete and warnings flag nonexistent methods as you type — trust the red underline over the tutorial.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.