UUM-138111
Fixed in 6000.6.0b6Mentioned in 19 release notes.
First fixed in 6000.6.0b6 (Aug 4, 2026); relisted in 18 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.7.0b8 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b7 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b6 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b5 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b4 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b3 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b2 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0b1 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0a6 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0f1 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0b10 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0a5 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0b9 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0b8 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0a4 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.7.0a4 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0b7 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0b6 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. | |
| 6000.6.0b6 | Fixes Multiplayer | Fix | Deleting an activated virtual player from the scenario configuration removed it from the config without stopping the running instance, leaving it orphaned. |