So i dunno if this bug happened after update.
But yep. Ash hits a random enemy now.
Which makes it better tbh.
But is a bug.
1 Like
Ah all good, thats me misunderstanding - ill get this reported either way!
1 Like
Is it random? I’ve only seen it hit the last enemy. Instead of second last.
Might just be luck, though.
Yea mate. Iv been using wand ash 2x emberclaw.
And if bottom 2 enemies are gone. She hits the tops.
Either of them? Yeah, that sounds like the same bug. She’s either hitting the last (which would be the 2nd down if 3 and 4 are gone) or the second last (which is the top if 3 and 4 are gone).
Good team. I like swapping an emberclaw for King Heliodor, so I have someone to deal damage to first troop.
1 Like
Just looking quickly, the only other effects in the game that might be affected are:
Swamp Rat (troop)
Order and Chaos (weapon)
I don’t have the weapon, but I’ll try testing Swamp rat, to see if it is bugged.
Yea only using it in underspire. But its kicked but upto yellow.
Just tried casting it a few dozen times. It’s hard to be sure, because it only has a 50% chance to hit the second last troop, and sometimes it was hitting the last troop and killing it, so I couldn’t tell if it would have hit them a second time if they’d survived, but I only saw it do two things - hit only the last enemy, or hit both the last 2 enemies.
Even if one or more enemies were dead, it only did that. And if only one enemy is alive, it never seems to hit them twice.
So, swamp rat is (probably) not bugged.
It definately happed after update tho.
As i test the next weeks underspire team on thd saturdsy before. And Ash was definatrly only hitting 2nd to last. And that was dead. Was doing nothing.
Would be great it they just cganged the spell text. Any random enemy would help nexus. Its not great for damage dealers.
1 Like
Yeah. That’s the main issue at this point. The spell text needs to be right, whatever the spell actually does, so people know what to expect.
Random enemy would be fine. Last enemy would be fine. Second last was always a bad option.
1 Like
Yea but last enemy and 2nd last are the same.
If you terror or deathmark last enemy.
Itll do nithing if only 2nd to last left lol.
I think all the spells that pick the enemy placing are a bit naff lol.
Nah, if you terror or deathmark the last enemy, and they’re gone, the second last becomes the new last.
Like if you kill the first enemy, anything that targets “first enemy” hits the new first enemy.
I’m against randomness, generally. I much prefer knowing exactly who I’m gonna target, regardless of where they are, so I can plan for it.
I’d prefer knowing it targets the first or last, over not knowing which enemy it’s gonna go for. But that’s just me.
2 Likes
Also a note, the issue originally reported in this thread does appear to be fixed in 9.1
Your video though, it only shows one enemy available to cast upon so they are hit. If you had more than one enemy, and had a video of it showing her targeting any other troop other than the second last one, that would be appreciated.
As so far we haven’t been able to reproduce what you are reporting, which is that she isn’t targeting the second last troop - again, if you only have one troop left, then they will be the only one hit
It has one enemy, which is not the “second last” enemy, and it targets that enemy. That is not in line with what the spell says it does.
The spell description needs updating if this is intended (or the spell needs to be changed).
You haven’t been able to replicate her targeting the last enemy? Even though several of us players have said that is happening? And I literally have provided video evidence.
Weird.
But that is NOT the “second last” troop.
Again, if this is intended, the spell description is wrong.
Either the spell is bugged, or the spell description is. Something needs fixing, because they do NOT match up.
They did before. But since the last update, they do not.
Zuul - originally people complained that queen ash would only hit the second last troop if there were at least two troops, and it would hit no troop if there was only 1 opponent left. This became painful because of the Nexus trials where you are forced to use her.
Following community feedback, I think the devs tried to make it so it would hit the second last troop unless only 1 was left, and in such cases queen ash would hit that final opponent.
Do you agree that queen ash is operating ‘as described in my 2nd paragraph above’? Or is something else not working this way?
In my tests, it is operating as per para 2, and therefore is working as the community requested and devs expect.
I get your point that the spell is misleading (as it can hit a ‘non-second last troop’ when only 1 troop is remaining). The issue may be the wording of the spell to correctly describe this is too long?
3 Likes
If there’s only enemy left it’s like electron - in a superposition of states)
It is first troop and it is the last troop and it is the random troop at the same time) so let hip be the second last too)
1 Like
Oh yeah, I know. I remember.
For some reason people have been complaining about this troop for years, pretending it was bugged, when it was actually working correctly, but potentially badly designed.
Yes. That is exactly how the spell says it should work. Terrible design, but that’s how it says it works, and until the last patch, that was how it worked.
Yeah, but not JUST her. And totally agree, she would be better if her spell was designed in such a way that she doesn’t become mostly useless when you get to the last troop. Dunno why they designed her that way to begin with, but they did.
It’s unclear. One dev apparently claimed she was bugged, then they did nothing for over a year. Now they stealth changed her - possibly on purpose or possibly just as a new bug - so she doesn’t always target the second last troop. So, if that is what they want, they should change the spell description to reflect that.
If they don’t change the description, the description is not accurate to how the spell actually works. Which is clearly a bug.
We have whole sections on the forum for bad translation errors, where the spell description isn’t accurate. I don’t see how this is different, assuming the current version of the spell is how it was supposed to be.
So, the spell should say that. Simple fix.
It is operating as described by you. Which is not how it is described in the game.
I’m fine with a spell that works like that. But if that is how they want the spell to work, then the spell should say that.
That is totally what I’m saying.
EDIT: If that’s the issue, and it just comes down to “We wanted this spell to do way too much and now we can’t fit it all in the little box”, I’d get it. But that’s still a problem.
If the correct wording of the spell would be too long, they should just change the way it is done. Like scatter damage - troops don’t have a long description of scatter damage on every card, they just say “scatter damage” and there’s a tooltip to explain how that works. Or splash damage.
Just make this kind of thing (targeting a set enemy, unless there is only one, then targeting that enemy) a set term and put that in the spell.
So, the wording would be something like:
" Deal (magic+4) heavy splash damage trampled to the second last enemy, boosted by Brown Gems and Allies. Pull them to the front. Then create 3 Elemental Stars."
Tooltip: Trampled Damage - Deals damage to a set troop or to the last troop if such troop is not a valid option.
It’s just one extra word at that point, and they can use the same concept on other troops without people getting confused over which troops it does and doesn’t target.
1 Like
It there is one person in a room, and they leave, (and nobody else leaves, because nobody else was in the room) they are the first one to leave and the last one to leave. They are not the second one to leave. They are not the second last one to leave. They aren’t the third or twelfth or two hundredth. They just aren’t.
But the spell doesn’t HAVE to pretend it only targets the second last. It can just say it targets the second last and have some word to show it switches targets if that target isn’t possible.
Deferred. Trampled. Proxied.
Anything.
Just toss a word in. Explain what it means, elsewhere. And the spell is perfect.
Or don’t. And the spell is wrong. It’s bugged.
And people will keep arguing over this. Like we have been for well over a year.
4 Likes
post by OminousGMan on Feb 3, 2023
Hey everyone,
Thank you for letting us know about this. I’ve tested Queen Ash on our side and discussed how the spell Graven Seal is meant to bework when cast and this is a bug.
Even with one enemy troop on the board, the spell should be targeting it. I’ve reported this to the dev team to get this corrected.
Thanks again.
OminousGMan - Support Human
Original Dev reply to post of Jan 2023 reporting that it won’t hit anything if no 2nd last slot. Not that isn’t the first bug report for Queen Ash, there’s a few well before this, it’s the one that confirms it needs fixing.
I’ve not tested it since 9.1 as not played much, but I’ve used Queen Ash 1000s in blue PvP. I always use in blue and brown ToD too. It’s one of the more underrated troops in the game because of Elemental stars counting as brown for +1 magic for matching brown it explodes stars and its damage is half decent. Knock out blow for Mael for example after first Chrys.
It’s Nexus as is Emberclaw and a hero plus Flower/Chicken Dragon = +9 magic and Nexus team bonuses as well as all other ones.
For it to actually hit other targets with its spell is awesome. It’s took 3 years to get here…
Let’s try and make sure it doesn’t get broken again 
1 Like