A little help on mechanics of pausing tscn while in different tscn

jbskaggs

In my cancer game I am getting pretty darn close to being finished.

Could someone help layout the mechanics for pausing for one scene while another scene runs?

So in the game you have a body map that has cancer sites popup, green ones turn into red ones. If you click a red one it takes you to another scene where you use a cannon and kill the cancer tumor.

I need to pause that body map and stop it from running and spawning new cancers while in the battle scene, but keep the data intact before the scene change.

Thanks

cybereality

You can set the process mode.

set_process(false)

However, I usually just use a boolean value like "is_active" and wrap the update code in an if statement:

func _process(delta):
    if is_active:
        # all the game code here

TwistedTwigleg

@cybereality said: However, I usually just use a boolean value like "is_active" and wrap the update code in an if statement:
func _process(delta):
    if is_active:
        # all the game code here

I often use this to pause functionality as well, though I generally check for it being false and returning to stop executing functionality:

func _process(delta):
	if is_active == false:
		return
	# all the game code here

But it's basically the same technique, just a different way of writing it.

Sometimes it can helpful to use visible to disable/enable functionality, as then you can disable functionality easily from other scripts and animations. The downside of using visible though is that it's harder to debug and you have to set visible to false on the node itself to disable functionality, even if the parent node is not visible.

For example:

Parent (visible)
- Child (not visible = not executing)
Parent (not visible)
- Child (visible = executing even though its parent is not visible)

But I find it can be helpful and an easy to to track if something should be executing by just checking it's visibility.

jbskaggs

Thanks.

cybereality

Right, I do the return trick as well, I thought the boolean check would be easier to understand.

Also, you can simply remove a node from the tree and it will disappear from the screen and also be in a paused state without changing any code (and it will return at the exact frame it left on when you add it back).

var my_node = get_node("whatever")
remove_child(my_node)

jbskaggs

@cybereality said: Right, I do the return trick as well, I thought the boolean check would be easier to understand.

Also, you can simply remove a node from the tree and it will disappear from the screen and also be in a paused state without changing any code (and it will return at the exact frame it left on when you add it back).
var my_node = get_node("whatever")
remove_child(my_node)

Hmm I did not know that!