error at line i cant reach?

W00F_test

Hello! while writing a dialogue manager, i encountered this error that seems to make the game stop in it's tracks.
It's listed as;

Error at (0, 0): Unexpected "Identifier" in class body.

Clicking on it does nothing, i cant scroll up any further to reach 0,0 and i have no clue what the identifier means unless it is counting the command export? Very confused.

any help would be appreciated!

kuligs2

W00F_test

Script files usually have something like

Scripts extend some class type or node type..

Your script starts with export something which is wierd ..

xyz

W00F_test What is the first line supposed to achieve? Who wrote it, you or a chatbot?
Variable exporting to the inspector can be used in any of the following ways:
https://docs.godotengine.org/en/4.4/tutorials/scripting/gdscript/gdscript_exports.html#doc-gdscript-exports

ArDanZ11

W00F_test You need to say extends BlahBlahBlah (Node that the script is controlling) and that should work.

W00F_test

kuligs2 Yes! this is because when originally starting, the extends [node] would bring up an error similar to the one im having trouble with. It brings up the same unexpected identifier.

I figured then, it must be the node in question but neither changing the node nor testing it on a different type of node changes anything, and of course, when moving the extends, it brings up the 0, 0 line error.

W00F_test

xyz I wrote it while following a video on the same topic. The goal is to get the json file text to load into the text labels in the same scene using an input i.e the enter key.

I fear it may be some sort of issue with godot itself, as any other help or video online for dialogue seems to mention using a plugin or addon/asset instead of just the base coding engine.

ArDanZ11

W00F_test What node is this script controlling? You need to use the EXACT name of the node. For instance: If I was using a VehicleBody3D node, the script would say extends VehicleBody3D. Same goes for any other node.

xyz

W00F_test It's not a Godot issue, you're just using the wrong syntax.

Here are the "rules":

the first non-blank line of every script must be the extends statement or class_name statement
the export keyword changed from export in Godot version 3 to @export in version 4. So if you're referencing a version 3 tutorial, you need to have that in mind and change it to @export. If you're a beginner, using a v3 tutorial with a v4 engine is not a good idea as there may be other compatibility issues between script versions. Use the matching tutorial/engine versions.
the ways @export can be used are listed in the documentation link I posted above. Read it and use the form of @export that best suits your needs

W00F_test

xyz Just wanted to say thanks! it was indeed a syntax error i couldn't seem to wrap my head around, ha, thank you for your patience ! Now i just have to figure out the rest of the errors, thank you greatly!

kuligs2

What node does the script is attached to? Show full picture.. its hard to say but yes that export is wrongfully written.

Try to delete and see what errors it shows.. if none well there is your problem..

Sometimes godot will error out on few lines before the real problem because it cant compile the thing at runtime and stops at the thing or something.. not sure but i had some errors where it wasnt erroring on the line that was badly written.

ArDanZ11

Restart your computer, I have problems like this all the time. It thinks things are null when they don't exist, because there are so many errors that Godot mixes things up and gets confused.

xyz

ArDanZ11 Restarting won't remove that obvious syntax error in the code 🙂

kuligs2

xyz youre wrong, sometimes it does.. the engine sometimes throws errors for correct code, you need to relaunch project to make it work..

xyz

kuligs2 It may do so "sometimes" but it's mostly when classDB hasn't been updated properly. In that case reloading scenes/scripts can force it to update. However this code contains obvious syntax error. The code is not correct. No amount of restarting will fix that.

Toxe

xyz However this code contains obvious syntax error. The code is not correct. No amount of restarting will fix that.

This. Also, I don't think I ever had to restart my system because of some issue with Godot. The editor to reload the project? Sure. But the whole system? Not that I can remember. That would be weird.

xyz

Toxe I don't remember needing to restart even the editor for any type of issue to resolve. An occasional rare ClassDB glitch can happen, but, as I said, it can be flushed by merely forcing one or more scripts to recompile

Toxe

xyz I remember that in the early days of Godot 4, which is when I started with it, I had to restart the editor to reload the project and/or delete the .godot directory. And sure, no big deal, I have used Microsoft products before. But these issues are long gone now. But restarting the whole system? I think not.

xyz

Toxe Yeah, there's not even a theoretical way Godot can accidentally trash the system. The only thing I could think of is crashing the Vulkan or GL driver in some severe way. And doing that is not an easy task. As the meme goes: "One does not simply crash the Vulkan driver" 😃

xyz

ArDanZ11 You need to use the EXACT name of the node

That's not entirely true. A node will accept a script extending any native class that's upstream in node's inheritance hierarchy, or any custom class with whom it shares a common native class ancestor.

For example if you have a script that declares:

class_name MyClass extends Node

You can attach that to absolutely any node type.
If you then make a script that declares:

extends MyClass

You can attach this to any node type as well.