Sith Eternal Emperor Stuck in Infinite Animation During Territory Battle
Product: Star Wars: Galaxy of Heroes
Platform:iOS
What type of device are you experiencing the issue with? PC
OS Version Windows 11 Home 24H2 26100.2894
Ally Code: (Find it here: http://bit.ly/AllyCode ) 588-427-458
What type of issue do you have? Gameplay
How often does the bug occur? Rarely (0% - 9%)
Summarize your bug Sith Eternal Emperor Stuck in Infinite Animation During Territory Battle
Steps: How can we find the bug ourselves? After activating SEE’s ultimate ability, the animation started and then got stuck in an infinite loop. The game became unresponsive—I couldn’t do anything, even after trying to alt-tab, adjust game speed (1x, 2x, 4x), or press any menu buttons. Game Mode: Territory Battle (Phase 1, Dark Side planet) Character: Sith Eternal Emperor (SEE)
Connection Type Wifi
Please select your region Europe
Country Hungary
Title: Bug Report: Sith Eternal Emperor Stuck in Infinite Animation During Territory Battle
Content:
Hi team,
I encountered a frustrating bug while playing Star Wars: Galaxy of Heroes in the Territory Battle game mode. Here's what happened:
- Game Mode: Territory Battle (Phase 1, Dark Side planet)
- Character: Sith Eternal Emperor (SEE)
- Issue Description: After activating SEE’s ultimate ability, the animation started and then got stuck in an infinite loop. The game became unresponsive—I couldn’t do anything, even after trying to alt-tab, adjust game speed (1x, 2x, 4x), or press any menu buttons.
This caused me to lose points for both myself and my guild, which will negatively impact the final rewards.
Other players in my guild mentioned on Discord that they’ve experienced the same issue, so it seems like this bug affects multiple users.
Please investigate and address this issue. I've attached a video to demonstrate the bug in action.
- EA ID: Szega1987
- Ally Code: 588-427-458
Thank you for looking into this!
Best regards,
Szega1987
Thanks for the crash report. If you see this more often, please follow our troubleshooting steps from this article.