Skip to content

[godot] Addresses #2899, #2980, #2985#2996

Merged
lukeeingram merged 3 commits into4.2from
4.2-godot-fixes-2899-2980-2985
Dec 16, 2025
Merged

[godot] Addresses #2899, #2980, #2985#2996
lukeeingram merged 3 commits into4.2from
4.2-godot-fixes-2899-2980-2985

Conversation

@lukeeingram
Copy link
Collaborator

Addresses the loader/saver registration issue in #2899.

Additionally, makes it such that you can adjust the SpineSkeletonData in the inspector without crashes. This appears to have been caused by a dangling pointer.

Finally, double-clicking on JSON in the inspector opens the text editor and does not crash the Godot editor.

Addresses the loader/saver registration issue in #2899.

Additionally, makes it such that you can adjust the SpineSkeletonData in
the inspector without crashes. This appears to have been caused by a
dangling pointer.

Finally, double-clicking on JSON in the inspector opens the text editor
and does not crash the Godot editor.
Additionally, CI builds were failing due to the commit where SpineSkin
had an init() method added, but this caused Godot 3.x builds to fail.

Our formatter was also run, so it should no longer fail the format
check.
@lukeeingram lukeeingram merged commit de8ae9e into 4.2 Dec 16, 2025
35 of 36 checks passed
@lukeeingram lukeeingram deleted the 4.2-godot-fixes-2899-2980-2985 branch December 16, 2025 00:30
badlogic added a commit that referenced this pull request Dec 16, 2025
Port from 4.2 branch (PR #2996):
- Fix dangling pointer in SpineSkeletonDataResource destructor by using
  ObjectID validation instead of direct EditorFileSystem access
- Register format loaders/savers at CORE level for GDExtension to fix
  loader/saver registration issues (#2899)

Additional fix for GDExtension:
- Fix crash on editor shutdown by properly removing import/inspector
  plugins in NOTIFICATION_PREDELETE before the extension is unloaded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant