devtrackers.gg
Looks like Slayers are getting back in.
Happy hunting, everyone!
Looks like Slayers are getting back in.
Happy hunting, everyone!
Dauntless is currently down, and we are receiving reports of wider outages across other services. We are investigating this issue and will provide updates soon.
Thanks for your patience, everyone!
External link →Those 2 interactions may or may not be intentional, if the cell's health sacrifice was coded as a general rule of wether or not it counts as taking damage it would apply to both cells, but the fact that it procs one and doesn't remove the other, makes me think this was more intentional.
And yea, the risk vs reward aspect of it shines brighter than my future x)
Yes, it was an intentional choice to allow both Rage and Predator to be active on this Omnicell.
Congrats!
Thank you very much for this reply. It is appreciated greatly.
<3
Read more External link →Server Status @ status.playdauntless.com
We are working hard to quickly resolve live issues. For more help, contact support @ support.playdauntless.com
Please also keep an eye on the current tracked issues @ ...
And it doesn't seem to matter how many times we bug report it... Really it's not OK to ignore problems with premium store cosmetics, annoying the very people supporting the game through purchases!
We have received your bug reports <3 the issue posted here will be fixed in 1.8.3 (Dec 2)
Absolutely no communication on this from devs. Little reminder that indeed any premium skins you purchase will end up broken with either misplaced VFX or in the case of recent skins the VFX won't even show at all.
Hey! I replied elsewhere on the thread, but for your awareness this will be fixed in 1.8.3 (Dec 2).
As an aside, I totally understand being frustrated when cosmetics do not look as promised, and I want to be clear that if there is MTX that you are not satisfied with we will work to fix it. If we cannot or do not fix it, we will refund you the plat if you write to us through support.
I am really sorry we missed communicating with you on your previous post, and that this bug is still happening! We are working on a fix for it now that will be in the 1.8.3 build (going live on Dec 2).
