I’ve submitted an example file for them. It looks like they are looking into it. Hopefully we see a fix soon. This all happened right as we hired a company to playtest and QA our game. Imagine if this had happened during the release month, oof. I think after the update that fixes this we may hold off on updating construct until after base release.
I will be happy to report the issue using your link. But I will say that the issue is as simple as this: Containers do not work with persistent objects. They do not create the contained object.
EDIT: Looking further into your bug report it would be impossible for me to follow your guidelines. My project is massive with over 30,000 actions. I can not submit an example that uses minimal events.
As stated before, Persistent Objs with containers do not spawn in their contained obj when you re-enter the room they are in.
EDIT 2: I have created a tiny new project that showcases the issue. This is great as this tells me that this is solely a container issue and not some code in my project. I will upload this example. Recreating this issue lets me know MANY construct users will run into this problem with containers if used with persistent objects.
github.com/Scirra/Construct-3-bugs/issues/6444
Hi there Ashley, this is a significant update! We have discovered that Container objects are broken to some degree. If you enter a layout for the first time with container objects that hold persistent objects they work. But if you leave the layout and then come back in only the persistent objects stay. The container objects don't spawn. This has caused many existing mechanics to break in my game, BioGun. Can you please look into this? Before this update, we did not run into this issue. Excellent work as usual! :)
-John
Member since 25 Jul, 2020