Can we tag a scene?

Vale-git

Hi, there is a way to set a tag in a scene like we set class_name in a script? This in order to accomplish 2 goal 1) find that scene in "create new node" window 2) avoid to set path when we load that scene.

thanks

DJPercy

Hello,

use Groups:

docs.godotengine.org/en/latest/classes/class_node.html?highlight=is_in_group#class-node-is-in-group

Greeting, Denis

cybereality

Thanks for responding @DJPercy but I'm not sure that's what the OP is asking for.

I think the OP wants more like a class that is on the same level of the built-in classes.

You can do this with "class_name". Here is a simple example:

Animal.gd

extends Node2D
class_name Animal

var sound = "Grrr"

func speak():
	print(sound)

Dog.gd:

extends Animal
class_name Dog

func _ready():
	sound = "Roof"

Main root node (parent of Dog node):

extends Node2D

onready var dog = get_node("Dog")

func _ready():
	dog.speak()

You see you can search for both Animal and Dog in the new node screen and that you don't need any hard-coded path names. Hope that helps.

Vale-git

Title: Can we tag a scene? Goal: get rid scene's path.

cybereality

If you use a group, and make only one object in each group, that would be like what you are looking for.

NeoD

In my project I have an autoload script for that purpose, I centralized the scenes paths in a dictionnary. Not sure if my solution is optimal but that works.

Edit: Maybe the dictionnary is not necessary. Put directly the paths into member variables.

Vale-git

I give you an user case to be more clear why I asked this question:

I have a scene we call "house" - its a complex sum of other scenes and have some connections with "council" scene that is in another tree branch. One day I want to move this "house" from my "garden" node to "beach" node. So I don't want loose all connection with my "council". Ideally the project have to be in charge to update all tree paths and I have to be able to use my "house" like before :)

As you understand we have different kind of connections (tree, signals,resources, events...)

What @NeoD said was my first attempt but still.. I need to modify manually each path - Also for signals I found out that Is better not to set in Singletons unless there are no other choice.

About what @cybereality said I'm not sure what you mean. Groups are inside scenes.. Right?

cybereality

So you can set a group name on the scene. Just click on the scene, look on the right next to the inspector and click the node tab. Then type in a group name and click add.

Then in your code somewhere, you can do this:

var house_nodes = get_tree().get_nodes_in_group("house")

If each group is unique (meaning only one scene is in each group) then the result of that call will be an Array with one item, the scene inside that group.

Not sure exactly if that solves your issue, but it's a good trick to look into.

Vale-git

@cybereality said: So you can set a group name on the scene. Just click on the scene, look on the right next to the inspector and click the node tab. Then type in a group name and click add.

Then in your code somewhere, you can do this:
var house_nodes = get_tree().get_nodes_in_group("house")
If each group is unique (meaning only one scene is in each group) then the result of that call will be an Array with one item, the scene inside that group.

Not sure exactly if that solves your issue, but it's a good trick to look into. Thank you, I was aware the groups existence ofc. But I was not sure how they work : if i copy my "house" in another project I can use it without any changes? Or I have to rewrite all groups again?

cybereality

You set the group to the root node inside the scene, then all instance will share the same group.

Vale-git

@cybereality said: You as the group to the root node inside the scene, then all instance will share the same group.

I don't understand, Can you elaborate please?

cybereality

So you have a branch of the tree you want to use as an object. You can right click the start of the branch, and choose save branch as scene. Then click the movie icon next to the new scene to enter it. On the root node inside that scene, click it once, then look over on the right of the inspector. Click the node tab, then add a new group name. If you later create an instance of the scene in code (or even if you copy manually in the editor) then it will be part of that new group, which you can use group logic on (find all in group, check the group name, etc.). Hope that helps.

Vale-git

I will try. thanks