It also happens that when all charges get disarmed on by one on site, the detonator still pretends to be connected. Ultimately, it's up to BI to decide what's intentional. I could see though why it could be partially intentional. Could make sense if you are far a way with the detonator and someone else is disarming them. In contrast, it's less sensible if you are the one that disarms them on site, as arming/disarming behavior become inconsistent that way, i.e. arming connects detonator and adds fuze vs disarming only removes the fuze, but leaves the detonator connected.

I'm sorry, this ticket can be closed. I can no longer reproduce it today. I suspect it was some issue with the remote console and not this specific method. If I figure out a repro, I'll make a new ticket.

Can be closed, as removing [BaseContainerProps()] from the template, while keeping it for the instantiated, resolves it, which makes sense.