Glassor + Hit By Missile = Crash

[Gabee1611]

Most times I have glassor active and get hit by a missile or sometimes when glassor destroys a missile, the game crashes. I tried reinstalling and it still happens. Ever since the recent update on ios this issue has been happening frequently.

Topic

[Sumit Arora]

And I thought I was the only 1 Having this problem. It started today only I mean the crash stuff and has happened 5-6 times!!

[Optimus_Pig]

What does Glassor do?

I’ve only tried a few of the Enegonicons up until now.

So far, I’m a big fan of Snipernaut and Photoblast.

[Sumit Arora]

Works like Sentinel Prime’s weapon, just activating it destroys every single block on the screen, fully charged Glassor will shoot 9 times hence 3 energy beams per hit making it a total of 27 beams :D

[Optimus_Pig]

“I have noticed that, in general, when there are a lot of missiles, shooting exploding, a node will crash.”

Yeah, basically there’s so much going on, that it overwhelms your poor wee beastie of a tablet / phone.

I’ve noticed the same thing.

[Red7827]

Pretty similar glitch, but when you use Airstrike when getting on board of Astrotrain, the game crashes too.

[Sumit Arora]

For me it is totally because of the Red Missiles due to which my game is crashing!!

[Optimus_Pig]

Wow, Glassor is pretty amazing. It’s got a very “godlike” feel, raining fire down from the heavens and all that ;)

[gemblung]

But compared with photoblast or rapidfire, Glassor is less effective for those mortar bots.

[Optimus_Pig]

I dunno, I’ve been totally wasting the mortar towers with Glassor.

[eugene]

I had the same problem with level 14 sound wave. Now the game won’t even open.

[Optimus_Pig]

This is interesting. I just experienced a crashing issue that I think is related to Glassor.

I ran a Beach node with E. Galvatron three times in a row using Glassor (different buddy each time) and on each run it crashed while I was using Glassor.

Then on the fourth try, I changed my energonicon from Glassor to Photoblast, and I completed the same node on the first try without any issues!