this post was submitted on 04 Oct 2023
16 points (100.0% liked)
Godot
5843 readers
18 users here now
Welcome to the programming.dev Godot community!
This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.
Make sure to follow the Godot CoC while chatting
We have a matrix room that can be used for chatting with other members of the community here
Links
Other Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Rules
- Posts need to be in english
- Posts with explicit content must be tagged with nsfw
- We do not condone harassment inside the community as well as trolling or equivalent behaviour
- Do not post illegal materials or post things encouraging actions such as pirating games
We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent
Wormhole
Credits
- The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
- The banner is from Godot Design
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd been having issues with this myself recently. I assume you're in Godot 4.1? I tracked the issue down to being cyclic references in GDScript. As an example from what you've provided, you may have LevelBase referring to the Player script, and then the Player script referring to LevelBase. This only seems to be a problem with the type hinting in GDScript like the following:
var player:PlayerClass
Removing the hinting may fix it. As for the bug, you can read some more on it here: https://github.com/godotengine/godot/issues/80877
As a side note, I've noticed that 4.1 has this issue worse than 4.0. In 4.0 it just unbinds the script from the scene, and allows you to rebind it again. But in 4.1 it causes the error message, making you unable to open the scene.
I'm using the latest Dec build, but it was a problem before that.