Mutable COIs built from ChildCustomizableObjects are engine only but do not denote that in anyway.

When creating a Mutable setup with nested Child COs, COIs can result with Editor-Only references, which will cause the COI not appear in the build manifest and the appearance to now spawn in game.

Example Setup:

CO_Main – Adds a Cube SK; Adds a 'Children' Object Group

CO_Child – Adds another SK to the Cube SK Component and attaches itself to CO_Main

When creating a COI from CO_Main the reference to CO_Main for Game and Editor exist – all good.

When creating a COI from CO_Child the reference to CO_Child is Editor-Only – it will not appear in the build.

Not knowing which COs would create proper COIs that would build and which COs and COIs would have to be re-created because they are missing Game References causes us some trouble.

Steps to Reproduce

• Create CO_Main – Add Cube SK Compoonen + Adds 'Children' Object Group
• Create CO_Child – Add another SK to the Cube SK Component and attach to CO_Main
• Create COI from CO_Child and inspect the References via Reference Viewer