GD Script in 3.2 does not inherit custome parent class variables

klaas

Hi Everyone, just tried 3.2 with my project and experienced this error.

Im extending one of my own classes. But the vars i declared in the parent class now throwing an error that they weren't decleared. Export varibles dont show up in the editor anymore.

I've browsed through the changlelog but did not find any clou to this behaviour.

Anyone experienced it too?

TwistedTwigleg

I have not experienced this issue with custom classes I've created. It sounds like it might be a bug.

I'm not sure if it will help, or if is part of the issue, but how are you defining your variables? I'm using code like export (NodePath) var node_to_follow_path in my base class and export (int, "physics process", "process") var update_method = 0 in the extending class.

klaas

Thank you for your replpy.

I've used it like so:

extends Spatial
class_name parentClass
export var radius:float = 0.5

the other class

extends parentClass
class_name extendedClass

func _ready():
	radius = 2

Wich resultet in "not decleared in current scope" when starting.

BUT, it seems its some kind of class caching problem when importing projects. I've created a new project and tried to replicate the problem. But i didnt show up. After some fiddeling with my project code, wich was changing it back and forth a bit, it now works as suspected with no change at all. I remebered a other strange problem where a non existing script produced redecleration errors on occasion. So i think its a problem with the project cache and its nearly impossible to properly reproduce for a valid bug entry.

TwistedTwigleg

So i think its a problem with the project cache and its nearly impossible to properly reproduce for a valid bug entry.

Yeah, sounds like that is what it is, and I agree it would be extremely difficult to make a bug entry simply because of how hard it would be to reliably reproduce. I'm glad you were able to find a solution though!

comfysoft

This is old at this point. For anyone reading: I had the same problem and it turns out I hadn't saved the changes to the base script after I declared the variable in question. As soon as I saved the base script the error went away.