Parser Error: Could not find type "DialogueResource" in the current scope.

[germanbv]

Describe the bug
After adding this addon to my project, I have started to experience this issue when hitting the play button... the engine randomly freezes until it displays Parser Error: Could not find type "DialogueResource" in the current scope. on dialogue_manager.gd line 76 (get_next_dialogue_line) and the game crashes, if I restart I have a good chance of not triggering the issue.

From what I've read, this seems to be an engine-related bug that has been around since 2019 and has to do with the engine not loading singletons on Autoload, I'm not sure though, since DialogueResource is a global class rather than a singleton... maybe you know a workaround for this?... I was thinking of maybe creating a c# version that's not part of the addon folder to see if the problem persists...

For reference see: godotengine/godot#32759

I have to add that DialogueManager is the only singleton I have on AutoLoad and it is the only addon I'm using on my project, in the other hand I also have other classes inheriting from Resource which don't have any problem.

Affected version

• Dialogue Manager version: 2.26.0
• Godot version: 4.1 Mono

To Reproduce
Steps to reproduce the behavior:
Add the addon and execute your game... The problem triggers randomly but it used to be more frequent after modifying a script file. Keep in mind that I'm using the Mono version and I'm working with C#. I haven't tested this on a normal version.

[nathanhoad]

Whenever I've run into missing classes I usually delete the .godot folder and let Godot rebuild all of the caches.

[germanbv]

thanks!, I'll try that and I'll report back if the problem persists.

[germanbv]

deleting the .godot folder didn't solve the issue, this seems to trigger after modifying C# scripts

[nathanhoad]

I've just merged in some improvements to the C# stuff including this line that might help with the error that you're seeing. I do think it's an engine bug but hopefully this is a workaround for now.

[germanbv]

thank you! I'll try that out... and yes, the problem is an engine-related bug... I kept investigating and it might be the same issue explained in: godotengine/godot#75388