Dauntless

Dauntless Dev Tracker




13 Jan

Comment

Hey!

So, I've been writing for Dauntless since around 1.7.0. Currently handling the weekly quests, journal entries, lore nodes, etc. My first big stab at narrative was Blazeworks, and I'm happy with the way it turned out. Working with the environment team to get those lore nodes in and create a story around Phaelanx was a really good time.

Right now, we're really focusing on the Ostian threat narrative (and all the players involved). I agree 100% that our next big narrative moment will be Radiant Escalation and I can't wait to work on it more. I haven't touched the time travel threads that were left after Chronovore dropped, because time travel as a concept is hard to do right. I also don't think we can fully put that cat back in the bag, but we can approach it with a lighter touch.

I agree with a lot of what's being said here. At its heart, Dauntless is a story about reclaiming lost lands, foraging new paths, and above all, fighting big Behemoths.

... Read more
Comment

Thanks so much! Seeing posts like this is always nice!


12 Jan

Comment

This will be fixed in 1.9.0 (next patch), sorry about your ears!😊

Comment

I'm the designer who made this change. It was done alongside the release of Heroic Escalation. At the time, I wanted to tune the balance of some of the most extreme amps, and Virulent Impact is the top of that list.

Virulent Impact is fun, no question, and I didn't want to take away from how powerful it was. I could've reduced its strength in a number of ways, but ultimately, I really like that Virulent Impact is always the best choice. I love the aspect of it where when you see it, you definitely want to take it. Where it defines and changes your run in a meaningful way when it shows up.

To fully fulfill that role, I bumped it up to Legendary, it's currently the only Legendary Amp but it deserves that status. It means that it shows up less often, but it also means I didn't have to reduce the power of it, and it can remain a dominant best pick when it shows up!

It's still Rare in Terra Escalation because it requires the investment of a Talent Point to show u...

Read more
Comment

This is adorable.


11 Jan


10 Jan

Comment

Originally posted by AresThreeFive

In-Game Name: AresThreeFive

Type of Bug: Audio Issue

Expected Behavior: The swarm of bees from Kharabak to stop emitting a sound after they are gone.

Actual Behavior: If you come into contact with the Kharabak bee swarm the sound that plays with them will never stop until you leave the hunt.

Reproduction Rate: 10/10 happens every time I come into contact with the bee swarm.

System: PC Windows 10

We have a fix for this issue going into 1.9.0! A very annoying one indeed. Makes me think of the Nicholas Cage meme, NOT THE BEEEEES!

Comment

Originally posted by Kr0nshi

In-Game Name: Kr0nshi

Type of Bug: Behemoth

Expected Behavior: Weekly Challenges to count Sahvyt dodges and kills.

Actual Behavior: Weekly challenges do not tick up at all when dodging Sahvyt's attacks, or killing him with chainblades. Have not tested the break all parts challenge.

Reproduction Rate: 10/10

I think this may have something to do with Sahvyt counting as Neutral pre-patch. The game doesn't seem to recognize "Shock" Sahvyt as the Sahvyt in the challenges and still wants "Neutral" Sahvyt.

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by MrGrakan

In-Game Name: SirGrakan

Type of Bug: Weeky challenges

Expected behavior: challenges related so sahvyt counting

Actual behavior: they are not counting

Reproduction Rate/Steps: Everytime

Geographic location: Portugal

The slay sahvyt with chainblades and the dodge sahvyt attacks aint counting, the dodging counted 1st day but ever since that stopped

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by LawmanBarry

In game name: Thezedd73 Type of Big: performance? Expected behavior: complete challenges once complete Actual behavior: the opposite of that Reproduction: Every time

Challenges not counting as completed when they are complete

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by der_Mechaniker

β€’ In-Game Name: Nixon Redgrave & Avitol Myopic
β€’ Type of Bug: Weekly Challenge
β€’ Expected behavior: Week 8: Bladestorming count increasing with Sahvyt Chain Blade kills
β€’ Actual behavior: No kill count increase
β€’ Reproduction Rate/Steps: 100% reproducible. Equip chain blades, kill Sahvyt, observe count remains 0/10
β€’ System Specs: Xbox Series X&S
β€’ Geographic location: CA, USA.

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by CranberryInevitable3

In-Game Name: TombstoneZombie

Type of Bug: Challenges

Expected behavior: To track current progress on Sahvyt challenges.

Actual behavior: Reads 0/10 sahvyts slain

Reproduction Rate/Steps: 10/10

System Specs: Console

Geographic location: U.S East

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by Soahtree

In-Game Name: Soahtree

Type of Bug: Behemoth, Challenge Progress

Expected behavior: Expecting credit for defeating Sahvyt with chain blades, expecting credit for dodging physical attacks from Sahvyt, expecting credit for 3x wounds in 1 Sahvyt fight, expecting credit for breaking all parts before defeating Sahvyt

Actual behavior: Progress towards completion of the associated Challenges does not occur

Reproduction Rate/Steps: Able to reproduce bug 100% of the time, in solo, in party, and in escalation over several separate sessions.

System Specs: 17 ping, 26 Mbps download, 31 Mbps upload speed. Windows 10. Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz 4.00 GHz, NVIDIA GeForce GTX 1060 6GB. Additionally have tried this on Switch and have been able to reproduce the error across sessions, with solo/team/escalation.

Geographic location: Washington state, USA

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by Yoyobunbuns

Sahvyt for bright wood Doesn’t seem to count for a lot of things. I’ve wounded it so many times and get nothing

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ

Comment

Originally posted by Danielmbg

In-Game Name: Danielmbg

Type of Bug: Behemoth/Bounties

Expected behavior: Killing Sahvyt on escalations should count towards Bounties and Daily Challenges that require killing behemoths.

Actual behavior: Killing Sahvyt on escalations does not count towards Bounties or Daily Challenges.

Reproduction Rate/Steps: 10/10 Every Sahvyt I killed on an escalation did not count towards my Bounties or Daily Challenges.

System Specs: Xbox One, Canada.

Bugged Sahvyt challenges should be fixed now, give it a go! πŸ™Œ