Bug: Destroy trigger fails on subsequent activations of groups
Bug #136
Destroy trigger fails on subsequent activations of groups
| Status: | Open |
| Priority: |
High |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Fixed In Release: |
Not set
|
Steps to Reproduce
- Create a group that contains an object and a destroy trigger set to destroy that object (or the group contents)
- Set up a mechanism to activate/spawn the group, let it destroy, and then re-activate/respawn the group a second time
- Observe the behavior during the first activation versus the second activation
Explanation
When a group containing a destroy trigger is spawned/activated multiple times (e.g., set to auto-destroy its own contents and re-appear via timer or spawner), the destroy Trigger only works during the initial activation.
Upon any second or subsequent activation, all objects and other triggers within the group (such as timer triggers) function as expected, but the destroy trigger stops executing. As a result, objects spawned on subsequent iterations fail to destroy.
Expected result:
The destroy trigger should re-initialize and destroy the specified object every time the group is activated or spawned.
Actual result:
The destroy trigger functions correctly on the first run, but fails to execute on the second and all subsequent activations, leaving the spawned objects intact.
Watchers
You don't have permission to comment on this issue.