Any activity?

Any news on this? Seems like a very trivial yet useful feature that just hasn't been merged yet?

Meanwhile for anyone else with this issue, use this workaround:

var tree = get_tree()
tree.current_scene.queue_free()
tree.root.add_child(my_scene)
tree.current_scene = my_scene

But it's 1. cumbersome to use in multiple places, 2. very beginner unfriendly, and 3. inconsistent with other change_scene_to_* methods.

Consider the user doing something like (simplified):

var node_a := Node.new()
var node_b := Node.new()

get_tree().change_scene_to_node(node_a)
get_tree().change_scene_to_node(node_b)

It potentially might be surprising for the user that node_a was freed as a result. The docs should probably explicitly note/warn that by passing a node to change_scene_to_node you kinda give up the ownership and it will be auto freed even in a scenario like above (node_a never became the current scene, it was a pending new scene only temporarily).

For comparison change_scene_to_packed is fine without such note/warn as it's not the user who instantiates the scene.

Besides that code LGTM, the addition is trivial.

Something like this?
[b]Warning:[/b] After using this method, the [SceneTree] will take ownership of the node and will free it automatically when changing scene again. Any references you had to that node may become invalid.

Something like this? [b]Warning:[/b] After using this method, the [SceneTree] will take ownership of the node and will free it automatically when changing scene again. Any references you had to that node may become invalid.

Yeah, LGTM, sends the message. 👍

Thanks!

Wow. I just literally ran into a situation where I want something like this. Glad to know it's been merged. Talk about timing 😅

Thanks!!