Tie reaper can't increase cooldowns of FO Tie Fighter

by hello_world23
Reply

Original Post

Accepted Solution

Tie reaper can't increase cooldowns of FO Tie Fighter

[ Edited ]
★ Apprentice

Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? Samsung Galaxy S5
OS Version Android 6.0
Ally Code: (Find it here: http://bit.ly/AllyCode )
What type of issue do you have? Gameplay
How often does the bug occur? Every time (100%)
Summarize your bug When attacking unbuffed FO Tie Fighter by Tie Reaper's "Heavy interference" it can't increase his cooldowns. Next time FO Tie takes a turn he attacks with this "Strafe"
Steps: How can we find the bug ourselves? 1. Wait until unbuffed FO Tie Fighter attacks target locked ships with "Strafe" (it's cooldowns is refreshed). 2. Attack FO Tie by Tie Reaper with "Heavy interference" ability. 3. When FO Tie takes a turn he uses "Strafe" as its cooldown isn't increased by 1.
Connection Type Wifi
Please select your region
Country

please fix this issue

Message 1 of 4 (292 Views)

Accepted Solution

Re: Tie reaper can't increase cooldowns of FO Tie Fighter

Community Manager (retired)
This was flagged as a bug and it will be fixed in one of the future updates. Thank you for the report.

View in thread

Message 4 of 4 (290 Views)

All Replies

Re: Tie reaper can't increase cooldowns of FO Tie Fighter

Community Manager (retired)

Thank you for your report. We flagged this for investigation.

Message 2 of 4 (267 Views)

Re: Tie reaper can't increase cooldowns of FO Tie Fighter

★★ Novice
I am noticing the same thing. However, I feel the Tie reaper is not adding +1 to any ships. I attacked Vader’s Ship, and his very next move was his special, Vader had no buff and took damage when I used Tie Reapers HI attack. Please look at Tie Reaper, the Heavy Interference is not working for human operators during battle.
Message 3 of 4 (218 Views)

Re: Tie reaper can't increase cooldowns of FO Tie Fighter

Community Manager (retired)
This was flagged as a bug and it will be fixed in one of the future updates. Thank you for the report.
Message 4 of 4 (291 Views)