Grandchildren Scenes don't inherit scripts

[RCastroAB]

Godot version

3.4stable

System information

Ubuntu 20.04

Issue description

When creating long chains of inherited scenes in Godot, the information of the script attached is lost for grandchildren and beyond.

Steps to reproduce

Create a scene A, then create an inherited scene B from A. After that create an inherited scene C from B. Now attach a script to A. B will have the script attached but C will not.

Edit: All scenes must be open in the editor.

Minimal reproduction project

InheritanceBug.zip

[kleonc]

Steps to reproduce

Create a scene A, then create an inherited scene B from A. After that create an inherited scene C from B. Now attach a script to A. B will have the script attached but C will not.

Can't reproduce (W7, both in 3.4.2.stable and 3.4.stable). C inherts the script just fine.
Edit: I guess I was closing the scenes after creating them. When keeping the scenes open in the editor (after the creation) then I can reproduce it, "B will have the script attached but C will not" indeed.

Minimal reproduction project

InheritanceBug.zip

For some unknown reason in Node2D3.tscn the script is overridden to null:

[gd_scene load_steps=2 format=2]

[ext_resource path="res://Node2D2.tscn" type="PackedScene" id=1]

[node name="Node2D" instance=ExtResource( 1 )]
script = null

Such override haven't appear (automatically from nowhere) when I've tried to recreate the issue.
Edit: it did appear when kept the scenes open.

[RCastroAB]

Thank you for your reply!

How strange, I just checked and it's generating that line into the file upon running the C scene. Before that, the file is generated as one would expect, and if the line is deleted the script will be attached correctly, but will not update if the script is detached on the parent. I created a new project, this time without running C, so the line shouldn't be there.

Inheritance Bug.zip

I also got this confusing error message somewhere along the way.

 scene/main/node.cpp:1560 - Condition "!common_parent" is true. Returned: NodePath()
 Cannot get path of node as it is not in a scene tree.
 (Node not found: "" (relative to "").)
 editor/editor_data.cpp:1033 - Condition "!p_node->is_inside_tree()" is true.

I have also had a seemingly unrelated issue with child scenes only updating their inherited scripts if the parent scene is loaded in the editor, but I'm unsure whether I to make another issue.

[kleonc]

How strange, I just checked and it's generating that line into the file upon running the C scene. Before that, the file is generated as one would expect, and if the line is deleted the script will be attached correctly, but will not update if the script is detached on the parent. I created a new project, this time without running C, so the line shouldn't be there.

Inheritance Bug.zip

I think I must have been closing the scenes after creating them, and the issue is happening only if that grandchild (inheritance-wise) scene is open in the editor. I've edited my previous comment.

Also it seems to happen for any property, it's not script-specific behavior. Try changing position or pause_mode in A (when B and C are open as well), then running A, and you'll see the changes being reflected in B but not in C.

I also got this confusing error message somewhere along the way.

 scene/main/node.cpp:1560 - Condition "!common_parent" is true. Returned: NodePath()
 Cannot get path of node as it is not in a scene tree.
 (Node not found: "" (relative to "").)
 editor/editor_data.cpp:1033 - Condition "!p_node->is_inside_tree()" is true.

I'm not getting any errors so it may be unrelated to this issue. Not sure what could be the cause.

I have also had a seemingly unrelated issue with child scenes only updating their inherited scripts if the parent scene is loaded in the editor, but I'm unsure whether I to make another issue.

Kinda related, kinda not, hard to tell. There are many issues for "inherited scene" reported, you can check them out.

Actually just looked briefly at few of these issues and seems like this issue is a duplicate of #55964.

[RCastroAB]

Nice to know I wasn't the only one. Should I close this issue, since it's a duplicate, or should I wait until the bugs are fixed?

[Calinou]

Duplicate of #7984.