@export_node_path

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

snowy-fox

So, export(NodePath) has been replaced by @export_node_path. But, it seems not to work. Rather than getting the supplied node in the NodePath and working on that, GDScript now seems to be attempting to work on the NodePath itself.

Am I using it wrong, or is it another aspect of @export that's not ready yet?

cybereality

You are storing a path in the variable, not a node (which is what the name says, node path). You can then use get_node() to get the node. Always a good idea to check the documentation, all this is listed there.

https://docs.godotengine.org/en/latest/tutorials/scripting/gdscript/gdscript_exports.html#nodes

snowy-fox

cybereality Ahh, gotcha. I'd not found that page... I'd been looking in the wrong doc.

Gotta say, though... I'm really not enjoying the new annotations. x_x I get that they were designed to be more intuitive for new users, but even as someone who hasn't been coding for long, they feel less intuitive to me. And less flexible, and more work.

cybereality

Yeah, I agree that they are more work and more keywords to learn. I think it was done this way because the old GDScript uses a lot of loose typing, Variants, and string identifiers. They have converted it to strong typing and more of a real programming language, but that also means you have to type more because everything isn't generic.