You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Godot 4's intellsense is very buggy, but I think Godot 4's issue with autoloads makes it majorly more difficult to code in lots of scenarios.
First, let's analyze the Godot 4 autoload to make sure there is nothing wrong with it:
As shown in the image, all (most) variables have been statically typed, so we should have no issues accessing them.
In Godot 4, variables inside of autoloads had no problem getting picked up by intellisense, as seen here:
As shown in the image, Godot 4 had no issues with loading the variables, it's just that trying to access the variables inside of these objects have issues.
Here's a temporary solution, but very hacky and kind of ruins the clear (I am an autoload) that autoload variables give:
Steps to reproduce
Create a script that has a variable, give it a class name
Create an autoload script, store a variable inside the autoload script that is statically casted to the script you created in step one
Create another script, try to access the autoload's variable's variable, you will see that the variable inside the autoload is picked up by intellisense, but the variable inside of the variable is not picked up by intellisense.
Godot version
4.0.3.stable.official [5222a99]
System information
Windows 10 - Godot 4.0.3.stable.official
Issue description
Godot 4's intellsense is very buggy, but I think Godot 4's issue with autoloads makes it majorly more difficult to code in lots of scenarios.
First, let's analyze the Godot 4 autoload to make sure there is nothing wrong with it:
As shown in the image, all (most) variables have been statically typed, so we should have no issues accessing them.
In Godot 4, variables inside of autoloads had no problem getting picked up by intellisense, as seen here:
As shown in the image, Godot 4 had no issues with loading the variables, it's just that trying to access the variables inside of these objects have issues.
Here's a temporary solution, but very hacky and kind of ruins the clear (I am an autoload) that autoload variables give:
Steps to reproduce
Minimal reproduction project
autoload_intellisense_issue.zip
The text was updated successfully, but these errors were encountered: