I only noticed this because I'm working on the mini gels grind for the achievement, and accidentally scrolled to the bottom of the gel search. But the Turtle Soup achievement seems broken. Mine shows 45/15 for the second tier, but it's red, like I don't have the achievement. I couldn't 100% say I've never gotten it, my ADHD brain doesn't retain that level of detail about the game, but I don't have the prize from it, and it's cool enough looking that I think I would have put it in my wardrobe (and I'm a wardrobe hoarder, so the odds of me having sold it along the way are pretty low). Figured it'd be worth flagging it since it's gel time! :D Thanks!

That is a new achievement, and I don't think it's 'active' until after that particular challenger is released during the event. Looks like you will get it once the challenger is released!

Oh perfect, thank you! That makes so much more sense lol!

For clarity, this happens when new achievement tiers are added to preexisting achievements. The achievement has been counting your wins ever since it was first created and you’ve gotten 45 since then. When a new tier is added, it can show that you’ve gone over the new amount (45/15). All you need to do is complete one more instance of the action - in this case, winning one more battle against Gelashell - and it will activate. If there are ever more tiers added in the future, your past wins will count for those too!

I wish I had known about the cumulative effect of wins beyond the achievement. I only learned about this yesterday! Ha! I'll try to get some extra wins in case more tiers are added in the future. It will be nice for those that only have to battle once to get achievements!

I love it most during Fireside. I always turn in tons of stuff to Charity, Fantine, and the Rreign each year so every time Amber adds new achievement tiers, I unlock them immediately :P

But it is a good thing to know for battling; every win counts! I’m all set on the rest of the gelly achievements and I’m glad I don’t need to worry about them.

Locking this up since it's not a bug. :)