Lando in TB Bug?

JRCPKT99

So, I did a quick search and couldn't find anything on here so I apologize if its been mentioned.

I used Lando lead today in the middle rebel mission phase 5 TB.

(By the way his lead works great)

First time I have used him in TB. On round 6 of the battle, Lando's turn came up and the orbital bombardment from the platton special came up, I choose to not use it and instead use his special. Next came up Fulcrum and I was planning on using it there but it said 63% percent, so I figured I just saw it wrong the first time.

So, I let the whole team work its way around and again came back to Lando lead and again the TB special was available to me to use, and again I pass and use Lando's special, and again it goes to Fulcrum and again its at 63% available. Again the team worked its way back around and again to Lando, this time I used the TB special and it worked.

I did not screenshot but wondering if others have seen this or if I am miss using the bombardment special.

Liath

There have been posts about it. It seems that the cool down counts differently for Lando than for everybody else, somehow.

JRCPKT99

Liath wrote: »

There have been posts about it. It seems that the cool down counts differently for Lando than for everybody else, somehow.

Thank you, I didn't manage to find the posts. My search skills are apparently lacking.

Rpaulsen310

Probably linked to his ability to reset cooldown on his special

Liath

Eh, I have no idea where they are, I just recall reading them. Searching for them would take too much effort.

I would imagine this has something to do with Lando's ability to reset cool downs with crits?

scuba

https://forums.galaxy-of-heroes.starwars.ea.com/search?adv=1&search=Lando&title=&author=&cat=9&subcats=1&archived=1&tags=&discussion_d=1&discussion_poll=1&comment_c=1&within=1+day&date=

Doesn't seem that CG has acknowledged any of them

CombatCommander7

Seems like it is connected to his cooldown reset ability. In the raids he used to be able to reset the escape ability by this, but that was fixed I think.