editor-undo-redo-contract

To ensure safe Godot editor mutations, you must wrap plugin changes in explicit undo actions using EditorUndoRedoManager. This requires matching do and undo operations to maintain deterministic scene history and prevent file corruption during automated refactoring.

EditorUndoRedoManager is Godot's built-in system for tracking scene and resource state changes. You need it when developing editor plugins that modify nodes or resources, ensuring that batch edits, autofixes, and tool actions can be safely undone.

Handling undo and redo for batch edits in a Godot editor tool requires grouping all property changes into a single EditorUndoRedoManager action. You must provide explicit do/undo parity for every mutated node to guarantee the batch reverts cleanly.

Godot undo redo works correctly across multiple scenes only when provided with a custom context. Managing multi-scene editor contexts requires explicit context assignment to keep scene history accurate and prevent cross-scene state corruption.

Godot plugin undo actions cause scene history errors when there is a mismatch between do and undo operations. Ensuring deterministic undo requires exact do/undo parity for every modified property, preventing broken history entries during automated refactoring.