Can't assign nodes to exported array

[RustyLongbow]

---

Bugsquad note: This issue has been confirmed several times already. No need to confirm it further.

---

Godot version

Godot 4.0 alpha 11

System information

Solus OS and Windows

Issue description

Can't assign nodes to an exported array of node pointers

output.mp4

Steps to reproduce

1. Export an array of node pointers (@export var node_pointer_array: Array[Node2D])
2. Try to assign an element to the array on the editor
3. Element will not be assigned

Or: check out the minimal reproduction project below

Minimal reproduction project

export array of node pointers.zip

[Seubmarine]

Can confirm the issue is still present in alpha 14

[mournguard]

Still present in alpha 15, furthermore, if you save and close the scene then reopen it, you get actual broken links.

I'm not familiar with the source or proficient with cpp but looks like this might be caused by #59564 as it's really the only related changes I can see.

Edit; I guess it could also be anything more general regarding the types nvm

[NoFr1ends]

Following I noticed in beta 1:

It doesn't show when you assigned anything but if you click on it the right node is preselected in the dialog.
The saved scene doesn't contain the node paths and instead only saves it as e.g. [null, null].
Reopening the scene loses the preselection mentioned in the first point.

[CernyAdam]

I can confirm that the bug is still present in beta5.

[Zireael07]

We're up to beta 8 now though?

[Defaultsound]

Still an issue in Beta 8. Also applies to custom node types as well.

[Seubmarine]

I look at the source a month ago and it looked like it misinterpret the Nodes Type to be a Path if I recall correctly.

[muno777]

Present in beta 10 also

[BeeRye]

I believe this is the same bug. Godot Beta 10, Windows 10.

Assigning null values to texture arrays (and I would guess other resource-derived item arrays) functions correctly in all circumstances save for assigning them in the editor.

See project below:

Run scene to see results from loaded resources with and without null values, and results from creating new resources and adding or changing values while including null.

Test Texture Array.zip

[Steveplays28]

Still an issue in beta 12.

Edit: still an issue in beta 13 (see #71603).

[Badaxis]

Maybe this PR could solve this "old" thread
#69248

[vonagam]

Sorry to disappoint, but no (at least not yet). Unfortunately at this point I don't know much about editor side of things, but the issue is easily reproduced and common, so I hope that it will be fixed in not-so-distant future.

[palodequeso]

Can reproduce, can easily add to array in scripting onready, but is def still a bug.

[sairam4123]

A good workaround would be to leverage the new array functions.

@export var switches: Array[Switch3D]

would become

@export var switch_nps: Array[NodePath]
@onready var switches = switch_nps.map(get_node)  # feels hacky but works, not in editor though!

[designer-trifonov]

Godot 4.0.1. In the console you can see that nodes are added to the array, but in the inspector itself the list is not displayed.

[NaleVex]

Godot 4.0.1: no effect on adding Node to array via inspector, no messages in console, actual value is Null

[YuriSizov]

Thanks for your reports, but there is no need to continue confirming this issue. It's been reported enough times, and it's still not addressed. It will be closed when there is a PR fixing it.

[Frontrider]

A good workaround would be to leverage the new array functions.

That was the obvious thing to try, but did not work for me immediately. This error was in the console.

  Attempted to set a variable of type 'NodePath' into a TypedArray of type 'Object'.
  core/variant/array.cpp:413 - Condition "!_p->typed.validate(value, "set")" is true.

I had to restart the editor to make it work.

Godot version 4.0.2.stable.

[nfjdu]

Stiil not fixed in 4.0.2.stable ? For me, at least. Have not tried @sairam4123 answer yet, but have same problem as on video.

[akien-mga]

The PR which fixed this issue (referenced above, #73256) was merged in the master branch for Godot 4.1, and this happened after the 4.0.2 release, so it's expected that you still experience the issue in that version.

It may be cherry-picked for 4.0.4 (not for 4.0.3, as we're still ironing out issues in the master branch).

[nfjdu]

The PR which fixed this issue (referenced above, #73256) was merged in the master branch for Godot 4.1, and this happened after the 4.0.2 release, so it's expected that you still experience the issue in that version.

It may be cherry-picked for 4.0.4 (not for 4.0.3, as we're still ironing out issues in the master branch).

Found it fixed in Godot_v4.1-dev2. https://downloads.tuxfamily.org/godotengine/4.1/dev2/ Thank you, for help

[VikingAntics]

This is indeed fixed in Godot 4.1 dev 3, however, it still does not work if you have @tool in your GDScript file. The same bug occurs as prior to the fix, but only if you have @tool.

[YuriSizov]

@Legendilu Please provide a reproduction project for your issue.