bug: add()'ing an existing object that had children doesn't add the children to physics

[dragoncoder047]

I made levels using addLevel() and then immediately destroy()'ed them so that they don't bog down the physics engine. But when I add() the level back, the children don't collide with each other anymore and stuff doesn't work.

[mflerackers]

You shouldn't re-add destroyed objects. That's not supported.

…

On Tue, 4 Mar 2025 at 07:30, dragoncoder047 ***@***.***> wrote: I made levels using addLevel() and then immediately destroy()'ed them so that they don't bog down the physics engine. But when I add() the level back, the children don't collide with each other anymore and stuff doesn't work. — Reply to this email directly, view it on GitHub <#623>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHIYW3QOD5FSA47BV6JH432STJYDAVCNFSM6AAAAABYIC4HCWVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA4TENBWGYZTCNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: dragoncoder047]*dragoncoder047* created an issue (kaplayjs/kaplay#623) <#623> I made levels using addLevel() and then immediately destroy()'ed them so that they don't bog down the physics engine. But when I add() the level back, the children don't collide with each other anymore and stuff doesn't work. — Reply to this email directly, view it on GitHub <#623>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHIYW3QOD5FSA47BV6JH432STJYDAVCNFSM6AAAAABYIC4HCWVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA4TENBWGYZTCNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Kind Regards, Marc Flerackers Software Engineer