Fix: Godot Control Anchor Preset Resets on Reload

You set a Control to “Full Rect” preset in the editor. Save the scene, reload, and the preset reverts to “Custom”. The element looks right, but the dropdown shows custom — and a code generator that reads the preset name fails to detect the intended layout.

How Anchor Presets Actually Work

The preset dropdown in the Inspector is not a serialized property. It’s a computed display based on the four anchor_* values and four offset_* values. A “Full Rect” preset means:

anchor_left   = 0.0
anchor_right  = 1.0
anchor_top    = 0.0
anchor_bottom = 1.0
offset_left   = 0.0
offset_right  = 0.0
offset_top    = 0.0
offset_bottom = 0.0

If any of those eight values drifts — for example, you dragged the corner by a pixel during editing — the preset displayed becomes “Custom”. Save and reload: the offsets persist; the dropdown remains custom.

Fix 1: Apply Preset via Script at _Ready

extends Control

func _ready():
    set_anchors_and_offsets_preset(PRESET_FULL_RECT)

This resets all eight properties to the canonical preset values regardless of what the editor saved. Use when you specifically want a node to always behave as a known preset at runtime.

Fix 2: Clean Up the Saved .tscn

For scene-driven layouts, open the .tscn file in a text editor and replace drifting values with the canonical preset constants. For PRESET_FULL_RECT on a default Control, the entire [node] block contains no anchor/offset overrides — the inherited defaults are exactly the preset values.

Or in the editor, click the preset dropdown to re-apply “Full Rect”. The Inspector writes canonical values back to the saved scene.

Fix 3: keep_offsets for Preserving Layout

When swapping presets at runtime without moving the visual, pass keep_offsets=true:

set_anchors_and_offsets_preset(PRESET_CENTER, PRESET_MODE_KEEP_SIZE, 0)

The anchor ratios change but the offsets are recomputed to keep the visual rect identical. Useful for reflowing UI between screen sizes.

Verifying

Compare the .tscn diff before and after reload. Drift values like offset_right = -1.0 or anchor_left = 0.001 reveal the cause. After applying script-based preset reset, save and confirm the scene file no longer contains drifting values.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Godot Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“The preset is what you see, not what’s saved. Reset via script for runtime certainty, or click the preset again in the editor.”

Drag-to-resize in the 2D editor can introduce sub-pixel anchor drift — click your preset once after any visual adjustment to snap it back to canonical values.