-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dont allow exporting Nodes from Custom Resources (par with gdscript) #654
Comments
Oh and maybe I should mention that the current behavior is that it allows you to select a node from the scene to use in the exported field like normal, but instead of adding the node to the scene as a node path (which would be nice for built in resources) it creates an a duplicate of that node that ends up being an orphaned object. |
What exactly needs changing in gdext? |
Im not sure how it would want to be shown - like as a compile error or a warning or something else when using the The gdscript behavior is that when you try to extends Resource
@export var x: Node Currently in Rust (or before this was fixed in gdscript) this leads to some unsuspected user bugs when it lets you set nodes in the editor, but then the nodes are duplicated orphaned objects instead of references as expected. But I am still curious if this behavior should be allowed (but fixed in Godot - to use node paths and not duplicate the node) for built-in resources, which I asked here. In which case the solution for disallowing this in So to answer the question - maybe the solution is to wait until that question is answered, and if the behavior is to remain the same then add some sort of checks to |
here's one way we could disallow it that lives entirely in the type system |
Par with gdscript per godotengine/godot#82843
It would be nice if this could be allowed for built-in resources. I left a comment here godotengine/godot#80538
The text was updated successfully, but these errors were encountered: