Weird bug in collection factories?

I think I’ve run across an odd bug in the way collection factories are dealt with, but not sure.

Structure initially looks like:

A collection
B controller.go
B1 controller.script
C factories.go
C1 factory1.factory
C2 factory2.factory

Trying to tell either factory1 or factory2 to make their prototype via factory.create resulted in an error, saying that this message went to a game object, not a factory. (even with specific /factories#factory1 messaging)

So I dragged and dropped factory1.factory and factory2.factory INTO controller.go and deleted factories.go

Results in this structure:
A collection
B controller.go
B1 controller.script
B2 factory1.factory
B3 factory2.factory

Doing factory.create on them as #factory1 and #factory2 gave me the SAME error I was having when they were nested in the other game object.

However. If I DELETED them and just re-made them inside of controller.go, it then works fine. They can be messaged by the script as #factory1 and #factory2, all is happy.

AFAICT nothing in their settings had changed. It seems like dragging and dropping kept some of their old structure? I saved and reloaded several times and it didn’t appear to alter this?

Is this a bug or is there something I don’t understand?

This may not be it…
I have noticed that deleting things can can mess things up. The .editor_settings file seems to be the guilty party, and/or deleting it has fixed issues I have had.

1 Like

Yeah in this case I moved it to a difference sub-structure. But may be the same thing!