How to save "meta" information in a scene
How to save "meta" information in a scene
I am coming from a Unity background and there I just had a component of some custom class in the scene which I could then easily get by calling `FindInScene<CustomComponent>` or something like that. Not in Godot this doesn't work, because I didn't find a way to get the actual class of an attached script. I always just get...
Im not really sure i understand. A scene is just a node with some children, if you want to store and read information from it then you just attach a script to the root node and declare some variables in it no?
If you add some custom node or instance to it, then you just get_node that by its path and access its variables.
Oh you want to know the name of the script that was previously attached to a node?
get_script().get_path() should return the filepath to the script that you used, not sure if thats what you want tho.
I see, looks like that is actually an issue.
github.com/godotengine/godot/issues/21789
Seems like you have to overwrite the get_class function if you want to detect custom classes.
extends Node2D class_name CustomClass func get_class(): return "CustomClass" func is_class(name): return name == "CustomClass" or .is_class(name) func _ready(): print(get_class()) print(is_class("CustomClass")) print(is_class("Node2D"))Defining a unique class name gets you the same thing as giving each script a unique filename and then differentiating between the get_script().get_path() but i can see how its not as clean for comparison.
Another solution would be to just give all your custom classes a var called “class_id” or something and then you can read that out if you need it.
Im assuming you have a predefined level scene, which you instantiate and add as a child to your main scene. If i were to save a bunch of metadata about that level scene, i would add a dictionary named “level_data” to the script of the root node of that levels scene.
extends Node var level_data = { "spawn_point": Vector2(x,y), ... }After you instantiate that level from your main scene with:
var level1_tscn = load("res://path/to/tscn") var level1 = level1_tscn.instantiate()You can then get or modify the metadata from that instance reference.
print(level1.level_data["spawn_point"])When you are done you can then add it as a child to the main scene with add_child(level1).
You can also do that right away and access the data later ofcourse, but if the values are needed in the _ready function of the level, then you need to modify them before adding it to the main scene.
Added something to the previous comment.
Im also not super experienced, i just make unsuccessfull attempts at making games from time to time :) But i do love godot a lot.
You generally use the same logic for literally everything in godot.
Spawning a bullet, enemy, item, ui component?
Instantiate, set values, add_child
Do you use C# since you’re coming from Unity?
You can use GetNode<CustomNode>() or GetChild<CustomNode>() to find the node you need just like in Unity. CustomNode will be the type of your script or if there is no script attached to your node you can use the builtin types as well (e.g. Node3D).
Once you have the node you want, you can either use Godots builtin functions SetMeta() and GetMeta() to set and get metadata on a node or use the C# way and access the public properties set on that CustomComponent class directly.
I don’t use GDScript but I assume you have the same methods available there.
You may find some value in Groups. This lets you assign a node to a group by name, then later get the nodes in the group by searching for that name.
In your specific example you mention being able to fetch the spawn points. I’d add each spawn point to a group called “spawn” and then later retrieve them with:
var spawn_points = get_tree().get_nodes_in_group(“spawn”)
I would create separate nodes for each piece of metadata within the scene you are loading, you can use a Node2D (or Node3D) to store a position (such as a spawn point) and there is a Timer node which can hold the time for a level.
Alternatively, under the node inspector there is an option to “Add Metadata”, which might be more along the lines of what you are looking for. It can be read with the get_meta function.
BentiGorlich
unexposedhazard
BougieBirdie