What I need to do to make a scene unique?

Vale-git

Hi, I have two scenes, we call them "Player" and "Turret". Both of them are using another scene called "HPBar".

The hp bar is the same scene used from both Player and Turret. If one of them, lets say the Turret, take some damage how I can be sure that the same damage will be not shared with the other one? I tried to make all script as "Built-in" but I didn't fix the problem. Any suggestions? thanks

cybereality

Different instances of a scene will share art assets and code, but should have their own values for variables by default. I don't think you need to do anything special to get that functionality. If you can share some code for the HP Bar, maybe there is some other error that is causing the problems.

Vale-git

this is HPBar

extends Node2D

    func _ready():
    	SIGNALS.connect("mini_health_changed", self, "update_mini_healthbar")
    
    
    func update_mini_healthbar(value:int):
    	$HealthBar.texture_progress = bar_green
    	if value < 60:
    		$HealthBar.texture_progress = bar_yellow
    	if value < 25:
    		$HealthBar.texture_progress = bar_red

	$HealthBar.value = value

nothing complicate I guess

to update this value i fire a signal (SIGNALS is my singleton):

SIGNALS.emit_signal("mini_health_changed",amount)

Both Player and Turret (inside Vehicle) have a func that update their HP and so fire the signal

the current setup is:

map -> Player -> vehicle -> HPBar

map -> Turret -> vehicle -> HPBar

cybereality

The issue is the use of a singleton, that would make all the objects act the same.

You can instead, connect the signal to each object itself:

connect("mini_health_changed", self, "update_mini_healthbar")

Then emit the signal on the specific object your want:

get_node("Map/Turret/Vehicle/HPBar").emit_signal("mini_health_changed", amount)

Hope that helps.

Vale-git

Thank you for your hint. I will try and I let you know :)

In this case what is the difference/advantage between inner and outer script?

cybereality

Awesome, please try it out and let me know if it works for your game.

I'm not sure what you mean by inner and outer scripts? If you are talking about the global/singleton, it should really only be used for things that are truly global (e.g. for pausing the game, keeping track of player score, inventory, etc.). In most cases it is better to have the objects in question deal with the logic themselves (e.g. between a bullet and a turret) rather than having the logic in a main script.

Vale-git

I call Inner script when you flag on "Built-in-script" in "Attach Node Script" popup

Your suggestions work ofc :) So means my plan to gather all signals in one place is a failed dream? :))

cybereality

The code:

signal mini_health_changed

Needs to be near the top of all the classes that use it (to connect or emit)

Vale-git

@cybereality said: The code:
signal mini_health_changed
Needs to be near the top of all the classes that use it (to connect or emit)

I used only when I have the connect statement , Do you suggest to put it in all classes? Why?

cybereality

No, not all classes. I meant all the classes that make use of that particular signal.