Lorem ipsum dolor sit amet, elit eget consectetuer adipiscing aenean dolor

Is there a timeframe for when

Impervious will be fixed. I got a Wulfgarok not too long ago and had all of the traitstones to max him but with all of these Kraken teams, he isn’t viable. At least not like he should be.

You would think with it being Blackhawk week, that they would want to fix this prior to.

Impervious should be fixed already. If it’s not, the devs need to know how it isn’t, as I don’t think they’ve got it on their radar anymore.

I was just eaten up and I wasn’t stunned.

I see; in that case, this should be considered a bug report. You should provide as many details as you can about what you were fighting and what you had on your team. That will help the devs narrow down the issue.

Okay, thanks.

Is it also a bug that sometimes when Kraken kills the last enemy he sometimes Devours the 3rd enemy or I have even seen him kill the two last enemies and Devour the third last enemy, as in kill, kill, Devour for 3 kills in one spell?

Make sure you manually downloaded the latest patch. I’m not sure it was flagged as mandatory on Android. I know you probably have, but I thought I’d have you check.

I usually only update when mandatory, I will see if that is the issue because it very well may be. I was sort of under the impression that it automatically updates when patches come out. Thanks for the pro tip.

Robbg I don’t think the kill 2nd enemy and devour the 3rd is a bug lots of troops work that way as long as I’ve been playing.

I can confirm that aspect of Kraken is working as intended. If his dmg will kill the enemies in slots 3 & 4, then his devour chance will target the enemy in slot 2.

With regard to kill two, then devour another:

In his original iteration released on PC/Mobile in the Adobe Air client, there was a concept I am going to refer to as “target lock”, where a spell with multiple components intended to affect the same target would select the targets once, and all effects would be applied in order to these targets. Kraken was one such troop in his original release - he targeted the last two troops, dealt damage, and has a chance to devour the “last troop”, meaning the last troop when the spell was initiated, meaning it if died, you wouldn’t get another devour. Target lock does not exist on Unity, therefore, all multi component spells have issues with their subsequent components “leaking” onto other troops (ie., Khorvash, Pride Hunter, and yes, Kraken).

I’ve seen people argue back and forth as to whether or not this was “intended” and citing the spells wording that it is supposed to work this way, but the fact remains that the current behavior is most likely a consequence of the engine switch. I highly doubt the devs singled out Kraken’s spell and said “Kraken isn’t good enough with the version we pushed through QA on our Adobe Air client where we designed him even though it has both board mod, damage two targets, and a chance to devour. Lets make Kraken’s spell better and more accurately fit the description by allowing it to simultaneously kill two enemies and devour an untouched enemy. Since Unity doesn’t have target lock any of the multi-component spells, just porting it over with the current targeting scheme will make it do that, but this is an intended and informed change we made that just happens to coincide with bringing the troop to Unity. Also, lets make it always work this way on Console, but PC/Mobile has to wait for this change until they get Unity, even though we could easily separate the spell components on Adobe Air since we already have other multi-component spells that don’t target lock”. A more accurate representation would probably be “oh, I guess it works that way now. I hope people don’t notice or it doesn’t break anything major, because that means time and resources that have to go into fixing it”.

Whether or not it will ever be “fixed” and whether it needs to be fixed are two different things that can be argued on their own merits, but I really don’t see how Kraken got to where it is now either by “always being that way” or by intentional adjustments to match spell text when spell text is much easier to change.

In short, yeah, it is probably a bug. And yeah, it is probably also “working as intended”.


If it working as intended then it not bug. Sometime I think you don’t understand meaning of bug. Bug is term when program not working as intended because of mistake in the code. Last troop is last troop, regardless of where it was position 1,2,3,4. If nothing exist below it then it is last troop. Is that simple.

Not literally working as intended, but “working as intended” (note the quotes), which is shorthand for “it works this way now, the game still works, and we can’t/won’t/don’t have the resources to fix it so yeah, we totally meant to do that”. The current behavior of Kraken is entirely an unintended consequence due to using a codebase that worked differently, an error by oversight, and therefore, yes, a “bug”.

1 Like

No, it actually is working LITERALLY. It does exactly what says LITERALLY on the troop in plain English. This what literal mean.

It’s likely your game has not been updated. You will need to do so to get the bug fix. :slight_smile:

1 Like