Original Post — Direct link

So, I've been around for a while... like 2018 kind of a while. That being said, I was quite surprised to find a dye that I didn't already own. New dyes aren't a bad thing; more to support the game or to grind for!.... It doesn't seem like it's purchasable though, and on the Dauntless wiki, it's not even the right color and says it's from the "Myth & Legend" huntpass that I very much completed way back when? I also have a "Vortex (Hero)" dye that looks like it's the correct color to the one mentioned on the wiki? Is my account bugged, or am I just not seeing something? Am most confused.

Locked Vortex dye

Other vortex correct dye?

External link →
over 2 years ago - /u/joshlhood - Direct link

Good spot, and thanks for the report! Both dyes are from older Hunt Passes, and looks like we've not made them available again yet - I'll get these set up, watch for them in a future patch!

over 2 years ago - /u/joshlhood - Direct link

Originally posted by KorrupiKid

Small correction. The Vortex dye was never released, but the one named Vortex (Hero) is from the Myth & Legend hunt pass.

Yep! That "Vortex" one was made for the Echoes of the Future season but not released. Some recent reshuffling of the dye UI surfaced it again.

Can confirm that both "Vortex" (keeping it's name) and the slightly renamed "Hero" will now be available for purchase in 1.10.3. Just finishing setting 'em up.

over 2 years ago - /u/joshlhood - Direct link

Originally posted by KorrupiKid

I just haven’t updated the wiki yet. The UI got updated in patch 1.10.0 and Vortex got listed there even though it’s not been released yet. At the same time the dye which used to be named Vortex got its name changed to Vortex (Hero). Another bug also renamed the Contusion dye to Eggplant. I have made the devs aware of this and it will hopefully be fixed soon.

I’m currently updating the wiki with all new cosmetics from this patch and will make sure to update the dyes as soon as possible to avoid any further confusion.

Contusion will also be fixed in 1.10.3 yep! Thanks for alerting us :)