Duplicate message actuator points to same object instead of other duplicate object

[mushroomeo]

hi discovred terrible bug that if you have multiple object with bricks pointing to each other then if you spawn that instance of obejct in game, then they point still to the original object. here is example video and file

this first video is from logic nodes.

2021-05-12_15-29-41.zip

and this second video from with bricks that can see if copy object then on some logic bricks the pointings name doesnt change with the new duplicated object.

2021-05-12_16-09-14.zip

here is the blend file if want make tests

Blast Fractor Game.zip

and here made video that shows how it should be in the game so it wouldnt break it and maybe is it hind to copy code from there i thought

https://user-images.githubusercontent.com/9019563/118016053-38b65e80-b355-11eb-9dba-4cc9a4a305e3.mp4

please please help , without this cant make normal game.. since spawning multiple objects with logic pointing to each other is super important

so because of this cant have somewhat complex ai spawning . its super terrible...

[lordloki]

Please, it is not necessary so drama to report a bug. :-)

The issue with this is that internally "To" field in Message actuator is a text field instead of object field like the other actuators. I don't know if it has an easy solution.

[youle31]

I don't really think it is a bug but more a design choice. As message actuator is using a text and not a pointer to Object, it can't work as track to actuator for example. Furthermore, as this "issue" can be workaround with copy property actuator as discussed on discord, we could close this issue imo as a potential "Fix" (changing "to_property" from string to Object pointer) would cause backward compatibility issues.