=DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward

=DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (Full Version)

All Forums >> [Artix Entertainment Games] >> [DragonFable] >> DragonFable General Discussion

Message

Chaosweaver Amon -> =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/18/2022 23:47:49)
quote: [image]https://www.dragonfable.com/images/DF/author/Verlyrus.png[/image] Verlyrus: Book 3: The Awakened Depths: The Way Forward Hey there, heroes! This week, we have another main story quest available! Tensions are rising as the Greenguard Alliance seeks a way deeper into the overgrown center of Dragesvard! [image]https://cms.battleon.com/DF/images/THEWAYFORWARDdn.png[/image] Will you be able to carve a path through the Hollow? And how will the DragonLord encampment fare under Captain Lestrad's aggressive leadership? The assault to reclaim Dragesvard continues! Head over to the Dragesvard camp in Tyndur's Depths to play this week's release: The Way Forward! Also this week, a couple fixes/adjustments! DeathKnight's Relic Barrier is now unaffected by buff detection effects. Fixed an issue where it was possible to go backwards in the Book 1 intro and restart the Twilly cutscene. Fixed an issue where it was possible to go backwards in the Book 3 intro and restart the Twilly cutscene. Next week, the we'll revisit the past of Book 3 with our next Reimagined release! Have feedback about recent releases? Have any crazy theories or ideas? Want to discuss all things DragonFable? Join the discussion on the official forums! Want to play DragonFable without using an internet browser? Check out the Artix Games Launcher! Follow us on Twitter for sneak peeks and updates (and feel free to tweet us your fan art and feedback too!) Verlyrus Twitter Dove Twitter Tags: #Verlyrus Tagged ~Peachii

Laeon val Observis -> RE: =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/19/2022 0:32:15)
Well, Falconreach is now roasting if the color of the horizon is concerned. Either we'll find out next week alongside the reimagining or on April 1st (04/01 is a Friday this year). spoiler: So that's how huge the fungus that plagues Dragesvard. And things are ramping up all the more. Once again, you can disengage your Containment helm once in the quest, but the penalty is 5 times bigger, making it less appealing to do so. Even if you find an over-maxing potion box in the ruins. And nice addition to the chronology. Who knows what the Magesterium would've done to Fluffy's reincarnation. Good thing that the current incidents in the airship are just misfiring engines. Was expecting more Doom-related phenomena cropping up.

Dratomos -> RE: =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/19/2022 6:33:15)
In Falconreach, sun is shining and getting closer every day. What a pleasant spring surprise! spoiler: Story is heading to a boiling point it seems. I do wonder if we will get camps in Dragesvard next month. And that reference to Angel of Azaveyr was nice!

ergotth -> RE: =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/20/2022 0:53:05)
Oh god that meteor xD Also, I LOVE the inspiration on a Veil Lady mushroom (Phallus indusiatus) for the fungus dome over Dragesvard.

DragonKeeper -> RE: =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/20/2022 8:01:22)
Pirate Monkey cannot equip or show the Self Containment Helm so I am unable to do The Way Forward quest with Pirate Monkey.

AstralCodex -> RE: =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/20/2022 16:36:19)
Cool quest! I really appreciated the double story release this month. Also, it's pretty cool how the new ring is BiS BPD, though I'm a bit puzzled by why it also needed to be BIS for so three different resistances. I still think DK Relic barrier change was unnecessary, and think the comments calling for it were quite misguided. DeathKnight did the fight fine before the change and it didn't make the fight noticeably easier after. (Before, you'd just swap to evil res gear after killing Achilles. Now, you don't have to, but doing the swap makes the fight easier, so you probably should anyways.) It felt like a change that added complexity for no reason - before, we had a simple rule for what triggered Patroclus ("don't use statuses that increased your stats!"), and now, we have to memorize another exception that doesn't really matter. I also think it's pretty inconsistent that DK Relic barrier was changed because people claimed it was "arbitrarily blocked" that it wasn't actually blocked from, while other perma status classes can get owned significantly harder in other fights without any changes in those fights. EDIT: that's not to say that I think all the old fights should be changed. Far from it - I think there are better things to spend development time on than to retag all the class passives to be ignored by bosses. I also think that having soft bans can make for interesting challenges for players to overcome - for example, I think Cyromancer's Pyromancer Weird Duo is very cool, and I enjoyed doing Failed Doom with DoomKnight.

TFS -> RE: =DF= March 18th Design Notes: Book 3: The Awakened Depths: The Way Forward (3/21/2022 0:41:43)
^For what it's worth, Relic Barrier was initially meant as a way to avoid re-statting all of the DeathKnight items in the first place. Having it trigger buff detection seems like an unintended side effect that wouldn't have been a balancing concern had the resistance just been on the DeathKnight items. This really just seems like future-proofing to avoid having DeathKnight be a balancing concern should a buff detection mechanic be used again on another monster. The same change was made to SWoT back when Leorilla came out, for the same reason. If you really want your class to be disadvantaged by a band-aid mechanic for whatever reason, monsters that just check for statuses in general (such as Pride) are entirely unaffected by this change. This similar-but-distinct mechanic could also end up in future releases and leave DeathKnight every bit as disadvantaged, so don't fret.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition

8.007813E-02