A Disabled Raider's Review of Patch 7.0 Duty Design

[Aurelle_Deresnels]

Navigation Links

EN

This is a LONG one. And unfortunately I was unaware of the limit of 20 images per post when I made my sections, so I had to split up the subsection reviewing the Patch 7.00 MSQ duties. Sorry, Japanese readers, I would have reserved more posts if I knew that in advance!

Introduction

1) Design Principles

2.1) 7.0 Duty Review - MSQ (two posts)

2.2) 7.0 Duty Review - Optional Dungeons

2.3) 7.0 Duty Review - Normal Raids

2.4) 7.0 Duty Review - High-End

3) Honey B. Lovely, Redesigned (this is the exciting example, start here if you want to see the principles in action)

JP

これは長い記事です。そして残念なことに、セクションを作ったときに投稿ごとに画像が 20 枚までという制限に気付かなかったので、パッチ 7.00 MSQ の任務をレビューするサブセクションを分割する必要がありました。申し訳ありませんが、日本の読者の皆さん、事前にそのことを知っていたら、もっと多くの投稿を予約していたのに!

はじめに

1) 設計原則

2.1) 7.0 任務レビュー - MSQ (2 つの投稿)

2.2) 7.0 任務レビュー - オプション ダンジョン

2.3) 7.0 任務レビュー - 通常レイド

2.4) 7.0 任務レビュー - ハイエンド

3) Honey B. Lovely、再設計 (これはエキサイティングな例です。原則の実際の動作を確認したい場合はここから始めてください)

[Aurelle_Deresnels]

Dear Respected Forum Master / Webmaster,

Would you please kindly forward this letter to Yoshi-P and the duty design team?

Thank you very much for your help.

Sincerely,
Aurelle

--------------------------------

Dear Yoshi-P and the Final Fantasy XIV development team,

I must first apologize for not bringing you this feedback more swiftly. I experienced health and safety issues with the graphical update, and was thus unable to partake of any Dawntrail content at all until over three weeks after the beginning of Dawntrail Early Access, when I found a postprocessing method that enabled me to see the game safely. As a result, I was unable to complete the Patch 7.00 Main Scenario Quests (MSQ) until the day before the release of Patch 7.05 and AAC Light-Heavyweight (Savage), so I judged it better for me to first complete the Savage tier and review all of Patch 7.0's duty design together and thoroughly.

I see that you have been working hard to bring players enjoyable duties, in particular responding to feedback about Endwalker's duty design. I am not advocating for a return to Endwalker's duty design, nor for making the game easier in general. In fact, I have completed every single duty available in Patch 7.0, and each and every one of them has made me bored in three completions or less!

I would very much like to attempt and complete harder duties, such as Futures Rewritten (Ultimate) (FRU) coming in Patch 7.11. Indeed, I completed The Omega Protocol (Ultimate) (TOP) during Endwalker, so it would be the logical next step for me to aim to complete FRU on-patch before the release of Patch 7.2.

But I will not get to do that, and may not get to complete FRU at all. And that is also because of Patch 7.0's duty design.

You see, I am a disabled player. Without getting into medicine or biomechanics that may be difficult for readers, especially in translation, my muscles respond slower than those of a "normal" human body. I have to use both arms through the shoulders in order to give inputs fast enough to play competently at all, and even then it puts a bit of a damper on my reaction time. Obviously not that much of a damper, since I can do TOP; but enough that during progression (practicing the mechanics of a high-end duty) I study the fastest mechanics more to learn to process them efficiently. Enough that I prefer to avoid reliance on "follow the leader" or callouts, and instead solve everything myself, because the extra delay from reacting to someone else's processing the mechanic can get my character KOed while everyone else makes it to the safespot. Enough that even with all the work I put in, I move like someone who has been slowed down by simple aging or high latency.

The vast majority of Duty Finder players could play with me and never notice. (I have often been "the leader" in Duty Finder, teaching parties the mechanics!) Even the vast majority of raiders could play with me and never notice unless I told them - though I do wind up telling raid groups sometimes, when they ask me to switch to a job I avoid raiding on due to poor input patterns for my body, or ask me to go past the raiding time limits I set to avoid injuring myself.

Why the time limit? Having seven other players' enjoyment relying on my giving all the inputs fast enough means that I hold myself to a higher standard. My body can only keep that up in a healthy way for so long; remember, I am already using both arms in full to play at all. I had to build up my stamina gradually when I started playing the game, and if I go beyond my baseline of raiding hours I will start having to stretch frequently, eat more and with a very particular nutrient balance, be more strategic about when I raid to give my body recovery time... just like an athlete has to when training intensively. (I cannot keep up hours beyond my baseline for more than a few weeks, either.) I sure notice the difference between me and an able-bodied player, because I am the one putting in all the work behind the scenes to still be able to play.

(Most people do not notice when meeting me on Earth either, unless tasks requiring high physical speed or high strength come up. I can hold a variety of jobs when offices do not insist on every last employee being able to lift heavy things or work unproductive overtime. There are some sports I can do for fitness, after consulting with my doctors. I can even drive a car - I passed all my road tests and my emergency situations training without knowing I was disabled, because my unconscious compensating skills were good enough on their own. (For example, it was years later that I found out that most drivers use their shoulder check as the first sign that a car is in their blind spot, not a confirmation check on continuously tracking the surrounding traffic.) There are lots of people whose disabilities result in worse performance than mine.)

Before Dawntrail, my baseline raiding hours were 9 hours a week. I had never gone beyond 12 hours a week until the very end of Endwalker, when I pushed to 14 hours a week in order to complete TOP before Dawntrail Early Access - despite progressing in Party Finder. At the time, I thought what I had to do for that was incredibly intensive. A rigid schedule of 2 hours every single day, not counting the time I spent practicing outside the instance using completion video footage and a striking dummy, with no days off. (Make no mistake, Party Finder does not make that easy - I had to tally up my time with each party each day.) Stretching not just immediately before, at the 1-hour mark during, and immediately after each session, but several additional times throughout each day. Eating ravenously and still having to carefully plan to pack all the protein, fats, and micronutrients into my diet. I even barely typed outside of my party chat, in order to reduce strain on my hands. Even with my Earth schedule allowing all these measures, the only reason I was willing to push my body so hard was that I knew I would get a natural recovery week - or two, if I needed it - from Dawntrail's launch and the accompanying MSQ.

Spending 9 hours a week progressing AAC Light-Heavyweight (Savage) was harder on my body in every way. Not just in stretching and food and sleep; Dawntrail was the first time my hands have hurt from playing any game, despite everything I do to care for myself. (I could not just stop as soon as I felt any pain, since the pain came afterwards - and took a full month of deliberate care to stop.) Dawntrail is the first expansion where I have had to contemplate applying my time limit to regular duties, not just raiding. Dawntrail is the first expansion that has effectively pushed my stamina down - rather than it slowly increasing with exercise - and caused me to seriously contemplate lowering my time limit to match.

In light of these results of Patch 7.0's duty design, I cannot know whether I am physically capable of completing FRU at all without personally analyzing the entire duty in depth - which I of course cannot do until well after its release, when large amounts of completion footage are available to properly understand the many possibilities arising from mechanic randomness. Likewise, even if I knew that I could physically do FRU at all, I cannot know whether it would be sustainable for me to do at least 9 hours a week of FRU progression without an even deeper analysis. (I was happy to commit to TOP and even Dragonsong's Reprise (Ultimate) (DSR) before their respective launches, because I had my baseline of 9 hours a week by the beginning of Endwalker.)

And with less than 9 hours a week, clearing an Ultimate in its launch patch becomes statistically highly unlikely, even with a static raid group (often shortened to "static") that goes from launch day through the remainder of the patch and uses its time efficiently. (I have spreadsheets that examine why this is, but the raiding consistency math is beside the point.) One simply does not get enough time to properly learn the mechanics to the high standards of consistency that Ultimate demands.

Knowing this, I cannot in good conscience commit to any static intending to complete FRU - and multiple friends have asked my interest in FRU statics! Doing so would be dishonest to the group and a disservice to my own health. I knew that even before you told us all to take care of our health when challenging FRU in Live Letter 83. And progressing an Ultimate through Party Finder in its launch patch requires even more hours per week, as I experienced with DSR: not just to compensate for time wasted in groups that are ill-prepared for the party's stated objective, but to keep up with the strong players who are putting in 30+ hours a week to complete the duty quickly. Fall behind them and one's parties start getting worse rather than better, and from there it is a vicious cycle.

So it is with great sadness that I find myself forced to sit out of FRU, at least until late in Patch 7.2 (when player interest returns after AAC Cruiserweight (Savage)) and possibly permanently. I have the interest in and dedication to difficult duties. I have the complete maximum Item Level Best-in-Slot set for SCH, designed for FRU progression rather than purely for maximum damage output, and the books to adjust the set if I want to. (And I can pick up weapons for other jobs if I want, since I have been repeating the Savage tier every week.) I even have the nostalgia for Eden Savage. But as much as I find myself bored by Patch 7.0's duties, my body simply cannot take the physical demands of the current duty design direction.

It is an unfortunate result of Dawntrail's overall design direction so far, both duty design and its interaction with job design, that the current duties are mentally very easy and physically very difficult. This is an exceedingly poor state of affairs for any game that is not designed as a form of exercise - and those games accept being limited to the niche of players who want that specific form and intensity of exercise. For an MMO that wants both broad and enduring appeal, this will not do. In the remainder of this letter, I will provide more detailed feedback aimed at correcting both sides of this issue.

Not just for myself, but for the many players who complained about the Strayborough dolls and the Honey B. Lovely duties - which garnered widespread complaint precisely because their mechanics are so heavily reactive that even young and able-bodied players find them frustrating. For the world progression raiders who are disappointed that they completed AAC Light-Heavyweight (Savage) in less than 10 hours, and the experienced raiders in general who find that tasks they have little trouble with are crowding out the interesting difficulty. For players who are forced to have slow reaction times purely by aging. (This game used to be considered "the retirement home for fighting game players" - a genre where the highest echelons of play do rely on fast reactions, and so top players outright age out of the genre!) For the players who unsubscribed a month or two into Dawntrail out of sheer boredom; combat design is not the only problem leading to such a precipitous drop in subscriptions that you saw fit to run a Free Login Campaign in the launch major patch of an expansion, but it is definitely on the list. (Yes, World of Warcraft released its own expansion, The War Within, but that was almost a month after Patch 7.05. Dawntrail got to show its graphics, story, and endgame first, so many more players would have stayed if it gave a good overall showing.) For the players who stopped saying "this is too hard" not because they adapted - they cannot adapt if they hit a physical or working memory limit - but because they were shouted down by other players or quit in frustration. (Notice that the interview in which you mentioned that was over two months after the start of Dawntrail Early Access. Even players who subscribe through time cards would have had the opportunity to unsubscribe by then, and would thus no longer be able to post here.) For everyone, really.

(I am not expecting you to change FRU's mechanical design at this stage. Surely it is already locked in by now. And Ultimate design is so exquisitely precise and interlinked that even if I had delivered my feedback upon Patch 7.05 launch, you probably could not have fully responded to it in time for FRU. (I have a great respect for the Ultimate duty designers, who take on the task of pushing us to our limits but not beyond them!) But I hope that you will be able to make use of it for Patch 7.3 onwards, if not also Patch 7.2 duties such as AAC Cruiserweight (Savage).)

In the interest of thoroughness, I have divided the remainder of this letter into three major sections. First, I will discuss design principles and overall style, with particular emphasis on those aspects where current duty design is falling short. Second, I will break down the Patch 7.0 repeatable instanced duties from my perspective, both the good and the bad, in order to provide many examples of how I experience mechanics. For those readers who find that tedious, I encourage skipping over the second section to the third: my complete redesign of Honey B. Lovely's duties, both Normal and Savage, to show the design style I want applied to a Dawntrail concept.

As I will be extensively discussing duty mechanics throughout the game's history, and sometimes their relationships to the lore behind the enemies, fellow players take heed: the remainder of this letter is full and open spoilers through Patch 7.05, including duties outside the MSQ.

[Aurelle_Deresnels]

As a reminder, I am not asking for the game to be made easier in general, nor for a return to Endwalker's duty design. In fact, if I had to describe the duty design style I want by reference to expansions rather than principles, the closest existing expansion would be Stormblood.

(Note to newer players: Do not judge Stormblood's duty design style by how its duties play with the Dawntrail jobs, or even most of the Endwalker jobs. Duty design style must shape the duties to create the demands on the player from playing their job in the duty, as that combined demand is what the player will experience. The Stormblood jobs were significantly more demanding across the board to reach acceptable competence for every type of duty, from MSQ dungeons to Ultimates. On top of that, there are several forms of expansion power creep involved: better food and potions becoming available each raid tier, better effective gear from syncing down, lenience in the stat squish applied with Patch 6.0, newer expansion jobs having outsized potencies below their original cap level, and easier raid buff synchronization due to the "2 minute meta" implemented with Patch 6.0.)

Stormblood's duty design style aims to challenge players at every level of play. It is not just the expansion that introduced Ultimates, it is also the expansion that put trios - otherwise an Ultimate mechanic type - in an Alliance Raid (Ultima, the High Seraph in The Orbonne Monastery). The expansion that gave us the original Thunder God Cid, which has since been nerfed three times. (And two of those are because it dared to ask Duty Finder for Extreme levels of party coordination.) The expansion with the infamous MSQ solo instance fighting Sadu. The expansion that made tanks check boss buffs for Local Resonance / Remote Resonance and move Omega-M and Omega-F accordingly... in Normal Mode. Of course, it has memorable and iconic Savage mechanics too - Playing Field, Grand Cross Omega, Forsaken, Hello World - but it does not limit the challenge to high-end duties.

Remember Omega's motto: "Fight, win, evolve." As a duty designer (and as a job designer), you should be inspiring players to apply it to themselves.

Challenge is necessary to avoid boredom and spur growth. Accordingly, you can and must challenge players. That means having penalties for failure, as it is those penalties that create the difference between success and failure. Hand out the avoidable hits, the Vulnerability Up stacks and Damage Downs, the KOs, and even some party KOs in regular duties.

But the immediate goal of duty design is not for the duty to "win" over the player by pushing the player into giving up. The goal is not even to push the player into trying to complete the same duty indefinitely, since eventually the player will lose patience and give up - and "eventually" is not that many attempts for most combinations of player and duty. The goal is for the player to complete at least the regular duties and improve in the process, so the failures need to be motivating rather than demotivating.

--------

Which raises the question: what is the difference between a motivating failure and a demotivating failure?

We have some intuitive understanding of this, but we also have existing scientific research that can give us more details. From my previous writing on balancing the magical ranged DPS role, in January of this year:

I must make a brief detour to psychology. In particular, I must explain Brehm's motivational intensity theory, which has not only been tested in video games and held up, but overall has been replicated so extensively that Richter, Gendolla, and Wright's summary paper had to direct readers to narrower summary papers. For brevity and clarity despite machine translation, I will explain only the points of the theory that relate to the question of balance at hand, and I will explain via example.

Suppose a player is considering a goal with a fixed difficulty, such as completing a dungeon. If they had to do something ridiculous to accomplish that goal, like find three other people and teach them the game in order to have party members, the player would almost certainly reject that goal and find something else to do with their time. Likewise if they had to do something blatantly impossible. This illustrates that they have a maximum amount of effort that they find worth it or possible, which we call their "potential motivation" in the context of that goal.

However, even if the player can complete the dungeon within their potential motivation, that does not mean that they will put forth that maximum amount of effort - they may be willing to spend an hour in the instance, but if the party completes the dungeon in twenty minutes, they will not then spend the remaining forty minutes in the same instance pressing their buttons with no targets. (They may well spend it in the same instance exploring the environment, but that is a new goal.) Rather, they will put forth the minimum amount of effort needed to accomplish the goal, and no more than that.

This theory makes intuitive sense from the perspective of conserving energy. A rice farmer who insists upon moving to a desert and constructing new rice paddies there will probably produce no rice and starve. A rice farmer who insists on hauling their harvest back and forth for no reason, not even physical training, will not put themselves in a good position either. The many experiments confirming the theory show that it is very much correct - conserving energy in this way is an evolved imperative of the human brain, and games for humans must bend to it.

At the risk of stating the blatantly obvious: Motivation is all about the player's perspective. They are working with their own information, interests, and capabilities, not those of a duty designer or even a different player.

(In general within this letter, I would rather state something you already know than omit something and be misunderstood. It is all too easy to wrongly believe that some knowledge is already shared, and working through a language barrier does not improve the situation.)

--------

From the player's perspective, the effort they must put in to complete a duty is fixed but initially unknown. (The same is true of longer-term goals, such as completing the MSQ up to a fixed point or completing a Savage tier.) Before entering a duty, the player has an estimation of the effort they must put in to complete it, based on factors such as their prior experience with the game and their understanding of the available duty difficulties. If that initial estimation gives too high a chance that the effort they would need exceeds their potential motivation, they will preemptively decide "not worth it" and not even attempt the duty. (Which is often a good thing - this is what keeps players with no desire to raid from joining progression parties for high-end duties anyway. But it can also keep a player who perceives themselves to struggle with MSQ from pursuing optional regular duties such as Normal Raids and Alliance Raids, even if they would perform acceptably there.) If they enter the duty, they will continuously refine their estimation of the effort they would need based on the feedback from the duty itself, the effort they put in and the mechanical successes and failures they experience... and if at any point that refinement gives too high a chance of exceeding their potential motivation, they will declare "not worth it" and quit the duty in frustration.

Hence the first major design principle of this letter:

Every time you tell a player that they have failed something, they must correctly perceive a way to do better next time that will lead them to success within an effort they find reasonable.

(There are two exceptions. One is when dealing with the small minority of players who thoroughly refuse to learn, as they will do that no matter how carefully you teach. The other is in high-end duties that players can enter while woefully unprepared in prerequisite foundational skills, where it becomes necessary to tell unprepared players "this is not currently a productive use of your time" to discourage them from making themselves and their party members miserable. TOP is admirably designed in this regard: its first two phases carefully test many mechanical skills required for the later phases, so players who are not ready to tackle the later phases will generally fail out in frustration early on, rather than after their whole party has each invested several dozen hours into the duty to reach the special surprises.)

Allow me to go over this wording in more detail to present sub-principles.

"Perceive": The existence of a route to success does no good if the player does not understand at least the first step.

For example, it is well within casual players' capabilities to avoid KO from Judgement Nisi in Alexander - The Burden of the Father (A4N); they need only arrange their characters such that the two healers avoid contact with each other and all other player characters for the 30 second duration of the Nisi debuffs, and have the healers heal themselves periodically. (The Nisi debuffs start with one type on each healer, spread by contact, and having more than one type is an instant KO.) But casual players cannot be relied upon to read their debuff bar, even in the healer role but especially outside it - and that is the only indication of the Nisi debuffs in A4N. Thus, players whose characters are KOed by Judgement Nisi often do not perceive even the immediate cause of the KO, only that their character "mysteriously exploded". And they are correct about their own state of confusion!

Accordingly, they become frustrated at a penalty that seems out of their control, even though technically the duty has given them both a way to succeed and the information to discover it. If preceding duties had taught casual players to reliably notice when their characters are debuffed, then they would perceive the information given to them and take it as a clue. Likewise, if the Nisi debuffs had an additional indicator that casual players would reliably notice, such as the overhead markers in The Epic of Alexander (Ultimate) (TEA), once again they would perceive the information given to them and take it as a clue.

In the Patch 7.0 duties, violations of this sub-principle (and the next) regularly manifest in the form of mechanics that discourage the player from looking in the correct place to understand the mechanic, whether by overwhelming visuals, forcing the player to fight their interface, or sometimes even actively unhelpful non-diegetic cues. When that happens, the player enters a mindset of "try to constantly look everywhere", which is not a fun kind of stress. (Notably, it is not physically possible at high fidelity, due to the layout of the human eye where details require using central vision. Plus, the player has no way of knowing if they can relax out of that state without learning the duties.) In high-end duties, it can sometimes be appropriate to ask the player to figure out what information is mechanically relevant, but that requires too many attempts to be viable in regular duties.

"A way to do better next time": The player must learn something from every failure, but not necessarily a complete solution to the mechanic. The player's evolution is the cumulative effect of many small steps they take to improve.

If the player correctly thinks "okay, I got hit by this attack, I should watch out for where it comes from", that is acceptable. If the player correctly thinks "I misjudged the timing of that attack, I needed to move earlier rather than staying to deal damage", that is acceptable at low frequency; it is necessary feedback for a player developing their timing, but they will require long practice over many duties to significantly improve those skills rather than always moving early and cautiously. (Which is why so many players come to love snapshots at the end of castbars, despite the visual mismatch with attack animations - the castbar provides a fair and consistent cue to use in timing judgements.) If the player correctly thinks "I need to learn the duty timeline to plan for that before it appears", that is only acceptable in high-end duties; not only is the practice and memorization too much to expect for regular duties, but requiring advance knowledge of the duty timeline often diminishes the story experience of regular duties. If the player correctly thinks "I need a reference sheet for this mechanic", that is only acceptable if it is one small reference sheet for the entire duty, that they can write or draw out themselves rather than relying on a second device or monitor. (Which is why The Ridorana Lighthouse is acceptable - a dyscalculic player can write themselves one small reference sheet based on the notes in the instance before the "math boss" or given to them by other players.)

If the player correctly thinks "I moved as soon as I knew where to go, but I was not fast enough", that is only acceptable insofar as they perceive an actionable step to know where to go faster on their very next attempt and are willing to take it. (Which not only limits the speed one can demand of players, it largely confines such demands to high-end duties.) "Oh, this cast is always followed up with another attack in a corresponding pattern, I do not have to wait to see the follow-up" is actionable so long as you can get the player to notice the connection between attacks. "I should be looking at my debuff bar when this cast finishes" is actionable, but only reliably perceived in high-end duties, since casual players as a whole have not currently learned to reliably look at their debuff bar at all. "I should drill my planned movement sequence for this mechanic" is only actionable for players who already have such a sequence and are willing to dedicate external study time to a single mechanic, qualities you cannot rely on at all below Savage - and even in Savage and Ultimate, there are strict time bounds to that before the player gives up instead.

"I just have to react faster" is not actionable under any circumstance, and therefore not acceptable. Even the vast majority of Ultimate raiders will not perceive "make time in one's schedule for generic rapid processing drills, and keep that up over weeks to years for at most 10%-20% improvement, before returning to progressing the duty" as an option - and if you directly tell them to do it, they will balk!

Proposed changes to the player's Earth circumstances are almost always not actionable either. The speed of light and the Internet infrastructures of different regions introduce unavoidable latency, but that does not make "move to live beside the servers" actionable unto the player. (Indeed, players may have moved away from their original region due to a variety of Earth circumstances, but not be able to move their character without losing various server-bound features (like housing!) and/or the ability to play with their friends on that region's Data Centers.) Even "get a VPN" may not be actionable for a player on a tight budget, let alone "change Internet Service Providers" or "find housing that allows for a hardwired Internet connection". Likewise, "get a better computer / console beyond the declared minimum specifications", "play on PC to use accessibility third-party tools", and "get another monitor to flip through many diagrams" are not actionable on budget grounds.

"That will lead them to success": The player must succeed eventually, rather than getting stuck in a dead end or an infinite regress of failing by ever-slimmer margins, or you will exhaust their potential motivation and they will give up. Simple enough, and another reason players find the prospect of "just react faster" demotivating - they often know intuitively that training reaction time reaches a dead end eventually, and are loath to invest heavily into it without knowing if they can improve sufficiently.

(Puzzle mechanics are an interesting case here. From the perspective of a player aiming to solve the puzzle, some reasonable directions for potential solutions may be dead ends, and that may even be necessary for the difficulty of the puzzle. But a well-designed puzzle mechanic will give the player clear feedback on all wrong potential solutions - even if only with some random variations of the mechanic - that tells them their plan is wrong rather than imperfectly executed. That feedback is what prevents the player from getting stuck in a dead end even if they enter it, since it shows them to rule out the potential solutions in that direction eventually. As for that "eventually", see the next sub-principle.)

"Within an effort they find reasonable": The player's cumulative effort put into the duty, both every mechanical failure you hand them and every mechanical success they work for, must not exceed the effort they are willing to put into it. The player does not have Omega's relentless drive to evolve, at least when it comes to your game rather than their life as a whole. They can walk away at any time. You have to work with the time and effort they are willing to give you.

Obviously the player's definition of "reasonable effort" will vary massively depending on the context - just about anyone will be quite frustrated if they cannot complete a regular duty before its instance timer expires without advance knowledge of the mechanics, while raiders tackling an Ultimate would be understandably angry if they could complete one that quickly.

"Correctly perceive": If the player believes incorrectly that a way forward exists, they will try what they believe to be a way forward, continue failing, then give up. If the player believes correctly that a way forward exists but is incorrect about what it is, they will try the route they perceive rather than the route that works, adding to their cumulative effort spent. Accordingly, the further your intended solution is from the player's existing mechanical knowledge, the more extensively you must guide them to the answer. The easier you want the duty to be, the more extensively you must guide the player to mechanic solutions. This is why regular duties cannot have puzzle mechanics - Duty Finder's matchmaking cannot even guarantee the presence of a single player who can solve the puzzle in the party, let alone the patience from the whole party to wait - and all the most elaborate puzzle mechanics are in Ultimates.

But the implications are not limited to puzzle mechanics. The Duty Finder population can actually learn quite a wide range of mechanics, but teaching through regular duties must be done in small incremental steps. There, the player is trying to finish their quest or roulette, and does not have the interest in studying anything outside of attempts at the duty to learn a complex concept all at once. (A key point in which Shadowbringers and Endwalker did better than Stormblood is the guidance and teaching: using markers, NPC commentary, and sometimes even NPC demonstrations to teach players in those small pieces.)

"You tell a player they have failed something": If a player in some sense fails but perceives no penalty, it does not matter whether they perceive any steps to improve; they have no reason to take them regardless.

This is often a matter for job design, as duty mechanics are themselves pass/fail, but it is relevant to duty design where jobs create multiple degrees of mechanic success. If a casual player only undertakes regular duties and never actually sees an enrage cast, it is fine for them not to understand any steps they can take to increase their damage output without upgrading their equipment - including mechanic resolution techniques such as slidecasting for jobs with frequent cast times or gap-closing back to a boss immediately after the snapshot of a mechanic that requires leaving melee range. Not accomplishing such things will not frustrate them, even though it is "failing" relative to optimal performance. Should they choose to pursue greater skill at their job, whether to undertake harder duties or simply for intrinsic enjoyment, then they may come to perceive the downtime / lower potency output as a penalty, and at that point the rest of the principle once more applies.

This is also relevant to regular duty design when it comes to giving feedback to the player(s) who can act upon it.

For example, Alexander - The Fist of the Son (A5N) contains a "tank swap" mechanic: a series of attacks targeted at the player character with highest enmity that are especially dangerous if the same player character takes all of them, encouraging or requiring the two tanks in a full party to swap who has highest enmity in order to split up the series of attacks. In A5N, the relevant series of attacks is very slow, with layers of feedback. The boss, Ratfinx Twinkledinks, grows dramatically before using four individual Gobjab attacks, each of which inflicts a stack of Headache. The Headache debuff description reads: "Suffering mild head trauma. Damage dealt is reduced. Increased trauma results in a Concussion." If this does not clue the player in, the Concussion debuff makes the player character unable to act with a special animation, which becomes quite obvious to the player. Only after that does the boss use the Gobstraight tankbuster, which deals massive true damage if taken by a player character with Concussion, thus producing a KO. Tank swapping at any point between the first Gobjab and the start of Gobstraight will avert the KO, and tank swapping at any point between the first and fourth Gobjabs will avert the Concussion as well.

The biggest problem is that all of this feedback is given to the player whose character has the current highest enmity, the "main tank". The player who needs to act in order to take highest enmity, and therefore needs to receive feedback, is the other tank, or "off tank". (Nowadays, the main tank can Shirk the off tank, yes, but that will not actually swap the off tank to highest enmity unless the off tank already had at least half the main tank's enmity. And Shirk was added in Patch 4.0 Stormblood, so tanks did not have that option when A5N was current. The off tank absolutely had to be the one to act, in an environment of job designs where the easy ways to have high enmity involved sacrificing damage output.) And the off tank perceives none of this unless they not only look at their co-tank's debuff bar, but read what the debuffs do - which the vast majority of casual players will not do! They will perceive only that their co-tank "mysteriously exploded", and will likely attribute it to a failure of mitigation or healing.

Given this duty design, what must happen for the casual player off tank to learn to do better next time, without the unrealistic expectation of reading their co-tank's debuffs? First, the main tank (or another party member watching the whole party's debuffs) must work out that it is possible for the off tank to act to split the attacks. Second, whoever figures this out must tell the off tank that they failed the mechanic, which requires both social willingness and some typing speed. Third, the off tank must accept this rather than blaming another party member. Fourth, some party member must break down the relatively complex concept of tank swapping so that the off tank understands when to take the highest-enmity spot, how to do so, and that the former main tank will have to take the highest-enmity spot back in a future tank swap at some point.

Casual players see all of these steps as significant hurdles, and so A5N could not teach the Duty Finder population to tank swap. (Players pursuing high-end duties do manage it, because the expectations surrounding high-end duties create a player population that is more dedicated, expecting to put in more effort to learn, and willing to kick players who cannot or will not take feedback from others.) More broadly, casual players cannot be relied upon to give others feedback or receive it, so you as the duty designer have to give the feedback to players who can act upon it.

(Indeed, Heavensward is further from the design style I want than Stormblood not because of its attitude to challenge, but because it did worse at teaching players. Alexander - The Burden of the Son (Savage) (A8S) is the duty that convinced me to pursue Ultimate, because I thoroughly enjoyed the difficulty and the intense focus required.)

Want to teach casual players to tank swap? You can, but not like that.

First, create a marker for attack sequences that should be tank swapped, so that players have a cue to apply the concept in future duties before seeing the enemy finish the dangerous series of attacks. (That could be on the castbar, like the "interruptible cast" marker introduced with Patch 5.0 Shadowbringers, or it could be on the boss's current target like the various tankbuster type markers introduced over the course of Shadowbringers and Endwalker. Either offers the opportunity to give extra feedback on a successful swap, over the "target of target" HUD element or by moving the marker to the boss's new target.) Then create a solo instanced duty with an NPC co-tank who can instruct and demonstrate. For example, if you wanted all players entering Dawntrail's endgame to learn it, whether they currently play tanks or not, the solo instance could have been in the MSQ as an Echo vision of Wuk Lamat's combat training with Gulool Ja Ja. (Even players who dislike Wuk Lamat as a character can still come away with new mechanical knowledge, and it would fit the themes of the existing MSQ.) In that duty, have the player character be the main tank first, while the boss begins a very slow and flashy tank swap mechanic that will show the player the new tank swap marker for the first time. (A5N did the "slow and flashy" part right.) During the series of attacks, have the NPC co-tank comment on the danger and demonstrate a correct tank swap to the player, taking the end of the series of attacks and moving into position to keep the boss still. Then, after a short "spacer" period of familiar mechanics, have the boss begin the same tank swap mechanic again targeting the NPC, showing the player the tank swap marker for the second time. Now that the player has seen a tank swap demonstrated, the NPC can comment that the player character needs to take the boss's attention back, and the duty can even give a non-diegetic prompt as some solo instances do. If the player correctly takes the highest-enmity spot from the NPC during the mechanic and keeps it through the end of the series of attacks (using Provoke and their tank stance), give them some appreciative feedback from the NPC and carry on. If not, KO the NPC and start the duty (or section of the duty) over.

(Concepts building on that foundation, such as when to use Shirk and double tank swaps, could be covered immediately afterwards but are best covered once players have solidified the basic form.)

Do that, and they will try to tank swap when they see the marker again on their co-tank in future duties. (And since they have seen both sides, they will not be confused when another tank swaps off them.) They will likely not be quick about it the first few times, but that would have been a good opportunity for the first two Dawntrail trials to allow players to practice with Duty Support without any fear of embarassment. For some concepts, you really have to guide the player's hand to get casual players to pick them up.

"Must": Why not "should"? Because "should" creates temptation to put the responsibility back on the players instead of the game design, without first seriously considering how the game can be designed to improve the player experience.

If a casual player mistakenly thinks that Normal Raids are Serious Raiding and avoids them accordingly, that is not the community's responsibility to fix - that is your responsibility to tell them otherwise. (Players who complete the MSQ through Duty Support may barely talk to other players at all!) If a colorblind player struggles to tell the difference between the two types of fists in Alphascape V3.0 (Savage) (O11S) or TOP, that is not their fault - that is because you did not make the shapes distinct enough without relying on color cues. (Everything else in TOP is thoroughly distinct for colorblind players... in contrast to the tethers in Asphodelos: The Fourth Circle (Savage) (P4S) Act 2, which have no distinguishing features at all other than the colors shown over player characters' heads. Likewise, the orbs in Emerald Weapon (Extreme) are distinguished only by their colors.) If a player cannot complete the Active Time Maneuver (also known as a Quick Time Event or QTE) in Seat of Sacrifice Normal, or injures themselves trying, that is not their failure to learn - that is your design error in considering what pace of inputs the game should really require or make players think it requires.

And yes, I am aware that that particular QTE has a "fakeout" where the first 75% of the bar depletes rapidly to make the player think they are always on the brink of failure. I have seen the metronome demonstrations that it can be completed at 200 actions per minute (APM), even though it looks like the player is about to fail. I am aware that QTEs in this game do not require clicking specifically; any button that does not open a menu, send input to the chat window, or cause the operating system to take focus off the game will do. It is still an unreasonable demand to make of players, because your actual gameplay is not nearly that fast even on fast jobs, so it needlessly excludes players who are capable of the interesting challenges you want to set them.

Let us take a very fast job and work through the math. Suppose a player is able to do a perfect MCH Hypercharge window, hitting Heat Blast / Blazing Shot every 1.5 seconds and hitting a Gauss Round / Ricochet / Double Check / Checkmate evenly in between every Heat Blast. That is two inputs every 1.5 seconds, so one input every 0.75 seconds. Suppose the player is able to keep up this pace of inputs continuously, not just during the brief period of Hypercharge. One input every 0.75 seconds is 80 inputs every 60 seconds, so 80 APM. Even if the player uses only one hand for actions with animation locks (primarily job and role actions), leaving their other hand completely free for movement and targeting, and they are capable of the same APM with their other hand while keeping both hands perfectly staggered... that is still only 160 APM. A player can be comfortably able to play one of the fastest jobs in the game and still be physically unable to succeed at that QTE. (Or be at high risk of injury from attempting it repeatedly!)

And since the penalty for a single player failing that is an instant party KO, in an MSQ duty, that locks them out of the rest of the game.

That math pretty much matches my APM, by the way. I deal with QTEs in this game by giving up on controlling what keyboard keys I hit for the duration, and instead devising an elaborate method of hitting multiple keys with each finger motion by "rolling" each finger along one axis with staggered timings while "rolling" each hand along a different axis. (Note that this method will not occur to most players, and is very demanding on the player's motor coordination, which means that a player with limited APM is quite likely to be unable to do it even if they think of it.) And even then I nearly did not make it through the sustained input requirement of the Seat of Sacrifice Normal QTE. It is absurd that anyone who can clear an Ultimate was nearly hard blocked from completing the MSQ. This is a clear design error.

In contrast, the QTE in Alexander - The Heart of the Creator (A11N) is entirely acceptable, as it requires one input in several seconds to avoid an individual KO, and that capability is likewise required for even beginner gameplay. Likewise, the required use of the Omega Jammer in Alphascape V3.0 (O11N) is entirely acceptable even though failure generally results in a party KO, since the Omega Jammer has a 1.5 second cooldown and the party has significant leeway on the number of collective uses they need to form the shield. That does not require any more input speed than playing a very slow job casually, nor does it require better input cadence, and the players who struggle most can still be helped through the duty by their party members contributing more inputs. They match up to tasks that are both much less demanding and inherently necessary for core gameplay, so you already have a good reason to require them.

Since QTEs are not used in this game for anything mechanically interesting, you could have an accessibility setting to remove them or turn them into single button presses like the A11N one. Or you could replace them for everyone with forgiving cadence checks like the Omega Jammer, which would still function well to represent the player character fighting independent of their job actions. You have the technology. But you need to think about that sort of thing every single time, or design errors will slip through.

Every expansion has various good mechanics, even Dawntrail. But having mostly good mechanics is not enough. It only takes one bad mechanic to ruin a duty. It only takes one bad duty to ruin a roulette. It only takes one mechanic a player simply cannot do to prevent them from continuing.

You must meet the bare minimum standard of the duty being playable without pain or undue injury risk every single time. It is simply the rigorous nature of the task.

--------

The first major principle comes of considering how the player's required effort estimation changes. What about how the player's potential motivation changes?

Well, what moves the player to enter a duty in the first place? Not the effort that they expect to put into the duty, but everything they expect to get out of it: story progression, power fantasy of playing their job, access to and power in later duties, access to other game systems and areas, cosmetics, light entertainment, personal accomplishment, socializing, completionism, ... Gear is either cosmetic, for access to and power in later duties, and/or a form of accomplishment. Gil is similar, though it can also be used for non-duty gameplay. The meaning of an in-game item comes from the journeys we take for them and/or with them, without which they are just pixels.

And from the player's perspective, the total rewards of completing a duty are fixed but initially unknown, just like the required effort to complete the duty. (Even if they know how many times they must do Expert Roulette to get all the tomestone gear they want, they do not initially know how much and what forms of enjoyment they will get out of the duties or the gear.) So they likewise continually refine their estimation of what they will get from completing a duty, changing their potential motivation. If their potential motivation drops below their estimation of the required effort to complete the duty, they will also declare "not worth it" and quit the duty - depending on the cause, this can be out of frustration, boredom, or apathy.

Hence the second major design principle of this letter:

When trying to make the game challenging, do not lose sight of making it fun throughout. You must challenge the player to avoid boredom, but you can only challenge the player in proportion to what they get out of undertaking that challenge.

Let us examine some corollaries.

The player is constantly refining their estimation of how much they will enjoy the game later based on how much they are enjoying the game now.

You cannot expect the player to persist in improving at combat for very long at all without giving them regular positive feedback of actually succeeding at something related to that improvement, even if the success does not take the form of a duty completion. Thus, especially for casual players, "fight, win, evolve" is actually the correct order of operations. The improvement comes by learning from failure, but it needs success too. Even Ultimate raiders get frustrated by spending hours on progression without doing the mechanic they are working on correctly.

Likewise, the player's estimation will naturally include factors outside of duty design, and outside of combat entirely. If the player is interested in the story, their finding Wuk Lamat poorly written will mean that you have less opportunity to challenge them in the MSQ, where they reasonably expect to see more Wuk Lamat for their trouble. If the player wants something specific out of their job, not having and funneling them into a job that matches that desire will make them get less out of duties, and so have less tolerance for putting effort into duties. If the player wants to play their Warrior of Light as a morally upstanding hero - which most players do - and considers the Endless to be people, forcing them to genocide the Endless has likely permanently put them off of all future storylines and the associated duties, even if they continue the game at all. Dawntrail has done rather poorly at giving players who are not already "good at combat" a reason to persevere.

(Personally, I started playing the game for the old crafting system, and pushed through my initial struggles with the MSQ duties to reach to new zones to craft and gather in. Indeed, I first started attempting high-end duties in order to prepare myself for future MSQ requirements, and then discovered that I prefer the planning-oriented design style of raiding and its encouragement of job mastery to any design style so far for regular duties. And that got me far enough to start seeing improvements in how I work with my physical limitations outside the game, which is an extremely strong motivation to raid. When it comes to player persistence, I am very much an outlier... and yet someone just like me who started playing today would not make it to the endgame at all. The new crafting and gathering actions are good for restoring rotation depth, but they are not nearly enough to sustain someone like me through the discouraging aspects of the Patch 7.0 MSQ duties.)

Of course, the player's expectations of enjoyment of future duties will be informed by the duty they are currently in, whether they complete the duty or not. (And the player almost always has some interest in completing future duties of similar difficulty if they have a healthy interest in the game - pretty much the only non-concerning reason for a player to lack that interest is pursuing a single Ultimate for glamour purposes.) Push the player too hard, and they will not enjoy the duty even if they complete it. And if they keep not enjoying a category of duties, they have good cause to give up on the category. This can arise from their party "carrying" them to completion, or in solo instances where the panic of repeatedly scraping by and worry about future duties push out enjoyment. Most players want to feel useful to their party, even in casual story-oriented play.

(When The Copied Factory first released with Patch 5.10, I struggled with certain mechanics and found them overly reactive. Having that experience once is one thing. Completing the duty several times in the first week, in order to get a specific gear piece for raiding purposes, and still having reaction problems with mechanics is another thing. When subsequent weeks still did not improve matters, I made a detailed plan for each such mechanic just like I did for final Savage floors, complete with prepositioning not only my character, but my hands, eyes, and camera... which resulted only in my character being KOed in the safespot instead of out of it. I then asked several raider friends to help refine my plans, including one who had already completed TEA, and none of them could suggest improvements.)

(At that point I had gone above and beyond to rise to the challenge, only to find that my initial impression of a reaction time problem was correct. So not only did I stop entering The Copied Factory, when The Puppets' Bunker released (with Patch 5.30) I refused to unlock it - to avoid further worsening my chances of getting a personally enjoyable duty in Alliance Roulette - and pointed anyone who protested on gearing grounds to my Eden's Verse Savage gear. To anyone who protested because they thought I would enjoy it, I replied "ask again when I clear an Ultimate." Not as a deliberately absurd statement, but as a logical conclusion: having already exhausted all the rapid ways to improve my practical response time by better planning and HUD Layout, the only remaining option was to undertake hundreds to thousands of hours of practice efficiently processing mechanics and hope for improvement... and already being comfortable in Savage, the only remaining higher difficulty that could show that improvement was Ultimate.)

(I knew full well that the other 23 players could carry me through an Alliance Raid even if my character spent the entire time KOed. I was even already playing a DPS. I was miserable regardless, and naturally unwilling to attempt the extended reaction time drills in the same duties that were making me miserable. Needless to say, the vast majority of players who see frustrating lack of personal improvement in a regular duty are not going to even attempt to fix that in Ultimate - they are just going to quit the game.)

It is also worth noting the game's repetition-based gameplay loop. If the player knowing all the details of a duty makes it boring - or frustrating - they will not want to repeat that duty. In particular, based on the Patch 7.0 duties:

• Delaying the first indication for what random variation of a mechanic the enemy is doing does not make the duty interesting or fun. It only teaches players to learn when that first cue appears and wait until then in boredom, despite the brief moment of stress from resolving the mechanic once the delayed cue is finally given. The result is a boring experience punctuated by brief moments of stress, and at no point is it fun. Even stressful and difficult duties can be boring; this is why I have been more likely to fall asleep in Dawntrail duties than those of any previous expansion!
• Movement sequences that push reaction within the sequence are not fun, nor are they interesting. The player is denied the opportunity to plan, and instead learns that there is no recourse but reacting repeatedly - with the result of being bored even during the reaction stress. (If you are expecting the player to get some sort of enjoyable adrenaline rush out of reacting, well, I do not get that, and the mixed player feedback makes it clear that I am not alone in that. It is annoying at best to people like me, and your player population has been shaped by the older turn-based Final Fantasy games, along with this game itself historically being quite lenient on reaction time for a real-time game. Anyone who does get a reaction thrill has lots of other options.) Instead, give the player the information needed to plan the movement sequence, and then ask them to execute it at a speed appropriate to the duty and intended effect of the mechanic.
• Making needed visual indicators difficult to see is anti-fun. (Mind that there are significant differences in style of visual processing even between able-bodied and fast-reacting players using the same console / computer setup! Plus a screenshot that gives a clear view of a mechanic is not an accurate representation of what the player sees with limited time, since the human eye does not have high detail outside central vision and various action effects briefly blur the screen.) For players with any sort of visual impairment, photosensitivity, reliance on rapid processing, or simply visual processing style you did not expect, it is an active detriment. And for everyone else, it does not matter either way. Have visuals that suit the lore of the duty, yes, but do it in a way that prioritizes visual clarity.
  (The word "needed" is important. The A8S Mega Beam obscured by explosions is quite fun, because it is actually a planning test - its earlier appearances teach the party that it is baited on a random player character, so they need only arrange their solution to the preceding mechanic to create a safe zone no matter who the boss chooses for the bait. Plus every duty has visual elements that are not mechanically relevant, included for other reasons, and those may be as subtle as the artist and/or lore writer creating them desires.)
  In fact, ensuring visual clarity makes for more fun mechanics that are easier to design. Why? Obscured visuals delay some players much more than others, while clear visuals eliminate that delay, therefore yielding a relatively uniform discernment time among the player population attempting the duty. (Many forms of obscured visuals also vary how much they delay the player based on random variations of the mechanic.) You can then plan around that discernment time when leaving time for other tasks in the mechanic, such as making a decision or moving their character. This gives you finer control of how long the player has for those tasks, allowing you to tune the challenge level more precisely while ensuring that it remains achievable.
• Adding randomness to a duty does not automatically make it more fun, or even less boring. To be helpful, the randomness must contribute to something interesting, while ensuring that all possible duty timelines created by random variation have a similar skill floor (required competence to complete) for every job. (Branching timelines regarding the order of mechanics, such as those in Alphascape V1.0 (Savage) (O9S) and Abyssos: The Eighth Circle (Savage) (P8S), are generally fine. (There is a limit, in that the player who puts in the effort to plan out all possible timelines reasonably expects to get to use all those plans before they stop returning to the duty.) Major variation in what mechanics are presented at all is prone to unexpected differences in skill floor, and therefore is best avoided.) Randomness in the wrong places can even make the duty less fun, by denying the player opportunities to plan uses of powerful job actions.

To reconcile giving the player an encouraging first-time experience with avoiding boring repeat experiences, encourage and reward skill expression so that the player will add more challenge to the duty at their own pace. Skill expression should be welcomed, not feared. (Which does not have to make fellow players feel bad, since the skill expression need not be clear to any player other than the one doing it.) This is tightly linked to job design, as it relies on the jobs to define what skill expression for each job is. Again from my previous writing on balancing the magical ranged DPS role:

The fifth problem [with relying only on the duties to provide difficulty] concerns the longevity of any given duty, even one of appropriate difficulty for the player. As I am sure you have experienced in raiding, one finds that any given duty gradually becomes much easier as one learns that duty's mechanics. Even if the duty incorporates randomness, one must still learn the variations to reliably complete the duty. In effect, familiarity with a duty lowers the skill floor of completing that duty with any given combination of job and equipment. (Though less so for jobs in different roles that have different parts to play in mechanics.) As a result, any duty that one can complete occupies less than one's full attention on subsequent completions, at any difficulty level from story to Ultimate, even without better equipment. What, then, can occupy the rest of one's attention in order to prevent boredom? Not the duty, by necessity - only the jobs can do so.

However, duty design can and should give the player both the opportunities and the tools to express their skill with their job. Having frequent cast times is what makes moving no more than necessary valuable, but it is duty design that can allow the player to know exactly where an AOE will hit so that they can remove unnecessary movement. (The Patch 7.0 duties have a recurring lack of floor geometry for the player to use as reference points.) Being limited to melee range to effectively attack is what makes staying close to enemies valuable, but it is duty design that can allow a tank to reposition enemies towards a safespot for a later mechanic. Having limited usage of mitigation and healing tools is what makes planning their use valuable, but it is duty design that creates the timeline and its patterns to plan around. (In particular for dungeons, fighting two packs at once - known as "double pulling" - is a form of skill expression. If you are going to deny the player that option for a given trash pack, you should present some other form of skill expression in that trash pack instead.)

Satisfying mechanics actively reward the player's skill expression, adding enjoyment and longevity to the duty. What makes a mechanic or player strategy satisfying to execute is not just the opportunity for the player to show their skill and/or knowledge of the duty, but also clear confirmation of doing well. An earlier mechanic leaving room to handle a later mechanic, or even being used to counter the later mechanic, because the party set it up that way. A spinning AOE dodge where the final hit comes almost but not quite to the player character's position, not by accident but because the player knows how far it turns. A healing and mitigation plan that effectively uses a cooldown exactly on cooldown multiple times in a row, because the party mapped out the fight timeline to make that happen. (This is not even limited to high-end duties - Eden's Promise: Anamorphosis (E11N) allows a magical ranged DPS to Addle three Burnished Glory raidwides in a row by using Addle early on the first Burnished Glory and then exactly on cooldown twice thereafter. Drift the cooldown and the last Addle will be too late.) And yes, sometimes a sequence that the party gets to watch resolve after they have set it up - a flashy sequence is a good way to let the party see the results of their work and create a breather before the next mechanic. The existing Dawntrail duties are sorely lacking in such mechanics, which does their longevity no favors.

--------

Since players have so frequently remarked on the demands on working memory and reaction time in Dawntrail so far, these two aspects of duty design deserve special attention.

Working memory mechanics are like soy sauce on sushi: a small amount enhances the flavor, too much overwhelms it. (Which is why the soy sauce is supposed to go on the fish, not the rice!) Totally aside from the appropriate difficulty of memory mechanics, Patch 7.0 has too many of them, crowding out other mechanics that could provide other forms of difficulty. The result is boring and repetitive duties.

As for the appropriate difficulty of memory mechanics, the player does have a working memory limit inherent to their brain, which they cannot change... and which they need to use for playing their job in the duty, not just doing the mechanics. (Yes, even for downtime mechanics - jobs still have healing, buff-based mitigation, and resource-building tools to think about.) The player finds a job and/or a duty less memory-intensive with practice not from expanded working memory, but from learning bigger "chunks" that they can work with fluidly. For example, an intermediate RDM can think "basic melee combo" for what a beginner has to break up as "Enchanted Riposte, Enchanted Zwerchhau, Enchanted Redoublement, Verflare / Verholy, Scorch, Resolution".

Plus the player cannot be expected to offload the task of remembering to their chat log - even if they have the APM to type in combat, they may be using a controller without a keyboard in reach or extra hotbar space for text macros. They can only be relied upon to have one tool for storing a duty-provided piece of information outside their brain, and that only if surrounding mechanics permit: moving their character to a location related to the mechanic, such as a direct or conceptual "first safespot". (Prior to Patch 5.2, the party as a whole could also agree on moving waymarks to remind themselves of the random variation shown, but since players can no longer move waymarks in combat, that is no longer an option for memory mechanics.)

What is the working memory limit of the human brain, then? Well, the classic "seven plus or minus two [items held in memory]" is at best an upper bound, and newer experiments best fit the idea that there is no fixed number of items at all, but instead pushing to remember more items results in less complexity and detail for each, until eventually there is too little detail to usefully be a memory. If all the items to be remembered are very simple and familiar, such as individual digits of a number, then "seven plus or minus two" is roughly accurate. (Indeed, telephone numbers without area codes provide a ready demonstration of that specific working memory task, called "digit span".)

While memory mechanics can often be broken down until the player only needs to remember appropriately simple and familiar concepts like "spread" or "left", the rotational chunks of the jobs are not that simple - and making them that simple would be terribly dull. So we must take the low end of "seven plus or minus two" - that being five items - and set aside not just one item, but at least two and possibly more, for the player to continue playing their job. (As well as potentially more room to plan ahead for other mechanics!) Therefore, the total of "stored items not yet released" from memory mechanics may never exceed three simple items at any point in a duty's timeline, and should almost always be less. If the player has a good working memory, they can and should occupy themselves with their job, looking for hidden patterns, planning for later mechanics, ...

Examples:

• Some recurring sets of mechanics where the boss randomly choosing one counts as "one item" for a memory mechanic: {spread / pair / light party stack / full party stack}, {left / right / front / back}, {in / out}, {Deep Freeze / Pyretic}.
• In Eden's Promise: Eternity (E12N), the stored primal combination ground AOEs count as two items, since first-time players will generally remember the primals individually and work out the overlapping safespots. In the Savage version (E12S), the same primal combinations start as two items and end as one item, since the player will see them enough over the course of progression to memorize the overlapping safespots and work with those rather than the individual primals. (And for a final Savage floor, if the player is having problems with how fast they remember the safespots, they can actively study the five possibilities outside the duty, which does not take that long.) FRU would be able to treat them as one item from the beginning, due to the high expectations for external study and number of attempts at the duty in Ultimate.
• In Seat of Sacrifice Extreme, Quintuplecast looks like it violates the three item rule. However, the party can arrange themselves to do the whole mechanic in their clock spots for the Absolute Stone III proteans and close to each other (and the boss) for the Absolute Holy III stack, which allows the player to not bother remembering where those attacks are in the sequence. The remaining three attacks perfectly fit the three item rule, even if the player is not comfortable reconstructing the last attack from the previous two.
• Mascot Murder, the Living Memory World FATE against Mica the Magical Mu, is in flagrant violation of the three item rule. First the boss prompts the player to remember cards (all numbered from one through six) and displays six cards covering the arena, putting the player up to six items to remember as the boss hides these cards before the next section of the mechanic. Then the boss draws a card out of its hat, which the player must match to the cards covering the arena, though they stay at six items to remember since they can move their character to the matching card. (Though later repeats of the mechanic drop puddles on player characters after the hat cards are shown, which can drive them off the card in the arena if they are not careful about how they dodge.) Then the boss draws a second card out of its hat, which the player must again match to the cards covering the arena, and this time they have to remember the location as a seventh item. Then the boss draws a third and final card out of its hat, allowing the player to match the drawn card to those covering the arena once more before dropping the memory of the latter. Depending on how fast the player does the matching, they may briefly jump to eight stored items before dropping down to two. (Finally, the boss asks the player to answer which card it drew first, second, and third, with later repeats doing so in a random order and with other AOEs in between.) But even seven is wildly unacceptable, seeing as they are playing their job the whole time and not just doing a digit span test!
  Just because World FATEs are casual duties and players who struggle with working memory can be carried, that does not make it appropriate to make them miserable! (In my experience there is a hidden pattern (that the safe cards on the arena floor do not share any edges), but that does not matter - not only does the player need to have a good experience before finding any hidden patterns, but noticing them is harder under high attention demands.)

--------

As for reaction time, I wrote about this back in January, but I must expand upon what I wrote:

The second problem [with relying only on the duties to provide difficulty] you have also already experienced with Anabaseios Savage, but more subtly: there is only so much you can demand in duty mechanics. A player can only react so quickly, move so precisely, focus for so long, and so forth. They cannot improve these attributes much by "natural" practice once they have learned the basics of gameplay. And even a player who is dedicated enough to undertake deliberate and thoughtful practice on these attributes will only have so far to go before they run into the hard limits of their body, including their brain. Running into such limits as a player feels awful, especially if it is due to disability or being outside the human body's brief physical prime - a concern for both the aging MMO playerbase and the family members they may want to share the game with! (As a disabled raider, I could talk about this all day, but that would be outside the scope of this series.)

Both regular duties and Ultimates have been grappling with these limits for years, and Extreme and Savage have gradually started facing them too. (For one example, consider Anabaseios: The Tenth Circle (Savage) and its Jade Passage orbs. The fact that they appear within the Pandaemoniac Ray animation and fire shortly thereafter makes them quite reactive, especially when they are later combined with Daemoniac Bonds adding more flashy animations and movement requirements. This sort of design even encourages players to use third-party tools to remove the flashy animations or otherwise get information more quickly, and Anabaseios Savage is full of it.) Players have already started remarking on the fast pace of duties.

These physical attributes limit not only the range of battle mechanics you can make, but how hard you can make them, and how hard you can make them if you want high-end duties to be possible outside a brief player age range. If you refuse to place difficulty in the jobs, these same limits will extend to how difficult you can make the top end of the curve at all, and not in a satisfying way. A player who is currently stuck on an aspect of skill they can improve may aspire higher, reach further, remain motivated to play. A player who is stuck on a physical limit and knows it - or sees the highest difficulty held back by other players' physical limits - is necessarily demotivated, for they know that no amount of effort they can put into the game will fix it.

When I wrote that, I was imagining a continuation of the game's slowly increasing pressure on reaction time over the course of Shadowbringers and Endwalker. I was not expecting Patch 7.0 to take a flying leap into more reactive mechanics! (Especially since your engine and the inherent latency of long client-server trips do not suit reactive mechanics well.) In this regard, Patch 7.0's duty design direction has been the exact opposite of helpful.

Obviously this is a real-time game, and therefore requires the player to meet some standard of reaction time. (If a prospective player sets up their HUD Layout and keybinds to their liking, and still cannot react to a basic ground AOE in less than ten seconds, they probably do have some limitation you cannot reasonably accommodate.) But the real-time nature of the game only requires the player to meet a fixed standard and stay there - it is not necessary to demand that the player react ever faster. Indeed, demanding that the player react ever faster is only useful in niche games that are designed as reaction time trainers, since even action games will eventually have players hit their physical limits. Since Final Fantasy XIV is carrying on the legacy of the originally turn-based Final Fantasy series and attracts many "non-gamers" to play with their family and friends, a generous reaction time standard is best for the game even aside from the aging MMO playerbase.

Why, then, is it intuitively correct that the updated version of Copperbell Mines paces its mechanics slower than The Royal Menagerie (Shinryu Normal) and The Ghimlyt Dark? After all, all those duties are required by the MSQ.

• The player cannot be assumed to start the MSQ with familiarity with video games in general, let alone the genre specifics of tab-target and holy trinity MMOs. They can be expected to pick those up over the course of gameplay. In Copperbell Mines, they may still be getting used to the sheer volume of information on their screen, along with foundational concepts like "class / job", "party", and "target". You can show them something slowly, but at that point you cannot rely on them seeing it at all! By The Royal Menagerie, not only are they used to the game's basic systems, they have built on their fluency with foundational concepts to be comfortable with recurring mechanics like "stack", "tankbuster", "raidwide", "add", ... Without any change at all in their reaction time, they understand more quickly what the duty is asking of them because they are better able to organize the information given to them and fit it into their existing concepts.
• The player starts the game with the default HUD Layout and keybinds, which are almost certainly not ideal for them - and may even be downright difficult and counterintuitive to them. (For example, nothing in the game tells the player to try both Standard and Legacy movement modes.) In Copperbell Mines, they may well not know what to consider in setting up the interface to suit them, and may even still be slow with their movement keybinds. By The Royal Menagerie, they have gotten used to their interface and looking over it, even if they stick to the default rather than adjusting it for themselves.
• One way to improve and maintain the human brain's generic rapid processing is real-time video games. Like this one. If the player does have any easy improvement in reaction time available to them, they get it over the course of the early MSQ and other regular duties!

Out of all these reasons, the only one that continues essentially indefinitely is expanding the player's library of game-related concepts, the mechanical layers of which are also known as "mechanical vocabulary". The average player in Stormblood duties will handily beat the average player in early A Realm Reborn duties in mechanical vocabulary, overall game familiarity, interface comfort, and reaction time. The average player in Dawntrail duties will handily beat the average player in Stormblood duties in mechanical vocabulary, but nothing relevant to their speed at dealing with mechanics.

Accordingly, Dawntrail duties can expect the player to make better guesses about what the duty is asking of them during their first time, use their existing concepts more effectively, pick up new mechanical concepts faster, ... than they did back in Stormblood. But the player in Dawntrail duties cannot practically respond to mechanics any faster than they did back in Stormblood. Indeed, one reason that Stormblood is the closest existing expansion to the duty design style I want is that it is the last expansion before mechanics that were still too fast even with practice started creeping in.

Some players have complained of mechanics being too reactive and feeling split-second, and other players have replied that the game does not actually give the player less than a second between presenting the first cue for a mechanic and snapshotting whether the player character has completed the necessary action(s) to resolve the mechanic successfully. While that latter statement is true, it is not a useful response to player frustration for two reasons:

• There are many steps other than the player's conscious perception of time to decide / react between the server sending the first cue for a mechanic and the server checking whether the player character is in the correct state to resolve the mechanic successfully. Those include the server sending the packets indicating the cue to the player's game client, the client system's latency in processing those packets and giving the cue to the player, the player's sensory nerve conduction time, for visual cues the player moving their eyes to focus on the cue (unless they are already looking at it or trained to manage it by peripheral vision, whether by planning or accident), the player's sensory perception processing time, the player's motor planning time converting their decision / reaction into nerve signals, the player's motor nerve conduction time and muscular response, the client system's latency in processing the player's input, however long the player character takes to perform the required action(s) (such as moving over a distance) client-side, and finally the player's game client sending the packets indicating the completed action(s) back to the server.
  Subtract all those other steps out, and the player may well be left with less than a second to decide / react even for a completely individual mechanic, and be accurately reporting that length of time! (For mechanics that involve acting relative to the party, including such basics as stacks and spreads, there are more steps unless the party has prearranged positions.)
• More importantly, [B]it does not matter to the player's motivation whether they have actually hit the hard physical wall of minimum reaction time imposed by their body. What matters is whether they have hit the soft wall of the practical reaction time they have now[B], such that their wanting to do better next attempt is not leading them to an actionable way to improve - and if they are complaining, that is already the case! (If they perceived a way to improve that they consider reasonable and actionable, they would take it instead of complaining.) Remember, motivation is all about the player's perspective.

When I find something too reactive now, I probably really am hitting my hard physical wall. But if you ask a player to jump through all the hoops I did to get there, they are almost certainly not going to oblige you. They are instead going to say "that is ridiculous to expect me to think of, let alone do" and quit.

--------

Let us examine what it means to avoid pressuring the player's reaction time in different types of duties through an example.

The basic spread is an A Realm Reborn mechanic, that has recurred over and over again in both regular and high-end duties. It recurs so often that it is the very first marker you teach in the new section of Hall of the Novice added with Patch 7.10. So why has the Duty Finder population never mastered it after 11 years? Why will experienced players still sometimes get their characters hit by two or more spread AOEs in regular duties, and even occasionally have a slow party KO by stacked spread markers KOing all player characters who can raise?

Because Duty Finder does spreads by reacting to each other, and asking the player to react to another player's choice will always inherently pressure their reaction time. No matter what fixed standard of reaction time you or I desire to set, one player meeting it in such a situation will give their party members less warning - and thus less time to react - due to client-server delays. The player improves up to a point by learning heuristic guidelines like "run away from other party members" and "let those with frequent cast times stand still", but that route will never save them from getting stuck in a loop of adjusting to another player. Even continuously tracking the positions of every party member will not lead to perfection.

(Client-server delays are not the only reason for adjustment loops. People do experience them face-to-face, classically when trying to pass each other in a hallway and both moving the same way. But the resolution is usually much smoother in a hallway - there is no "I was ahead of you on my screen!")

In contrast, the Party Finder and Raid Finder populations spread perfectly, even players who are new to high-end duties and doing their first Extreme. And this is not because the players in Party Finder / Raid Finder are better at the game - Duty Finder matchmaking can put a party full of world-class raiders together, and they still might fail a spread in that environment! Why is this?

Because Party Finder and Raid Finder do spreads by planning, not reaction. The party agrees upon a spot for each player character to go to, and they expect each other to go to their own assigned spots. They may react to seeing the mechanic appear again in progression, but they are not reacting to each other. (And they can make such plans for regular duties if they please, as world progression groups used to do back when Normal Raids were released alongside their Savage versions.) In fact, trying to react to each other instead of following the plan is often frowned upon, with phrases like "never adjust".

--------

More broadly, regular duties must be designed for the Duty Finder population and player expectations.

Imagine the "worst reasonable" party that Duty Finder could matchmake together: all first-timers with no foreknowledge of the duty, all at minimum Item Level, only casual knowledge of their jobs, no knowledge of how to plan for specific mechanics even if they want to, never met before, some returning to the game, others tired and under-hydrated after a long day of work and/or caregiving. (Yes, the latter will make their reaction time worse.) They are all trying to finish their quest and continue the story attached to the duty, and they are a little impatient. They are trying their best in the moment, but not looking beyond the moment, and they certainly have no grand plan of personal evolution.

That party should generally complete the duty before the instance timer expires, and if they do not complete the duty they must correctly perceive that they have come away with enough knowledge to individually queue back into matchmaking and get it the next time. Either way, they should enjoy their time spent in the duty. Challenge them - perhaps even hand them a few party KOs - but without discouraging them from continuing the story. As a result:

• Duty Finder does not prepare outside the game, and rarely prepares outside attempting the duty. Part of why the Hall of the Novice update is so welcome is that "try this solo instance" is about the limit of what casual players can get each other to do, even when the whole party is cooperating. (After all, the player may be on console without a separate device to watch videos or browse guides.)
• Duty Finder is perpetually operating on reaction, since first-timers cannot plan for what they have never seen and even players who complete the duty frequently are unlikely to have its timeline memorized.
• Duty Finder's practical response times are not fast, so the player needs a generous lead time and long periods of information visibility. They are not looking in the right place when the duty first gives them the information they need, they have never actively thought about how they can efficiently move their eyes between information sources in the interface, and they will take time putting it all together - which have so much impact that I often beat my matchmade parties to safespots. (They may also be looking away from cues entirely in order to raise or read party chat.) I have even been regularly beating able-bodied and experienced healers to raising KOed party members in current duties ever since I settled into endgame, despite that being a reaction test that is not even from the duty timeline - because I have taught myself to notice KOs while keeping my party list in my peripheral vision, and they have not. (Sometimes my party position tracking is enough to alert me of the impending KO before it happens, and I can target the player character and use Swiftcast before they even go down on my screen.)
• Duty Finder does not prepare for specific mechanics, as a natural result of not knowing what mechanics are coming. This is why Thunder God Cid did not work out and had to be nerfed: getting three player characters into each tower and getting all of the six Shadowblade AOEs to avoid overlap are more advanced versions of spreading, and thus reliability requires planning who will go where in the Party Finder and Raid Finder style.
• You can get Duty Finder to do a tightly limited amount of general preparation - roughly one thing that is useful without foreknowledge of specific mechanics - before players run from the starting area of the duty in impatience. In Stormblood, that one thing was "wait for the healer(s) to cast Protect on every party member." In Heavensward and A Realm Reborn, that also included waiting for Stoneskin if the party had a CNJ / WHM. In an alternate timeline, that one thing easily could have been agreeing on "clock spots" via a macro or around a waymark, that would then be reused for a variety of mechanics just as Party Finder and Raid Finder do now. (If you really wanted to, you could still do that, but it would require a substantial amount of teaching players new expectations from Hall of the Novice up.)
• Duty Finder requires most mechanical mistakes to allow for recovery and duty completion within that attempt. With no plan and no foreknowledge, they are not going to reach the standard of making very few mistakes per attempt in any reasonable period. As such, mechanics should be carefully examined for what sorts of mistakes can result in an immediate or delayed party KO. Most mistakes should not even guarantee an individual KO for players with good equipment, healing, and mitigation.
• Duty Finder accepts only infrequent penalties for its lack of preparation specifically. The player, so long as they are reasonable, will not be angry at their party members or the game for occasional stacked spreads and similar mishaps. But they will get frustrated by too high an incidence of such things, so mechanics that invite such mishaps are ill-advised.
• Skilled players in Duty Finder will have a completely different experience than the baseline, and it is up to you to make sure they also have a good experience by giving them opportunities and rewards for skill expression. Do not neglect those opportunities in even the easiest of duties. As I have explained regarding healer design and magical ranged DPS design, anything that is appropriate to put in front of casual story-oriented players will not challenge a party that is comfortable in Extremes, let alone Ultimates. (And even the "worst reasonable" players will have a very different experience the 90th time they see the same dungeon in Expert Roulette.) Since your gameplay loop puts all those players in regular duties, that different experience is either going to be occupying themselves with skill expression or it is going to be boredom. Simply completing the duty faster is not enough - strong players can do that while falling asleep by already-acquired skills alone. This is why I made a point of bringing up the connection to job design and satisfying mechanics.

This same approach is why the casual player does not learn complex concepts unless the game (or a fellow player) takes the time to break down the concept into small pieces and teach them that way. Their tracking of effort and reward is long-term, but they are only willing to put in effort in the moment. Guide the casual player to one step at a time, and they will climb a mountain. Set a hill in front of them with no explanation, and they will perceive it as a wall.

--------

In contrast, high-end duties must be designed for the different expectations of players tackling them. The player still likely does not have any grand plan of personal evolution, but they do have a plan to improve at the duty in front of them. While Duty Finder lives in the moment, Party Finder, Raid Finder, and statics live in the future: job performance standards, party coordination, advance planning based on the duty timeline, practicing their execution of those plans in progression... and for putting more effort in, they expect more rewards out in how the duty treats them. Not just rewards in the gear, but in the gameplay experience of the duty itself.

(Of course, there are degrees to this. A player in Extreme probably remembers their plan for a mechanic upon seeing the castbar and executes it with some hesitation, which is the right general idea of planning, but not nearly enough for Ultimate plans. For example, consider shielding TOP's final iteration of Wave Cannon correctly on SCH: in both cases the party must move around extensively during the Wave Cannon castbar due to Alpha Omega's preceding mechanic, so the correct time to cast the first shield without expending Swiftcast is during the preceding castbar while looking at the preceding mechanic's cues, planned carefully not to be so early that the shield expires before absorbing damage. (Raising is almost useless there due to the structure of the Dynamis buffs, so one can expend Swiftcast to shield without much of a tradeoff, but it is more fun not to.) And then the second shield must be in place 6 seconds after the first shield is fully used, in which time the SCH must also move and help heal the party back to full HP, so the slightest hesitation will lead to a party KO. Oh, and they must also remember the other mitigation that the SCH and the party as a whole must apply to every hit, regardless of what cooldowns they have planned to use where. The whole plan is based on knowing when each of Alpha Omega's attacks will land before they even begin, and it is a delight, but a player new to high-end duties will not be doing it.)

• In high-end duties, the player expects and wants to prepare outside attempting the duty, including for specific mechanics. Remember the community reaction declaring Deltascape V1.0 (Savage) (O1S) too easy because the world first completion took only a single attempt? It is too easy for Savage, but let us be precise: the world first team was able to complete it in a single attempt because they could use their brief exposure to the Normal version and their general preparation to do the Savage mechanics by reaction. They had good reaction times on their side - that is a physical attribute world progression teams select for - but that would not have averted a party KO if the duty had forced them to make a mechanic-specific plan. (The very first time I entered O1S, without a timeline, I could not do its mechanics on reaction, but I could see exactly why the world first team could.) Nothing in O1S demands a mechanic-specific plan, and that makes it too easy for even Extreme.
• In high-end duties, the player's practical response time for a mechanic improves significantly over the course of learning that mechanic, and more so the more extensive their planning. Here the player can plan to always be looking in the right place when the duty first gives them the information they need, to move their eyes efficiently between information sources, to preposition their character for the possible random variations of the upcoming mechanic. They can work out how different sources of randomness combine in advance. They can practice executing their plan efficiently and without hesitation, even if they never actively think about prepositioning their hands or distilling animations down to the first visual cues.
  TOP provides an excellent example of this in the opening to Run: ****mi* (Omega Version), popularly known as "the Predation Dodge" due to its resemblance to Ultimate Predation in The Weapon's Refrain (Ultimate) (UWU). Those readers who are unfamilar with TOP can see many examples of the Predation Dodge in real time, courtesy of Sausage Roll's study playlist. Without knowing that the footage is from TOP, the casual player observer can tell that the mechanic is not suited for them; they may not identify it as an Ultimate mechanic, but they understand that putting it in Alphascape V4.0 (O12N) would be a miserable failure. And they are correct - even though every single one of those AOE shapes is known to and manageable for the casual player in Alphascape Normal, as is the notion of AOE combinations! (Omega-F casts her cross AOE, Optimized Blizzard III, and her "Hot Wing" front-to-back-line-safe AOE, Superliminal Steel, in O12N. Omega-M likewise casts his point-blank AOE, Efficient Bladework, and his donut AOE, Beyond Strength, in O12N; in fact, the safespot for Beyond Strength is bigger in TOP to accommodate the combination with Optimized Blizzard III. Both have the same weapon tells in O12N that they do in TOP. (They do cast their AOEs simultaneously in O12N too, though there their positions and facing are dependent on the tanks' choices and the combinations are more limited.) And while the casual player does not get to fight Final Omega, they have seen the hourglass AOE sequence with the same safespots in Alphascape V1.0 (O9N) as Latitudinal Implosion / Longitudinal Implosion.) The casual player even has the notion of remembering an AOE pattern without orange telegraphs on the floor. So why is the Predation Dodge out of reach of the casual player?
  The mechanic is purely individual dodging, so there is no coordination requirement. There is no unavoidable damage in it, so there is no healing or mitigation requirement either. And while there is a hard enrage to the phase as a whole, the damage output requirement is not what the casual player is looking at. What they correctly perceive is that they do not know where to go fast enough, even though all the information has been given to them.
  The casual player does not know that the Omega-M and Omega-F pairs always spawn on opposing intercardinals, and so does not know to begin the mechanic looking at an intercardinal with their character prepositioned on a cardinal such that all intercardinals are visible on their screen, nor to look immediately at the opposite intercardinal after locating one clone and processing its weapon. The Ultimate raider at this point in TOP progression does know all that, and even in blind progression has been primed to expect opposing spawn locations by the earlier appearance of a single pair in TOP Party Synergy. (In fact, I check the pairs for the Predation Dodge entirely by looking at the arms of each clone, since three of the weapons are visible there and "no held weapon" is always the skates for Superliminal Steel. Only Party Synergy has a decoy clone.)
  The casual player has to work out what the overlap of safespots is for each combination while the cues are being shown to them. The Ultimate raider at this point in TOP progression memorized each clone pair combination back when learning Party Synergy, and now can memorize how each clone pair overlaps with the hourglass cleaves from Final Omega. (And from there, how each combination flows into each possible other combination, all outside the duty. That is a large part of why the study playlist exists.)
  The casual player has no practice in picking the light gray weapons on the dark gray clones out of the mid-gray floor, gold overlay or not. The Ultimate raider at this point in TOP progression has practiced that abundantly for Party Synergy and still fully expects to take several individual KOs - potentially cascading into party KOs - here. Indeed, by this point the Ultimate raider has gone through hundreds of party KOs in TOP, and the casual player is not willing to persist anywhere near that long for a duty completion.
  If you immensely slowed down the presentation of cues in the Predation Dodge to allow the casual player time to work out the overlaps while in the duty, and guided the player's eyes around the arena by presenting one clone at a time with the matching weapon transition / creation animation followed by a "freeze" to have them go off in pairs, that version of the mechanic could have gone in O12N and posed little difficulty to the casual player, even with the resolution of the AOEs at full speed. (The only remaining pain point would be working out the correct distance from Omega-M without waymarks for the Optimized Blizzard III + Beyond Strength combination.) The difference between this hypothetical Normal Raid version and the extant Ultimate mechanic is purely the processing speed demanded of the player, which the Ultimate raider attains through planning for and practicing upon the specific mechanic. Their underlying reaction time need not change at all - for me the Predation Dodge went from scary to comfortable within a few hours of study and practice, long after I had already plateaued in reaction time. Even before knowing the snapshots, I have extra time for the movement in all but the "outer" combinations (Optimized Blizzard III + Efficient Bladework) that have the longest distances to move between the two safespots.
• In exchange for their effort in planning and holding themselves to a standard of job skill, the player expects that a reasonable amount of effort put into a high-end duty will yield a plan that (when executed correctly with practice) leaves them ample leeway on their reaction time and results in a "clean" duty completion every single time. ("Clean" as in "no KOs, Damage Downs, or other penalties for failing mechanics". Recovering from failed mechanics necessarily involves reaction to the failure.) High-end duties can, should, and generally do move faster than regular duties, but only ever to force the player to have a plan and execute it with appropriate fluency. Give them all the information they need well in advance and then demand that they act at a specific time, or even perform a sequence of actions without pausing, yes. Have some of that information include debuffs and/or markers given to other players' characters, yes. Demand that they act while receiving and processing information about the next mechanic or portion of a mechanic, yes. Display some necessary information for a limited time, yes, though the tightest limits are only viable in Ultimate to force the player to work out an order of processing and remembering cues. And all that will result in mechanics that can feel reactive while the player is still learning them, because the player does not have the practice with their plan to process the specific mechanic efficiently at that point. But that feeling must disappear with a reasonable amount of practice, as the player's practical response time for that mechanic improves; once the player learns the mechanic, they should have enough time left over that reaction time is not practically a factor. Mastery should feel turn-based, recovering the feeling of the older Final Fantasy games in the real-time format of this one - half the battle was already won in the planning stage.
• Accordingly, any mechanic that requires the player to react to another player's choice, or where all plans that eliminate such reaction are unsuitably elaborate for the duty, is unacceptable in high-end duties. (Responding to information that another player must pass on, such as in Eden's Promise: Anamorphosis (Savage) (E11S) Prismatic Deception, requires a long lead time - for two players' reaction times and an extra client-server round trip - and a way for players to pass on that information without relying on typing, macro space, or out-of-game communication. E11S did it right, but such mechanics can never be fast.) Yes, this means that some mechanics are permitted in regular duties but not in high-end duties. Players put more effort and resources into individual attempts at high-end duties, and taking a party KO or even a personal penalty there because of forced reaction is annoying.
  (TOP is perfectly fine in this regard, as players can devise a priority system for the "open choices" presented by Run: ****mi* (Sigma Version) and Run: ****mi* (Omega Version) without undue effort in planning or execution - that players in Party Finder turned to third-party tools instead is not the duty designer's fault. (Technically, there is also an "open choice" in Run: ****mi* (Delta Version), but that is assigned even more easily using the Remote Regression and Local Regression tethers from Patch.) I even know how to take the priority system management load off my party with manual sign placement, I just do not have the APM to personally place the signs!)
• In high-end duties, the player expects the duty to present a deadly dance with harsh penalties for failure. That is not just part of the difficulty, but also part of the thrill of attempting these duties. If you feel inclined to build in lenience for failing a specific mechanic in a high-end duty, rather than overall tuning allowing for a small number of mistakes, the mechanic is almost certainly not suitable for high-end duties in the first place. That desire for lenience is a sign that the mechanic does not yield to appropriate planning.
• While high-end duties require a degree of skill from the player to have the baseline experience, the player actively expects satisfying mechanics for their trouble, along with ample opportunities to express their skill beyond the baseline. Not every mechanic must be satisfying in itself to execute correctly, but it is a disappointment that there is not a single such mechanic in all of AAC Light-heavyweight Savage.

In high-end duties, the player will solve puzzles and learn complex concepts from fellow players entirely to the extent that they grasp the bigger picture. (Arena floors may be almost entirely flat after players learned to tilt Twintania's divebombs in The Binding Coil of Bahamut - Turn 5, but their real third dimension has always been time.) The best players work with the whole duty timeline and the whole party as one, creating a single branching plan that is executed by eight players - and in return, they expect both the planning and execution layers to provide them the joy of smoothly countering the duty's every move. The party of players as a whole takes on the role of the single "planner" player controlling a party of characters in the older Final Fantasy games, as well as their individual surface roles in executing their plan.

So in high-end duties, give us planning problems that are worth the effort. Reward the spreadsheets, the hours at a striking dummy, the hours in a single duty. Reactive, otherwise easy mechanics can never do that.

--------

For all their faults, Heavensward, Stormblood, and Shadowbringers were close enough to these principles to inspire me to fight. To work my way up from being a terrified new sprout to being Ultimate-ready. (It definitely helped that Shadowbringers had very nearly the perfect job for me.) But also to do roulettes long after I had hit my weekly cap of Allagan Tomestones, with no jobs to level, just for fun. I did not mind even Sastasha, because I could still enjoy myself there by working with my job.

Endwalker broke my job, and that was a massive blow to me; this letter is about duty design, but I have always been a systems-oriented player and the jobs are the core systems of combat. I role swapped to keep raiding, because the personal improvement in working with my physical limitations was and is important to me. I did roulettes comfortably to reach my weekly cap of my Allagan Tomestones and level jobs, but not beyond that.

Dawntrail essentially did not change my job. Yet it is the first time I have had to actively remind myself to reach that weekly cap, despite having jobs that could use the Allagan Tomestone gear. A habit sustained for years was broken in less than two weeks, because the Dawntrail duties are so physically demanding that my brain notes the excessive injury risk and pushes me away from them. (Of course, the fact that I am forced to sit out of FRU by Patch 7.0's duty design direction does not help. Ultimate-level skills do not do much for me if I cannot safely commit to the Ultimate.) And injury risk aside, the Patch 7.0 duties are boring!

What Dawntrail has moved me to do is play more RuneScape. In some ways that game is less accessible than this one - its combat system has a far higher APM ceiling than even the old manual Embrace SCH - so I cannot play it perfectly, but at least I can play its combat system solo in my own way and the game will reward me for that. They have something for me, and that is better than having no duties that suit me.

Their latest boss rush dungeon is not only great fun, it copied your attack telegraphs and your system of limited KOs in Duty Support trials to teach the player mechanics... to wild popularity of the Hard Mode that turns the KO forgiveness off! Their "tutorial boss" for recurring mechanical concepts has not only instructional NPCs but individual mechanic selection with a randomized order, allowing the player to choose what they want to focus on practicing... and its own Hard Mode that activates and amplifies all the mechanics. With the mechanics still randomized and repeating once the boss has finished the set, so the player must have at least two plans to avoid KO from each mechanic, in case the boss picks it twice in a row and their cooldowns from their first plan are unavailable. And the Hard Mode smoothly scales from low Extreme to mid-Savage difficulty for an individual completion, while offering a "killstreak" system that gives better loot for chaining up to 200 kills in a row with increased scaling each time - successfully rewarding Ultimate-level consistency! Even their latest gathering boss deliberately allows for strategies ranging from slow but low-effort to fast but high-effort, to encourage and reward skill expression.

(RuneScape is not just copying the best aspects of your duty design history, by the way. They have also been seriously improving their tooltips, combat feedback, and overall new player experience, including by launching their own version of a pet class last year with a full teaching questline. Which inadvertently resulted in their player community learning your term "job gauge", because a player made one for them and it took off enough to start supporting their other forms of combat. Their players can literally bring them the best parts of your interface.)

There is nothing quite like raiding in your game when you design it right. RuneScape would not be in serious consideration for combat challenge if you did. But Patch 7.0's duty design direction has lost sight of both long-term fun and appropriate challenge.

Give us challenges we can all rise to meet and aspire to master, not barriers we cannot do anything about.

[Aurelle_Deresnels]

Now to go over the existing Dawntrail duties and their mechanics from a duty design perspective, both the good and the bad. As a reminder, this section is necessarily tedious, and any player readers who are not interested should skip over to my redesign of the Honey B. Lovely duties. (Navigation links are at the top of this thread.)

Certain duties are very time-consuming to repeat with exact mechanics and tuning for review, namely MSQ solo instanced duties, hunts, treasure dungeons, regular FATEs, and World FATEs. Due to the inordinate time that would be involved in reviewing them thoroughly without access to test servers, I have omitted these to focus on the 21 readily repeatable group duties available. Most of the omitted duties follow much the same design style as the ones included, so this along with the discussion of principles should apply well to their issues.

----------------

Due to length, I have split this section into four subsections, in increasing order of acceptable and expected difficulty.

I will begin with the duties appearing in the Patch 7.00 MSQ, in the order of their appearance there. As completion of these duties is functionally mandatory for a player to continue with the game, these duties must be held to the highest standards for providing an encouraging experience to even the returning and very weak player. They know that their access to all further content - combat or otherwise - relies on their completion of these duties, and that knowledge becomes a heavy weight if they worry about their ability to do so. Enjoyment for the stronger player and in subsequent completions of these duties must be created without compromising those standards.

----------------

Ihuykatumu (Level 91 Dungeon)



Mobs Before First Boss

Three Packs (On River Boat)

These are forced single pulls (one pack at a time), and they do nothing more than a small amount of basic ground AOEs. If you are going to make the player do single pulls, make them individually interesting so that stronger players do not get bored. Throw in some more fish that come to feed on the remains of the previous pack as each mob dies, or some pattern AOEs from Bakool Ja Ja's "gift", or something. It does not have to be as resource-draining as the Holminster Switch forced single pull section, which has no downtime.

Being the opening of the first dungeon of an expansion, it is entirely possible that this is the first group duty the player has done in a while, so a gentle opening is reasonable - but that can still be interesting! This is not, and that makes the story sequences all the more grating when running the dungeon to level rather than for MSQ.

First Boss - Prime Punutiy



Hydrowave

Narrow cone AOE, easily dodged, nothing special. It is fine.

Resurface

The AOE spam after the castbar is visually overwhelming with its speed, since the Flytrap add casting the donut AOE appears during that AOE spam and forces the player to look at more than just their character's feet. If the player could just look at their character's feet, it would be visually on the high side but acceptable, because the player could and would remove distractions and speed up their time to see the relevant cues by focusing under their character's feet.

I can do this, but it is not fun - all it encourages me to do is try to constantly look everywhere as best I can, especially the first time when not knowing about the Flytrap. Even when I do know about it, the Flytrap is usually pretty far from my character's feet, forcing me to visually bounce back and forth between looking up at the arena as a whole and down at my character's feet until the AOE spam ends.

Suppose instead that the boss pulled up the Flytrap during the castbar, putting it in the arena and on the player's enmity list. The AOE sequence could then play out the exact same way, but the first-time player would have a reasonable chance to see the Flytrap and think "this probably does something" before the donut telegraph appears and probably covers the whole area around their character. On future attempts, stronger players would have the option to path to the known location of the Flytrap during the AOE spam, making it more interesting in how that interacts with their job.

Song of the Punutiy (Adds)

This is a good mechanic, with light damage from the spreads going into increased tank healing from the adds. Allowing the party to bait most of the adds' positions for when they first become targetable could provide an opportunity for skill expression, although here it does little because two of the spreads are so large.

Shore Shaker

Easy but fun - just step in when the telegraph in front of one's character disappears, and since the player knows to look there based on seeing the sequence of telegraphs appear, the timing is fine.

Overall Impression (Boss)

This boss is pretty easy other than Resurface being an issue. As the first group boss of the expansion, starting off with a visual design issue raises concerns to the player immediately.

Mobs Between First and Second Boss

First Pack - Bats and Widowmaker

Nothing interesting here. This does allow for a double pull, though, so it is fine.

Second Pack - Doblyns and Treant

Ditto.

I appreciate not having to target and interact with the ladder once this pack dies, and the same goes for the later ladders in this dungeon.

Third Pack - Mimiclots

The idea of "they've copied our forms" is cool, but nothing seems to be done with it other than apparently making these enemies stun immune - and the player is not going to see that without a WHM in their party. Even something simple like giving them each a basic AOE that draws on a "classic" job in the role (though some of that recognition has been eroded by job changes) would sell the concept mechanically: front-facing cone for the tank (MRD/WAR), point-blank AOE for the healer (any healer but AST), line AOEs for the DPS (LNC/DRG).

(The healer does have such an AOE, but none of the others do and the cast does not look like Holy. Plus I had to find that out from videos, not from my own completions, despite using Duty Support first for immersion and then to avoid hampering other players' experiences when reviewing the duty.)

This pack does allow for a double pull, so it is not boring, just a missed opportunity.

Fourth Pack - Doblyn and Widowmakers

Still nothing interesting here.

Second Boss - Drowsie



Sow

If you are expecting the player to see where the seeds dropped from this cast, that expectation is unreasonable - they are too small and show for too short a time for the player to track four objects. Since players have sufficient time to see them from the later Drowsy Dance, telegraphs, and Wallop, this winds up mostly being a "warning, something happened" cast.

Drowsy Dance

Grows the seeds with telegraphs, fair enough.

Wallop (cast by adds)

I appreciate the facing markers here, which make this reasonable to dodge since the player can just look at the base of each root. Having to follow each root upwards to find its facing direction would be too much.

Mimiclots

Since the Mimiclots return from the earlier trash, this is a great opportunity for them to do a mechanic (with the player having a good guess based on the trash) every time, rather than simply being AOE fodder when I completed this with Duty Support. Sometimes having AOE fodder in a boss fight is fine - it provides a change to the healing requirements and an opportunity for everyone to switch between single-target and AOE rotations - but this is a missed opportunity to do something more than that...

From seeing videos of other players' completions, the Mimiclots do have a mechanic here! Why can Duty Support completely eliminate a mechanic?

Sneeze

Big cone, long cast to dodge it, no problem.

Overall Impression (Boss)

The name of this boss and the fact that it starts sleeping do suggest sneaking past, which inevitably creates tension between players who want to leave it be based on their character and players who want the XP for defeating it. To remove that tension, perhaps this should have been a point where one of the other claimants' teams forced the fight?

Mechanically, this is okay.

Mobs Between Second and Third Boss

Four Packs

Nothing mechanically interesting here, but can be double pulled.

Thematically, the dead animals are a cool hint at the boss, but that is not mechanics.

Third Boss - Apollyon



Razor Zephyr

Basic line AOE, reasonable cast time.

Appearing Beasts

A thematically cool "warning, something happened", and I like the red text that hints at how the boss has powered up.

Swarming Locust

I do not love the boss jumping around without prior telegraphs for the sequence, just from a visual tracking perspective, but it is acceptable in moderation in contexts like this. The jumps are not that fast, and the next attack does not require knowing the precise position of the boss.

Blades of Famine

The empowered line AOE, and since there are four of them, being away from the boss after the jumps is helpful to the player rather than annoying.

Repeats twice, including the jumping around.

Levinsickle

I quite like this mechanic. Each of the sets of radial cones covers the arena across its sequence, and there are two of them so the player wants to step from the empty space into the overlapping space. It encourages the player to think, with all the information clearly given and a reasonable amount of time.

(no castbar) Appearing Beasts

A different mini-phase, this time adding a donut after the tankbuster.

Windwhistle

I do not love having to keep an eye on the resulting Whirlwind for so long as it pulses the snowflake of line AOEs. I find it doable, but it is definitely a visual stress since its movements are not cleanly predictable.

Overall Impression (Boss)

This is actually a pretty solid boss, despite Windwhistle. The concept of a boss that eats other predators and takes on their attacks is a good one, and could allow for a degree of "mechanics the player has already seen, but empowered / in succession" without the overwhelming nature of Tower of Zot's final boss.

Overall Impression (Dungeon)

The boring opening is not great... and Resurface looms over the entire dungeon. It put me in "try to constantly look everywhere" mode from the beginning, and that is not fun.

--------

Worqor Zormor (Level 93 Dungeon)



Mobs Before First Boss

Four Packs

Nothing mechanically interesting here, but can be double pulled.

First Boss - Ryoqor Terteh



Fluffle Up

An AOE sequence from adds, that the boss modifies by freezing some of the adds. The first two show the patterns from the different types of adds; the small Rorrloh Teh on the cardinals hit a quadrant of the arena in front of them (safespots for each hit opposite each other), and the large Quorrloh Teh on the intercardinals hit a point-blank around them (safespots for each hit beside each other). These first two are fine.

Good visual clarity with the ice tethers, guiding the player to look from the boss to the adds.

Snowscoop

Nice sidestep between the two sets of line AOEs through the center of the arena.

Sparkling Sprinkling

These spreads appear during the preceding mechanic, allowing the player to notice others near them and try to dodge away. You still are going to get players overlapping spreads, because Duty Finder does not plan spread locations, but this is a mechanical overlap that is easy enough for MSQ.

Fluffle Up (repeated)

Now the two patterns are combined, and the boss puts out four ice tethers. While the boss is reversing both patterns, with each reversal previously shown individually, the first-time player does not know that and may not even know that the individual patterns are always reversed. For all they know, the boss could be manipulating each add individually to create a sequence of three hits instead of two, or only reversing one of the patterns.

So when the tethers come out, the previously working method of "stand in / note the first safespot, then if tethers appear, move over to the area that would be hit by the tethered adds" no longer works. The first-time player must try to remember which of the adds were going to go off first, which is itself not easy as a spatial memory mechanic with four things presented at once, and match those up with the tethers. That is not really reasonable to pick apart in the time given.

Once the player has time to think about this mechanic after the battle, it becomes fine or even too easy. "The boss is going to reverse both patterns, so stand where all the orange is" is the obvious guess and the correct one. But this is an MSQ dungeon, where the player's first attempt is a critical story experience, and many casual players do not have the notion of hidden patterns in mechanics at all.

This is a difficult mechanic to fix, because you also do not want to slow down the battle so much as to bore players on repeat runs. It may well be more suited to a Trial or a Normal Raid than a dungeon, as those allow for longer bosses that can do things like refresh the player on Spell-in-Waiting markers and still have time for another concept.

Overall Impression (Boss)

This is a good boss concept, focused on manipulating the timing of AOE sequences by freezing adds. It only gets to be too much for the first-time player during the later Fluffle Up casts.

Mobs Between First and Second Boss

Four Packs

Nothing mechanically interesting here, but can be double pulled.

Second Boss - Kahderyor



Crystalline Crush

The stack tower here sets the party up for success with the immediately following Wind Shot, which is especially nice since this boss has a substantial amount of unavoidable damage.

Wind Shot (Player Donuts + Crystals Safe)

If the party stays where the tower was and the crystals appeared, they will be fine! Good introduction to what this wind mechanic does. The color for the wind AOE could use a sharper green, though.

Earthen Shot (Spreads + Away From Crystals)

Again a good introduction, since the player should reasonably guess that a different element requires a different response, and the last one was "stay where the tower was". Though the color for the earth AOE could use a sharper yellow even more than the previous mechanic, or potentially even replacement with another element given the later mechanics.

Crystalline Storm (Line Crystals)

Three small line AOEs that leave behind crystals.

This is why the elemental AOEs could use sharper colors. When the player has to check the AOEs from all three lines at once and react to their party's movements for both donuts and spreads, high contrast really helps them process the visuals quickly. (Having only seen each element once before, the first-time player may not have picked up on what the tie is between the crystal locations and the elemental safespots. Casual players have a lot to think about going in!)

Wind Shot (Player Donuts + Crystals Safe)

Stepping into any line will avoid the ground AOEs, so the player need not remember or remind themselves of all the line positions. There is a decent amount of room for stacking or spreading the donuts.

Earthen Shot (Spreads + Away From Crystals)

Now there is little room, the party is reacting to each other for spreads, and the earth AOEs are yellow on light brown. I imagine this is miserable for anyone with reduced color vision in the red-green range, even if not full-blown colorblindness.

Seriously, perhaps the earth mechanic should have been replaced with fire or lightning instead? Fire is already associated with ground AOEs, lightning is already associated with spreads, and the embedded crystals are purple.

Seed Crystals

Break out of the crystal adds. Easy enough.

Sharpened Sights

Enters a gaze + AOE mini-phase, casting first Stalagmite Circle (point-blank + look away from boss) and then Cyclonic Ring (donut + look away from boss).

The gaze combined with AOE is very well done, showing the player the combination where they will naturally succeed before asking them to respect the gaze while dodging the ground AOE. Using the contracting gaze ring rather than the icon on the enemy is an excellent way to get the player to see the gaze in this context, especially since the head of the boss may be off their screen.

Overall Impression (Boss)

The elemental effects really could use some more pop on the ground, to maintain visual clarity when they are coming from the crystal lines. Otherwise, solid boss.

Mobs Between Second and Third Boss

Four Packs

Not much mechanically interesting here, but can be double pulled. A good tank can and should bring the Cloudtrap into the group or vice versa.

Third Boss - Gurfurlur



Stonework (Fire, Expanding Square AOEs + Spreads)

A combination mechanic right from the start, but giving the first-time player plenty of time to expect something big and understand that the mechanic comes from the stone plate.

Stonework (Water, Knockback)

This one is not a combination, but it shows the player that the water knockback comes from the side with the plate, not the plate itself, which is important later.

Sledgehammer (Multi-hit Line Stack)

From a raid healing perspective this does not hit that hard, but anything that did would be too much for casual players. As it stands with the big marker and threatening name, this slow cast is enough to invite a casual healer to prepare to heal the party rather than reacting, and to invite the rest of the party to mitigate, both of which are good skills.

Arcane Stomp (Damage Up Orbs)

The large number of orbs to intercept here creates a faster section, encouraging players to use their movement tools efficiently and split up the arena between themselves. Good for making the boss "less of a striking dummy" without compromising on the slow, powerful attacks of a giant. (On repeat runs, the player may well notice that the boss only intercepts the orbs when they reach the middle of the arena, not his hitbox, and use that fact to make smaller movements.)

Notably, the buff from the orbs only lasts a minute on player characters, but lasts indefinitely on the boss, which looks scary from the casual player's perspective. And this being a leveling dungeon, it has a tight implicit Item Level sync.

Enduring Glory (Raidwide)

Again, this does not hit that hard from a raid healing perspective, but a raidwide after a damage up is scary in concept.

It does cleanse all the Damage Up stacks from the boss, which is really probably not necessary - Sledgehammer as it stands can be completely countered by Liturgy of the Bell / Seraph / Macrocosmos / Panhaima if the healer brought in Anabaseios tome gear. With this much lead time and seeing a whole mechanic dedicated to the Damage Up stacks, a casual healer can be asked to find more than one AOE healing tool; this could cleanse half or two-thirds of the stacks instead. Even if they do not find more than one AOE healing tool, the party will probably just be left at low HP instead of KOed.

(And if the party does take a party KO to some of the Damage Up stacks remaining, they can just try again with knowledge of the Damage Up. The blatant obviousness of Arcane Stomp makes sure that the (reasonable) player notices the orbs and infers that the orbs power up the boss even if they do not look at enemy buffs, so they are unlikely to blame the healer.)

Stonework (Wind, Tornadoes + Double Knockback)

A combination that invites the player to think about using their knockback immunity! The first knockback from the center plate will likely be taken to a corner since the player does not know the distance, which leaves the player well set up to position for the tornadoes before they start. The second is much less immediately pleasant, having the potential to knock the player character right into the tornadoes just before they leave the arena - but from a duty design perspective this is great, as it presents a problem to the player while making sure the tools to solve it are at their fingertips.

Stonework (Fire + Water)

This looks scary, and what that does is encourage the player to think about the combination and how the mechanics interact. The water knockback is timed to match the first hit of the square fire AOEs, so the player can have it wash their character right into the safespot and then just move for the spreads. Having seen the pieces of the combination earlier, the player is empowered to make a guess at the timing and prepared to move their character shortly after the knockback.

Sledgehammer (Multi-hit Line Stack)

As before, but coming right after a raidwide this time. The long cast makes it still very reasonable to heal.

Overall Impression (Boss)

Great! More like this for dungeon bosses. Visually clear, the voice sells the "weight of history" idea, and the mechanics are gentle enough for a casual first-time player to understand their mistakes while having frequent combinations and optimization opportunities for strong players. The spectacle both tells the story and helps cue the player, which is not possible for every concept but awesome when you make it work.

Not every dungeon boss should be this slow, but for a giant it works to have slower and more powerful attacks.

Overall Impression (Dungeon)

So close to being fun all around without issues, and at least the issues do improve on repeat completions. The mechanics carry out the themes very well.

--------

Worqor Lar Dor (Valigarmanda, Level 93 Normal Trial)



(no castbar) Animation Tells

This boss has three recurring animation tells for basic attacks using three elements: the wind swirling donut (center of the platform safe), the fire stomp (leave melee range), and the lightning beak cone (front corners of the arena safe). These animation tells are supposed to be taught by the red text the first time, and then the player is supposed to recognize them with no other cue thereafter.

So let us consider these three animation tells and the text that is meant to teach them.

• Wind: "A tempestuous wind gathers around Valigarmanda." This directs the player to look at the boss model for a swirling wind, suggesting a donut around the front of the arena... which is not where the wind is, the wind is around the platform instead and Valigarmanda later enters the swirl. The most accurate lesson the player can learn from this is that your pop-up text can be wrong.
• Fire: "Valigarmanda gathers its strength." This says absolutely nothing about where to look. (Where to look is at the boss's legs, since its body starts glowing red and its legs are close to the platform.)
• Lightning: "Blinding energies build within Valigarmanda's wide-open beak." This gives a correct description of where to look - but Valigarmanda raises its beak off the screen during this animation at the default camera tilt or even slightly higher, and most players are never going to adjust their camera tilt. Indeed, there is no way to get Valigarmanda's beak comfortably on the screen without sacrificing ground visibility either camera-ward of one's character or by looking very side-on, which results in the player fighting their interface to both see this tell and dodge other ground AOEs smoothly. To make matters worse, the boss also glows red during this animation!

Every one of these teaching texts is either useless or wrong. One of the tells is not even reliably on the screen. And this is for a mechanic set the player is meant to recognize by animation alone while other things are going on in the duty?!

What I did in response to this is launch straight into the "try to constantly look everywhere" mindset and stay there even for subsequent MSQ duties, combined with following the Duty Support NPCs for the animation mechanics in this duty once I realized I was better at tracking them than finding the then-mysterious-unto-me animation tells. This is not fun, but it was the best option open to me short of finding a guide and finding and memorizing a timeline for a Normal Mode trial.

You can have animation tells without other cues; the old version of Aurum Vale did it and was fine. You can have animation tells on a large boss model if you are careful; Alphascape V2.0 (O10N, Midgardsormr) did it and was fine. But you have to make sure the player actually gets to learn the tells, and can see them consistently without having to try to constantly look everywhere. "Welp I got hit by this animation tell mechanic shortly after this castbar attack, somehow I am supposed to look at both at once" is not actionable!

(There is something of a rhythm to when this boss uses its animation tell attacks; I was much more comfortable returning to this trial after doing the Extreme version. But that does not help any player who does not complete the Extreme version. Plus between this being a high-level trial and having Duty Support, even players who queue Trial Roulette will see it very infrequently beyond their own first time - the first-time experience is not just critical but the default, and then the player does not have any knowledge of that rhythm.)

One way to significantly improve this without making major changes to the boss concept:

• Wind: Change the teaching text to "Valigarmanda creates a tempestuous wind around you.", "Valigarmanda creates a tempestuous wind around the platform.", or something along those lines. The player must be directed to look at the tell that appears with a reasonable lead time, which is the wind gathering at the corners of the arena. The wind effect could also use a little more green for contrast.
• Fire: Change the teaching text to "Valigarmanda channels fire into its legs."
• Lightning: The teaching text is accurate, if incomplete. Change the animation tell to start with the boss lowering its beak right onto the platform, so the player can reliably see it at the default camera tilt. Change the glow on the animation to be a purple lightning glow from Valigarmanda's head only. These changes would make the color and motion also dramatically distinct from the fire attack.
• All: These changes allow the player to "rest their eyes" on a spot roughly around the resting position of either one of Valigarmanda's legs, because all the animation tells are in close proximity to those spots and the teaching texts show them that. This notion of a "resting point" is essential to having the player see animation tells without giving them another cue for when to look at the animation. (Aurum Vale's "resting point" was the bosses themselves, those being significantly smaller and having few castbars to look at. O10N cues the player every time, on top of having very dramatic animation tells that are visible across a large portion of the screen.) "In this duty, look at this spot when not looking at the enemy's castbar / my character's feet / the party list / ..." is actionable, and allows you to have an animation tell mechanic whenever the player has some time to return their eyes to the "resting point" after the preceding mechanic.

A second issue with these animation tells is that this boss is not actually programmed to show the player all the different elements before the repeats begin. It can roll wind, fire, wind, (other attacks)... and then finally wind up teaching the lightning attack in the middle of the duty. This is not appropriate when the duty is already ramped up, and contributes to the "oh gods look everywhere" mindset.

You do not have to show the player each animation tell multiple times the way O10N did, or even show them in a fixed order, but you do have to make sure the introduction period for a mechanic consistently introduces the mechanic. If you want high randomness, have the first one be completely random, the second be completely random out of the two elements not already used, and the third one be the remaining element.

Opening Phase

Aside from the animation tells, this is simple enough. Really, it is almost entirely the animation tells, which does little good when the player has been directed poorly on how to learn them.

Skyruin

Nice clear phase transition warning raidwide, with the random element clearly visible at the front of the arena.

Ice Phase

(no castbar) Avalanche

Here the red text usefully tells the player to turn their camera around and check the avalanche, and it does in fact appear every time so the player does not have to worry about constant camera turning. This is fine as is, though I prefer the Extreme version where the player can learn to dodge by the text alone.

Freezing Dust

An excellently marked Deep Freeze, with both the warning marker counting down to the start of the movement period and the Freezing Up debuff counting down to the end of that period.

(no castbar, snowflake AOEs) Arcane Spheres

The shrinking yellow underline to the red text lightly indicates when the AOEs are about to go off. I can work with that, though red-green colorblind players may well have a bad time.

However, the safespots for these are relatively small, and there is no geometry on this floor for the player to work out where the edges of the safespots are. Trying to reactively correct one's positioning based on the brief telegraphs is not fun. To support mechanics like this, give the player some floor geometry to visually trace out the snowflakes. This is perfectly possible on a snow / ice floor, as demonstrated by Eden's Verse: Refulgence (E8N) and its Savage version (E8S).

This becomes even worse after the fire phase, when these can be combined with avalanches or Freezing Dust.

Thunder Phase

Thunderous Breath

I like this. It is a logical empowerment of the lightning beak, and the telegraph clues the player in right away that there must be some tool other than getting out of the orange available to them. This gets them to try the levitating sections of the floor, making sure they know the usage for later mechanics.

Hail of Feathers

Here - unlike the Extreme - the player does not know the pattern that the feathers will come in, so the cast itself winds up as a multi-hit raidwide that places the feathers to avoid later. The feathers could stand to have more contrast against the floor, though their large size does help.

Blighted Bolt

I like the concept of this. It shows the player that levitating is not always desirable, complete with telegraphs that disappear when leaving the levitating sections. The red text also nudges players to think about how they might counter lightning bolts, and "be grounded" makes logical sense.

However, there are two problems with the execution. First, the player can get hit even if they do it correctly, by another player not quite making it and having their bolt hit the nearby otherwise-safe area. Second, the feathers from earlier have point-blank AOEs at the same time as this cast finishes, and the lightning strikes that are meant to clue the player in to that happen while the player is likely looking under their character's feet for "do not levitate". This again discourages the player from seeing what they are intended to see, particularly since none of the feathers levitate so the logic for feathers is different than for player characters.

(no castbar, line AOEs) Arcane Circles

These are the same circles as the snowflakes in the ice phase, and these ones work well. The red text tells the player to look out, the tethers from the boss tell the player where, and the levitating / not levitating floor sections provide sufficient geometry to at least locate one edge of the safespot. It might not be the edge the player wants for optimization, but the player will never have to react to the brief telegraphs.

These continue to work well after the fire phase, when they are combined with Thunderous Breath.

Add Phase

Ruinfall

The stack tankbuster tower is very clear despite combining three markers, and is a cool concept that encourages the tanks to use Arm's Length on the knockback immediately afterwards

(no castbar) Repeating Line Stack + Cone AOEs

Duty Finder does not make mechanic-specific plans. Even Duty Support will not give the player a clear plan of where the NPCs are going to dodge the ground AOEs. Dodging the cone AOEs is not interesting, and trying to get the full party to stay together to take the stack is a fiasco.

If the player character has the stack with Duty Support, they have a coin flip of blowing their one allowed KO right here by not dodging the same way as the NPCs. And if they already used it on learning mechanics, they are sent back to the beginning for something that is not really a mistake.

Fire Phase

Tulidisaster

An appropriately big, long, scary cast, with multiple hits that go through the different elements of previous phases before starting the fire phase with the permanent DOT.

Permanent / long-lasting DOTs as a different style of heal check are interesting, and this is an appropriate introduction that is gentle enough for casual players.

Eruption

These puddles should be significantly more opaque and red. A stack full of them is visible enough, but the party may not be stacked - especially after the first dodge - and just one is not cleanly visible against the reddened floor.

Overall Impression

Please for the love of Hydaelyn, if you are going to do animation tells, then make sure the player can actually learn the tells and know when to look for them! The fun ideas like branching phase order and permanent DOTs are ruined by the constant stress of trying to look everywhere.

--------

The Skydeep Cenote (Level 95 Dungeon)



Mobs Before First Boss

Four Packs

Nothing mechanically interesting here, but can be double pulled.

First Boss - Feather Ray



Troublesome Tail

The cast, Nuisance debuff effect around each player character, and "You are cursed to be a nuisance to your party..." text provide an appropriate warning that the player should look out for what mechanic the boss is putting on their character.

Worrisome Wave

A narrow front cone AOE, followed after several seconds by each player character repeating it. The overhead marker provides an excellent cue that something is about to happen, having seen Troublesome Tail the player has a good guess as to what, and from there they have enough time to do okay even though they are inherently reacting to their party members' movements.

Hydro Ring

A donut that leaves its area covered in water, but really is the setup for the next mechanic.

Blowing Bubbles

Starts a bullet hell sequence signified by "Feather Ray produces copious bubbles...". There are four sets of bubbles, one pointed at each player character, so the player is expected to move their character at least once.

This is not my type of mechanic, but in this form it is tolerable, since the player has lead time to see where their party members were and therefore where the bubbles are aimed.

Rolling Current

Creates an array of large bubbles that stay still on the arena before being pushed by a knockback, with enough time to see the array. The first time, the player does not know if the knockback will hit their character or the bubbles, but they can understand it once they see the knockback resolve. When this repeats, the player has the knowledge to succeed.

Hydro Ring

Effectively shrinks the arena again, setting up for more bullet hell.

Troublesome Tail

Here is where the real problem begins.

Trouble Bubbles

While the boss does not directly emit bubbles at the party here, each party member emits bubbles at every other party member, starting as soon as the "Feather Ray produces copious bubbles..." text appears. This means that the player must process bubbles coming at their character from three different directions, filter out the bubbles their own character is emitting, try to find a nearby open space, and repeat because the next bubbles will be aimed at their new location - all reactively! The result is a reaction sequence from visually overwhelming input of fast-moving bubbles.

Oh, and individual KOs from failing this come very quickly - even if the player did the first Rolling Current successfully, two bubbles are enough to KO a non-tank from full HP. A player can easily have their character KOed before the "Feather Ray produces copious bubbles..." text disappears, regardless of their physical reaction time! (Remember that this is the first time the player has seen the Trouble Bubbles castbar. They have reason to expect bullet hell and a mechanic repeated by the player characters, but they also have reason to expect a different pattern for a different castbar and an overhead warning before the repeated mechanic begins.)

To make matters worse, the fact that these bubbles move so fast also means that if the player has even moderate client-server ping, each bubble travels a significant distance in the round trip between the server sending a packet with that bubble's position to the player's client and the player's client sending back the player character's position to the server. (Remember, some regions span very large geographical areas and older Internet infrastructures, even before getting into high ping players connecting to a Data Center whose region does not match their current residence.) As a result, the positions the player sees on their screen are substantially different from the true state of the battle on the server. Not only does this give them less time to dodge than is visually apparent, the form of the discrepancy often results in the player seeing that the server says their character was hit (based on the damage and Vulnerability Up) while the positions they see show their character sidestepping that same bubble. A perfect recipe for the player shouting "I was out of that!"

Of course, the same client-server delays apply in principle to every mechanic. This is something that raiders learn to work around when studying moving object mechanics in high-end duties, and even casual players learn with practice to intuitively account for their ping when judging the end of a castbar. But the speed and targeting of these bubbles creates a visual state that looks unfair in an already reactive mechanic, readily apparent to the casual player, leading to annoyance at both the mechanic and the broken immersion.

If the bubbles were in a very simple pattern fixed relative to the player character emitting them, like "always behind the character", that would be acceptable in this context. More complex fixed patterns like "every intercardinal of the character" would be acceptable in Criterion, where the party can plan around the pattern. As it stands, this is a pile of unfun stress, since failures will likely come from visual overload and/or reaction time.

Overall Impression (Boss)

If the player wanted a bullet hell game, they would be playing a bullet hell game instead of this one. Reacting to where fellow players emit their bubbles from is annoying, not fun!

Mobs Between First and Second Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

Skydeep Quarriers into Skydeep Vessels

Now this is a reason to force a single pull on occasion - the Speaking Stone makes it into a forced chain pull (next pack added before the mobs already pulled die) and therefore a cooldown and rotation management test.

Second Boss - Firearms



Mirror Maneuver

A short cast, but a good opportunity for the player to see - or at least be prompted to look for - the mirrors that complicate the next mechanic.

Thunderlight Burst

This is a fun mechanic. The dangerous AOE is massive, with the same radius as a side of the arena, and the player has to figure out where the AOE will explode from by following the boss's aim through the mirrors to an orb. But the long, clear cast makes this very reasonable for the player to do, or understand what happened if they mess up the first time. Later repeats add more mirror bounces, but remain reasonable.

Ancient Artillery

Sets up where the AOEs expand from for the next mechanic.

Emergent Artillery

Another fun mechanic. Combines cross AOEs from the beginning, introducing it with two AOEs (four safespots) the first time and using three AOEs (one safespot) thereafter. The iterations with three AOEs also have spreads afterwards, and the timing is very nice for a gentle combination - the spreads appear near the end of the cross AOE expansion and resolve after the cross AOEs, so the player can naturally move their character to an edge of the preceding safespot and then out.

While on the simple side at first, it fits with the large arena making the player leave more time for their character's movement, and it is still fun.

Overall Impression (Boss)

Good! More like this for dungeon bosses. The player might fail a mechanic, or even multiple, but they have all the information to understand why they got hit. And while it is simple, the large arena means that players who want to tackle movement optimization will.

Mobs Between Second and Third Boss

Skydeep Packers

I understand the reasoning for the barrier, and even the sharp turn to reveal the Alexandrian section of the dungeon, but why is this a single pull? Toss in a barrier guardian or something.

Two Packs

Not much mechanically interesting here, but can be double pulled. The Stonemasons having higher HP is a nice opportunity for skill expression without affecting the experience of weaker players, as it allows stronger players to deliberately target the Stonemasons with single-target cooldowns and falloff AOEs.

Third Boss - Maulskull



Stonecarver

A "punch" AOE sequence with very good teaching, between the castbar, "Maulskull draws power into its fists!" red text, and audio cue with glow pulse for each AOE locking in. Since the telegraphs are not shown on the floor, this is technically an old form of memory mechanic, but it is completely fine since even the first-time player only has to remember one {step through / stay} for the second hit.

The teaching is important to set the foundation for when this comes back in combinations.

Skullcrush

The player should be well familiar with knockback circles, but this may be their first time seeing the front-center placement in a relatively small arena. This gives the player the chance to think about aiming to ride the knockback towards a back corner of the arena.

The follow-up spreads are fine, giving the player limited directions to spread out in and a chance to practice that before later mechanics.

Maulwork

A faster, dramatic sequence of AOEs, which is fine even though it feels fast.

Deep Thunder

Big, scary multi-hit stack tower. More of a spectacle than a heal check, but regular duties cannot have difficult heal checks anyway.

Ringing Blows

Combines Stonecarver and Skullcrush, requiring the player to move fast coming out of a knockback. This is a great way to create excitement in a casual-friendly way, since it is a fast and flashy movement sequence but the player has already seen all the pieces.

Colossal Impact

A knockback from a back corner of the arena, followed by either a stack or a spread. Occurs several times.

My one problem with this is that in the spread variant, the player's view of their character can wind up blocked by the boss. (Pointing the camera at a knockback circle can help the player aim the knockback at their desired angle, which after the knockback leaves the camera off to the front and side of the arena. A top-down view has the same problem, since the boss is so large and looms over the arena.) The player should be fighting the boss, not their interface.

If the knockback was from a front corner of the arena instead, the player's view would be much less likely to be blocked by the boss. As a bonus, this would provide a more natural opportunity for the player to think about job optimization, moving into melee range (or staying out when playing a ranged job during the spreads) after the knockback. (As it stands, the player can try to optimize on a melee DPS or tank by moving out later when not using Arm's Length, but that is unintuitive since it leaves them less time to aim.)

Overall Impression (Boss)

Almost good throughout, except for the moments of fighting the interface. Veteran raiders get the bonus of recognizing many of the mechanics from Eden's Gate: Sepulture (Savage) (E4S), though of course the iconic E4S mechanics are not suitable for Duty Finder and the short format of a dungeon boss.

Overall Impression (Dungeon)

The only major issue here is the first boss, but Trouble Bubbles really sours the whole dungeon. The rest could use some polish, but is still decently fun.

----------------

Due to the 20 image limit for a single post, I must split this subsection into two posts. It continues below.

[Aurelle_Deresnels]

Due to the 20 image limit for a single post, this is a continuation of the same subsection as above, on duties within the Patch 7.0 MSQ.

----------------

Vanguard (Level 97 Dungeon)



Mobs Before First Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

Vanguard Sentries

Not only can these be double pulled, but their opening AOEs add some mechanical interest and change up how the tank approaches the first pack. (The mobs notice the tank from a long distance, but will generally wind up behind the party from their telegraphed dash.) Nice to see things like this.

First Boss - Vanguard Commander R8



Enhanced Mobility

A spatial reasoning mechanic right away, with the "Beware the wingblade!" text to warn the player that there is an aspect beyond the telegraphed AOE. Great work.

Each execution of the bike dash creates a brief forced downtime. Having some forced downtime is totally fine, and the timings are very clear so strong players can plan around the downtimes.

Dispatch

Summons bike adds that do their own basic mechanics, the first set doing the dashes the player saw in the trash and the second doing large circle AOEs that expand from the initial telegraph. While both types have the same castbar, the former adds stay on the ground and the latter fly up into the air, making them visually distinct early on.

Later iterations have two sets of adds, with either simultaneous dashes (perpendicular to each other) or sequenced circle AOEs. Big danger zones, fair timings, especially since the circle sequence is corner to center rather than corner to corner.

Electrosurge

Spreads that go off at the same time as the simultaneous dashes, telling each player to find a different safespot for the dashes. There is not a lot of time with the spread markers visible, but that is fine since the player should be well into working out the dash safespots before the spread markers appear.

Overall Impression (Boss)

A very fair, spatially oriented boss. (It is on the slow side for me, but that is probably a boon to those who struggle with spatial reasoning, and this is a MSQ dungeon.) Not every boss should be this focused on spatial reasoning, but this is a solid one with that focus. It definitely has a place in the design style I want.

Mobs Between First and Second Boss

Two Packs

Gives the option to double pull, with the second pack having a ranged sentry that good tanks will bring into the group. Its moderately large Spread Shot AOE draws attention to its presence.

Two More Packs

Again can be double pulled. The pair of Vanguard Aerostats is very reminiscent of The Twinning, sharing the same trash model and donut AOEs as a pair there, which helps sell the high-tech theme for players who remember that. Like in The Twinning, this is a fun AOE type to use sometimes in trash, since the melee and casting uptime strategies are completely different.

The turret Electrobeams are less good, because unlike the earlier dashes there is no path to walk through. The player must either be at the front of the party, wait, or take the AOE, and the latter two options are not fun or interesting. If they fired in sequence or had spaces between them, they would be fun.

Second Boss - Protector



Search and Destroy

Circle and line AOEs under every player character in every round, creating a visually dense bullet hell effect reminiscent of Another Mount Rokkon. This is the annoying kind of stressful, since it forces the player to rapidly react to the AOE placements and constantly move rather than doing anything interesting. (The later combination with Fulminous Fence does not help, despite Fulminous Fence being a good mechanic, since the underlying requirement is still repeated reaction.)

This boss could have player-baited AOEs on theme in a much more interesting way, fitting both the name of the cast and the idea of the boss using turrets. Since this boss already uses Acceleration Bomb, it could start by placing Acceleration Bomb on every player character (with the warning it gives now) and then drop a single slower circle AOE under every player character as the Acceleration Bomb is about to expire - creating a test of sticking to the plan of not moving and only then acting on the AOE, rather than running away in reaction. Then it could progress to planning various simple baits around repeated Acceleration Bombs.

Fulminous Fence

Creates lightning fences that inflict Paralysis when moved through. This is a neat way to change up the movement for later AOEs from the player's normal patterns, though it cannot be used too often by necessity.

Battery Circuit

The spinning cones and periodic circle AOEs are made interesting by the presence of the lightning fences. If this was the only movement-heavy mechanic on this boss, it would feel good to plan as a place to use movement tools efficiently. But as it stands, movement tools for jobs with frequent cast times have probably just been used on Search and Destroy, which furthers the annoyance with Search and Destroy.

Motion Sensor

This is a great warning for Acceleration Bomb, between the cast name and the red text "A motion-sensitive bomb has been affixed to you." The player has a fair shot at understanding the debuff without reading its text, even if they have never done non-MSQ duties to see the concept regularly before.

Blast Cannon (cast by turret adds)

A simple sequence of line AOEs covering the arena, that is complicated by the Acceleration Bombs. Very fair, great mechanic.

Heavy Blast Cannon

This standard line stack functions as a spacer mechanic, leading directly into a raidwide so the healer has to work a little. Nothing too hard, but good.

Overall Impression (Boss)

Why the spam of AOEs under the entire party? This could have been a great, really fun boss if it focused on using different movements than normal around the Fulminous Fences and Acceleration Bombs instead.

Mobs Between Second and Third Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

Two More Packs

Again can be double pulled, and the first pack of this pair adds some mechanical interest by opening with a mix of line and donut AOEs.

Third Boss - Zander the Snakeskinner



Soulbane Saber

A line AOE directly in front of the boss that then explodes into a half-room cleave hitting the whole area that was in front of the boss during the cast.

After showing this once and having a tankbuster where the player can think about what they saw, the boss launches into repeating it while rotating in the middle of the arena - a smooth combination with itself, as the first AOE of the current cast goes off at about the same time as the second AOE of the preceding cast. This is also a fair combination, even once it ramps up to add spreads, since the player has had the chance to see all the pieces first.

This mechanic is a great choice to work with the story constraint of a dungeon boss needing to die and then revive stronger without lengthening the dungeon enough that players try to avoid it. Since it combines well with itself, it allows the boss to show a combination within a very short phase, rather than needing to do only simple attacks or else go too fast to give the player a fair shot at learning. With some concepts it is better to have such a short phase be all introduction in order to use more mechanics later, and with other concepts this way is better.

(no castbar) Revive Sequence

This is short enough that I do not mind it, though I am sure some players got annoyed with it while grinding the dungeon for glamour.

Mechanically, this serves as an opportunity for the healer to heal up from the repeated stacks, a forced downtime that the player can work with rotationally regardless of their job, and an opportunity for the first-time player to think about what mechanics might come from the snake transformation. (Even though they do not know what a feral soul is yet if they are going through MSQ unspoiled, they can still see the changed boss model and the dialogue "I call on the soul of the serpent, the great devourer.")

Syntheslean

A simple 90 degree cone in front of the boss after it turns, but it helps the player pick up on Syntheslither at full speed.

Syntheslither

The indicator showing the boss's attack path and four swords for four attacks is a good one, but alone it would not be enough for the speed of this sequence. (If the player is not looking directly at one of the AOEs, they will probably miss the shape since it appears so briefly.) Showing the player the Syntheslean cone first makes it much more likely that the player will pick up on what attack is being repeated in a reasonable time, allowing this attack to be fast and snake-like while remaining fair.

Slitherbane Foreguard / Rearguard

An upgrade to Soulbane Saber, having the half-room cleave go off immediately and be either at the front or the back of the boss depending on the cast name. The fact that this upgrade also combines smoothly with itself is great, mechanically selling the boss's power-up.

Overall Impression (Boss)

This is a fun boss, and an excellent way to work with a very difficult story concept. Dungeon bosses are time-crunched even before splitting the boss into before and after its first death!

Overall Impression (Dungeon)

This would be an amazing dungeon if not for Search and Destroy. Everything else in here is very well done.

--------

Origenics (Level 99 Dungeon)



Mobs Before First Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

One Pack

A dull forced single pull, followed by an open section for story reasons. The story reasons are all well and good, but you could have found some way for mobs to be there and be cleared out.

First Boss - Herpekaris



Vasoconstrictor

Sets up venom puddles that the boss then punches.

Venomspill (repeated many times)

The fact that the boss lifts its arm and punches a side is fair enough. The player has seen lots of enemies with the same arm animation before, and it is intuitively "hits the side with the raised arm" regardless, so the only real question they should have is how far the arm punch extends.

But the way this mechanic actually works is not only reactive, it is actively working against the player's desire to learn and improve.

The first problem here is that where the attack actually hits is a random selection of puddles that can cover almost any area except the edge of the arena furthest from the lifted arm, but generally does not cover that whole area. So at the most basic level, the player will look at the first set of telegraphs to learn where this cast hits, and will reliably learn the wrong thing from that first set. At higher skill levels, they are denied the ability to dodge just outside the AOEs (and thereby enjoy themselves) because the AOEs are not in a consistent place every time for them to learn. The player is left with no recourse but to run from one end of the arena to the other or risk getting their character hit.

The second problem is that the player cannot even start moving their character preemptively, because the repeated Venomspills are random rather than alternating. Even for a player who understands prepositioning and begins moving their character back to the center every time, it is still quite reactive, and the casual player cannot be relied on to have that knowledge!

(Plus sustaining a movement input to preposition partly pins down the player's hand (or other body part used for input), which makes pivoting to run the other way take slightly more time unless the player splits their movement inputs between both hands. Whether such a hand split is even possible using a controller is irrelevant, since a controller cannot split the character movement joystick. With a mouse and keyboard it is possible, but counterintuitive: on Legacy movement the player must face their camera sideways to the boss to make the mouse forward movement useful in the split, and on Standard movement there is the added complication of turning the player character around to face the camera for the "keyboard direction". I am not convinced that the Standard movement split method is actually an improvement, since turning the player character is added inputs, and even the Legacy movement split method is absurd to expect here. Not only does it make assumptions about the player's input scheme, but this is a leveling MSQ dungeon boss and the struggling player will generally not think of that.)

(I do in fact use the Legacy movement split method in some duties, because it is slightly faster and I naturally prefer Legacy movement. However, I need to know the duty to know to do it in the first place - which is completely not the context here even before the anti-learning nature of this mechanic.)

This is the core mechanic of the boss, and it is awful. (Even before being combined with spreads.) It could have instead been something interesting like "hit one side with the edge of the AOE right down the middle, which flings the venom to consistently cover the other side and little more in a fixed pattern". That would have been a reasonable two-step dodge.

Writhing Riot

An acceptable memory mechanic, but nothing special. The player can stand in the first safespot and then either remember both subsequent hits or remember the second hit and use it to work out the shared safespot with the third hit. This puts it under the three item rule, and allows strong players to plan to dodge in a single movement.

Overall Impression (Boss)

The core mechanic of this boss is so intensely anti-learning, and little else is in here.

Mobs Between First and Second Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

Two More Packs

These are mechanically interesting as a double pull, combining the Aerostats (with donut AOEs) and a ranged enemy for the tank to bring into the group.

Second Boss - Deceiver



Bionic Thrash

Hits two quadrants of the arena opposite from each other, shown by the arms. Nothing special in itself, but returns later in combination with the boss's core concept.

Initialize Androids

A functional warning cast, telling the player to look for the adds at the front of the arena.

(no castbar) Line AOEs From Androids

The concept, that some of the adds are not fully spawned in and therefore do not attack, is a good one. The telegraphs covering the whole floor prompt the player that something must be going on to create at least one safespot.

However, the boss dialogue "Active camouflage operational." makes it seem like the adds that do not fully appear are the ones that will attack, since the other adds appear normally and cannot really be considered "camouflaged" in any way. The player will learn after the first hit, but it is annoying to be misled by the text when instead the text could have said something that is better than guessing without it.

The visual effect for "this is not fully spawned in" is also not really adequate for the player to rapidly scan rows of adds. If they happen to be looking when the "flicker" effect is not active, all that distinguishes the adds is the incompletely spawned ones having a vague green aura, which does not stand out in the bloom-heavy environment.

The adds then come in to be killed, which is good to have sometimes for the same reasons as previous bosses.

Initialize Turrets

Another functional warning cast, this time for large blocks on both sides of the arena that will fire larger line AOEs. I do not like calling these "turrets", since that has been long associated with smaller enemies and line AOEs, but there is nothing strongly obvious to call them. If I had to pick something for the castbar without help, I would call them "cannons" or something similar that at least does not point the player away from that AOE size.

(no castbar) Line AOEs From Blocks

The blocks fire one side after the other, creating a sequence of AOEs to dodge where the whole arena is covered over the course of the sequence. The player can see which side will fire first, as the telegraphs roll out from that side to cover the other side.

However, the visual clarity of which blocks will fire is worse than for the androids, as all of them have particle effects and substantial glow in their charging animation, which mimics the "not fully spawned in" visual effect.

Surge

These spreads with line knockback are good for the player to utilize the AOEs they just saw (or look back at the blocks), since this time the fully spawned blocks prevent their character from being knocked into the wall. Fun follow-up to the sequence.

Bionic Thrash + (no castbar) Line AOEs From Androids

A solid overlap. This time there are fewer "not fully spawned" androids, which is fine in concept since the player should know which type to look for.

Overall Impression (Boss)

Good concept, and well executed except for the introductions and visual clarity not being the best. This would be a good boss given a better presentation.

Mobs Between Second and Third Boss

One Pack

A dull forced single pull.

Two Sentries

Another dull forced single pull, except that the Sentries burst out of the door as soon as it opens rather than letting the tank pull. This does not change much, as they are not strong enough to create the resource-draining effect of the Holminster Switch forced pull series and the party has downtime while they run to the next pack.

Two Eyeborgs

These have multiple telegraphed mechanics, reminiscent of Coincounter in Aurum Vale, and can be double pulled with the next mob / miniboss. Pulling them together is fun, having fewer enemies but more complex AOEs than a normal pull.

Automatoise

I do not mind the large AOE Hard Stomp from this single mob at all. The player has ample time to dodge, they can strategize regarding range, and once they see it repeat they can strategize about it. In particular, the party benefits from dodging together, for both healing range on the tank and melee range on the Eyeborgs if double pulling.

Third Boss - Ambrose the Undeparted



Overwhelming Charge

The way the boss holds its spear is not initially clear about hitting the front or the side, which is not amazing, but the player will learn that it hits the front from the first hit so it is acceptable.

Psychokinesis (Cages)

Comes with red text "The nearby cages are under strain from psychokinesis!", which is good at prompting the player to look at the sides of the arena with the cages, even if they have forgotten the dungeon after a long break and did not get the cutscene replayed. The castbar is also suitably long.

However, the breaking cage doors could use some more visual pop. They shake, their bars are warped, and they glow slightly, but this is a high-bloom environment and the player has to split their time between checking two opposite sides of the arena. (Having the doors shake is a nice touch to not rely exclusively on contrast for clarity, since peripheral vision is relatively motion-sensitive.) The floor lines for where the cage doors can hit are clear, but the doors themselves are not until the very end when they shake heavily.

(no castbar) Uncaged Adds

A very logical place to have some adds to kill.

Extrasensory Field

The player need only move to one quadrant that does not point off the arena (or use their knockback immunity), for which the tell is clear enough even though the arrows fade out quite strongly during their pulses. Since the player has long enough to look to see an arrow pulse bright several times, they can make multiple eye movements to locate a suitable spot and still have time to move their character.

If they did not notice already, seeing this go off gives them another chance to pick up on the pattern that two opposite quadrants point off the arena to the sides, and the other two point in to the arena to the front and back. (Which is good, as it further distinguishes the quadrants rather than making it a natural guess that the player character would be swept through the midline of the arena and then off it.)

Psychokinetic Charge

Combines Overwhelming Charge and Extrasensory Field, asking the player to use the knockback to dodge the front AOE. A nice fair combination.

Electrolance

A simple circle AOE from the thrown spear, nudging the player towards the boss.

Psychokinesis (Spear Dash)

This is not very clear about how wide the spear will hit, nor does it have easy floor references, but the dash sequence starts away from the boss so the player character is naturally positioned to avoid the first couple of dashes and see the rough size. This is not good for enabling precise dodging, so it gets dull after the first time.

(From here on, the two forms of Psychokinesis and the Psychokinetic Charge repeat with added spreads. None of these mechanics play poorly with spreads, and this is a decent mechanical expression of "the boss is desperate to win" for an MSQ dungeon that a very casual healer must be able to clear unaided.)

Overall Impression (Boss)

An okay boss, nothing special even if the visual clarity was up to par.

Overall Impression (Dungeon)

Many boring sections including a horrible first boss, and nothing particularly special or exciting.

--------

Everkeep (Zoraal Ja, Level 99 Normal Trial)



Double-edged Swords

This is a great cast name, cueing the player to expect the second hit even before its telegraph appears. And since the two hits cover all of the arena exactly once, the player must move their character to succeed but is likely to get it the first time based on the castbar.

Calamity's Edge (Activates point-blank AOEs from the Visions)

Nothing special, but fair enough. After all, anything on the battlefield is not likely to be completely harmless.

Vorpal Trail (Dashing Swords)

My first reaction to this was an excited "newbie's first Exasquares!" ("Exasquares" being the colloquial name for the upgraded Cosmo Arrow in the final phase of TOP.) I saw the swords dash at the edges of the arena and come in, and it was cool. Having them start at the edges is a good choice combined with this small boss hitbox, since the player character is likely not near an edge of the arena when it starts, and so the player has a chance to see the pattern before interacting with it.

My second reaction to this was "oh no the floor is not helping". TOP gets away with that, putting a mechanic that operates on a square grid into a circular arena, by both having a very crisp visual effect for each hit and being an Ultimate. This duty has neither of those to make the mechanic work.

Getting hit by this once would be fine. What makes the lack of floor references actively annoying is that this repeatedly combines with Double-edged Swords, and the player has neither a timing reference nor a position reference for this mechanic to plan their movement for the combination. (Especially since the first section of this trial has very few mechanics in total.)

Since this is meant to be a precursor to the swords from the distorted worlds in the rest of the trial and the Extreme - where the floor does have appropriate lines - I would suggest having the floor shimmer and bring in that reference grid beforehand, both providing the mechanical reference and representing Zoraal Ja's twisted thinking. That would make the mechanic less frustrating and so allow the excitement of the combination to shine through.

(There are no further notable mechanics until the cutscene and phase transition.)

Smiting Circuit

The red text "Zoraal Ja readies his blades!" is a good cue to look into the arena for the environment tell. My only frustration here is that the chosen glow effect for the large swords is very similar to that of the "death wall" at the edges of the arena, making it needlessly difficult to pick them out of the environment. (The player does not have the boss's stance to help them, as Zoraal Ja is not holding the swords for the point-blank / donut, and the glow effect distorts the shape of the swords.) In the Extreme, the player learns to overcome that through duty knowledge and practice, but that is not useful here in the Normal.

Since the glow effect is thematically showing that Zoraal Ja is burning through souls, I would instead change the effect on the death wall. It could have been in glowing electrope purple like that in the background of the instance, with a brighter section that rises up to create the sharp wall contrast, and that would maintain the sharpness of the death wall while making the swords visually clear.

Dawn of an Age

This is a really nice way to shrink and transform the arena, allowing for the "distorted worlds" mini-phases. The AOE is itself simple enough and shown for a long enough time that the player will almost always dodge it successfully, allowing for the covered parts of the arena to disappear. Great work.

Vollok

Putting the swords down directly on the available platform the first time is good, priming the player to look further afield for the swords when this cast repeats. The first cast also shows the player that the swords hit on the grid.

Sync

A nice long cast paired with the red text "The distorted world comes into synchrony." This very fairly asks the player to look for which additional platform(s) have been activated and will perform their AOEs shortly after the end of the cast.

If this did not need a delayed activation to allow for an overlapping cast in the Extreme, for consistency and clarity I would keep the timing and lengthen the castbar so that the AOEs hit at the end of the cast.

Bitter Reaping

Double tankbusters cannot hit that hard in Normal, but it is nice to have one so that casual players remain familiar with the concept.

Gateway

Sets up the tethers that move dashing swords between the platforms. Giving each piece of this setup a separate cast is good for encouraging the player to see all the pieces in the order they appear.

Blade Warp

Another setup cast, placing the dashing swords. Again, this is good, and allows a relatively complex mechanic to work fairly in Normal.

Forged Track

The combination of the cast, the tethers to the swords being activated, and the red text "Blades go soaring through dimensions." really makes this work. The dashing swords need the tethers since they are so far away from the player character, while the earlier planted swords do not. (Indeed, the planted swords are too numerous to tether without clutter.)

Actualize

Transforms the arena back, allowing the fight to switch back and forth between mini-phases.

Half Full

This cleave is significantly easier for the first-time player to find than Smiting Circuit, because they can follow the boss's raised arm to the sword. This allows the cleave to work with the blue background tint of the "distorted worlds" arena later on.

Half Circuit

Logically combines Half Full and Smiting Circuit, which would be very reasonable with the changed death wall and background.

Duty's Edge

The big multi-hit line stack is scary, but it hits slowly enough to be reasonable in Normal.

Overall Impression

The first section (before the cutscene) weighs this trial down, between the repetitiveness overall and the positioning frustration of Vorpal Trail. Everything after the cutscene would be a sound, fair Normal given a touch of visual polish. Working with a diagonally oriented boss is a nice change of pace without being unapproachable.

--------

Alexandria (Level 100 Dungeon)



It is unfortunately necessary context that many players are not going to want to be here, due to moral disagreements with the MSQ's requirements of their character. If they stick around for endgame, they will likely see this again in Expert Roulette, but the first-time experience is still important.

Mobs Before First Boss

One Pack

A dull forced single pull. This was annoying enough in leveling dungeons, and is outright egregious in endgame dungeons that will appear in Expert Roulette.

You want the player to move through the Alexandrian environments in a very staggered way, fine. Make the single pulls mechanically interesting. Give us multiple AOEs, or minibosses that interact with the environments, or something.

Two More Packs

Nothing mechanically interesting here, but can be double pulled.

Immunization Protocol B9

This is literally one mob, a robot elephant that does nothing interesting, and the party has no option to fight it alongside other enemies. (It does spawn directly after finishing the last pack, but that is hardly resource depletion when it does little damage.) Boring!

First Boss - Antivirus X



Immune Response

Cleaves either the front or the sides of the boss, with telegraph and glowing front beam / side tentacles. Simple on its own, interesting when later combined with the sequence of donut and cross AOEs.

(no castbar) Five AOE Sequence

This mechanic has good cues to what is happening, between the red text "Foreign entity removal initiated.", the circles and pluses appearing in green one at a time over the five purple dots that start the mechanic as the lightning flows through them, and the telegraphs and audio cue as they go off. The pace is also good, giving the player time to plan out their movements.

What would make this mechanic really great is adding a visual indicator for how long each AOE has until it goes off. (A falling object over the circles would look too much like a tower, but a second color could fill in the circles and pluses one piece at a time, or something like that.) That would help the player time their movement around the cues and their Global Cooldown, rather than partly reacting to when each AOE goes off (until and unless they learn the snapshots from sheer practice). Especially with the overlapping Immune Response casts, this mechanic could have lots of room for skill expression and satisfying resolution - it just does not have the indicator to enable that.

This is the core concept of the boss, repeated often, and it would go from decent to great with that visual change.

Quarantine

An AOE tankbuster and a stack for everyone else. Not hard, but it is different, pushing the tank to stay out of the stack.

Overall Impression (Boss)

A good boss that could be a great boss, just needs that visual representation of the sequence timing to enable and encourage mastery. When I was checking a video of this, the party in the video took about three party KOs on this boss, and they kept going because they understood their mistakes and saw improvement each time. That is what encouraging failure looks like.

Mobs Between First and Second Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

One More Pack

A dull forced single pull with a short downtime before the next pack spawns.

One More Pack

Still not interesting, and a series of only two packs is not long enough to create resource depletion the way Holminster Switch does - especially in Expert Roulette, where despite the tighter Item Level sync, once the player gets their gear going they will come in with 30 Item Levels above the minimum.

To make matters worse, after this pull, the party spends a long time waiting at the pile of wood and stone rubble before being able to reach the second boss. While the dialogue there is story-relevant, in repeat completions the placement is boring, and it negates any resource depletion by giving time for cooldowns to come back. This being Expert Roulette, that is a lot of boredom and frustration.

Instead, I would present the opportunity for a standard double pull and have the storytelling sequence start as the last pack is engaged, playing out during the party's fight against that pack. The rubble would then be shot down just after the last mob dies, allowing the party to move on without waiting. Even if the player has returned to the game for the Dawntrail MSQ, the five preceding leveling dungeons will have refreshed their familiarity with a standard dungeon pull, and the extant voiced dialogue of the sequence would allow them to take it in without diverting their eyes from the pull at all.

Second Boss - Amalgam



Disassembly

The boss splits itself into many pieces, matching the name, and slowly creates a triangle enclosing half the arena before hitting that triangle with an AOE. This whole battle is purple on purple, and only the edges of the danger zone are marked until the "there was another indicator for this" telegraph at the very end, but this still works: it has a long lead time, the red text "Amalgam divides into parts.", and the boss model changes dramatically.

Centralized Current / Split Current

Casts with growing purple glows, hitting the front-to-back line of the boss and the sides of the boss respectively. The veteran player may recognize this pairing as Hot Tail / Hot Wing.

While this mechanic is fine, the credit for that mostly goes to the castbar. The glowing areas initially do not give any clue that the AOEs will hit beyond the bright section, and the eventual front-back line on each is too thin to be reliably seen even aside from its lateness. If you want the player to have a good chance to guess this pattern from the visual, rather than relying on the castbar and perhaps getting hit once, the visual needs to be better tied to the area being hit.

(no castbar) Electrope Beams

There are five spaces for circular cannons to drop down at the front of the arena, three of which are filled in the first iteration and four in subsequent iterations. These perform simple line AOEs that combine with Disassembly.

The combination is fine, but very much relies on the cannons being at the front of the arena (thus likely to be on screen already), the lead time of Disassembly, and the red text "Energy accumulates in the electrope!" to be viable. The thin lines extending from the cannons are not suitable to draw the player's eye on their own.

These are followed up by spreads that appear just before the combination goes off, prompting the player to spread out of the combination safespot. The timing is acceptable, but significantly more likely to get the player caught in an adjustment loop than the similar setup from Firearms in The Skydeep Cenote.

Ternary Charge

Easy but fun, just like Shore Shaker from the Prime Punutiy in Ihuykatumu. This is the same sequence of concentric circle AOEs.

Overall Impression (Boss)

An okay boss, nothing special despite the potential in the theme of a boss that splits and recombines. Scraping by visually; this is about the worst viable visual design before it gets annoying.

Mobs Between Second and Third Boss

Four Packs

Nothing mechanically interesting here, but can be double pulled.

Third Boss - Eliminator



Partition

A simple side cleave that sets up for Reconfigured Partition.

Reconfigured Partition

The cast name is an important clue that the sword will move to and hit the other side, making this a fair mechanic instead of a reaction to the animation.

Subroutine

The boss splits one or two parts off, so that those parts can later perform distinct AOEs. (The claw does a line AOE and the orb does a donut AOE.) In theory, this is a fun way to build on and connect to the preceding boss, Amalgam.

However, the initial positions of the parts on the boss's back are so high up that they are not properly visible when the player character is close to the boss at the default camera tilt or even slightly higher, which makes this functionally only a warning that the boss set something up. Since in the story this duty is taking place in a computer, the cast name "Subroutine" could set up just about anything, and that is all the player gets if they do not see the parts separate.

(I literally did not know that this boss splits itself until I went into this dungeon with Duty Support for this review - the comments from Krile and G'raha Tia clued me in. On my first attempt with a friend and Duty Finder matchmaking, I did not see the parts separate due to the combination of camera tilt, camera position, and rapidly moving my eyes trying to learn the duty. On subsequent completions, I had learned to anticipate the potential positions for the part mechanics and look there at their scripted times, which meant I was not looking at the boss to see the parts separate.)

Since it is not practical to expect the player to adjust their camera tilt in combat - APM aside, they may not have the keybind flexibility to do so - and camera tilt is important to the player's HUD Layout and seeing around their character, I would fix this by moving the detachable parts of this boss model down and having their removal significantly change the boss's silhouette. That would make the first-time player much more likely to see the separation without Duty Support commentary, while also not changing the boss's unified color scheme.

(cast by Elimination Claw) Terminate

A wide line AOE cast at the same time as another mechanic from the boss, with the only indicators being the cast on the enmity list and the purple lines extending part-way from the claw at the side of the arena.

If the player reliably saw the claw leave the boss and move to the side of the arena from the preceding Subroutine, this mechanic would be okay but on the fast side for processing the combination. Since that is not reliable, the purple glow is not sufficient to reliably draw the player's eye when combined with the other nearby purple from the Reconfigured Partition when this first appears. And since this does not have a long cast, the result is annoying "gotcha" potential where the player does not see what hit them. (Remember, the player has a lot to see their first time in a duty, especially for casual players.)

(cast by Elimbit) Halo of Destruction

A donut cast at the same time as another mechanic from the boss, with the indicators being the cast on the enmity list, the darkening of the unsafe areas of the arena, and purple vertical lines clamping down on the "spotlight" of the safe zone. The donut is followed up by spreads, or later by a Terminate also asking the player to move their character out of the donut safe zone.

Again, if the player reliably saw the orb detach, this would be okay. Since that is not reliable, the indicators are somewhat lacking, though less badly than Terminate; at least something is shown over essentially the whole arena.

(started by Subroutine detaching both parts) Add Phase

The six spread Lightning Generators have the potential to be interesting, as different jobs can rotationally benefit from multiple targets in different ways. However, in the context of a dungeon boss where an add phase must be very short, the lack of party coordination on who will target which adds first limits the skill expression from these adds in Duty Finder matchmaking.

(cast by Elimbit) Light of Salvation (Line Proteans)

These come with telegraphs, as is necessary to get the player to spread by reacting.

Here, the initial presentation of proteans is fine but not good; the Elimbit has moved after its donut and before the first appearance of this, so between the movement and the adds the player may well not even see the Elimbit and purely react to the telegraphs. (Compare to Ktisis Hyperborea having Hermes cast True Aero, which is also a line protean - and even has a baited follow-up - but comes directly from the boss, which the player is reliably tracking.)

After the add phase, this is sequenced after a knockback circle (no castbar), with the protean telegraphs appearing just before the knockback resolves and leaving several seconds to spread between the knockback and protean resolutions. While that sequence is in itself reasonable, the need to react to fellow players' choices necessarily draws the player's eye away from the Partition / Reconfigured Partition that the boss starts casting during the spreading.

That last part can easily hand the first-time player an individual KO - remember, their character just took damage from the knockback and the protean even if they avoided being knocked into the wall - without giving them the opportunity to see that any avoidable damage was coming at all, let alone what it was. And even on repeat completions, the visual demands are too much for a mechanic that Duty Finder can only do reactively: Partition / Reconfigured Partition require looking at the castbar and the sword, while reacting to fellow players' choices effectively for the proteans requires looking at one's character's feet the whole time. As a result, the most practical method is for the player to try to take their protean close to the front-to-back line of the boss as prepositioning to react to the Partition / Reconfigured Partition, and resolve that on reaction once the proteans resolve. This further pushes reaction within the sequence, making it unfun.

Any mechanic that is going to push the player into reacting to fellow players' choices using vision must be designed around the assumption that it completely occupies the player's eyes for the duration, due to the inherent pressure on reaction time pushing them to keep looking at the relevant locations. Surrounding mechanics must also be chosen and designed on that basis.

Elimination

The boss slashes the arena several times, dealing light damage each time and leaving a set of lines slashing the ground. These lines then expand and explode in the same sequence, requiring multiple movements to avoid further damage as the pattern is quite dense.

If the visuals were clearer about where each set of AOEs will hit, I could enjoy looking for areas that will not be hit often and plan to dodge accordingly. But the visuals given focus more on glow and flash than clarity, and there are no floor references to work with, so this is unpleasant to look at and annoying to analyze.

Overall Impression (Boss)

Would have a much better first-time experience if the player could reliably see the pieces of the boss separating and reattaching. Manageable on repeat completions, but still noticeably annoying.

Overall Impression (Dungeon)

Slow and boring, not allowing the concept of the first boss to shine. When it comes to slowness, the tighter Item Level sync compared to the rest of Expert Roulette at least has a reason to be there - the single pulls and forced wait do not.

--------

The Interphos (Sphene, Level 100 Normal Trial)



As with Alexandria, it is unfortunately necessary context that many players are not going to want to be here due to moral disagreements with the MSQ's requirements of their character. As this is a story trial, despite the lack of Duty Support the player has little reason to return after their own MSQ completion, so they are statistically quite likely to be here for their MSQ.

As a general visual note, the NPC illustration on the Queen Eternal's battle dialogue popups extends a little too high, obscuring target buffs and debuffs in the default HUD Layout position of the target bar. Rather than expecting even the most casual player to move their target bar in order to track their own applied debuffs, I would move the NPC illustration down - or better yet, allow the position of these popups to be adjusted in HUD Layout.

Legitimate Force

A fine one-two punch sequence, with visuals on the boss's four arms that allow the same side to be hit twice while displaying both parts of the sequence. Clear enough, and the first glow naturally draws the player's attention.

Aethertithe

The initial many-hit raidwide is fine.

The subsequent puddle AOEs and final hit on each section are completely sunk by their visuals. The red text "The absorption of aether accelerates!" is a fine warning and not the issue. The issue is the distorted grid visual for the danger zones. For me, I manage, but it looks like it should be a draw-in mechanic even if not caught by the final hit on each section. However, some players got so motion sick from it that they vomited, and I can understand why; the appearance that the floor is moving in a distorted pattern can throw off visual balance feedback quite strongly.

In theory, using the motion of high-contrast objects is a way to provide a visual cue that will reliably be seen without resorting to glowing or standard orange telegraphs, working with the motion sensitivity and contrast requirements of peripheral vision. In practice, the results of this have made it clear that such technique should not be used to distort a floor - and if you want to experiment with it in other ways, run tests with players who suffer from various forms of motion sickness before putting those visuals in the live game.

Coronation (Circle AOEs)

The way these targeted AOEs leap towards the selected player character is spooky and not helpful, since it reduces the player's lead on the AOE and often does not help the player figure out who is being targeted. (The party is likely stacked from a previous mechanic.)

If this instead came with a Prey targeting marker, like its other version, it would be a reasonable mechanic with an appropriate lead time.

Virtual Shift

Transforms the arena into a different environment.

Hourglass Arena Mini-Phase

A very restricted arena that makes for some fun and approachable challenges.

Coronation (Double-Targeted Line AOE)

This is a really cool mechanic. The two targets can work together and pull the cannon around with their tethers so that no one gets hit by the beam, and they have a long time to see the telegraph and how the cannon responds to them. The crisp visuals are also excellent, helping the player see the pieces of the mechanic regardless of whether their character is tethered.

While Duty Finder does not coordinate, and this mechanic seems to be here because of the Extreme version coming in Patch 7.1, this still functions in Duty Finder due to the long lead time and only taking a single Vulnerability Up for getting hit. The player has long enough that they have a good shot at sorting it out without ever feeling pressured on their reaction time, and if they fail they are still able to continue fighting without even waiting for a raise.

If you want to have some complex mechanics where the player must react to another player's choice, this is how you do it. Such mechanics are still inherently limited to regular duties, but this is how you do it.

(This mechanic also appears in later rounds of the "main arena" mini-phase, combined with Aethertithe.)

Downburst

A simple, familiar knockback from a corner or the center of the arena, complicated by the restrictive arena shape. It is not hard, but it is fun, with enough time for the player to fairly reason about the complication their first time.

(no castbar) Donut AOE from Drone Circle

Nothing special, but a fine mechanic. The visual cues of the drones swirling in to form the circle and then lighting up the edge of the danger zone is what makes this work.

Powerful Gust

Another simple, familiar knockback, this time from a side of the arena. Has exactly the same design results as Downburst.

Levitation Mini-Phase

The way this phase opens by moving the player character to make sure there is no floor under them is an important trick, pushing the player to notice the levitation without having to read their debuff bar. After all, this is Normal Mode. The forcible move is not ideal, especially out of melee range, but doing it during an arena change makes it less jarring.

Castellation

Giving the player ample warning of every height change is what makes this work. The opening showing the levitation and the red text showing the changes with "Gravity increases, making you fall." and "Gravity decreases, making you float." are crucial.

I must also compliment the attention to visual clarity while having the wall still look like part of a castle. Not only do the edges of the holes glow, but some light shines through the holes into the safe zones to help the player line up with them.

Since failing this mechanic is a one-hit KO (the wall sweeps the player character out of the arena), I would lean even further into the visual clarity by making the irrelevant top of the wall less jagged and less glowy. I would also consider making the safe zones a little wider, since this is mandatory for MSQ and very casual players may not have the required movement precision. (Especially for the quicker sequence of two Castellations in a row - the down to up transition ensures that the player character is already close to a safespot, but that does not help a player who lacks the movement precision to land in it with their first movement attempt.)

Legitimate Force (with levitation follow-up)

The same mechanic, but this time the player will fail the impending fall if they keep their character close to the center of the arena.

Now that the player has already worked with the levitation mechanic, this is reasonable, and the timing of showing the red text shortly after the second arm glow is perfect. Since they have already seen Legitimate Force several times and the basic format is already familiar, the red text will appear pretty much exactly when they have likely finished processing the second glow cue, encouraging them to smoothly add "and then move to a platform" to their movement plan if the hits alternate.

The timing of the fall allows for a moment of hesitation, which is necessary since the casual player has no practice in executing movement sequences without hesitating.

Overall, this is a good example of how to set the player up for success with a movement sequence mechanic.

Main Arena Revisited

Absolute Authority

The sheer length of this castbar, the dramatic dialogue, and the 5-second countdown are normally associated with very high damage mechanics, making the player likely to shield and/or tank Limit Break this... which is largely useless, since the cast does only moderate damage right away and instead applies debuffs for a mechanically intense sequence.

Duty Finder does need a breather before and after dealing with all of this - there are flares, "stand with someone" triangles, Acceleration Bombs, and petrifying gazes attached to player characters in quick succession, combined with rounds of circle AOEs on the ground and repeated pulses of damage throughout the sequence. However, this presentation is frustratingly misleading, as the party does need their healing and mitigation tools but not for the opening of the mechanic.

To improve this mechanic, I would split the presentation into two castbars. The first would apply an "inactive form" of all the debuffs and faded "frozen" markers for the flares, showing even the casual player that they should prepare for something to happen later. The second castbar would still be long to give the player time to think, and at the end would "activate" all the debuffs and start the sequence. In this way, even if the player does not read debuff bars, they would spend the long cast preparing for a sequence involving later healing rather than expecting a massive raidwide.

(Yes, my proposal would be gently introducing Duty Finder to the same "this debuff is not active yet" concept that underlies the Code Smells in TOP, but with a later activating cast rather than an expiring timer. It is a good concept for all skill levels, and really does not need to be limited to Ultimate.)

Once the player actually knows what this mechanic is, it is reasonable, as the debuffs are suitably timed with overhead markers and the player need only look under their character's feet to dodge the circle AOEs. The pace feels scary because there is no breathing time during the sequence, but there is enough time to do it.

Divide and Conquer

What a sweet way to get Duty Finder to do line proteans. Awesome mechanic, excellent work.

Unlike in Alexandria, here the player is generally looking at the source of the proteans. Then the hits one at a time nudge the party into spreading out, especially since each hit has crisp telegraphs and the "selected for something" overhead marker - meaning they will probably be fairly spread out for the final hit on every party member at once, so they have a good chance of managing the final protean positions. (They still might get caught in adjusting loops and fail, but there is only so much to be done about that when the player is approaching the duty based on reaction rather than planning.) The cast name is also fitting, but it would not be nearly enough on its own.

More like this, please. Short of retraining the Duty Finder population to do general preparation including protean positions, you would never be able to drop the "guide rails" off of mechanics like this, but you could still gently introduce so many concepts. That would make the regular duties better stepping stones to the high-end duties, without making the high-end duties any less of an accomplishment.

Final Phase

Wuk Lamat's intervention here is demotivating because she steals the spotlight from the player, both in storytelling and by doing so much damage that the party's efforts are largely irrelevant. How can you expect the player to put in effort if you tell them that their effort does not matter? To make matters worse, the cutscene sharply interrupts the second Absolute Authority resolution (unless the party has not yet met the generous boss HP threshold to allow that), viscerally stopping the player from carrying out the duty's scariest mechanical sequence! They are all wound up and going, and then control is suddenly taken from them by Wuk Lamat forcing them to cede the stage.

NPC intervention in a duty can be done well, but it must not take away from the importance of the player's actions. For example, The Final Day (Endsinger Normal) also has an NPC intervention cutscene, but the Scions praying for the Warrior of Light's success makes the player's actions more important rather than less important. That is very fitting for the climax of an expansion's MSQ, while this is not. Likewise, The Final Day's NPC intervention comes when the player is expecting not to have control of their character, because they see the raidwide coming that previously needed a tank Limit Break 3 and they see that they do not have the Limit Break available to them. (As a result, the motivating effect of the Scions' prayers in The Final Day is similar to that of Phoenix's intervention in The Unending Coil of Bahamut (Ultimate) (UCoB).)

Having an NPC intervention related to the power of friendship is all well and good. It can even be based on trying to restore Sphene's memories. Suppose instead that after the second Absolute Authority completed, the Queen Eternal continued to overload and then a cutscene started. In this version, Wuk Lamat would be accompanied by G'raha Tia and Krile in trying to restore Sphene's memories, and for their success Sphene would summon one or more of the bosses from Alexandria. The NPCs would engage those boss(es), allowing the player party to continue fighting Sphene. Since the three NPCs are not enough to form a light party, the player would see the NPCs' resources slowly deplete from their own fight over the course of the final phase, creating a thematic sense of urgency and possibly even a (generous) hard enrage.

Dynastic Diadem

A basic donut with a small safespot, encouraging the player to move their character to the front center of the arena. This would be helpful prepositioning for Royal Banishment, but the shared point of the cones there does not match the center of the circle here, so it is not great.

Royal Banishment

Raidwide spam and an appropriately slow alternating cone sequence. A fine mechanic to convey Sphene's overloaded state, having simple movements and many small hits of unavoidable damage.

Overall Impression

This trial is really brought down by its final phase and its story context. The actual mechanics of the other phases would be very good to great with some polish to a few mechanics.

----------------

Despite many strong concepts and some truly excellent mechanics, every single group MSQ duty has at least one major design flaw, several of which are in visual design. This is not good, both for immediate enjoyment and for getting the player to the endgame with the confidence that they can enjoy it.

I may be an Ultimate raider, but I always worry when doing a new MSQ duty for the first time. I always have to. I nearly got hard blocked from continuing the MSQ once, and any new duty could be the one that stops me... or the one that tells me that the game is moving towards demanding something I cannot improve at. Patch 7.0's MSQ left me with a lot of concerns in that regard, since not a single one of the group duties felt good to play.

[Aurelle_Deresnels]

I will now continue my review of the design of the Patch 7.0 duties, in this subsection covering the two optional dungeons that are not required by the MSQ. Conceptually I would include Arcadion Light-heavyweight Normal in this subsection as well, but I have split them up for length, since both dungeons have mechanics that deserve extended analysis.

Being Expert Roulette dungeons, these duties can benefit from the player being encouraged to return to them many times after completing their stories, but they must still provide an encouraging first-time experience to the casual player while holding up to the repetition. After all, the rewards for the repetition-based gameplay loop become frustrating if the player is too discouraged to go back to the duty.

Since these are endgame duties, and returning players will often warm up first in the MSQ even if they return in later patches (when the latest MSQ is the patch MSQ not required for these duties), these duties have less need to concern themselves with the very weakest players. However, most active endgame players are still casual players.

(Since Duty Support does not include these dungeons, I had to take the arena pictures in Explorer Mode, so as not to inconvenience other players. Please forgive the lack of bosses in the arenas.)

----------------

Tender Valley (Level 100 Dungeon)



Mobs Before First Boss

Four Packs

Not only can these be double pulled, but each double pull has one to two individually more dangerous mobs with higher HP. This is the same sort of opportunity for skill expression as it is in the leveling dungeons, and it is even more welcome here with the heavy repetition and full job toolkits of Expert Roulette.

First Boss - Barreltender



Heavyweight Needles

This would be a normal set of cone AOEs originating from the boss, except that the early telegraphs are narrower than the actual AOEs; the telegraphs only expand to show the actual areas to be hit at the last moment. Only the larger open areas actually contain a safespot, while the more numerous small open areas get expanded over and hit twice.

As a result, the first-time player most likely follows the telegraphs and moves their character to either a small open area or the edge of a large open area, thus failing the mechanic. But even though they know what to do next time, they feel baited rather than encouraged.

Why? Because there was no other tell that the early telegraphs do not match the actual AOEs, nor are the expanding telegraphs used in the player's favor. (Fighting Kefka is fun in Sigmascape V4.0 (O8N) and its Savage version (O8S) because there is a tell for when he is being a trickster and the telegraphs do not match the actual AOEs, not just because the player is told by the story that he is a trickster boss. The expanding telegraphs in the circle version of Dispatch (Vanguard Commander R8) are acceptable because they start expanding early and are positioned carefully to guide the player into a true safespot.) There is no skill to be learned here, nor is the player expecting (or willing) to undertake the process of progression for a regular dungeon boss. This is a "gotcha", where the player just has to know / remember that the telegraph system lies here even though 100 levels of gameplay has taught them to trust it. (All the worse if the player remembers that telegraphs are granted by the Echo!)

This is the boss, and by extension the game, punishing the player for doing exactly what the game has taught them to do. That is not an enjoyable experience in any way; if anything, it is treating the player as lesser.

As such, this would be a better mechanic if it used something like the glowing lines from Black Cat Crossing (in AAC Light-heavyweight M1 (M1N)) as needles, even though those are further from the actual AOE shapes - at least it is intuitively obvious that the actual AOEs are not pixel lines, so the player would expect to discover how far they expand and in what shape.

What about the player who already knows how the mechanic works?

Well, "find a large open area" on its own is not interesting, even if the player does not know the hidden pattern. (There are only two possibilities: either the safespots are north and south-east, or north-west and south.) Even for the casual player, this is boring the 90th time, and this is cast twice at the start of this battle before combining it with any other mechanic.

To avoid that boredom, the player must be presented with opportunities for skill expression. This mechanic could permit skill expression by dodging only as far as necessary if the floor geometry had references for the player to work out where the AOEs will expand to. But the floor has no such reference lines, so that opportunity is denied to the player and the mechanic is just boring.

Just because the lore concept is an open desert field rather than a "settled" area, that does not mean you cannot have good floor geometry to facilitate skill expression. This boss jumps to / hits the center of the arena as part of several of its attacks, including this one, and the floor already has cracks to convey the arid desert environment. It would have been perfectly reasonable to have the bigger cracks radiate from the center of the arena due to the repeated impacts of the boss hitting that spot - after all, the battle takes place in the boss's home - and use those to mark the potential edges of the safespots.

As it stands, at no point is this mechanic fun. First it is unfair, and then it is boring.

Tender Drop

Drops many cacti, that will explode shortly after the resolution of the next cast (either Heavyweight Needles or Barrel Breaker). There are two types of cacti: those with small explosions are bare, while those with medium explosions have light brown spines and a pink flower.

I could just correctly say that the tell distinguishing the two types of cacti is inadequate and low-contrast, since the spines are tiny and the pink flower blends easily into the orange floor. But I want to show you what the player can easily wind up seeing while looking around at all these cacti.

Here are some freeze-frame screenshots from a gameplay video without third-party tools:







While the video does not load in perfectly, you can see that the player's interface is much clearer than the cacti, because various visual effects are blurring the cacti. In the first screenshot, the blur is exclusively coming from the boss itself, as part of the animation for a subsequent cast that will resolve just before the cacti explode. In the second screenshot, the blur is coming from the point-of-view player's own job actions, which are often left on as an important source of job fantasy and/or gameplay feedback. (Even if the player knows about the option to set those to Limited or Off!) In the third screenshot, both sources of blur are present simultaneously, albeit with a different subsequent cast.

This is already bad for visual clarity. But what the player sees is even worse than this, especially when they do not already know about the flowers and spines indicating different explosion sizes.

Consider the player's time window to look over the cacti. They cannot do so immediately at the end of the Tender Drop cast, since the boss has just thrown the cacti into the air from itself. The cacti land in clouds of dust that obscure any spines and reach up to the flowers, so the player cannot practically use that time to rapidly look between the cacti either. They can only begin checking for spines and flowers once the dust settles, leaving them precious few seconds to look over all the cacti and the subsequent cast before deciding where to move for that cast.

As a result, the first-time player is forced to move their eyes rapidly either trying to locate all the cacti accurately enough to match them up with the subsequent cast, or waiting on the subsequent cast before checking the cacti near its potential safespots. (I say "trying" because there are far too many cacti for the player to succeed with precise locations for every one in the available time. The human eye has limits.) This rapid eye movement effectively creates further blurring, whether the player is using visual information from while their eyes are in motion, is locating some of the cacti purely via peripheral vision in order to have fewer eye movements, or both. (With some disabilities, it is also possible for the player's eye muscles to move their eyes slower than those of an able-bodied person.)

If you blur those screenshots further and look at each part for only a split second... well, the flowers and spines are no longer really discernable on the cacti. What the player actually sees of your beautifully rendered cacti may be politely described as "a blurry heap".

So the player may well not discover that the flowers and spines exist and are relevant from looking at the cacti before the mechanic resolves - to discover that on their own, they have to happen to catch a cactus with them and a cactus without them in their central vision for long enough to notice those elements, in close enough succession to remember what the other type looks like, in the midst of battle with a boss whose core "feature" is that the early telegraphs lie.

What about from looking at the explosions as the mechanic resolves for the first time? Then the player is encouraged to look at their character's feet, both to see how far the early telegraphs expand and to see if they got their character far enough from all the cacti. Unless they stood their character on top of a cactus, that is a terrible place to look to see either cactus type, let alone both. (And the size difference in the explosions is not large enough to be easily visible by looking at the curvature of the circle telegraphs, whether a small part in central vision or the whole circle in the sea of orange in peripheral vision.) So the player is even less likely to discover that the flowers and spines exist and are relevant at that point.

As a result, the player can easily go through the entire mechanic without discovering that two types of cacti exist at all, and be left with the impression that they failed because they did not locate the cacti quickly and precisely enough to locate a safespot. (Or that they succeeded by chance for the same reason.) In turn, this impression drives them to focus even more on locating the cacti next time, which is not just uncomfortable, it drives them further into exactly the rapid eye movement strategies that make it so unlikely for them to notice the different types of cacti!

For a significant subset of players, the visual design of this mechanic takes the effort they put into learning and steers it into a dead end. Once the player is in such a dead end, the only ways out are for a fellow player to tell them or for them to check video footage slowly with the intention to improve at the mechanic. Neither is likely, especially for the casual player! They will generally just conclude that the mechanic is unfair or that they cannot do it, especially in the context of a "gotcha boss" that has already shown them a willingness to be unfair.

And to make matters worse, disabled players are disproportionately likely to wind up in this subset no matter what their disability is. Visually impaired players suffer for the obvious reason. But a player with a non-visual disability will pressure their vision more to compensate for their disability, and has had ample practice doing so from the MSQ necessary to unlock this dungeon - which also drives them to rapid eye movement strategies, especially given the long history of past mechanics in their mechanical vocabulary where precisely and rapidly locating many explosion sources is the necessary method!

(I wound up in exactly this dead end, until a friend told me that the flowers and spines existed. Cue another friend shouting "what flowers and spines?!" There were only three people in that conversation, no bystanders, all raiders that can handle at least final floor Savage... and the two people other than me had not been delayed by the graphical update, so they had the flowers and spines on their screens many times.)

This is completely unacceptable. It is your job to prevent the player from getting stuck in dead ends, not encourage that!

What about the experience of the player who does know about the two different types of cacti, and that the safespots are always near flower-less, spine-less cacti?

Consider the sequence with Barrel Breaker. The player with this knowledge can plan to have their character ride the knockback into a corner, and accordingly look for a corner with a safespot. So for each corner, they naturally look at only the cactus closest to that corner, and the hidden pattern (that there are two safespots in opposite corners) ensures that they will find one after looking at at most two cacti in their central vision. This is a reasonable task for the time given, and thus a reasonable sequence.

(Notice that the hidden pattern does count as helping the player here, because the player does not have to know it exists to benefit from it. The player who does know about the hidden pattern only needs to look at one cactus to find a safespot for this sequence, and that does not count.)

But consider the sequence with Heavyweight Needles. There is not even always a shared safespot between the two mechanics, so the player may have to check the cacti over most of the arena to locate one that will have a small explosion and plan to dodge accordingly. And even if there were always a shared safespot, the player would still have to either check all the cacti near the Heavyweight Needles safespots once the early telegraphs show, or start checking all of the cacti before the early telegraphs show and waste some of their effort. (In either case, most of the cacti they check have flowers and spines, and so will not stop their search.) This is not at all reasonable when each cactus has to be checked in central vision to discern its explosion size.

I understand that your duty design team is neither your 3D art team nor your story writing team, but you must ensure that each visual indicator's necessary standard of clarity is communicated between teams and tested extensively before release. It is the visual design equivalent of marking "this cast name is a mechanic cue, fancy translations cannot be at the expense of clarity at speed" that you learned from Starboard / Larboard Wave Cannon in O11N and O11S. Otherwise the work you put into making each battle express the surrounding story is liable to cause gameplay problems, as it does here.

To salvage this mechanic, obviously the two types of cacti would have to be made visually distinct despite the game-induced blur on the screen and the effective blur from the player's eye movements. Rather than rely purely on high contrast and glowing at the potential expense of the battle's lore concept, I would both heavily differentiate the cacti and present the mechanic in a way that gives the player more time to check them.

Remember how I mentioned changing the floor geometry for Heavyweight Needles? Working from there, tiny green buds of cacti for all possible positions could be present at all times, and then this cast (suitably renamed) would grow the selected cacti from the bud form before they release their spines explosively and shrink back to bud form. This would naturally eliminate the time period before the cacti land and the dust settles, when the player currently cannot check the cacti effectively. More subtly, this would show the player that the set of possible positions is limited but large, and allow them to review the set in "free time" between mechanics or even outside of battle entirely.

While that would also eliminate the spines as a tell between the different types of cacti, the spines are nearly invisible in the midst of battle anyway so that is not much loss. Instead, I would have the cacti with small explosions grow thin and tall with no flowers or branches, while the cacti with medium explosions grow spherical with a glowing blue flower from all the water aether they are taking in to grow. Not only would the completely different shapes and moderate glow actually manage some visibility through the blur for the first-time player, but once the player realizes that the tall cacti have smaller explosions, they can handle future repetitions by looking for the tall cacti in their peripheral vision and then getting the precise position of one tall cactus and its surroundings in their central vision. (Which would stop their visual search much faster than is currently possible, especially for the Heavyweight Needles sequence. This is why I did not suggest simply making the cacti with medium explosions bigger - those are not the ones the player needs to find first.) So their effort put into learning would steer them away from the dead end and towards a reasonable method for finding the necessary visual information.

Barrel Breaker

The boss winds up a punch to the center of the arena, knocking back all player characters unless they use their knockback immunity. Simple on its own - aim for a corner - but is always directly after a Tender Drop cast.

Prickly Left / Prickly Right

While the early telegraphs and the glowing side of the boss show this as a 180 degree hit to that side, they again lie about the actual size of the AOE. But even for the first-time player who applies the "gotcha" from Heavyweight Needles here and tries to dodge just far enough for that, this mechanic still baits them into getting their character hit since the AOE expands much further. (The only safespot is entirely opposite of the indicated side.)

Once the player knows how this mechanic works, they can use the facing arrows on the side of the boss's targeting ring to locate the safespot precisely for optimization, so this is less bad than Heavyweight Needles. But it is still annoying that the early telegraphs lie with no other tell, and the mechanic is just not that interesting once known.

Overall Impression (Boss)

The core concept of this boss is unfair the first time, and poor visual design prevents it from redeeming itself on repeat completions. Even if its visuals were cleaned up, it is not interesting.

Mobs Between First and Second Boss

Four Packs

These can be double pulled, again with a single larger mob in each double pull. Each double pull is also preceded by a water pipe slide, both separating the encounters and showing the story of reaching a once-settled area.

Second Boss - Anthracite



Anthrabomb (Basic Form)

Tosses three bombs onto the arena floor, with black arrow arcs leading to images of the bombs where they will land. (The bombs then explode with a single point-blank AOE each.) The arcs are a good and important part of the visual indicator, as they allow the player to locate all the bombs by following the arcs out from the boss. The cast length is also appropriate.

Anthrabomb (Line AOE Tutorial)

Tosses a single bomb into a pipe opening in the arena floor, with a yellow arrow arc leading to a yellow arrowhead (and no bomb image) over the pipe opening. (The matching pipes on one side of the arena then do line AOEs that knock back any player characters hit, with the two types of pipe being distinguished by color, shape, and patterns used as decorations by the previous civilization that built the arena.) The cast length is again appropriate, and showing this cast alone is important to have the player notice that this AOE does not hit directly where the bomb landed.

The edges of the line AOEs are supposed to be something the player can work out via floor geometry, specifically the slightly reddened lines of smaller stones across the arena that meet the edges of each side pipe. However, the color difference and the gaps between stones are so small that these lines become invisible as soon as any effective blurring is introduced, whether from job actions, boss animations, the player's eye movements, working in peripheral vision, or the player's camera movements. And even when they are not blurred, they are still interrupted by the ground pipes, which take up much of the space that is near the entrance to the arena and therefore is most likely to be near the first-time player's camera at this point.

I understand that this battle takes place in the ruins of a previous civilization, but you can and must still find a way to have either suitably crisp floors or mechanics that do not require them for visual clarity. (And I know you can do that; despite the restricted color scheme for the floors of Alexander - The Cuff of the Son (A6N), Alexander - The Burden of the Son (A8N), and their Savage versions (A6S and A8S), the raised and lowered panels for Swindler's Height debuffs are very clear.)

For example, you could have had the previous civilization color their floors and pipes using the natural and enduring colors of various stones, rather than fading paint. (Presumably the boss would blow away any dust.) That would give you a much less constrained palette, even within the hard building stones readily available in the western United States of America that Shaaloani is based on. (While it would limit the logical decorative pattern choices of the building civilization to relatively large, blocky options that make sense as being constructed directly out of stones, the current decorative patterns are not reliably getting seen anyway. Finer detail for lore purposes could be provided by carving the stone if you want.) If you are willing to grant the building civilization the ability to preserve softer stones in transparent and durable material, you could even have the edges of these line AOEs marked in ornamental obsidian, which would be very high contrast and available in the geographical area.

Regardless of your choice of justification for contrasting colors, the floor geometry showing the edges of the line AOEs should extend over the floor pipes. As it stands, the red circle pipes leave little to go on even once the player realizes that the floor pipes are each bisected by one edge of the line AOEs.

Anthrabomb (Final Form)

Tosses three bombs combining the initial two forms; two land on the arena floor and one goes into a pipe. Would be entirely reasonable with good visual design for the floor and pipes.

Carniflagration

Three final form Anthrabombs in quick succession, followed up by a basic spread, with no intervening castbars. The time given for each Anthrabomb is not terribly short, but the second and third appear during the placement and detonation of the previous bombs. The spread markers appear as the final set of bombs is thrown.

Here, it becomes even more important to mark the floor pipes and the edges of the line AOEs in high contrast, because the player's view of the indicators for the second and third sets of bombs will be blurred at some points by the movement of their camera as they move their character to dodge the preceding set.

But there is another problem with this mechanic.

With this sort of mechanic, the player knows from long experience that they only need to find one safespot, and that doing so is faster than mapping out all the safe areas in the arena. So especially if the player is used to playing jobs that can do their full damage at range, a natural response to the faster pace is to start by moving their character away from all the bombs - for which they only need rough locations from peripheral vision - and then further move their character to the nearest spot that will not be hit by a pipe. (This second movement is guaranteed to be small by the alternating layout of the pipes, which the player learned from the line AOE tutorial Anthrabomb, and the player can begin locating the yellow arc during the first movement.) For other mechanics of this sort, this is an excellent method to handle lack of practice with the specific mechanic's visual indicators, or simply high speed demands.

However, this method applied here generally drives the player to move their character up against one of the side walls, beside the pipes. (More so due to the lack of contrast in marking the edges of the line AOEs, encouraging the player to use the side pipes themselves as references.) At that point, consider the behavior of the player's camera. If they try to place their camera over the side pipes, it will instead hit the invisible wall over the side pipes and press up against their character, giving them a view of very little. If they instead place their camera away from the side pipes, even at the maximum distance from their character it cannot show them the whole arena for the subsequent sets of bombs. (If the player primarily moves with a mouse, that will incline them to do the latter.)

As a result, the player must fight their camera rather than the boss itself. This is annoying, both from the immersion break of fighting the interface and from the player's prior learning failing them because of the interface. The player winds up having to avoid this method of dodging at this boss, not because it would not be effective for their character but because it does not allow them to see the later bombs.

If the side pipes did not have invisible walls over them, the player would be able to point their camera into the arena from there and have it be useful just like they do with most arenas, which would eliminate the issue. If the attacks after the first were of some other form that did not need a clear view of the whole arena, perhaps something dodgeable by the castbar, the views available to the player after any first dodge would be adequate. If this mechanic was presented in a context that effectively granted the player an extra-zoomed-out camera to see the whole arena with, as Anabaseios: The Twelfth Circle (Savage) (P12S) does in its Gaiaochos mini-phases, that would also eliminate the issue. (Raiders colloquially and lovingly refer to those mini-phases as "UAV", short for "unmanned aerial vehicle", for the distinctive feel that is fully designer-intended but acts like the camera zoomhacks used in the TOP world race.) But none of these options are true here as the boss stands.

Should the player persevere and be strong enough to seek out hidden patterns even in a mechanic they find hectic, the situation does eventually improve for them. Many seemingly possible sets of bombs are actually blocked, creating several locations away from the side walls that always have a safespot nearby. Once the player learns to keep their character away from the side walls, they have the view of the arena needed to notice one or more of these locations via extended repetition. In turn, should they gravitate to one of these locations, the smaller required movements from staying within that area make the mechanic less hectic, finally allowing them the time to reliably reference the low-contrast markings on the current floor during the mechanic. They may even be able to optimize their movements for job uptime. But the path to that point is needlessly discouraging, and struggling players may not be able to follow it at all.

Overall Impression (Boss)

This boss is an unfortunate victim of its visual design and the game's standard camera. There is optimization potential under the surface, but it requires finding hidden patterns to avoid fighting the interface and the visual design.

Mobs Between Second and Third Boss

Two Packs

These can be double pulled, and the second pack includes two Yok Huy Vessels whose auto-attacks cleave an unmarked circle around their target. This is mechanically interesting. Further, it is not unduly burdensome to the casual healer even if their party chooses to take the auto-attacks for better damage output, since every healer job at level 100 has a variety of AOE healing tools that can easily handle this amount of incoming damage.

Indeed, I consider this a good thing, as it encourages less skilled healer players to try using some party healing cooldowns on trash pulls and then notice being able to use those cooldowns again on the next boss. This gently hints to them that AOE healing cooldowns can be effectively used on trash pulls, even if only the tank is taking damage.

After these two packs, there is an arrow slide:



This arrow slide is clearly meant to introduce the player to the arrows that the next boss places for Greatest Labyrinth. However, since it is completely straight, the player engages with it in exactly the same way as the water pipe slides in the previous section. This makes it easy for the first-time player to miss the behavior of the arrows, especially if their party members are already familiar with the dungeon and charge ahead. (Even if the whole party is there for the first time, they may well be looking at the treasure coffer or still thinking about the previous trash pull.)

To make this a less missable introduction, I would have the arrow slide take the same amount of time, or at most the amount of time that the physical pipes take, but include some turns without turning the whole hallway. (The exact setup may have to be tuned to avoid motion sickness.) This change would make it clear that the behavior is different from the earlier physical pipes, without requiring the player to already understand the arrows or adding frustrating delays to repeat completions.

One Pack + Miniboss

The second pack after the slide is a single Yok Huy Attestant, standing in this arena:



The veteran player who has leveled many jobs through the Shadowbringers range may well recognize this arena from The Qitana Ravel, and expect similar mechanics, depending on how they leveled. And they would be correct; the mechanics of the Yok Huy Attestant are almost identical to those of the Ronkan Dreamer minibosses there, with the only difference being that here the Sun Toss ground AOE dropped on a random player character is targeted immediately as the statues fire their line AOEs from Ancient Wrath. Such a player already knows how the statues work, and can manage this timing by verifying the statue dodge before that animation begins.

However, the player who only subscribes intermittently, or who is newer and so has not had an extended period of being caught up on the MSQ (or nearly so) to level many jobs while being able to access The Qitana Ravel, may only have seen the Ronkan Dreamers in one dungeon completion - and that two expansions of MSQ ago. They are unlikely to remember the miniboss or the statues, and so must learn how the Yok Huy Attestant works without that reference. Therefore, they must watch the animations of the statue AOEs to check their guess at Ancient Wrath, which pulls their eyes away from the Sun Toss telegraph. While they will probably notice the orange telegraph, the delay in looking at it makes it reactive for them until they stop looking at the statue AOE animations.

As a result, even though neither mechanic is reactive once learned, the player's learning processes for the two mechanics interfere with each other. Even veteran players can be in this situation if they do not often repeat leveling dungeons, or if they level each job to the cap each expansion by directly queueing the highest dungeon that job can access, and so have not seen The Qitana Ravel in two expansions. Or if they simply want to re-check their understanding, since this is a different dungeon and this miniboss is the first strong hint of similarities to Ronkan design.

In high-end duty design, such interference is often an acceptable side effect of forcing the player to manage their attention through rapid mechanical sequences. It is acceptable there because the player is expecting and willing to undertake the process of progression, and so allows for getting their character hit by the next attack in the sequence in order to learn the current one. But this is a regular dungeon, where you have none of that patience from the casual player. They may easily require more than the two casts of Ancient Wrath before Sun Toss is added to learn the former mechanic well enough to be comfortable not looking at its resolution, and then judge this section of the dungeon on the resulting poor first impression. (Especially if they had bad experiences with mechanics in the Patch 7.0 MSQ to get here, and/or are being extra careful after the "gotcha" mechanics of the Barreltender.)

Even if the player does know Ancient Wrath well already, it is still a little satisfying to actually get to see the uptime dodges that stay in melee range / Line of Sight without worrying about Sun Toss. Let the player have those moments.

To make this section still strongly reminiscent of The Qitana Ravel without being exactly the same, I would swap out Sun Toss entirely for a different mechanic on the smooth timing of the older miniboss. The replacement mechanic could be a little harder than in The Qitana Ravel, since the player here is more experienced, this dungeon is not strictly mandatory for MSQ, and Expert Roulette dungeons are repeated more than Leveling Roulette dungeons. For example, the Yok Huy Attestant has the same 3D model structure as Lozatl (the first boss of The Qitana Ravel) complete with the crystals on each shoulder that glow to indicate hitting that side of the arena. Those side cleaves would have fit well here, being simple on their own but combining with the ruined wall segments to present new considerations to the player, and would also be a recognizably Ronkan mechanic in the context of the model and the statues.

Other than the one disappointing timing choice, I do like this section. It is a good way to hint at story through mechanics before spelling it out in the post-dungeon cutscene, and being able to pull the preceding pack into the arena is welcome in Expert Roulette. (Even if the second Ronkan Dreamer in The Qitana Ravel offers a harder pull, with an additional pack and a tighter Item Level sync.)

Third Boss - The Greatest Serpent of Tural



Bouncy Council

The most repeated mechanic of this boss, spawning a set of smaller serpents that each do one ground AOE (simultaneously) and then leave.

(The first cast is exclusively thin front-to-back lines, the second cast is exclusively point-blank circles with one corner open, and all subsequent casts mix the two types. These subsequent sets always have exactly two circle serpents that occupy adjacent corners, and three line serpents occupying the remaining corners and the middle of the arena. Line serpents may only be pointed north-south, east-west, or directly diagonal.)

I appreciate that these serpents have bright white-blue arrows marking the direction they are bouncing in. This is a crisp, high-contrast cue that does not obscure the lore idea of the serpents creating their AOEs by bigger bounces once they have wound up, nor does it rely on glow effects. It provides exactly what the player needs to work out for themselves what form and direction each AOE will take. Excellent work. I would personally prefer that the arrows appear immediately, but they are structured very well.

Unfortunately, the placement of these AOEs relative to the floor tiles is not good. This floor is composed of square tiles carved with geometric patterns courtesy of the Yok Huy, and each corner serpent is precisely centered on a tile - but the width of the line AOEs is slightly larger than the side length of a tile, denying the player precise reference points even for the AOEs that are oriented along the tile grid. (And since the telegraphs showing this appear for less than a second, the player can easily mistake them for exactly the same width as the tiles. If they then use the tile edges mistakenly as reference points and get their character hit, they will likely blame the hit on snapshotting or lag rather than having any inkling of the true cause.) The diagonal and circle AOEs have nothing resembling reference points on the floor, which avoids being misleading but still denies the player the opportunity to precisely dodge. Such reference points could have been made by incorporating their possible edges into the carving patterns.

If these AOEs and the floor were tweaked to provide the appropriate reference points, this could be a really fun mechanic, especially as the final form creates small safespots. There is enough time for the player to see all the serpents and work out roughly where they will hit, which would move up to precise locations with the floor references. So for their effort, the player would be rewarded with the thrill of seeing all the AOEs miss their character despite the small safespots, plus of course the job optimization opportunities as previously discussed. But as it stands, those opportunities are not really available to the player, and having only a rough location for the safespots results in worries about reacting to the telegraphs to adjust their character's position.

Greatest Labyrinth

This mechanic opens by drawing all party members into the exact center of the arena, which is useful in some circumstances. However, since here the player must immediately undertake a visually demanding task, the draw-in is disruptive to their view of the arena and their personal tracking of their character's location.

If the player moves their own character, they will naturally include that movement in tracking their character and their camera movement relative to the arena. This allows them to partly compensate for the camera movement automatically, using many of the same brain systems that have evolved for movement on Earth. Forced movement mechanics do not permit this, and instead force the player to re-establish that tracking once their character is in the new location. (Especially forced movements that give no prior indication to the player, such as this one. Mechanics that ask the player to plan around a forced movement at least prepare them for the disruption, especially if they show the player character's new location such as in Eden's Verse: Iconoclasm (E7N) and its Savage version (E7S).)

This does not make forced movement mechanics inherently bad. Far from it. Forced movement has even been used to spectacular effect in some mechanics, such as opening the levitation mini-phases of The Interphos, or the ending of each Relativity in E12S.

But the effects of forced movement on the player's visual tracking must be considered when placing forced movement mechanics and visually demanding tasks. In this context, where the visually demanding task of working with the arrow placements is the core of the mechanic, having a forced movement immediately beforehand disrupts the task without being interesting or necessary.

To avoid this disruption without compromising the arena transformation, I would use the same technique that Everkeep does in Dawn of an Age: place a clear ground AOE with ample time over the parts of the arena you are going to change, and have that AOE KO (and/or move) any player characters that remain in it at the end of the cast. There is no problem with extending that AOE somewhat further to prevent player characters from stepping over onto a just-formed arrow, nor with the bind while the arena transforms.

After the arena transforms, the player is presented with the red text "You feel a longing to vacate your mortal coil...". I understand that this is meant to alert the first-time and/or casual player to the Greatest Curse debuff, which KOs their character if not cleansed by the correct corner tile. But this is not a good use of the red text.

First, this text is exclusively focused on the consequence for failure, not what the player must do to succeed. Such a focus would be appropriate for some puzzle mechanics, where saying too much about a route to success would spoil the puzzle. But this is not a puzzle mechanic; it is a rapid visual processing mechanic. Second, this text is vague and flowery about the consequence. Even if the player is well familiar with reading their debuff bar and with various consequences for failing mechanics, they still have to mentally translate this before they arrive at "failure results in KO". Again, time is of the essence here. Flowery text can sometimes be useful for lore puzzles, which this is not.

I would change the text to "Navigate the labyrinth to break the curse!" That is straightforward and focused on the route to success, mentioning the debuff only as needed to alert the player to its presence.

So what must the player do to succeed at this mechanic? (In more detail than "navigate the labyrinth".)

To cleanse the debuff and thus avoid the KO, the player must get their character to the single corner tile of the arena marked by a blue circle. The arrow tiles prevent the player from simply moving their character there normally. So the player must look over the arrows - the labyrinth - to find out which directly reachable tile will move their character to the desired corner. (There is only ever one such tile out of the eight tiles adjacent to the unchanged central area.)

Let us break down the steps of this task. In particular, let us break down the most efficient general method that guarantees a solution for the player who understands what the mechanic is but has no knowledge of any hidden patterns.

First, the player must check the corners of the arena until they find the one tile marked by a blue circle, the conceptual endpoint to the labyrinth. (The corner markings are not prominently visible until Greatest Curse has ticked down to 16 seconds remaining, even though it starts at 18 seconds.) This may require them to check all four corners, depending on where they start looking. The first-time player wil likely need to see the circle to know that that tile is the correct one, requiring them to check the corners individually in central vision. (The same is true for the player who has completed the dungeon before but has any form of colorblindness that makes the blue and the purple difficult to distinguish.) The player who has done this before, barring colorblindness as mentioned, can use their peripheral vision to check multiple corners at a time. In either case, they may require a camera turn, as viewing all four corners of the arena with their character in the exact center is only possible with precise camera tilts and angles, and even then uses the very edges of the screen that are often covered in HUD elements. (Ironically, the camera tilt settings that make this possible are the same ones that put Valigarmanda's beak off the screen during its lightning beak animation tell. Further, the range of viable settings and angles that eliminate the camera turn would be larger if the player moved their character on their own to the edge of the unchanged central area.)

Second, the player must work backwards from the endpoint to the central area. They work tile by tile to discover the path, asking and answering the question "how can I get to this tile?" over and over again on the smallest scale. (Those readers familiar with computer science may recognize this method as a breadth-first search.) So they look at the two tiles adjacent to the endpoint, and check each of those for whether its arrow points into the endpoint. Due to a hidden pattern allowing the player to return their character to the center of the arena for melee uptime, exactly one of those tiles will point into the endpoint. (The player does not necessarily know that, but they still benefit from it after checking both adjacent tiles by not having to look for paths to both.) They set the one tile pointing into the endpoint as their intermediate goal, since any path there will lead them to the endpoint.

Then they look from their intermediate goal to the two tiles adjacent to that (not counting the endpoint itself, since they already checked it) and check each of those for whether its arrow points into their intermediate goal. One or both of those will, and they set their intermediate goal to those new tiles. (Yes, eventually there can be multiple tiles pointing into an intermediate goal tile.) Then they look at all the tiles they have not yet checked that are adjacent to their new intermediate goal(s), again looking for arrows pointing in. (Some intermediate goal tiles will eventually have three unchecked adjacent tiles, being not on any edge of the arena.) They repeat this process until they find an intermediate goal tile that is adjacent to the unchanged central area, since they know they can reach that tile by normal character movement.

Finally, they move their character to the intermediate goal tile they can directly reach, and wait for the arrows to transport their character to the endpoint. While travelling the path requires no further input from the player, they must leave time for it to occur before the debuff expires.

(What about working forwards from the directly reachable tiles? Tempting as that is, the player has no guarantee that doing so will not lead them all around the arena checking long and fruitless paths. (Even if there is a further hidden pattern guaranteeing that, the player has no way to find that out without either risking many failures or consulting many videos. Regular dungeon guides are generally made shortly after the duty's release without such in-depth knowledge, and working backwards keeps the player's eyes away from most of the directly reachable tiles. Plus the Patch 7.0 duties leading up to this point have inspired no confidence in the player that your mechanics will be consistently visually reasonable.) And if they put their character on a wrong path, the forced camera motion effectively blurs their screen for the duration, leaving them less time to try again.)

(What about working backwards but considering each new intermediate goal tile as soon as it is identified, rather than continuing to check each adjacent tile to the current intermediate goal tiles? That would guarantee success, and indeed in computer science that would be known as a depth-first search. But that would place greater demands on the player's working memory - to hang on to each not-yet-checked tile for longer and accumulate a larger list - without improving the worst-case scenario.)

This requires a large number of visual checks overall, most of which are checking arrow directions. And the arrows are green on brown, with the green color ranging from dark to lightly glowing in a way totally unrelated to the direction of the arrow. The glow is visual clutter, not an aid to the player. So in order to discern an arrow's direction reliably, the player must not only put that arrow in central vision, but they must also stop their eye movement on that arrow briefly to pick it out from the surrounding brown tile. (Especially if they use postprocessing to cope with the forced bloom from the graphical update!)

(You may find that you can discern an arrow's direction reliably when looking at an adjacent tile, not the arrow itself. But I cannot, and I have a recent clean eye exam including peripheral vision and colorblindness testing, so clearly that capability is not available to all your players. I can only imagine this is worse for players with visual impairments. As such, I will proceed based on checking an arrow's direction in the manner I described in the previous paragraph, since that is a much more realistic assumption of the player.)

And the tiles the player is checking at each step are not adjacent to each other, resulting in short eye movements in many different directions. As a result, the player is forced into a flick-stop-flick-stop repeating eye movement pattern, which can be physically uncomfortable to sustain even without a disability raising the time pressure.

Let us take an example to see how much eye movement this is in a bad case.

Suppose that the player goes through nine goal tiles in the course of their search, including the endpoint but not the directly reachable tile, and that each of them has two adjacent tiles not yet checked. (This is very possible when dealing with a long path and/or multiple intermediate goal tiles in the same step. I am not convinced that it is even the worst case.) Suppose also that the player checks the tiles in the worst reasonable order, so they must perform a camera turn to find the endpoint and must check both adjacent tiles for each goal tile until the last one (where they can reason out to prioritize the directly reachable tile).

The camera turn acts similarly to one eye movement. Then the player - even if they can identify the endpoint in peripheral vision - must move their eyes to one tile adjacent to the endpoint, then the other. The same goes for each of the remaining goal tiles until the last one. So that is one eye movement from the camera turn, plus two each from the first eight goal tiles, plus a final eye movement to check the directly reachable tile. 18 eye movements, each of which requires a brief stop.

Suddenly 16 seconds is not all that long, even setting aside time for the player to reorient, the player to move their character, their character to travel along the arrow path, and client-server latency. In fact, when including those, this mechanic demands almost two eye movements per second to ensure success.

This is an even higher eye movement frequency than Ultimate mechanics such as TOP's Party Synergy (initial clone AOEs) and Predation Dodge, where the player can reduce character movement time with planned Sprint and expects ample practice to improve their visual processing speed. (Notice that Sprint does especially little here, since part of the character's movement time is along the arrow path where movement speed buffs do not help.) Sure, those include some larger eye movements and that does matter, but both repetitive motion and rapid stopping and starting are their own physical burdens.

(Party Synergy method: Check Playstation markers before the clones appear, so you must preposition your eyes for the markers rather than the clones. Ignore the middle clone, locate the side clones (and the eye) roughly by spawn sound and peripheral vision. Look at the arms of the side clone visually nearest after checking Playstation markers; if they are empty, look down to their feet to check whether they have skates or regular feet. (Skates means Superliminal Steel, regular feet + empty hands is the decoy. There is only one decoy.) If you found the decoy first, look at the arms of the next clone nearby. Upon identifying a weapon, regardless of finding the decoy or not, start moving your character to the general area of the two potential safespots while looking towards the opposite side of the arena for the other clone. Again look at the clone's arms; if they are empty and you have not yet found the decoy, check their feet. Identifying the second weapon stops your search.)

(Worst case to start of character movement: 3 eye movements (arms, feet, arms). Worst case to complete solution: 5 eye movements (arms, feet, arms, feet, arms). Your eyes will only have to cross the screen once. Time between clone spawn and AOE snapshot: 5 seconds. This is slightly over one eye movement per second, with some visual clutter from the decoy but less than in Greatest Labyrinth.)

(Predation Dodge method: Look at the arms of one of the first clones to spawn. (There is no decoy here; empty arms always come with skates.) Then look at the arms of the clone opposite it. Preposition character roughly between the two potential safespots and preposition eyes on one of the remaining intercardinals, where the next clone's arms will be. Once that clone spawns and you identify its weapon, look opposite it at the arms of the last clone. Then look at Final Omega until the glow shows for the hourglass cleaves. Move your character to the first safespot, while looking at the first safespot for precise positioning. Preemptively look at the second safespot, again to aid positioning.)

(7 eye movements every time, in 11 seconds between the first clone spawn and the first AOE snapshot, with no visual clutter. Your eyes will only have to cross the screen twice. If you can do Party Synergy, you can almost certainly do this, with some extra time to handle the Final Omega overlap.)

Some players do choose to use more visually demanding methods for TOP than those I have just described, because they prefer to always start with the same gender of clone in identifying each pair of AOEs. But that is an option. When they do that, they are choosing to do a harder eye movement task in exchange for an easier pattern matching task. If they find themselves struggling with the harder eye movement, they can take the easier eye movement task and learn the pattern matching starting from either clone by practice and memorization, which gives them an actionable route to success.

Greatest Labyrinth has no alternate option. (Other than trial-and-error and following fellow party members, both of which are unreliable and not really solving the mechanic.) The player who finds the repetitive flick-stop-flick-stop eye movement physically uncomfortable, injurious, or outright impossible is just stuck with it.

Why is a regular dungeon mechanic more demanding than an Ultimate in raw eye movement frequency and sustaining that frequency, both of which the player cannot change if they find themselves limited?

This is absurd.

To examine the intensity of this visual task in another way: the time that the human body (including brain) takes to initiate a "flick" eye movement varies quite a bit even testing the same person at different times, but a typical time is around 200 milliseconds, or one-fifth of a second. That is not counting any time the player spends deciding where to look depending on what they see. So by asking the player to make almost two eye movements a second, you are asking them to spend on average almost 40% of the search time literally waiting for their eyes to get moving. Again, this is absurd.

(Some readers may be aware that in some circumstances, such as examining a face, humans regularly make multiple eye movements per second. Presumably that is not mired in delays because the task of looking at a face allows the human brain to plan several movements ahead to look at different facial features - a sort of planning Greatest Labyrinth permits very little of, Party Synergy permits somewhat, and the Predation Dodge completely supports once the first clones appear. And the tasks where such frequent eye movements are common also do not have such hard stops, hence why we regularly miss details such as accidentally repeated words when reading. I can tell you that I find reading much more comfortable than Greatest Labyrinth, despite working far faster to read at my natural speed.)

The only reasons this demand did not create an obvious disaster are that the player can notice their party members' attempts in peripheral vision, and that party KOs do not lose particularly much time on regular dungeon bosses.

Extending the time limit could improve the situation, especially given the hidden pattern. (The hidden pattern is well-designed, allowing faster players to optimize for job uptime without having to worry about estimating the time taken to travel the correct arrow path.) That is why Deltascape V3.0 (O3N, Halicarnassus) does not suffer the same way from its own visual labyrinth, despite relatively low contrast; even if the player cannot use the motion of the tiles to find the tile directions in peripheral vision, they have far longer to search and several still tiles to work towards along the way. It asks the player to do several small searches, which limit the length of the worst-case scenario, with a generous timer.

But I think there is a more elegant solution here: make the glow help the player visually, as would be expected from such a mechanic.

Each arrow is already composed of one large triangle as its head, two chevrons pointing towards the head, and a tiny triangle filling in the middle. I would make the head triangle glow clearly regardless of bloom, and have the rest of each arrow in a single non-glowing medium green. (Including on the arrow slide earlier in the dungeon.) The idea is that when the player is looking at the endpoint or an intermediate goal tile in their central vision, they would reliably be able to see the glow of any adjacent arrows pointing towards it in their not-quite-central vision, clearly differentiated from those pointing in other directions. Making this reliable eliminates the need to look directly at adjacent tiles that do not become intermediate goal tiles. This would cut the required eye movements almost in half and make the directions of motion much smoother, thus making the visual demand far more manageable without changing the idea or the complexity of the visual labyrinth.

The faster the player needs to see and process a visual indicator, the clearer it has to be. The necessary standard here is much higher than it is in O3N because the player must work faster.

Moist Summoning

This would be a simple multi-hit stack, except that each hit leaves a puddle from the serpent add that hits the stack area. As a result, not only does the first-time player have to react to the presence of the puddle, but every time the player must react to their party members' choices of where to move out of the puddle.

While this need to react to fellow players is not a disaster, it introduces just enough of a delay that each puddle's time to activation is annoyingly short. This would be a less reactive mechanic if it overlapped with something that suggested a movement direction to the party, such as a rotating cone AOE, despite the overlap technically making the mechanic harder.

Greatest Flood

A simple knockback from a corner tile, specifically (relative to the center of the arena) slightly further out than the closest corner. This is only complicated by the puddles from Moist Summoning persisting.

A fine mechanic; the puddles present a consideration to the player without being too difficult, and the player can use their knockback immunity for uptime or dealing with bad puddle placement.

Great Torrent

Hey, an actually fun mechanic! The player has the time with the telegraphs to precisely position outside the first AOE in the sequence, and enough time to spread after the sequence completes.

Overall Impression (Boss)

This boss has a perfect reason built in for excellent floor geometry and the mechanics to match, but it does not actually give us the floor geometry that would enable precise dodging. Greatest Labyrinth is also a low point, since it leaves some players with no actionable route to success.

Overall Impression (Dungeon)

The trash mobs are interesting but not too difficult almost across the board, but every single boss has serious visual design issues.

The fact that visual design plagues every single boss in this dungeon, not just one mechanic or even one boss, makes it feel like this is a test of whether lowering visual clarity makes for fun difficulty. Whether or not you intended it as such a test, I will give the answer: no, and that is not something the vast majority of players would give you useful feedback on regardless.

The average Ultimate raider does not consciously think about what sorts of capabilities a mechanic requires, nor how they move their eyes to do a mechanic. Any given casual player is even less likely to think about such things. If they struggle with a mechanic because you obscured the needed visual indicators and references, outside of obvious cases like "this duty is orange on orange" they will generally not perceive that their issue is with a lack of visual clarity.

They may instead notice only that they keep failing the mechanic without any improvement past a certain point, and simply say "this is too hard" on that basis. They may completely miss a core part of the visual indicator, as with the cacti created by Barreltender, and base their assessment on a mistaken idea of what the designer intended. They may notice that they are unable to get all the information they need in time and deem the mechanic or duty "unfair", especially since Barreltender shows a willingness to be unfair from the beginning of the dungeon. They may find themselves delayed in discerning the needed information, correctly perceive that their time to make a decision with that information was very short, but declare the mechanic "reactive" since they do not consciously perceive that the delay came from obscured visuals rather than no visuals. Or they may simply not like it but be unable to pin down why.

All this gets drowned out not only by the angry back-and-forth over "is Dawntrail too hard?", but also by things that are easier to complain about. It is within the reach of the average casual player to identify the Strayborough dolls as annoying, so you get lots of complaints about them. It is not anywhere near the reach of the average casual player - in effort or knowledge - to explain how your visual design choices affect their visual processing of mechanics, the way that I have done here.

Meanwhile, the player who can handle the obscured visuals is totally unaffected. The mechanic is not any more exciting for them, because the mechanic underneath is the same. The arena and animations do not fit the lore and story any better, because an immense variety of lore concepts can be presented with clear visuals for needed mechanical indicators. I described how I would change the visual design of this dungeon to demonstrate that lore fit and visual clarity are not mutually exclusive. And of course, visual elements that are not relevant to mechanics can be as subtle as the artist and/or lore writer desires.

It is exactly as I wrote in the design principles section of this review: making needed visual indicators difficult to see is anti-fun.

I have taken the time to give this detailed breakdown because I want you to adopt - and follow - visual clarity and accessibility standards that suit the real-time nature of this game. No more orange on orange, as players told you about Eden's Verse: Furor (E6N, Ifrit and Garuda), Asphodelos: The Third Circle (P3N, Phoinix), and their Savage versions (E6S and P3S). Those were two raid tiers apart, you had the time to act on the feedback from Eden's Verse in your production pipeline for Asphodelos. No more indicators that require color vision or are heavily obscured without it. And nothing the player needs to see should ever wind up as a blurry heap!

Build visual clarity and accessibility standards into your design process. Make them reflect the requirements of the mechanics that use each visual element. Seriously.

--------

The Strayborough Deadwalk (Level 100 Dungeon)



Mobs Before First Boss

Four Packs

Nothing mechanically interesting here, but can be double pulled.

First Boss - His Royal Headness Leonogg I



Falling Nightmare

Introduces part of the dolls' punishment for failure by putting the falling heads over each player character, but with the opportunity to dodge since the player character has not been bound by a doll. This would be a good introduction, except that the heads have barely any contrast with the floor and the dolls are awful to deal with.

(The heads inflict 10 seconds of the Benoggined debuff, which has a "ha ha you messed up" visual as well as being equivalent to Out of the Action combined with Heavy.)

The heads do have green sections with more contrast, but the player cannot readily learn to use those sections, since their 2D shapes on the screen vary greatly depending on the boss's choice of the head's facing relative to the player's camera.

Team Spirit

A brief warning cast for the dolls lining up around the edge of the arena, preparing to march. In itself, this is a good thing.

Spirited Charge

Has the dolls begin marching across the arena.

Since these particular dolls are one of the most complained-about mechanics of Patch 7.0, let us go over them in detail. Why are these so annoying, when players have previously enjoyed moving object mechanics such as the brooms in The Grand Cosmos?

First, note that the dolls march quite fast, even faster than Honey B. Lovely's moving hearts. Their speed feels comparable to the bullet hell bubbles created by Feather Ray in The Skydeep Cenote. So just like those bubbles, the player's screen tells them that they got hit by a doll while also showing positions that would have resulted in a successful dodge if those positions were accurate. The resulting "I was out of that!" is all the more unpleasant when encountering the dolls over and over again in Expert Roulette.

Second, the time available after the dolls line up is not enough to check all of the dolls' starting positions. There are only four seconds between when the dolls first stand still in their starting positions on the player's screen and when the dolls begin moving visually, which means even less time between when the player first has the opportunity to see the dolls' starting positions and when the dolls have actually started moving on the server. This is not remotely enough to check what seems to be 16 dolls, arranged in roughly a square with four to each side. (And the player needs to see all the dolls, not just those aimed to march near their character or a single potential safe spot, due to the overlapping mechanics.) To make matters worse, the arena is a circle whose markings do not correspond to any "lanes" for the dolls, making it more difficult to visually trace their future paths. And since the dolls are relatively densely packed, the player needs precise positions to locate safe areas, which they must obtain from central vision.

Third, the starting positions are not sufficient on their own to know the dolls' entire paths, nor the timing of the dolls traversing those paths. Different groups within the square of dolls start moving at different times, which are completely unmarked other than by watching the dolls move. (Even if the order is static, the player would have to spend a long time watching the dolls - without worrying about their job or dodging - to find that out. I think it is a static order, with the east group always moving first.) And when a doll reaches roughly the edge of the arena (perhaps an edge of the hidden square) after marching from the line-up in Team Spirit, it aims at a party member's position (seemingly at random) and marches a second time in that direction. (In one section of the battle, the dolls even repeat this process of picking targets and marching multiple times, as the boss is too busy casting other mechanics to present another Team Spirit or Spirited Charge.) As a result, even in theory, the player does not have enough information to know the dolls' paths and timings until after each doll has not only turned around, but moved far enough to show which player character it targeted / direction it chose for its final march. They could try to determine the dolls' aim from facing, but seeing each doll's precise facing requires central vision and they cannot put every doll in a group in their central vision at once. (Again, the doll heads have barely any contrast with the floor, and the doll dresses are not much better.)

Fourth, the player does not have just the dolls to deal with. Even the first Spirited Charge has another mechanic begin resolving before the dolls finish their march. Naturally, this places greater demands on the player in every aspect of mechanic handling, as they are contending with more than one mechanic simultaneously. On top of that, the nature of the overlapping mechanics blocks the most comfortable way of dealing with the dolls.

The preferred strategy for the dolls alone would be to stand still in the center of the arena while as many dolls as possible pick their targets for their second march, then move out of the center between two dolls' paths. (The center of the arena maximizes the minimum distance between the player character and any point from which a doll might target them, thus providing the longest guaranteed lead time for the player between a doll's choice of target and needing to move their character or fail the mechanic.) But this strategy will fail every single one of the overlapping mechanics. Technically, the Looming Nightmare chasing AOEs allow the half of the party whose characters are not targeted by those AOEs to adopt this strategy, but that is not sufficient to reliably cover every player who would want to use it. Pushing some but not all players into a task they find unpleasant is still bad game design.

Fifth, this is a reactive mechanic. The player does not strictly need to react to their fellow players' choices, only to the dolls' paths, but they have very little time to react to the dolls' paths considering what information they practically have and when they receive it.

Even to check the safety of a single spot for the dolls' first march, the player must check all four sides of the hidden square for the precise positions of dolls that would pass by, involving at least eight dolls due to the tight spacing. Setting aside the question of the player's visual path tracing capability, that is eight eye movements just to get those dolls' locations in central vision, so doing that before the dolls begin moving requires at least two eye movements a second with stops on each doll. That speed is even higher and more burdensome than Greatest Labyrinth in Tender Valley, which was already a serious problem, making the only realistic assumption that the player cannot do it.

Instead, the player checks only some of the sides of the hidden square before the dolls begin moving. (For example, the most comfortable way to do this is to pick a corner of the hidden square and move one's character towards it while looking at it, refining the precise choice of position so that the nearby dolls pass by one's character. All the dolls that pose immediate threats are visually close to each other, their closeness to the potential safespots allows the player to look at spaces between dolls, the player need not look elsewhere to place their character in their chosen safespot, and a corner grants the longest time before the dolls on non-adjacent sides reach the vicinity.) But this means that the player must check the other sides of the square while the dolls are already moving on their screen.

A doll visually crosses the arena in about seven seconds, which sounds like a lot of time. But the player has less time than that to complete their character's movement, both because the true server position of the dolls is ahead of their client display and because putting their character in the edge of the arena is a mechanic failure of its own. (A less punishing mechanic failure than being caught by a doll, as the wall inflicts a DOT rather than the usual instant KO, but still a failure.) Moving their character takes time of its own, as does the decision-making aspect of reacting to the remaining dolls' paths. Their character's movement takes time to reach and be processed by the server. If they are playing a melee DPS (or a tank with a melee DPS in the party), they will be disinclined to move their character to a corner. Even if they picked a corner, they may well have picked the corner beside the dolls that start last, not first - remember, even if there are hidden patterns, the first-time player does not know that. (And the last dolls start about 2.5 seconds after the first dolls, so that in itself would buy testers who knew a hidden pattern quite a bit of extra time.) The player can look at the first dolls far away from their character while waiting for the last dolls near their character to move... but during their first time, they do not know when the dolls near their character will start moving, and they need that information to know when they can safely move their character for later dolls and overlapping mechanics. (Likewise, they need to know if the doll hitboxes are bigger than the visual models.) So they will likely look at their character or the nearby dolls instead, making the time pressure even worse until they know the timing well enough to stop doing that.

Let us generously not assume the worst case, the first-time player who has been trained by their job to stay in melee range. Instead let us consider the player who is confident that their chosen initial character position in a corner will evade the dolls that start nearby, and so moves smoothly to looking for the dolls from the far sides that will eventually be near that initial position.

Let us say that those dolls will reach their chosen initial character position in six seconds from the start of the dolls' motion, since it is close to the edge of the arena but not quite there. Take out half a second for the client-server round trip and all of the latency internal to the player's client and the server. Say they have to hold down their movement key / joystick / mouse buttons for a quarter of a second to get the movement distance they eventually decide on, and leave another quarter of a second for their raw, physiological, non-decision-making reaction time. So they have five seconds to get all the visual information they need and make their decision on where to move.

They have four dolls left to check from the two sides they were forced to skip earlier, in two groups that are almost across the arena from each other. They must locate each of those dolls precisely to determine its path precisely, or else risk having to look again later on to update their path prediction. Since the dolls are already in motion, they do not naturally know exactly where to look, and have to get that from their peripheral vision. Oh, and there is another overlapping mechanic starting during this time, the details of which will inform their decision even if they know the battle timeline completely. Since the vast majority of players never attain perfect timeline knowledge of Expert Roulette dungeons, and even for those who do their earlier experiences are important, we must take it that they do not have that timeline knowledge. So allot at least two eye movements for the overlapping mechanic: one to the castbar for a general idea of when the mechanic will begin, and one for either the cast name or an arena tell that draws their eye. That makes for six eye movements before the player can make their decision.

Suppose that the player can make 1.5 eye movements a second, including the two larger movements to the other group of dolls and then to the castbar, while stopping on each object for long enough to draw the needed information from it. (Recall from my analysis of Greatest Labyrinth that this speed is comfortably above the requirements of Ultimate.) This would allow them to complete the six eye movements in four seconds, leaving them one second to make their decision on where to move their character. That is tight for a mechanical overlap, and will draw heavily on the player's previously learned tactics for general dodging, but it is manageable. Indeed, this case is how I handle the first part of this mechanic.

But that is not the worst case.

If the player is here for their first-time completion and looking around their character for when the nearby dolls pass by, that can easily consume the entire second of decision-making time. They are then forced to either try less reliable methods (such as looking for spaces between the moving dolls or tracking them in peripheral vision) for the sake of speed, knowingly work off of insufficient information, or not even notice some component of the ongoing mechanics and get caught out by it. If the player does not choose to start with their character near a corner, and instead tries to work in the middle of the arena for melee uptime, that more than consumes the entire second of decision-making time, leaving them the same set of options as the first-time player. If the player reflexively looks at the overlapping mechanic when it is presented, that may throw off their entire plan for checking the dolls.

And that is just for the first march. The later marches are worse.

Since the overlapping mechanic will be failed by the player keeping their character in the center of the arena for the doll baits, to succeed at the combination the player must have their character at least moderately close to the edge of the arena during that period. Because the dolls' turning points are fairly evenly spaced along the edge of the arena, this guarantees that some of the dolls will be near the player's character when they choose player characters to target. And the closer the player's character is to the center, buying them time to check the closest dolls, the less time they have for the furthest dolls.

But for the later marches, we do not need to consider many cases on how far the player character is from the center of the arena and how the player distributes their eye movements accordingly. To succeed they must check all 16 dolls, and to look at each doll individually with the necessary stops at 1.5 eye movements a second would take 10 and two-thirds seconds - long enough for all of the dolls to more than cross the arena. Regardless of the player's chosen order, it is not a realistic expectation for them to get detailed path information on all the dolls.

So the player is forced into tracking the broad movements of the dolls using the motion sensitivity of their peripheral vision, only looking directly at dolls that they think will come close to a specific spot they care about, usually their character's feet. (This is a natural strategy for bullet hell games / levels that do not provide strong patterns for the player to plan around.) In turn, this means that they select a doll to look at only after either it has moved far enough from its turning point for them to pick up its motion towards their chosen spot in their peripheral vision, or it has moved close enough to where they are looking that they see it specifically in their not-quite-central vision. The former case is reactive enough, since that means the doll has already covered a substantial part of the distance towards the player's chosen spot, but the density of the dolls in the arena prevents the player from reliably selecting a safespot based purely on their peripheral vision. They must either wait for the latter case or move their eyes away from their chosen spot to look directly at the doll.

If the player continues looking at their character's feet and waits for the doll to enter their not-quite-central vision, they do not have enough time to decide where to move their character on that basis - remember, each doll is visually behind its true server position. All of the components of a successful dodge that I described for the first march still apply, with much less time and the other dolls demoted to peripheral tracking. If the player looks at the doll before that, they give themselves enough time to make a decision regarding that doll, at the expense of looking away from their character's feet and potentially missing another doll entirely in that time.

Oh, and some part of the arena will be visually blocked by the boss itself. And the player has to handle the overlapping mechanic at the same time, which is a further visual and decision-making task.

The dolls really are reactive. There is not enough time for the player to get the visual information they need and make their decision without pressuring their reaction time, if they get that information at all. Break down the time taken for each part of a mechanic before you lock in the design, let alone release it, so that you discover these things in the design stage when you can fix them easily. Err on the side of breaking down even things that seem very similar to but not exactly the same as existing mechanics. Have a testing art library with varying levels of contrast and visual clarity, so you can have early internal playtests that flag where major changes are needed.

Sixth, the falling head dropped one player character being hit by a doll can also hit other nearby player characters. So not only does the player have to keep track of the dolls and the overlapping mechanic to reliably succeed, but they also have to keep track of any nearby player characters or the falling heads generated by other players' mechanic failures. Not only is this a further visual burden, but the falling heads blur into invisibility against the arena floor under the visual burden of tracking the dolls. So the player gets unfairly penalized by a falling head they did not see coming from a doll their character did not get hit by.

In The Copied Factory, the pink orbs also explode onto all nearby player characters when touched, but at least the player has the chance to see them coming and stay far away from all the orbs. (Which is visually easier than tracking all player characters near each nearby orb.) And even there, it is still annoying to successfully make a close dodge for uptime reasons and be penalized by someone else exploding the orb.

Seventh, the penalty for the player's character getting hit by a doll is particularly attention-getting and unpleasant, disrupting the player's participation in the battle. The initial bind forces the player to watch as their character receives further damage and Benoggined, then the Out of the Action and Heavy restrictions prevent them from doing anything but slowed character movement for 10 seconds, and on top of that they are shamed with a doll head and potentially battle dialogue. (And remember, the player can wind up with the latter two penalties even if their character avoided all the dolls!) The Vulnerability Up may last longer, but it is not the annoying part of the penalty even for the healer.

If this mechanic were reliably doable, the sharp penalty would be fine. One-hit KOs are similarly disruptive, and have been used without issue in regular duties for relatively easy mechanics. (Along with their use in high-end duties, gradually rising from the moderately easy mechanics to just about any mechanic as the duty difficulty increases.) But because the mechanic is not reliably doable, such a harsh penalty adds to the annoyance of it. You would have gotten a fair amount of complaint even about The Copied Factory's orbs if their penalty was this harsh.

Eighth, the nature of this penalty easily cascades into further mechanical failures and difficulties for the party. The bind often results in the player's character getting hit by the overlapping mechanic, taking further damage and Vulnerability Up stacks even if they are not KOed. The Heavy from Benoggined makes it more difficult to dodge further hits. And the player cannot help their party members with mitigation, healing, and/or raises while their character is Benoggined, denying them the opportunity to help a struggling fellow player.

(Yes, Benoggined does not stack, but that does not really mitigate the cascading nature of the penalty - one-hit KOs would result in later dolls running right over the player character too.)

Ninth, the nature of the penalty makes the battle drag on, since Benoggined directly prevents the player character from damaging the boss and cascading failures can indirectly reduce the party's damage output. As a result, the more the player struggles with this mechanic, the longer the battle will take for them on average, and the longer they will have to deal with the annoyance. Further, this encourages their party members to become annoyed with them for extending the battle, which causes social friction over the player's physical limits they can do nothing about.

Salvaging this mechanic would require solving all these problems, which in turn would require a complete redesign of the dolls and the whole boss, as the doll marches are the core mechanic of this boss as the doll king. As I have little to go on for what the design intention of this mechanic is, I will instead compare to existing moving object mechanics that function well, and remark upon why they do so.

In The Grand Cosmos, the five brooms move slowly, making the player's screen relatively accurate to their actual positions. They are large with moderate contrast, combined with tiles providing light lane markings on the arena floor, allowing the player to use peripheral vision to locate each one and match it to its lane. (The arena is exactly 20 tiles deep, divided into five lanes. And since the brooms also alternate, the player can count the number of brooms to a side once they notice that. Indeed, the brooms remain on the enmity list for the entire battle, reinforcing their permanence.) The player is given ample time to see both the brooms and the dirt puddles (which cause brooms passing over them to pause and sweep up) before the broom movement begins, which is all the information the player needs to know the brooms' paths and timing. The player can react if they so choose, but they have the opportunity to plan - if they get caught by surprise, it is a fair surprise arising from their lack of planning, and they can change that next time. (Indeed, working out uptime strategies around the brooms' movement serves as an enjoyable opportunity for skill expression. The whole arena is covered each time the brooms move, so the player must move their character to succeed, but can plan around when to do so.) Overlapping mechanics do not create unreasonable combined visual demands. And while the penalty for failing a broom is an attention-getting sweep, it is brief and allows the player to continue fully participating in the battle. That is a fun mechanic that held up to the repetition of Expert Roulette while being gentle enough for a dungeon required by MSQ.

In all iterations of The Jade Stoa - Normal, Extreme, and now Unreal - Byakko uses Unrelenting Anguish, where he stands in the middle of the arena and emits moving orbs from himself. There are no lanes on the floor or permanent brooms to aid the player, and the orbs move at a moderate speed. But his orbs are in a fixed spiral pattern with widely spaced arms, even using two arms rather than three in the first phase of the Normal to gently introduce the mechanic. Combined with the high contrast of the orbs against the floor, this allows the player to dodge entirely by peripheral vision in the wide-open spaces if they please, which is the melee uptime strategy. For casting uptime, the player may instead keep their character near the edge of the arena, buying them time to look directly at only the oncoming spiral arm and identify a gap to slidecast their character into. Both strategies are fun and remain visually reasonable when combined with overlapping mechanics. And again, the penalty for failure is just damage and a Vulnerability Up stack.

I notice that both these successful examples only require the player to find a moving object's position to know its path, without use of the moving object's facing. Having to look carefully at an object for facing or path information adds a lot to the visual demand. I expect this is why bullet hell games favor high-contrast bullets whose facing is clear from their shape alone, which the dolls are distinctly not, to allow the player to rapidly combine the rough shape with the rough motion in their peripheral vision.

Evil Scheme

A standard "flower" of exaflares from the center of the arena, having all cardinals start before all intercardinals or vice versa. Has been a fine mechanic in other places, but here it is combined with dolls, and that makes it just another annoyance to the player.

Looming Nightmare

Another standard mechanic, chasing AOEs.

These are particularly annoying in combination with the dolls, for three reasons. First, the requirement to keep moving makes it more difficult to visually check for dolls, as the player must check around a path rather than a single spot. Second, the natural way to do this without the AOEs getting in the party's way is to work at the edge of the arena, putting the player's character very close to doll turning points. Third, if the player's character does get hit by a doll, the chasing AOE will catch up during the bind and hit them repeatedly.

Scream

Another standard mechanic, a cone AOE sequence that covers the whole floor in three groups of two cones each. This is the simplest of the mechanics overlapping with the dolls, and is once again ruined by the presence of the dolls. This also starts the sequence of many doll marches from a single Spirited Charge.

Falling Nightmare (Repeat)

This is almost the same mechanic as before, with two rounds and some extra heads randomly placed each round. If the heads had good contrast, the mechanic would be okay but not good for casting planning.

But it comes with the battle dialogue "Apologies for breaking character, but... perhaps it's time you stopped resisting? There are limits to my patience." If the mechanics were enjoyable, this dialogue would be funny. Since at this point the player's patience has been tested repeatedly by the dolls, it is grating.

Overall Impression (Boss)

The use of the dolls is a reactive disaster, and all the other mechanics do not express the lore concept of the doll king. Having a boss express its concept via a complication to otherwise standard mechanics is fine, but the whole combination needs to be reasonable; here, the dolls are not reasonable alone.

Mobs Between First and Second Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

Two More Packs

Between these packs, there is a Ferris wheel that falls as the party passes by:



Specifically, it falls shortly after the first time a player character gets close enough to it, with just slightly more than enough time for that player character to run by if they have Sprint active.

To the first-time player, this is a minor "gotcha", as they have no real reason to look to the side of the path while focused on the upcoming mobs, and so most likely will not notice the Ferris wheel's presence until the briefly flashed telegraph at the end.

And then once the player knows about this AOE, they are faced with a choice: try to keep their character at the front of the party's charge to get ahead of the Ferris wheel, deliberately wait until it falls, or take the hit on purpose. None of these options are good. Trying to get ahead of the Ferris wheel involves judging the party's relative positions, for which the client-server round trip making the player's screen inaccurate is highly relevant. Waiting draws the player out of the battle, both from the waiting time itself and the delay in their character reaching whichever party members charged ahead. And taking the hit on purpose just feels bad.

Environment features affecting trash pulls can be fun and interesting, but this implementation is not.

Suppose instead that the spinning Ferris wheel was behind the last pack of this section, and slowly destabilized with a sound effect during the party fighting the mobs. Both of these would encourage the player to see the Ferris wheel well before its AOE. And then rather than the AOE covering the whole area, it would leave safespots between the spokes, shown by a rotating telegraph that slowed down as the Ferris wheel slowed and fell over. (This is physically accurate as well; gyroscopes are more stable when they spin faster.) That way, the player would be presented with a combination between the mobs' basic AOEs and the environment feature AOE, which is not too difficult but would help make the pull interesting.

Second Boss - Jack-in-the-Pot



Troubling Teacups

Sets up teacups around the arena and ghosts entering them to create large point-blank AOEs. The ghosts' targets are nice and clear, since they each tether to their chosen teacup and add white smoke to the teacup's purple smoke while tethered.

(The first cast has only the outer ring of teacups and one ghost. Subsequent casts have two rings of teapots and two ghosts. All rings have four evenly spaced teacups.)

This is an example of a good setup cast that does not have to resort to active glowing. The tethers are effective despite the multicolored arena floor, and the white smoke contrasts the purple smoke.

Tea Awhirl

Starts the teacups spinning around the arena, with the AOEs coming shortly after the teacups stop. (If two rings of teacups are present, this includes the rings swapping with each other.) Since the ghosts are now concealed in the purple smoke filling the teacups, this is a visual tracking mechanic where the player must track the teacups' movement. When dealing with multiple ghosts, there is also a memory component, remembering the shape of the combined AOE relative to the teacup / point the player chooses to visually track.

In purely angular motion, all the teacups rotate at the same speed, and they all swap in/out the same number of times. These facts are apparent from watching the teacups in peripheral vision a few times while keeping one teacup or one fixed location in central vision, which are the natural tactics for the first-time player. In turn, knowing these facts confirms for the player that either of those visual methods yields an effective solution. They can follow one teacup around the arena and remember the combined AOE shape relative to that, or they can watch one point in the arena to count the teacups that pass through it and the ring swaps. I appreciate this flexibility.

I can do this mechanic just fine, but I do not like the pulses of smoke over the arena as the teacups start spinning. They are not fun or interesting - in fact, I did not really notice them until I looked at videos for this review - and instead feel like part of a neurological test, purely a means to add stress to the player's visual processing. (There is a reason that you use similar techniques to make arena transformations less jarring to the player.) Neurological tests do not generally make good gameplay.

I also wonder if the relatively even spin of the teacups could induce motion sickness in some players. I do not get motion sick from these, but I would not be surprised if other players did. In contrast, the jumping dogs in Eden's Promise: Litany (E10N) and its Savage version (E10S) make it very clear from the animations and the individual jumps that they are moving, not the arena floor.

Other than those two things, this mechanic is fine. Which is good, since it is repeated very often by this boss.

Toiling Teapots

A sequence of expanding circular AOE puddles, themed as teapots filling static cups to overflowing and leaving tea behind. The relative slowness makes the puddles work, since dodging back into the first AOEs results in taking the puddle DOT.

This is also a good choice of mechanic to express the lore concept of the boss.

Overall Impression (Boss)

Nothing special, but it is okay. Just take out the masking smoke pulses.

Mobs Between Second and Third Boss

Two Packs

Nothing mechanically interesting here, but can be double pulled.

Two More Packs, with Large Dolls

This is an interesting double pull, as the two large dolls that form the last pack perform light staggered raidwides on top of the usual amount of basic AOEs. This gently encourages the player to consider their mitigation tools, AOE healing tools, and potentially even strategies such as "kill one doll first to halve the raidwides".

I would not go harsher than this in regular dungeons, since fairly weak healers do have to be able to complete the duty at minimum Item Level without drawing ire from their party members.

Third Boss - Traumerei



Bitter Regret

Hits either the middle or the sides of the arena, with a crisp glowing animation tell in Hades's style. Simple on its own, but comes back in sequences later. The edges match lines on the floor nicely for casting optimization.

Poltergeist

A short pure warning cast for the poltergeist tether setup, good to cue the player to prepare for something. Only appears before the first Memorial March.

Memorial March (Walls + Poltergeists)

Places walls in the arena that can be passed through in ghost form. The poltergeists choose their positions, one to each player character and close to an edge of the arena, and appear as the second wall begins to visually drop. The narrow AOEs with clear telegraphs function effectively to nudge the player character definitively into a quadrant of the arena, to make use of the ghost form necessary.

After the poltergeists appear, they begin casting their proximity tether blasts. Even if the player has not picked up on the battle dialogue, they will quickly realize that the walls do not allow them to move their character far enough to stretch the tether by normal means. This is perfect timing for the activation of the ghost/flesh platforms and the (correct) blue text "A section of the floor begins to glow!" The player may not get it right the first time, as going to one of the platforms after this realization leaves them not much time to double back through and well past a wall, but they are pushed towards the information to figure out how to succeed.

(Nice touch that this text is blue rather than red, since it talks about an aid to the player character rather than a warning of danger. Of course you cannot rely on the player seeing the color difference, but they do not need to here so it is just nice.)

This is also the sort of mechanic where one player doing it correctly automatically demonstrates the solution to their party members, which helps the first-time player catch on even though the necessary information is not where they would look when running their character away normally. Such situations allow you to have slightly counterintuitive mechanics in regular duties, though not full puzzles.

It is good that the tethers do not do terribly much damage if not sufficiently stretched, using only moderately increased damage and a Vulnerability Up stack to indicate failure. This ensures that the first-time player does not feel discouraged by the likely failure or two when first learning the mechanic, and allows the later overlaps and combinations to not be too punishing as a whole.

Ghostduster / Fleshbuster

Visually these are spread AOEs, but the cast names and the red texts show that spreading has nothing to do with it. (The texts are "Traumerei prepares a ward against spirits!" and "Traumerei prepares a ward against the living!" respectively. They appear every time.)

If the player character is in the opposite form at the end of the cast, they take no damage at all, complete with the "DODGE" flying text, green checkmark over their head, and "ding" sound effect for the player. If the player character is in the same form at the end of the cast, they are immediately KOed, complete with the "9999999" (true damage) flying text, red X over their head, and another "ding" sound effect for the player. This is a good use of your feedback tools to help the player learn the mechanic, as both possible outcomes are relatively extreme compared to most other mechanics.

(The first of these is always Ghostduster, to teach the player that ghost form is not always preferred. Eventually they randomize.)

The length of the casts is suitably long, allowing the player to move their character to a transformation platform even if their initial position is bad. This is important given the harsh penalty for failure, and done correctly.

The one thing I would change about this mechanic is to use the generic "targeted for something" marker instead of a spread marker. Spreading is not at all relevant to the mechanic - the whole party can stack up and take no damage - and the generic targeting marker is plenty obvious considering its recurring form and its own sound effect.

Memorial March (AOE Sequence)

The boss spawns two sets of ghosts at the front of the arena, both tethered, with the rows alternating between sets. These create line AOEs that resolve in the same order while the boss is casting Bitter Regret. Showing the tethers and giving the player time to see the ghosts during this cast is what makes the sequence work, since it allows them to be looking at the Bitter Regret animation tell instead of the ghost AOEs as they resolve.

Memorial March (Combination)

Combines the walls and poltergeists with something else. Can be a set of ghosts at the front that will hit two of the quadrants at the same time as the proximity tethers, can be Bitter Regret, can be Ghostduster / Fleshbuster. Once the player understands using the ghost form, all of these are manageable and offer different optimization opportunities. (For example, with the ghosts hitting two quadrants, the player can keep their character in melee range and succeed at the combination by starting their character in front of the ghosts, so that their poltergeist spawns near the ghosts and they can run their character away from both.) This is very welcome.

The pace would be fast if not for introducing each element individually first, but it works since they are introduced that way.

Ghostcrusher

A line stack while the walls are up, which encourages the party to run into the walls to stack. This works, which is good. Oddly given the name, it does not penalize characters in ghost form, but the length of the cast is not long enough to do that without being annoying.

Overall Impression (Boss)

A fun boss that could easily have been in a Stormblood or Shadowbringers dungeon. The opportunity to strategize around the ghost/flesh transformation is very welcome in Expert Roulette.

Overall Impression (Dungeon)

The dolls ruin this dungeon. This is the prime example of "it only takes one bad mechanic to ruin a duty", as there really is only one bad mechanic in here - but the one mechanic is so bad that even young and able-bodied players get annoyed by it easily.

----------------

Both of your "experimental" dungeons are plagued by unworkable visual demands. Please for the sweet love of Hydaelyn, adopt and follow visual clarity and accessibility standards that account for the time pressure of mechanics.

[Aurelle_Deresnels]

I will now continue my review of the design of the Patch 7.0 duties, in this subsection covering the Arcadion Light-heavyweight Normal Raids.

The same considerations apply here as for the optional Expert Roulette dungeons in the previous subsection. These are still endgame duties that must welcome the casual player. They should be a touch harder, which works out because the party is guaranteed to have at least two members who can raise, but the biggest difference design-wise is that the longer time with a single boss allows for building up a concept over more mechanics.

----------------

AAC Light-heavyweight M1 (M1N, Black Cat Normal)



Before getting into specific mechanics, this is a very well-patterned floor. There are major grid marks that get used later even in Normal, minor grid marks, and diamonds in the center of each floor section.

The only tweak I would make is turning the brightness down slightly, and not even because of the floor itself - because waymarks and the Savage clone tethers are forced to be very bright by the floor brightness, and that makes them uncomfortable to look at for the extended periods that come from progression and less-than-ideal weekly reclear parties. (Sometimes even after changing hardware settings. My monitor is at 0% brightness already. Only this duty and its Savage have this issue out of every duty in Patch 7.0, so it is clearly brighter than the rest of the game.)

Since it is easier as a developer to make one visual asset and reuse it in both the regular and high-end versions of a duty than to make two, and it is more welcoming and immersive as a player to see familiar visuals from the regular version when learning the high-end version, in cases like this it makes more sense for me to comment on the Normal version about changes that are for the Savage version.

Bloody Scratch

First used as a simple opening raidwide, unlike in the Savage version. Pitching the casual player directly into a dodging mechanic could be fine if it were a very simple one, but the standard opening raidwide serves as a gentle warm-up here.

One-two Paw

The cast name cues the player to expect a sequence, the cast length is good, and the glowing elongated claws are very clear about the order of which sides will be hit. (Unlike the various one-two punches in the MSQ duties, this one always alternates sides.)

I would tweak this to hit with the Savage timing, with the first hit right as the castbar ends, rather than the current Normal timing that hits a couple of seconds after the castbar ends. While that would make the mechanic harder in theory, it would be more consistent with the general snapshotting rules of the game, making it easier in practice both here and for stepping up to Savage. The casual player would still have plenty of time to see the claw animations, especially since the boss shows it twice before doing anything else.

Black Cat Crossing

A fine sequence dodge, which works thematically even for the casual player who never sees its Savage upgrade (Quadruple Crossing). The glowing lines do not tell the first-time player exactly where will be hit, but that is completely fine - the natural guess is "these extend from the boss" and the cones confirm that as the first cast resolves. On later casts, strong players can use the floor grid to dodge precisely.

Mouser Mini-Phases

Mouser

A big flashy sequence that draws attention to the gradual transformation of the arena, which is excellent to prepare the player for manipulating the ring themselves during Elevate and Eviscerate. Since the player can avoid all damage here by planning one movement or finding one square that does not get hit, this is an acceptable memory mechanic with plenty of time in the resolution for the player to see the effects on the arena.

The "My riing!" voiced reaction from Metem is a nice touch for story and immersion, though it does not do much to make the mechanic work since it occurs after the player has most likely seen the arena transformation.

Elevate and Eviscerate

Here, the "Going up!" voice line comes at the start of the first cast, so the player can use it to guess at what the mechanic does.

Incredible attention to detail in the visualization of this mechanic. The visual feedback during the cast is what makes such a complex task doable in Normal. (To avoid a KO, the player must manage the direction and the distance of the knock-up to land on a full-strength tile. To know to do that, they must understand that the knock-up will also move their character horizontally and that their character's landing will affect the floor. That is a lot to do, especially since they cannot be expected to learn the distance of the knock-up in Duty Finder.) All of the necessary pieces are incorporated in the visualization, and in a very clear way for the first-time player.

The arc of arrows in the visualization shows what the direction and distance of the knock-up will be if the targeted player character stands still, along with the fact that it is a knock-up rather than a knockback, and even includes a generic humanoid model travelling along the arc. If the player character would land safely on a full-strength tile if they stand still, that whole tile is highlighted green with a vertical "bounce" indicator that signals the impact on the floor. If the player character would not land safely on a tile if they stand still, the whole arc of arrows turns red and ends on either no tile or a partly-broken tile with a pure red highlight, no "bounce". (The fact that there is more than just a color indicator for safe / unsafe is awesome; so much to show and still colorblind-friendly.) And while the source of the knock-up varies - in the first of these mini-phases it is the boss, in later iterations it is a clone - there is always a tether between the targeted player character and the boss / clone. That tether leads to the boss / clone continuously facing that character, showing the player where the knock-up is coming from and therefore how to manipulate the direction. Plus all of this is completely matched up with the player character's movement on the player's screen, so it has to be client-side for rapid feedback. So many visual elements that come together perfectly, enabling the targeted player to control their character's landing, the rest of the party to react to where that character will land before the cast finishes, and the whole party to learn the mechanic.

The only minor pain point of this mechanic is that since the boss's position for the next cast in sequence is set by it dashing to the previously targeted player character, occasionally the boss winds up positioned relative to the remaining full-strength tiles such that there is no place (or only an impractically small place) to move their character and avoid the KO. It is not common, but it is very frustrating when it does happen, since the player who takes the penalty has nothing actionable to do about it. I would fix this by making it more similar to the Savage version, where the direction of the knock-up is the targeted character's facing and therefore fully under the targeted player's control. (This would not require the clone to appear in the first of these mini-phases, just having the boss dash behind the targeted player character.)

Future arena manipulation mechanics like this would still need to only target one player character at a time in Duty Finder, to avoid adjusting loops and to allow the casual player time to learn from their party and breathe. Since this is only one player character at a time, it works well. The selection order even has every player character be targeted once over the first two occurences of this mini-phase, just like Savage, where reasonably possible.

There are small forced downtimes from the knock-up itself, which are an optimization opportunity for stronger players since the boss gives ample warning when the downtime is coming. There are also melee downtimes in the first iteration from the boss turning and dashing, which are not really optimization opportunities because of the reaction to the targeted player's choices.

Overshadow

This simple line stack only appears in the second and later Mouser mini-phases, with the boss casting it as the clone casts Elevate and Eviscerate. This placement is good, being just the right amount of added mechanic for the player to handle once they have seen a few rounds of Elevate and Eviscerate. In particular, the player whose character is targeted for Elevate and Eviscerate can still handle that by looking at the visualization, and the rest of the party can react to each other by looking at the stack. (Spreads would not work here, being a little too much reacting to each other when combined with the Elevate and Eviscerate targeting.)

Shockwave

It is correct and important that this knockback can be negated by Arm's Length / Surecast in Normal, as broken tiles may well leave no safe place to ride the knockback and a party KO from that would be an annoying surprise.

Regular Arena Mini-Phases

Predaceous Pounce

This mechanic is fine but nothing special. It is thematically appropriate, with the animations of the resolution being very fast, but on a purely mechanical level it feels like the sort of thing that is put in a Normal to replace a Savage mechanic that cannot be usefully adapted for casual play. (Being so fast, following the boss around is a dangerous pain in the first usage, which is done by the boss rather than a clone.)

The follow-up spreads (no castbar) ask the party to not stay clumped up in their final safespots or around the boss, which is again fine. They give lots of time.

Leaping One-two Paw

A good introduction to the "boss jumps and immediately does a mechanic" concept of the Leaping casts. The tether visually leads the player to the glowing pin, which provides not just a clear indicator of direction to the first-time player but also a precise reference for exactly where the boss will jump. In turn, that reference enables the player to precisely dodge when seeing this mechanic again, including for the spread follow-up on the second and subsequent casts.

Just like the base version, I would give this the Savage timing.

Leaping Black Cat Crossing

Another good Leaping cast, which is correctly the second use of the concept as dodging its pattern requires the player to have a better grasp of the boss's landing position. The second and subsequent casts of this again have the spread follow-up, which is more complicated here due to the narrower safespots.

Overall Impression

Fantastic core mechanics, made possible and elevated by incredible visual design. Just turn the brightness down a little and make Elevate and Eviscerate use character facing. That I got bored quickly here is entirely the fault of job design, not duty design; any duty that could challenge me in a fun way once I know it would be functionally impossible for the Duty Finder population, and the current job design overall is not up to the task of filling in the gap.

--------

AAC Light-heavyweight M2 (M2N, Honey B. Lovely Normal)



This arena also has an excellent floor, but the mechanics only utilize it in Savage so it is better discussed there.

Tempting Twist, Honey Beeline (Basic Forms)

The visual effect for each is important to give the first-time player a rough idea of the danger zone. (Tempting Twist is always first.) These are fine.

Honeyed Breeze

I find it very strange that this double cone tankbuster is not given the Savage cast name for the almost the same thing, Stinging Slash. (The only difference between Honeyed Breeze and Stinging Slash, aside from the obviously higher damage in Savage, is that Stinging Slash has much wider cones of roughly 90 degrees each. Which would be perfectly fine for Duty Finder, since the player can learn to give the tankbuster a wide berth from seeing the animation.)

Even if the design intention here is to not present Killer Sting (the tank stack from Savage) to prevent one tank from taking it alone with an invulnerability, matching cast names between regular duties and their high-end versions help the player looking to learn the high-end version.

Beat Mini-Phases (Charm Gauges)

Honey B. Live

The longer cast and arena-wide animation of this raidwide are an effective warning that the boss is setting up something. A good primer for the player to notice the overhead charm gauges when they appear.

(The "Beat" name for these mini-phases is from Savage, where each of these casts is numbered in the cast name.)

The heart stack debuffs shown by the charm gauge do come with a light DOT per heart, which is healable by even a single casual healer so it is fine.

Love Me Tender (Spreads)

The very first cast of Beat 1, showing the player that attacks with hearts on the telegraphs also inflict a heart on their character when taken. It is correct and important to do this, since the first-time player does not know how the charm gauge works. The red text after this hits for the first time, "You are growing infatuated with Honey B. Lovely...", helps reinforce the lesson.

(no castbar, follow-up effect of spread / stack Love Me Tender) Heart Towers

(In Beat 1, four towers spawn. In subsequent Beats, six towers spawn.)

One of the worst mechanics of Patch 7.0. Let us examine why.

Now that the player has seen the heart spreads and their effects, they understand that taking an attack with a heart on it adds a heart to their charm gauge. They are trying to further learn how the charm gauges work, and most likely infer correctly both that taking a tower will give their character a heart and that the party leaving a tower alone will cause it to explode and inflict a heart on every party member. From there, they understand that the party as a whole will get the best results by placing exactly one player character in each tower.

Even the very casual player understands both what the heart towers are and the intended resolution, since the necessary information has been put right in front of them. (Plus the casual first-time player almost always has the benefit of the story up to that point warning them to watch out for charm-related mechanics - cutscene skippers have no need to be in this duty other than wanting the gameplay of the Normal Raids, the unlock for the Savage counterparts, or gear for other duties, so if they are in this duty they usually have decent gameplay skills.) Player understanding is not a problem here.

From that understanding, how does the player try to do the mechanic?

This is a regular duty, with the party probably being formed through Duty Finder matchmaking. The player is operating on reaction. When they see a tower and their character is not already standing in it, their first reaction is to move their character towards the tower unless they have a reason to keep their character elsewhere (such as already standing in another tower). Their second reaction is to try to redistribute between towers if any are left empty after the party first moves. Accordingly, the Duty Finder population handles towers by reacting to their fellow players' choices.

With normal towers, this is not a significant issue, with only the occasional failed tower. Multiple players will put their characters in the same towers, and leave them there because that resolution of the mechanic does no real harm to the party's chances of success. With the heart towers, multiple players seeing their characters all in the same tower will react by moving their characters out, trying to get to exactly one character in each. That makes the tower empty, so they react by putting their characters back in...

The first problem with the heart towers is that they actively create adjustment loops. Not just invite adjustment loops, actively create them. If the player cautiously waits for a party member to take a heart tower, they are still reacting to their fellow players' choices, and that strategy is equally prone to adjustment loops. If the player prepositions their character near a potential heart tower location to indicate intent to take that tower, that gives them longer to try to break out of an adjustment loop but does not make the loops any less common.

As a result, the Duty Finder population has a very high failure rate for this mechanic, and will never be able to master it short of spending tightly limited general preparation time on a priority order of taking towers. (Which I would advise against, since there are much more flexible and interesting things to use that time on if you were going to teach Duty Finder to do general preparation again.) What happens when the party fails and a tower explodes?

Well, the tower explosion inflicts a heart on every player character who is not KOed or charmed (the Fatal Attraction debuff). And since the towers always come after a spread or a pair of stacks in the same Beat, every player character already has at least one heart unless they actively avoided a stack earlier. So those player characters who have not yet taken a tower go to two hearts, and are able to continue fighting. Those player characters who have already taken a tower are forced to three hearts, inflicting Fatal Attraction followed by the Sustained Damage debuff (a DOT that may very well KO them when combined with the damage of a failed mechanic), so they cannot continue fighting immediately at a minimum. And there are Vulnerability Up stacks added on top of that!

The second problem with the heart towers is that failure inflicts the heaviest penalties on those players who did a service to the party by taking earlier towers. This discourages the player from taking a heart tower at all, compounding the issue of adjustment loops.

Once one tower explodes, the only player characters who can take the remaining towers without being charmed are those who either were already charmed or avoided a stack earlier in that Beat. (In particular, those about to resolve a tower can be pushed to two hearts by the explosion and then three hearts by the tower they were already standing in.) This makes the mechanic create cascading KOs very easily, which is not inherently a fatal flaw but compounds the annoyance and anger with the mechanic. The serious penalties for lack of preparation are much more than occasional here.

And if the party makes it through the series of towers, they are then presented with a reaction dodging sequence of AOEs that all also inflict hearts. After seeing that, the player is further discouraged from taking a heart tower (or the stacks preceding the heart towers in subsequent Beats) if they have any concern about their ability to manage the reaction sequence later in that Beat - especially since being charmed during that time often results in taking further AOEs while unable to act.

The third problem with the heart towers is that the surrounding mechanics encourage selfish play, while the towers make the party's charm gauges a communal resource. If there were no stacks, towers, or even spreads, and avoiding a filled charm gauge was purely a matter of individual dodging, that would be one thing. (In fact, using a similar concept to present reaction dodging sequences without seriously penalizing the player until they reach three failures in the sequence would make such sequences a lot more tolerable, functioning as a gentler Thrice-Come Ruin since party members could heal a struggling player's character through it.) But those are not the mechanics here. The party's charm gauges are clearly a party resource, while the mechanics encourage the party to fight each other over it.

The first problem alone is enough to completely scupper the mechanic. All three together are a disaster. The Normal Beats in their current forms were knowably doomed to be anti-fun before a single party saw them.

Surprisingly for a mechanic that drew so much complaint and has so many fatal flaws, part of the underlying notion of heart towers is usable even in Duty Finder. But making it work well with the current Duty Finder population requires changing the whole structure of the duty timeline. For that, see my redesign of this duty and its Savage version.

Love Me Tender (Reaction Sequence)

Moving hearts emitted from the boss and from the edges of the arena all at once, combined with both small and large circle AOEs rapidly appearing, creating a bullet hell section with the added danger of filling the charm gauge. (The moving hearts from the boss are in a hidden fixed pattern, but the first-time player does not know that, and the sequence as a whole is so chaotic that even a strong player who completes the Savage may not notice it.) The hearts from the edges of the arena start in random places and each pick a random player character to aim their (straight line) path through, practically guaranteeing that the player will have to dodge at least one in a panic. And the pink circle AOEs very effectively hide the pink moving hearts from peripheral vision.

On its own, this is visually overwhelming chaos. Combined with the heart towers, it is an invitation to anger. The only thing the player can do about struggling with this is try to avoid hearts from the towers and stacks.

Blow Kiss

A wide cone AOE targeted on a random player character's position at the start of the cast. Annoying when there are still moving hearts in the arena, acceptable otherwise. The cast name is odd, since blown kisses are not avoidable on Earth, but that is relatively minor.

Love Me Tender (Fixed Circle Pattern)

This is acceptable, since even if the player does not remember the "Shiva circles" pattern from previous duties, they can see the sequence of telegraphs appear and have enough time to plan their movement.

Love Me Tender (Heart Stacks, used instead of the spreads after Beat 1)

Each of these two stacks inflicts a minimum of four hearts distributed among the player characters within, but also will inflict at least one heart on each player character within - so each stack will give more than four hearts every time that more than four player characters stand in it.

The arrows around the stack circle are yellow just like normal stacks and they have the same sound cue, being distinguished only by surrounding the arrow pointing to the targeted player character with four floating hearts. So the first-time player might not even notice the difference from a normal stack, being so familiar with the standard stack marker as to not need to look at every part of the visual, and having long experience that keeping track of the stack locations is important when dealing with more than one simultaneous stack. Even if the player does see the hearts and count out the four of them on a stack, whether on sight or in later attempts at the duty, that says nothing about the extra hearts generated by having more than four player characters in a stack.

(Even if the stacks each gave exactly four hearts, that would be a difficult concept to visually convey, since too much difference from the normal stack marker would stop the player from reliably recognizing it as a stack. The added hearts for extra player characters makes it even worse to convey. You could consider having the four hearts instead be part of the four arrows around the stack circle and drawing the entire telegraph in pink, but that still would not reliably have the player see all four arrows.)

The player most likely understands the preexisting concept of multiple simultaneous stacks; not only have they seen two or more simultaneous stacks in prior duties, but it is the logical guess that they are meant to be separated, since if you wanted the whole party to stack together you could present one stack marker. (Though Syrcus Tower does not help matters now that it has the standard stack marker, since those ones can and should be stacked.) From there, it is natural to try to split the whole party evenly between the presented stack markers.

But the Duty Finder population has not mastered that either, as evidenced by the regular individual KOs and even party KOs to two simultaneous stacks in duties such as E7N. Just like the basic spread, splitting the party into two even (or roughly even) groups by reaction requires reacting to fellow players' choices - so the Duty Finder population can never master it so long as they are operating on reaction. (If their general preparation included light parties and there was a community standard flex order within each light party, they could, but that is a far cry from the current player expectations.) Even separating the two stacks is the same way.

Using hearts instead of short-term damage type vulnerabilities to enforce splitting the two stacks does not change the fundamental nature of the task. The Duty Finder population still can never master it so long as they are operating on reaction.

If this were the only mechanic in a Beat that caused inherent problems to Duty Finder, the use of hearts could be a benefit to the mechanic, allowing the party some "free hits" from imperfect coordination without taking any severe penalties. (Indeed, the sequence of these two stacks into six heart towers only mandates that the party take 14 hearts out of their collective maximum of 16 hearts before player characters begin being charmed, allowing for two "free hits".) But in the context of the duty, this is always followed by the heart towers and then the reaction sequence, so the party must both stretch that lenience across the whole Beat and compete over it for the reaction sequence. As a result, the presence of these stacks sets the party up for annoying failure, both in encouraging selfish play and in potentially having too many collective hearts to avoid charms from the towers without making any real mistakes.

Honey B. Finale

A raidwide that transforms the arena back and cleanses all hearts. The damage is only scary because of the high chance of failed heart mechanics earlier.

Regular Arena Mini-Phases

Splash of Venom

This stores a spread for after the upgraded random ground AOEs, though the player does not need to remember that here since it comes with telegraphs. It serves a fine dual purpose of ramping up the duty in a way the casual player can handle while showing what the cast will do in Savage.

Tempting Twist, Honey Beeline (Upgraded Forms)

Now these ground AOEs leave Splinter honey blobs that explode afterwards. Oddly, these are not in the Savage patterns, which is another missed opportunity to help the player learn the Savage version should they choose to. The Savage patterns are still just ground AOEs that the player can learn by seeing them.

Drop of Venom

This stores a stack for after the upgraded random ground AOEs, again with telegraphs. This cast does not and cannot teach its Savage version, since that is partner stacks and partnering by reaction to fellow players is nowhere near reliable.

Alarm Pheromones

This mini-phase is better discussed by the patterns that appear in its different iterations, rather than by cast names, since it has the same cast name every time.

Over all the variations, the visual design of this mini-phase is a miss in both thematic appeal and mechanical fairness. Surely the Groupbees' line tells should be black instead of the current green, perfectly fitting the bee theme and providing high contrast against the yellow-brown honeycomb floor? And the line tell for each Groupbee should extend across its entire path, clarifying that they dash across the arena rather than stopping within it.

Helix Pattern (Alarm Pheromones 1)

A good introduction to the Groupbees' behavior, allowing the first-time player to see them dash one by one while presenting the strong player with an uptime optimization opportunity for tanks, melee DPS, and jobs with frequent cast times.

Bowtie Pattern (Alarm Pheromones 1 and 3)

In Alarm Pheromones 1, this directly follows the helix pattern on its own. In Alarm Pheromones 3, this goes off while the boss is casting the upgraded Honey Beeline, most likely creating a sequence dodge from the main tank dodging the Groupbees and thus pointing the front-to-back line of the boss into the safespot of this pattern. (There is no repeated cast separating Alarm Pheromones 2 and 3, just a Tempting Twist into spread resolution into Drop of Venom.) Both are fine.

If there was another use of simultaneous Groupbee dashes, the first occurence of this pattern would serve as a good introduction to it, but this is the only simultaneous Groupbee pattern in the Normal. In Savage, such introductions are less necessary, as the player has already seen the basic concept of the Groupbees from the Normal and is inclined to study specific mechanics for their patterns anyway.

Random Baits (Alarm Pheromones 2)

The annoying pattern, where the Groupbees appear one at a time in random positions and each set their paths to go through random player characters, with no advance indication of the spawn order or who is baiting which Groupbee.

Here, the player does not strictly need to react to their fellow players' choices, only to the Groupbee paths. So why is this such a troublesome mechanic?

Consider where the player must look on their screen to find out whether a particular spot, such as under their character's feet, is safe.

If they work in the middle of the arena, the Groupbee lines do extend that far but they are heavily exposed to most of the Groupbee dashes, and must react frequently - including potentially being forced out of the middle by multiple dashes in that area. Thus they must also contend with the other case below.

If they work near the edge of the arena, they cannot just look at the spot they are working with, since the Groupbee lines do not extend that far. Nor can they rely on the baiting of a Groupbee towards their intended spot to draw their eye, because the green on yellow is low contrast even for those without colorblindness. Instead they must check a substantial radius around their intended location, and they must do so by moving their eyes around that radius so as to catch the Groupbee lines in the rather small area of their central vision. Even though the Groupbees' Blinding Love cast is 6.5 seconds long, subtracting out the time for the Groupbee line to appear, the player to make a decision about where to move their character accordingly, their physical reaction time, and of course client-server latency leaves substantially less time than that - in which they must scan that entire radius, requiring uncomfortably rapid eye movement even if they succeed. And just like in Tender Valley, that rapid eye movement creates effective blurring.

(Does the player need to stop their eyes on each Groupbee line? It depends. A relatively isolated line will generally be discernable without a stop, since the shape shows the direction. If two or more lines cross near the player's scan circle, they may need to stop and pick out whether either one will pass through their chosen spot.)

In either case, if their character does get hit by a Groupbee, their character is knocked along that path, putting their character in a new location that they presumably have not been able to scan the appropriate radius around. (Or into the death wall at the edge of the arena.) Since such a failure necessarily occurs during the Groupbee dashes, they have even less time to try to scan the appropriate radius around their character's new location, so failures cascade rapidly on an individual level. In turn, this leaves fewer player characters for the remaining Groupbees to target, putting more pressure on the remaining players and thus making failures more likely to cascade on a party level.

And on top of it all, the pace of the Groupbee spawns makes this a reactive mechanic given the nature of all the dashes requiring the player to consider where to move their character.

If the visual design for the Groupbee lines allowed the player to get the strictly necessary information by looking just at their character's feet, this mechanic would still be reactive and unpleasant, but it would be a lot more manageable. The lacking visual design turns the mechanic from merely reactive into a fiasco.

Overall Impression

Where The Strayborough Deadwalk is ruined by one bad mechanic, M2N is ruined by fundamental misunderstandings of how to use randomness and what the player can do by operating on reaction. It is a shame that such a strong lore concept led to such an annoying duty, which is one of the reasons that I chose this and its Savage version for my redesign examples.

--------

AAC Light-heavyweight M3 (M3N, Brute Bomber Normal)



You clearly put in effort to give this floor markings, even though this is meant to be a wrestling ring and most wrestling rings have no such internal markers. You did a good job of making the markings look thematically appropriate. Yet the floor geometry does not match any of the mechanics that would benefit from them, such as Lariat Combo and the exploding bombs. (It does not match any mechanic here in Normal, and the one Savage mechanic it matches cleanly has no need of floor geometry, since it comes with full telegraphs.) What an odd choice, and one that makes multiple mechanics needlessly annoying.

Opening Phase

Everything before Doping Draught ramps up the attacks, though the first-time player does not know that yet.

Brutal Impact

Initially a two-hit raidwide, it ramps up to six hits after Doping Draught. The initial form is so light that I would be inclined to give it four hits like the Savage version, especially since its only use is right at the beginning of the duty and so allows for prepull shields.

Knuckle Sandwich

A tank stack, like in Savage, but with only a single heavy hit.

Oddly, this does not ramp up after Doping Draught at all; I would be inclined to turn down the power of each hit both before and after, then give it just one extra hit when ramped up, to gently hint at the Savage multi-hit forms without being too deadly if the off tank is unavailable or runs away after the first hit.

Brutal Lariat

The boss dashing to a side of the arena, raised arm, and fire animation make it clear that the attack will hit that side of the arena, even for the player who does not know that a lariat is a real category of wrestling moves on Earth that all involve charging and swinging an arm at one's opponent. The name is a nice touch, very thematically appropriate.

Unfortunately, even once the player has seen the attack resolve, they have no good floor references for how far they must move their character to be safe. They can try to estimate it based on the circles, but that is not reliable when the pace starts ramping up.

Murderous Mist

The green poison mist and bubbles hint at the 270 degree AOE shape where only the back of the boss is safe, sometimes called Sweep the Leg from its appearance in The Jade Stoa (all difficulties) or Conflag Strike from E6N and E6S. But the mist and bubbles do not do a good job of showing the shape.

First, they are mostly high up, so on the player's camera they will show over a significantly different part of the floor than the attack actually hits. (A true top-down view is not possible from the game's camera in battle without third-party tools.) Second, their sparseness and high variation makes them mostly visual clutter, especially since they do not show an edge.

The first-time player could easily think this is a DOT raidwide, since that is what the mist and bubbles look like. Even the boss leaning back with arms spread could equally be interpreted that way. The player will learn the AOE shape, but by the brief telegraph and animation of the attack resolution rather than the visual effects during its cast.

Because of this, the combined penalty of high damage, presumably heavy DOT, and Vulnerability Up stack are a bit harsh even though the DOT can be cleansed with Esuna. It is not inherently a one-hit KO, but it becomes one quickly unless the party notices and applies healing resources, which is too much for a mechanic where the player can correctly prepare for what they see and still fail.

Since the DOT nature is the core concept of this attack, and important for Savage, I would change the visual effects. Have the effects be further down and show the edge with moving mist, or something like that. (This would be especially useful for those with frequent cast times judging if they have to move, since the boss can be tilted for this attack, unlike in Savage.)

Barbarous Barrage

These knockback towers have excellent visual design, making it clear to the first-time player both that they are towers and that they inflict knockbacks when taken. This makes the long knockback distance completely fair for a regular duty, since the first-time player expects the knockback even if they do not know the distance, and so can position conservatively to keep their character from being knocked into the fire DOT wall at the edge of the arena. (It would be a bit much if the wall produced an instant KO, but that is only in Savage.)

These towers also have the same reference markers for knockback angles around their edge that are helpful in Savage, even though the player has much less use for them here. This is good, helping the player step up to Savage should they choose to.

Plus there is skill expression here in whether and when to use one's knockback immunity, especially when this is sequenced into other mechanics like Fuses of Fury.

More like this in regular duties, please! This is fair, fun, and encouraging.

Fire Spin

A simple spinning cone that hits each spot in the arena exactly once. Nothing special, but fine and here to be ramped up later.

Fuses of Fury

Places eight bombs in a square within the arena, leaving the center free. While this is conceptually fine, it has two visual issues.

First, the short fuse bombs (which explode first) and the long fuse bombs (which explode second) are distinguished only by the length of their fuses. Both have the same swirling pattern on their fuses, stretched out on the longer fuses. This is not enough of an indicator, especially for the first-time player who does not yet know that the bombs explode at different times despite being placed all at once. They will pick up the bombs in their peripheral vision, but not necessarily the fuses, and the directions of the fuses vary as well. The red text "The fuses are ignited!" also does not tell them to look at the fuses, only that the bombs have been set off.

To improve this, I would put the swirling pattern on only one of the fuse lengths, and have the other fuse length be a solid color. I would also avoid using black in either of the unlit fuse designs, to improve the existing teaching visual of the fuses burning to black as the fires travel along them to the bombs.

Second, there are no floor markings corresponding to the edges of the bomb explosions, even though there are circles marked on the floor. Since the explosions are fairly large for the density of the bombs, this is annoying right away, and even more so when these are sequenced with other mechanics such as Lariat Combo and Barbarous Barrage.

Doping Draught

A very thematic spectacle cast, giving the player an extended time to both enjoy the NPC interactions and think about what more dangerous attacks the boss might present. Even for the first-time player who knows nothing about stage wrestling, the dialogue and persistent buff on the boss make it clear to expect a difficulty spike.

For the sake of longevity through repeat completions and increasing average Item Levels in the Duty Finder population, I would want this to come slightly earlier in the timeline. In particular, I would cut the third Brutal Lariat, since two is enough to show that he can use either arm. The second Fuses of Fury before this is important to give the first-time player a second chance to look at the different fuse lengths.

Lariat Combo

Two Brutal Lariats back to back. Unfortunately, the pacing makes the second one reactive, especially since the lack of floor references prevents the player from reliably prepositioning their character just outside the first AOE. (So the player must be assumed to have their character out of position when reacting to the second hit, similar to when fighting Herpekaris in Origenics.)

As before, I would add floor references for this. But rather than only changing the floor geometry, I would enable an even faster pace by giving the player information about both hits in advance. This mechanic could show the boss charging up his arms for each hit, just like Maulskull does in The Skydeep Cenote. Alternatively, we already have the "Limit Cut" number markers (which you even included in your marker guide with the updated Hall of the Novice) that could be shown over his shoulders with the different shapes used in Alphascape V4.0 (Savage) (O12S) Fundamental Synergy. Either addition would allow the player to stand just outside the first AOE and start their character running / stay still as soon as that first AOE resolves, making the mechanic a small taste of executing a plan quickly rather than a test of reaction time.

(And yes, he would still turn after the first charge. Starboard / Larboard again, but this time with animation cues for the sides.)

Infernal Spin

The upgraded Fire Spin, this time combined with concentric circle AOEs and eventually also multiple sets of baited circle AOE drops.

Even though the Fire spin cone itself still only hits each spot in the arena once, the baited AOEs and the practicality of doing this with Duty Finder matchmaking are a hassle to those with frequent cast times. The player has a lot less to work with to plan their movement tools here in Normal compared to high-end duties, so use mechanics like this sparingly. Too much becomes annoying.

I would personally remove the baited AOE drops, but not due to the movement requirements. The timing of the baited AOEs means that the player who wants to preposition for an upcoming mechanic can find themselves blocked by not only moving too early themselves, but also by another player's character movement timing. This is a recipe for strong players getting annoyed at their party members, and is not happening much only because the strongest players have either stopped repeating the duty or regularly KO the boss before this gets sequenced into other mechanics. (Sure, the party can also get in each other's way in the Savage version (Fuse or Foe), but there they can correct each other effectively.)

Overall Impression

Whoever did the visual design for Barbarous Barrage should make more like that. Whatever process led to this floor having tons of useless markings and no useful references should be re-examined.

--------

AAC Light-heavyweight M4 (M4N, Wicked Thunder Normal)



This floor is in an odd state, being useful for some mechanics and useless to actively unhelpful for others. But in this case the mechanics that it does not fit have their own problems, such that the mechanics are ill-designed rather than the floor being ill-fitting.

Sidewise Spark

The lightning visual effect is by far the primary indicator for which side is being hit. In fact, when the boss has wings out, it is the only indicator, since she does not change stance in that form. Since this visual effect is very cluttered, quite high up, and ramps up gradually, it is not a good primary indicator. Imagine what it looks like for visually impaired players!

Unlike Murderous Mist in M3N, here at least the cast name clues the first-time player in that this only hits one side of the boss. There is no reasonably mistaking it for a raidwide.

But if the player happens to have their camera pointed along the side-to-side line of the boss, rather than the front-to-back line, it is unreasonably difficult to pick her stance shift out of the wall of sparks to find out which side is being hit - and the Savage version does actively make the player do that (during Electrope Edge 2), with another visual cue mixed in! At that point, her silhouette is the same either way, so the player has to pick colors out of the wall of sparks, and that is not an acceptably clear indicator.

You can have the thematic lightning sparks in a clearer way. This could have been animated with the boss pointing her hands slightly further down to send the sparks near or onto the floor, rather than creating a visual wall high up.

Shadows' Sabbath (Basic Form)

It would have been easier for you to have each clone's whole body load in on the player's screen all at once, like you do for most appearing entities, than to have the fancy "displayed gradually as the ring passes over them" effect that you created for this duty. You put deliberate technical effort into making the clones, and by extension the visual indicators of their attacks, both difficult to see and late-appearing.

That was a terrible use of your development time. The obscured visuals benefit no one and hinder a variety of player groups, as I covered in the design principles section. The format of the late-appearing indicators merely teaches the player to learn when the first indicator they can reliably discern will appear and wait until then in boredom, again as I covered in the design principles section. For visually impaired players who cannot rely on the clone's mane direction as the first-appearing subtle indicator, or for anyone if the timings are tight enough, the deliberately late appearance of the more obvious indicators makes their Sidewise Sparks needlessly reactive. And to top it all off, this design encourages the player to use third-party tools that instruct them on mechanics without waiting for the visuals to appear on their screen.

Using the falling ring around each clone to show when its attack will resolve is a good thing, as it clues the player in to the timing without relying on them looking at their enmity list for untargetable adds. It also allows for faster sequences where the player may not see each clone as it first appears. However, for some later clone types, both here and in Savage, it is not tied to the clone's attack timing at all - which breaks the consistency of the rule the player has been using since A Realm Reborn. This seems like a further effect of tying the movement of the ring to the visual display of the clone.

If each clone displayed fully when it appeared, this would be a good introductory mechanic leading into potentially interesting sequences with the clones. But the choice to deliberately obscure the visuals and make them appear late spoils the clone mechanics.

Ion Cannon Mini-Phases

(The name is from Savage, where the cannon hits after Stampeding Thunder must be taken to cleanse debuffs first introduced by the Ion Cluster cast.)

(no castbar) Stampeding Thunder (Platform Break)

The concept of the boss breaking part of the floor with her attacks is cool, and mechanically reinforces that Wicked Thunder and Black Cat are sisters.

But here, unlike Mouser, the player is not given enough warning of which side the boss will choose to reliably avoid all the hits; even in Savage with Sprint already active and lots of practice, it is not possible at moderate ping without the use of third-party tools. In Normal, without the benefit of timeline knowledge, practice, or even getting party members to stand away from the boss's targeting ring, it is even worse.

In fairness, the individual hits are light here and inflict no penalty other than the damage itself. But it still feels bad, because the game has taught the player for so long that getting their character hit is always a failure unless the attack was obviously unavoidable. It feels like a reactive mechanic as a result, and is to a degree, even though on close inspection it is clearly not meant to be fully avoided.

Plus it is an enticement for those players on melee DPS and tank jobs to take additional damage for the sake of melee uptime and expect the healers in their party to compensate for that, which is surely not ideal. (In Savage, the tanks can handle the extra hits themselves and any other role will be KOed by them, which makes it less of an issue.)

It is difficult to eliminate the extra hits entirely without making the floor feel relatively fragile, which would be a detriment here unlike in Mouser. But the animation could tell the player which side will be safe earlier, such as by having the boss point the cannon earlier and briefly charge it, removing the felt and actual reactive nature.

Threefold Blast

The introduction to how the cannon hits work when not pointed at the platform. The hits always alternate sides, and clearly are not meant to be taken since they inflict a Sustained Damage DOT.

For the upgraded forms this leads to, it is a good introduction. The name cues the player to expect a sequence, and it keeps the same time between hits as the upgraded forms. (The hits are 2.5 seconds apart, making them slidecastable with the right Global Cooldown alignment, but the heavy damage and Sustained Damage for each failure leads to many quick KOs if the player tries to learn that alignment technique here.)

As a memory mechanic, this asks the first-time player to remember two items: put their character in the first safespot, remember the other two. For the player who knows the pattern, this is not a memory mechanic at all, since they know that the hits always alternate and that is enough to succeed after putting their character in the first safespot.

Fourfold Blast

This introduces two consecutive hits that do not alternate sides, while the rest alternate. The non-alternating pair can be at any point in the sequence.

As a memory mechanic, this asks the first-time player to remember three items: each hit after the first. For the player who knows the pattern, they need only remember one item: where the "stay" is in the movement sequence.

At the end of the sequence, this also drops circle AOEs under random player characters. This is clearly meant to be an adaptation of the Savage debuffs, and "here are some baited AOEs, move" is useful sometimes. But here it feels mildly irritating, since the same circle AOEs are used so often in this duty.

Fivefold Blast

The final form of this mechanic, and the only Blast used after the first Ion Cannon mini-phase. Always has exactly one non-alternating pair, just like Fourfold Blast. Ends with a spread in the smaller arena.

As a memory mechanic, this asks the first-time player to remember four items: each hit after the first. For the player who knows the pattern, they still need only remember one item.

This is a regular duty. Yes, the hidden pattern is not hidden that deeply, but you still cannot rely on the player knowing it in order to fit memory mechanics within the three item limit. I picked it up quickly, but that does not mean everyone is going to. Please imagine the first-time player who is already tired after a long day of work and caregiving; their working memory is already impaired, and they are not likely to pick up on the pattern from a single Threefold Blast and Fourfold Blast. They do not need to succeed at every mechanic every time, but they should still have an encouraging experience, which "ugh I forgot the sequence" is not.

I see this whole mini-phase as a missed opportunity to express Wicked Thunder's fighting style and hint at the Savage version without spoiling its puzzle.

The Positron and Negatron debuffs already have clear visuals around the affected player character from the Savage version, and "restore balance in your character, with imbalance shown by visual on or over your character" is already a recurring concept in optional regular duties. (Complete with one-hit KOs for failure.) You could have had Ion Cluster itself here, along with the cannon hitting each side in a different polarity like the charging visual hints at and the Savage version does. Just remove the added debuffs that create the Savage puzzle of arranging AOEs in a small space, and lighten the damage of the cannon hits (when taken with the opposite debuff) to make the healing requirement mostly look scary rather than being too difficult for Normal Mode.

That way, the double cannon charges before each hit would remove the memory mechanic escalation, and would show her use of the cannon to force opponents to take damage before getting to the duty's final phase.

Regular Arena Mini-Phases

Wicked Bolt

A multi-hit stack shortly after the arena floor is restored. Can cascade rapidly if multiple party members are KOed at the end of an Ion Cannon phase, but that is not in itself an issue - it would be perfectly fine if not for further punishing players who struggle Fivefold Blast.

(And yes, if the Ion Cannon phases were changed as I suggested, this would make for a more extended healing requirement. A little taste of extended healing is okay for Normal Mode, it does not have to hit very hard.)

Bewitching Flight

As cool as this looks, it is difficult to see where this attack will hit precisely, and that is clearly due to your design choices rather than the lore idea of the mechanic. Since the safespots are quite small, this is annoying even to the casual player who is simply trying not to get their character hit.

The electrope "feathers" of the wings would not look right if they pointed straight down, but you could have made the lightning emitters on the "feather" tips point straight down; they even already have a spherical glow that would make the orientation change look less jarring. Because they do not, the player must choose between looking at the emitters that are offset from where they hit, or the moving spray of lines from each that does not even consistently show the whole area to be hit. Likewise, you could have made the spray of lines stay still for visual clarity, but you put in effort to animate it in a way that obscures the danger zones.

As for the floor, for some reason you chose not to match the spacing of these line AOEs with the width of the floor tiles. There are five line AOEs on a 4x4 grid, when you could have used four line AOEs without really changing any other mechanics. (You could also have made the floor a 5x5 grid, which would have saved you some work for Electrope Edge 2 in Savage, but that would require a different pattern inside the tiles to provide references for many other mechanics.) In fact, four line AOEs would look more natural and balanced, putting two emitters on each wing.

This is annoying enough the first time, when just the boss is doing this attack. It is even worse the second time (and presumably subsequent times), when there is also a clone doing the same thing on an adjacent side, giving the player less time to look at each one. (This is also one of the places where you decoupled the clone's ring from its attack resolution, because the player needs time to see the full visual of the clone.) Clearly someone on the duty design team knew this on some level, since the Savage version of this mechanic removes the clone in favor of using electrope cubes whose spacing does match the floor grid.

This really should have had four line AOEs spaced to match the floor grid, and then it would have been cool instead of irritating. At least this only hits once and does not create cascading failures.

(no castbar, name inferred from Savage) Electrifying Witch Hunt

The lines on the floor left behind by Bewitching Flight expand and explode one by one at random, with circle AOEs dropped under four random player characters after each line but the last explodes. (When there are lines left behind by a clone, a north-south line and an east-west line go off at the same time.)

This is quite a long individual mechanic, since nothing else happens until all but the last line is gone. It is dull, since the circle AOEs prevent strategizing around the areas that explode first, instead requiring extended movement. It is lacking visual clarity, since the expansion and glow of the line that is about to explode are quite mild until late in the process. And the misalignment of Bewitching Flight with the floor grid compounds the issue, since the only consistent visual reference for where a line will expand to is the lines beside it, which may already have disappeared. (Especially if the Sidewise Spark cast during the last line's expansion does not cover the last line, leaving a small safe zone.)

Sure, I can do this, but it is boring. And the length of the mechanic makes the boredom grating. This is not the "use sparingly" I mentioned when reviewing Infernal Spin in M3N.

With a clear visual indicator, the casual player would have been able to comfortably handle the Savage line explosion order; the only reason it is not great to ask them to look so far afield here is that you made the indicator spend most of its time being relatively indistinct. That explosion order would have made this a lot faster, freeing up time for more interesting mechanics and preventing it from being extended movement boredom.

Shadows' Sabbath (Clone Sequence)

(This is very similar to Twilight Sabbath in the Savage version.)

This mechanic does allow the player to optimize by placing their character in the center of the arena to make the required movements for each Sidewise Spark very small. Unfortunately, the deliberately obscured clones mean that I wait for each clone's mane to appear in boredom and annoyance, rather than enjoying the casting-friendly sidesteps.

And for players who cannot reliably discern the tilt of each clone's mane, this is a reactive mechanic! If you do not give them the visual information they need until each clone is about to resolve, or they have to spend longer looking at a clone to find out which side it will hit, of course the mechanic becomes reactive for them. And both of those compound in their own way through the sequence, which can make the final Sidewise Spark from the boss reactive as well.

Witch Hunt

This bears no resemblance to either of the Witch Hunts in Savage, so it seems like a filler mechanic that for some reason is given the same name.

The pacing is only reasonable on the outside of the square spiral, since the player cannot be expected to memorize or "feel out" the snapshots instead of going off the attack animations in a regular duty.

Soaring Soulpress

This basic stack would be completely unremarkable, except that for some reason it uses the Sunrise Sabbath tower jump animation for its own resolution.

Final Phase

The HP% threshold to trigger this phase really suffers from the arena transformation being both long and exactly the same as the earlier Ion Cannon phases. The first-time player who enters this duty well after its launch may barely get to see that this is not the same as those phases, especially if a party member uses a melee DPS Limit Break to cut the extended healing requirement short.

Wicked Hypercannon

(The "temporarily no positional requirements" targeting ring indicator and boss debuff are good, but that is more about system visual design than about the specific mechanic.)

This is thematically cool, and I think it should have amplified that theme by introducing the Duty Finder population to the Wild Charge concept. (That is, a line stack that hits the player character closest to the source of the attack harder, traditionally requiring a tank to take the brunt of the attack in high-end duties.) That would have further expressed Wicked Thunder's anger at the party's survival, provided a stronger opportunity for the tank power fantasy of protecting the party, and gently added to the casual player's mechanical vocabulary.

The smaller platform forces all party members into the line stack already. The whole point of the mechanic is that she is blasting the entire party as a last resort. This already has an enlarged line stack marker, showing that the whole platform will be hit, and the line stack marker already has an arrow pointing downwards, normally to the target player character. You could have made a new Wild Charge marker by replacing that arrow with a red orb (from the tank stack marker) that is always over the closest player character to the source of the attack, and making the stack arrows between that orb and the source spikier and red. (Naturally, then, a double Wild Charge that requires both tanks would use two tank stack orbs.) By leveraging markers that the player already knows, the intuitive guess would be the correct one.

That being a concept introduction, I would not be too harsh with it. I would only have it hit the closest player character harder, and not so much harder as to instantly KO a non-tank; just enough harder that a non-tank will require healing to stay up for more than a few seconds, so that the casual player has the feedback to confirm their guess and tanks are encouraged to use their defensive cooldowns.

(Also, I would remove the circle AOEs dropped under player characters. They are overused in this duty as it stands, and they would be a distraction to teaching a new mechanical concept.)

Overall Impression

Making indicators deliberately difficult to see is anti-fun!

Aside from that, this duty is brought down by not being daring enough, missing multiple opportunities to present exciting and casual-friendly mechanics. As the final floor of a tier, casual players have the weapon blades as an incentive to repeat it for longer than the other floors, so it can afford to be slightly more complex than the rest of the tier. (In things that the player can actually improve at, not hoping they notice the hidden pattern in Fivefold Blast.)

On a broader scale, I find it strange that this duty's design draws so little from the first major phase of its Savage version, which historically is strongly tied to the Normal, and so much from the second major phase after the Savage-only arena transition. Historically, the Savage-only phase of the final floor of each raid tier is the main opportunity for challenge-seeking players to take on the difficulty of learning mechanics without inherent help and expectations from the Normal version, and conversely a major opportunity for duty designers to present an entire major phase without being constrained by the need for an adaptation that works in the Duty Finder context. And that historical position works well, since the player who reaches it is no longer brand new to raiding, so they have less need of help from the Normal.

Drawing mechanics from that final phase into the Normal version reduces the former's challenge and spoils some of the surprise, while diluting the first phase mechanics beyond easy recognition is strange and unwelcoming. Heavily diluted mechanics often wind up as dull filler even by the standards of regular duties.

Sure, Duty Finder does not do mechanic-specific planning and so will not manage the proximity baits of the Savage Witch Hunts, but Narrowing Witch Hunt / Widening Witch Hunt without those is literally a sequence of alternating donut and point-blank AOEs. You could have put that in as a sequence of two AOEs instead of four, followed by a basic spread, and the casual player would have figured it out. (Circle AOEs dropped under player characters wind up replacing a lot of party coordination elements when adapting mechanics, but there is such a thing as too much of them and there are other usable mechanic components.) I covered some other potential adaptations when discussing their diluted Normal versions. Just about the only mechanic in the first major phase of the Savage version that does not adapt well to a regular duty is Electrope Edge 2.

----------------

I do see why so many players initially enjoyed this Normal Raid tier. It has a variety of lore concepts across the duties, each duty has its own music for the first time in years, and M1N is a very strong start to the tier. But M2N is an unmitigated disaster, M3N has its visual annoyances build up over time, and M4N gets extremely boring with repetition as the player almost literally sees through the clutter and obscured visuals.

[Aurelle_Deresnels]

I will now continue my review of the design of the Patch 7.0 duties, in this subsection covering the high-end duties. As each of these has a corresponding Normal Mode, readers may wish to compare to my reviews of the corresponding regular duties, particularly for visual design which is often shared.

These duties are simply not for casual players. This is the planner's world.

----------------

Worqor Lar Dor (Extreme) (Valigarmanda EX)



(no castbar) Animation Tells

Unlike in the Normal, here the player largely overcomes the poor teaching of the animation tells, and even two of them being overly similar, by repetition and learning when to look for the animation tells. But the duty would still be improved by the same teaching and visual clarity suggestions I made for the Normal.

Cataclysms (Phase Additions to Animation Tells, Charring / Crackling / Chilling)

The fact that each point in the timeline with an animation tell also comes with one of these makes the duty harder, but also reinforces looking for the animation tells at those specific points.

Opening Phase

Spikesicle

For this to be good rather than have the icicles be irritating, the player has to know the second hidden pattern: that the center base of the boss's targeting ring arrow does not get hit by any icicles after the first two. This is a bit much to expect the player to notice in an Extreme, and fellow players can easily wind up not passing it along if they do not themselves struggle with dancing around the icicles.

Skyruin (Fire Phase)

Triscourge

Though it is not apparent early in the duty, the way that each phase empowers its own elemental debuff is thematically cool. The long debuff timers are also welcome, both to aid the player in learning the timeline and to allow the debuff mechanics to be staggered throughout each phase.

(no castbar) Volcanic Drop

The red text "A volcanic eruption is imminent..." to cue the player to look for a volcano certainly helps with progression, especially "blind progression" without guides or other outside information.

Despite the volcanoes being far from the arena, this mechanic is fine visually, since the player only needs to look at one volcano and can then infer the state of the other.

The two sets of small baited puddles are also okay, since the party can plan to move as a group, though many parties wind up dropping them on reaction instead. It only takes one party member who forgoes the plan to make the party react to their puddle, and the open space means they are not penalized for it. Indeed, parties often do not bother making a plan for it.

I would prefer if the party was forced to make a plan for this rather than operating on reaction, not just for my personal enjoyment but also as skill-building for those new to high-end duties.

Scourge of Ice (Fire Variant)

The player can do this by reacting to the overhead marker, like they do in Duty Finder, so this is more a thematic mechanic than anything else. Its only real contribution to the high-end nature of the duty is that stronger players can use the debuff from Triscourge to know which of the two random timings they have in advance.

Mountain Fire

Thematically, this is a very cool tankbuster that satisfies the tank power fantasy of protecting the party. The spectacle of it helps with that too.

But despite looking right at the spectacle, I do not enjoy it except in videos, because in the duty I am too busy worrying about whether my character is correctly aligned with the tower blocking the boss. If there were floor geometry references for each of the three positions, this would not be an issue. (Most line-of-sight mechanics do not ask for rapid judgement of the attack source's location, and so there is time to get the alignment right comfortably.)

The movement is almost exactly every other Global Cooldown, which is fine and even suits RDM's Dualcast, but the player has to wait to see Valigarmanda's movement before starting their own character's movement.

Scourge of Fire (Fire Variant)

A good mechanic; the heal check is appropriate for a scary Extreme mechanic, this is always before the permanent DOT of Tulidisaster, and the puddles combined with light party stacks force the party to make a simple plan.

Scourge of Thunder (Fire Variant)

There is so much room here that parties often wind up spreading on reaction rather than making a plan. In this case, that is difficult to fix, since the mechanic is also constrained by making the other phase variants feel appropriate.

Ruin Foretold (Add Phase)

Unlike in the Normal, here the party can plan out where to take the stacks, and the light party Wild Charge nature requires them to. The heal check nature of this phase encourages healers to think about how they can reach both light parties, which is a good thing, without the heal check being too difficult.

I do not like the alternating cones being so fast and frequent in any duty that is supposed to be repeated often, but I will cover that where they come back in Savage. There they are much worse. Other than that, this phase is fine.

Tulidisaster

A big, splashy, thematic end to the add phase heal check, culminating in the same permanent DOT from Normal. The trickle of persistent damage changes up the style of the heal checks for the rest of the attempt, which is a good thing.

Skyruin (Thunder / Ice Phase)

The random phase order is totally fine. The mechanics to deal with before completing the duty are not changed, only the order.

Thunder Phase

Scourge of Fire (Thunder Variant)

This is still a planning mechanic in its weaker single-hit form, and the basic light party stack is a classic for those new to high-end duties for a reason. The fact that it cares about levitating or not in the thunder phase is an amusing reinforcement of keeping the light party together.

Hail of Feathers

Being able to see the feather order coming makes this a lot more fun than it is in Normal, even though the mechanic is harder.

Having the party create a safespot by killing an add is also nice to sprinkle in every once in a while, since it creates different rotation considerations. (There is such a thing as too much, since short-lived adds too often can break the structure of a job's rotation entirely, and long-lived adds eventually stop feeling like adds.)

Scourge of Thunder + Scourge of Ice (Thunder Variant)

The fact that planned spread spots require two different plans for this definitely encourages parties to just do all of the Scourge of Thunder spreads by reaction. Players new to high-end duties are not yet used to holding two plans in mind, but they have no trouble bolting for an apparent safespot like they have done often in regular duties. Since the floor does half the work of spreading for them and there are four extra spaces, they are not often penalized for this, making it easier for parties to go along with that rather than building their plan execution skills. (Or to not bother making a plan in the first place.)

The two plans are not out of the reach of Extreme at all. As with the Volcanic Drop, this would be a better mechanic if it gave the party less space to encourage remembering the plans.

Thunderous Breath (with Arcane Spheres)

This is the Normal mechanic overlap. If there was more party planning in other mechanics, that would be fine as the thematic breather, but as it stands this feels a bit easy.

Ruinfall

The visual design is good, just like in the Normal, but little is added here.

Ice Phase

Scourge of Fire + Scourge of Ice (Ice Variant)

Having the tanks stay out of their light parties for their spread AOEs is not a difficult concept, so it does a good job of gently introducing the idea of variations on the light party.

(no castbar) Avalanche

Here the player does not even need to turn their camera, which is good to focus on the spatial reasoning of combined AOEs instead.

(no castbar, snowflake AOEs) Arcane Spheres

There are so many snowflakes here that parties resort to using their waymarks to create floor references for these, since the arena itself does not provide them. Getting the waymarks right for that purpose is quite the hassle without third-party tools, since they cannot be checked at all until well into the duty.

The spatial reasoning aspect of this is really diminished by the annoyance of needing to either estimate where they go or use waymarks for it.

Scourge of Thunder (Ice Variant)

There is even more room here than in the fire phase!

Ice Talon

Teaching the off tank to make sure they are second in enmity is a good thing.

Final Phase

Wrath Unfurled

The Damage Up on Valigarmanda is a thematic warning before the final Mountain Fire and the enrage.

Tulidisaster (Enrage Sequence)

This definitely had to be the enrage. Not only is it on-theme, it would have been a missed opportunity if you had not done it.

Overall Impression

This is a lot more comfortable than the Normal, and overall a mediocre duty that is too light on the planning requirement. It definitely feels like the true form of the elemental phases, especially with each phase empowering certain attacks, but the lack of floor geometry for the ice and "regular" phases is a drag.

Notably, this is a very short duty, at not even seven and a half minutes. If it was relatively intense for an Extreme, that time frame would be fine, but the ease of the mechanics feels like there is not enough material in the duty.

--------

Everkeep (Extreme) (Zoraal Ja EX)



Opening Phase

Multidirectional Divide

Despite not having direct floor geometry, the clear spikes for the AOE lines make it workable to find safespots near them, and that is all the player needs here.

Forward Half / Backward Half

This is a fine random variation to use in overlaps, though it is easier to remember as "go where the castbar says, and for Forward go into the sword" than to do the spatial reasoning of the boss turning around with the sword.

Regicidal Rage

Players new to high-end duties have to learn tether taking somewhere, and this gives them lots of open space to do it. Since the tanks need to split them, they also practice planned spread spots.

Dawn of an Age (Distorted Worlds 1)

Vollok

Launching straight into the swords on other platforms is definitely correct here. So is going straight to the combination of two distorted worlds with Half Full, since all the pieces are familiar from the Normal version. Since each tile only has one matching sword across all four distorted worlds, the player can focus on checking the safety of one or two tiles rather than all 16.

Greater Gateway

The fire and wind tethers are clever upgrades to the Normal version. The player can do the spatial reasoning about one direction from each platform, keeping the task from being too difficult for players new to high-end duties.

Chasm of Vollok

It is nice to see tile spreads returning, complete with their marker from E4S and E12S. Standard spreads would not have fit well on such a small platform.

Projection of Triumph (Blade Field)

Both of these mini-phases are a fun way to encourage individual planning.

There is a lot going on for an Extreme once the overlaps begin, but the player has ample time to see the point-blank and donut AOE chains coming and keep them in mind for the overlapping mechanics. The blades on the floor that activate these AOEs also provide the appropriate floor geometry.

Projection of Turmoil (Stack Line)

These mini-phases are a really cool way to introduce the idea of planning to stagger debuff resolution gently, giving the party a lot of time and the ability to do it through staggered positions in space rather than going directly to moving at specific times.

Once it is learned, it becomes a breather mechanic, especially if the party is using the "conga line" plan where those with frequent cast times do not move until near the end. I enjoy the distance heal check of that method, even though it is suited to new raid healers, because it creates the opportunity for skill expression of reaching all the way across the large arena through my fairy.

In the second of these mini-phases, the Half Full casts are a simple overlap while encouraging the "conga line" plan, or at least coordinated movement.

Bitter Whirlwind

Tanks are going to learn to use their invulnerability cooldowns with a plan, rather than holding them in case of emergencies, and that is a good thing.

Dawn of an Age (Distorted Worlds 2)

The two-platform setup of this is good at gently teaching players new to high-end duties to be aware of healing range, since the DPS players have to make a small but active effort to be in range.

Drum of Vollok

This is not difficult so long as the role with the Enumerations stands still well in advance. If they do not, they tend to fling their partner's character off the arena, which is a good motive for antsy Disciple of War and SMN players to learn to stand still.

The downtime is exactly the same for everyone.

Sync

The two platforms both affecting each other is a nice twist, especially the way it includes the tile spreads. In particular, here the tile spreads enforce planning, since there are no extra spaces.

Aero III (Wind Tornado)

Reminiscent of The Cloud Deck (Extreme) (Diamond Weapon EX) in making the party coordinate to swap who moves when, though with role groups rather than light parties.

The angle of entering the tornado really matters here, which would be a problem if there was not both ample time and a convenient line between tiles to aim along. Since the time and the floor geometry is there, this teaches the player to be mindful of what is coming and not panic, which are both good.

Here, the downtimes are different for each role group, and so can mess with the player's personal cooldown usage a bit. I have definitely done the optimization strategy of using free heals to safely delay my Burning Chains tether break so that I can use Aetherflow first.

Actualize

I am not sure why this particular cast of the arena transformation raidwide comes with a knock-up. That seems like an oversight, as there is no mechanical reason for the forced downtime.

Dawn of an Age (Distorted Worlds 3)

The first sword AOEs leading shortly into tile spreads encourages the party to assign tile spread spots rather than reacting to each other. Some parties will wind up doing it on reaction anyway, but having a long time to see each other's positions and spread out during the Sync mitigates the dissolution of the plan.

(Otherwise, this phase is repeated mechanics.)

Actualize (Enrage)

There is nothing wrong with using a powered-up cast of the familiar raidwide as the enrage, but thematic enrages are definitely nicer.

Overall Impression

The best-designed high-end duty in Patch 7.0, with no major flaws and some clever mechanics. A strong contender for best overall duty design in Patch 7.0, competing only with M1N.

That I got bored quickly here is entirely the fault of job design, not duty design; nothing suitable for Extreme can challenge an Ultimate-level healer, and the current healer job design is not up to the task of filling in the gap.

--------

AAC Light-heavyweight M1 (Savage) (M1S, Black Cat Savage)



As with the Normal, this floor is great except for being slightly too bright. In fact, the brightness change I suggested there is primarily for this version.

Opening Phase

Quadruple Crossing

I like this. It turns the Normal version's Black Cat Crossing into a party coordination mechanic, a dodging mechanic the party has some control over, and a part of the heal check all at once.

Here it takes the place of the opening raidwide, both launching right into the duty mechanics and getting the player to practice the AOE baits in this form before it becomes complicated by Leaping, clones, and Nailchipper. This is an appropriate amount of advance practice, enough to keep the later forms from being intimidating but not so much as to create a boring opening. And since the player will be doing their opening burst during this time as well, they are encouraged to learn how the almost three second gap between each hit and the next fits in with their job rotation.

Nine Lives

This warning cast (indicating that the next mechanic will be stored in the next clones, appearing before every Soulshade) is not strictly necessary here in Savage, but it is very thematic, and for a first floor it is not a bad choice. The warning reminds the player to remember the next mechanic for later, creating lenience in the duty's requirements of timeline knowledge and attention control. Some lenience in those things is necessary at this difficulty, though naturally much less than in the regular duties, and this sort of warning cast is one of many tools to create that.

One-two Paw

Finally a timing that feels right for this, rather than the Normal delaying the first snapshot from the end of the castbar. The time between the first and second hits is not so tight that the player must learn the snapshots rather than reacting to the first animation, but is tight enough that the player must be ready to go rather than hesitating, which is the right speed for a very simple concept like this at this difficulty.

One-two Paw (Double Clone)

A fine simple spatial reasoning mechanic, which is not actually a memory mechanic since the player can use their character's current position as a reference for the second safespot of the One-two Paw being released. If the player struggles with doing the spatial reasoning in real time, they can memorize the possible patterns or a condensed rule outside the duty, making this not an unavoidable spatial reasoning test either.

The time given is quite long, including both the clone awakening and a second Nine Lives to warn of the next stored mechanic. For stronger players and/or repeat completions, no longer needing the warning cast, it is up to job design to fill that void.

Double Swipe / Quadruple Swipe

Partner / light party stacks are a classic random variation in high-end duties, and this is a clear and thematically appropriate name that the player can process quickly. This is good, since they have to process it quickly coming out of the double clone One-two Paw.

Leaping Quadruple Crossing

The player has seen Leaping Black Cat Crossing in the Normal, so what this does is immediately quite clear. But they must remember to dodge into their planned positions for the stored Swipe, which is just enough to keep them from treating it the same way as the opening.

Bloody Scratch

This physical raidwide is scary in this form, always coming directly after unavoidable damage and requiring mitigation for Disciples of Magic to avoid KO at full HP and 10 Item Levels above the minimum. Teaching the party that they have to mitigate is welcome, even though it results in some frustration for new raiders and those in their parties. (Especially since the healers themselves are more likely to wind up with KOs from lack of mitigation.)

Mouser (Mouser 1)

The gradual arena transformation itself feels very good here. Going down to four tiles, all of which are already fragile, emphasizes the deadly dance and prepares the player for the lack of extra tiles, while the maximum of two movements to evade all the hits and the long cast make it not too difficult for new raiders.

Once the player is aware of the hidden pattern to start on the south-west central tile and look at the south-east central tile, they only need to remember one item: whether that south-east central tile gets hit once or twice. And here in Savage, you can ask the player to find hidden patterns or learn them from fellow players within reason, so this works out.

Elevate and Eviscerate

The random selection of whether each DPS will be targeted in this phase and each tank or healer in Mouser 2, or vice versa, is perfectly fine. For the task of completing the duty, it largely evens out since each player character is chosen exactly once unless there are KOs or disconnects. For those seeking parse runs, they generally want to skip the downtime entirely by getting the random variation where they are selected late in Mouser 2, then KOing the boss first, but duty design should not be warped around facilitating the perfect parse run every time.

The random order within each role group is also okay, though it can get to be a bit much for players who enjoy precisely mapping out their plans for playing their job in the duty. There are eight possible times where they could take the downtime and two possible clone orders in the Leaping phase, creating 16 possible timelines to work with. Not only would the player finish gearing a role before reaching 16 duty completions, but the downtime can force the player to leave a major personal cooldown unused, thus affecting their timing for subsequent uses for the rest of the duty and encouraging them to make separate plans for that case. (All these downtimes are outside of raid buff windows, which is a necessity given the "2 minute meta" in current job design.) Obviously the knock-up makes it difficult to employ a bind and permit the player to continue their rotation, but the effect is worth noting.

As for the attack itself, I hope your design intention is for the player to realize they do not need to know whether the clone is preparing the knock-up version or the downward punch version. (The "braindead" strategy is to put one's character at one corner of the chosen strong tile and facing inwards, causing both versions to land on that tile.) Party members can leave the clone under the boss from when they were targeted, so the player cannot reliably see the clone's stance and glowing arm, hence the popularity of a strategy that does not require them to look at the clone at all.

One minor pain point for optimization-oriented players and those with bad ping / reaction times is that this mechanic is not hard enough to force players to plan out who will take which strong tile and in what way, as an inherent result of the random selection order and cast variation necessitating time for the selected player to position and face their character. This leads to parties operating on "use eyes" reaction to each other instead, especially during progression, which is annoying when trying to cast, do positionals, or just not get one's character swept off the arena by someone making a last-moment tile change. Not every mechanic can avoid this result, but it is worth trying to keep it from happening too often.

For all its flaws, this is still mostly a fun mechanic.

Shockwave

Since this knockback goes through knockback immunity, unlike in the Normal version, it enforces for the party that they must avoid breaking tiles with Elevate and Eviscerate in order to leave themselves room for this. The visual for which tiles will be restored first is not particularly dramatic, but it does not need to be since the player has plenty of time to look at it and is expected to plan to look at it. It is clear enough for its job.

Grimalkin Gale

Tries to enforce that the party plan out spread spots and split up accordingly using the Shockwave, with moderate success given the light hand on a new-raider-heavy population. Some parties do still spread by reaction after the melee pairs of each light party gapclose in and the ranged pairs stay out. For me, with a full plan and a strong desire to avoid adjustment loops, moving my character to a planned location immediately and stopping there usually works to get my partner to move accordingly.

Memory Phase

Since this phase centers on working memory and spatial reasoning, I will count out items in working memory over the whole phase.

Leaping One-two Paw

The mechanic itself is familiar from Normal.

The player must look at which clone is spawned, then transfer the leap (direction shown by a buff on the boss, though not for long given the spatial reasoning task) to the clone. This creates one item in working memory, the clone's leaping position. It looks like two items initially, since the positions are intercardinals, but the player can either use the intercardinals as a set or place the number waymarks over the possible leaping positions to compress this into one item. (The latter method is very popular, since it also provides a reference for the clone's Leaping Quadruple Crossing resolution point.)

They must also remember which side is safe first, as in/out since all clones in this section face into the center of the arena, creating a second item in working memory.

Leaping Quadruple Crossing

Familiar from earlier, except that the boss turns to the center of the arena and makes a second Leap from its earlier position. This makes checking the direction harder until the player realizes to either re-orient or use the buff on the boss.

Storing this clone's leaping position creates a third item in working memory.

It looks like there should be a fourth item here, to remember which clone has which cast since they activate in a random order. However, since they are stored in a fixed order, the player can use the order of the items in their working memory to reconstruct which clone has which cast. (The north position will always be tied to the north clone, and the south position to the south clone.) As a result, this phase just barely scrapes by the three item rule, which is part of why typing out the stored items into party chat is so popular. (The other reason is that players who are comfortable with the spatial reasoning can help their party members by doing this.)

The two timelines from different clone orders are fine. The party will want to have a different healing and mitigation plan for each, but they have ample warning for which to use once they see the first clone activate.

Tempestuous Tear

These light party stacks force the player to not just remember the stored clone position and first safe side, while also being the only major magical damage in the entire duty. Magic-only mitigation tools get piled on here.

Nailchipper

Again forcing the player to do more than just remember the stored clone position, and also to potentially bait in the opposite role order for Quadruple Crossing. The hardest mechanic in this duty, so it is probably wise that this comes with only a single item retrieval from working memory.

The size of these spreads makes me think that Quadruple Crossing is best baited on the cardinals, leaving the intercardinals safe, to allow the role group with Nailchipper to leave ample room for the other group. Having this sort of strategic consideration is a good thing! (Unfortunately for my own duty completions, that is not what Aether Party Finder does, and the Normal version does not have the flexibility to suggest it.)

Mouser (Mouser 2)

All the considerations are the same as in Mouser 1, except for the addition of Overshadow / Splintering Nails.

Overshadow / Splintering Nails

Party stack or role stack is also a recurring random variation, and this adds a moderate heal check to the phase. There is enough time for healers to set up the party healing between their own Elevate and Eviscerate hits, though it makes them think about doing that, which is good.

Final Phase

Raining Cats

This is the type of mechanic where tank invulnerabilities are always going to be the preferred method unless the duty forces the party not to use that method. It is simply more consistent for the party to involve fewer players and fewer steps in resolving the mechanic, tethers or no tethers, and more consistency results in a greater chance of duty completion on each attempt. Which results in most parties not practicing the "normal way", and therefore having trouble doing it if the tanks use their invulnerabilities earlier to salvage an attempt.

As long as you know that, this mechanic is fine.

Predaceous Pounce

When reviewing this mechanic in the Normal, I wrote "on a purely mechanical level it feels like the sort of thing that is put in a Normal to replace a Savage mechanic that cannot be usefully adapted for casual play." So why is it here in Savage?

This is not interesting to do at a basic level, and offers little to optimize around. (Trying to remember all the jumps would be excessive as a memory mechanic, which removes optimization options, plus the One-two Paw overlapping the end limits the player's choice of safe locations anyway.) It is boring. Its saving grace is that raiders so rarely see it, since it is the last major mechanic of the first floor, and so it is often skipped by combination of gear advantage over the minimum Item Level and better job performance than is required for the duty.

Mouser (Enrage Sequence)

As rare as it is for the player to see this, it is very cool. Not only is it thematic to take the floor out from under the party using the pre-established gradual arena transformation, but it is still worth it for the player to do their best to track the sequence in order to dodge for as long as they can before they run out of tiles.

Overall Impression

A decent first floor, if on the easier side even for the first tier of an expansion.

It is worth noting that the unavoidable damage to non-tanks in this duty is almost entirely physical damage. In such a duty, the difference between mitigation tools that mitigate only magical damage and those that mitigate both physical and magical damage is very large. In duties where that damage is entirely magical or almost so, the difference between those mitigation tools is small or even irrelevant. Just like Anabaseios: The Tenth Circle (Savage) (P10S) Harrowing Hell, the duty design choice to present a largely physical heal check is what made the job design difference in tanks' party mitigations become a problem. (I could write a whole other post about good and bad homogenization, but that would be outside the scope of this review.) With Patch 7.10, you granted DRK and GNB some physical damage mitigation on their party mitigation tools, but that was not available to them in Patch 7.05 when you released this duty.

--------

AAC Light-heavyweight M2 (Savage) (M2S, Honey B. Lovely Savage)



This arena's floor is very well designed for the mechanics of the duty. There is no grid because there is no need for a grid. The cardinals, intercardinals, and even half-way points between cardinals and intercardinals are all marked with sharp contrast from both the regular honeycomb pattern and the blue Beat stage. The triangles that mark these at the edges of the arena are perfectly sized to provide reference points for dodging every Tempting Twist, Honey Beeline, and their Splinter follow-ups without telegraphs, enabling the player to precisely find their spread and pair spots for their party's strategy. As a bonus, these also mark every possible Groupbee spawn position.

Opening Phase

Call Me Honey

A classic opening raidwide, but also necessary to show the party how hard it hits before Rotten Heart. Due to the Beat raidwides, it does not come back until then.

Splash of Venom / Drop of Venom

Spreads and partner stacks are another classic random variation pairing for memory mechanics, and this is the only type of memory mechanic in this duty. (Including the Beat versions that give hearts instead of high damage, Spread Love / Drop of Love.) Since there is only ever one of these stored at a time, this duty is comfortably under the three item rule.

However, this memory mechanic is overused in the duty. Six times in eight minutes gets boring, especially since the opening is forced to have two of them back-to-back to show the player the Savage forms of the Splinter AOE patterns. It also does not help that the memory mechanic is never combined with anything other than Tempting Twist / Honey Beeline in its resolution, though that would be fine if not for the overuse.

While the cast names here are not blatant about the number of hits, they are still quickly processed so they are fine.

Tempting Twist / Honey Beeline

The follow-up Splinter honey blob patterns here should have been in the Normal. Duty Finder could have done them fine, even though the casual player will generally not appreciate how cleanly they lay out the spread / partner spots and how little movement is necessary for Honey Beeline.

Killer Sting / Stinging Slash

Since there are five points where the boss casts one of these two tankbusters at random, there are 32 different possible timelines for tank mitigation. But the total lack of hidden patterns denies the tanks, and by extension the party, most of the planning possibilities around invulnerability usage. This is a good example of some randomness making the duty more fun, and too much making it less fun.

Honey B. Live: 1st Beat (Beat 1)

You made this Beat only force the party to take 23 hearts, not the maximum safe 24 hearts, because on some level you knew that the party making a plan and executing it correctly is not enough to guarantee that no extra hearts would be taken. As I explained in the design principles section, that means the mechanic is not appropriate for the deadly dance of high-end duties in the first place.

On the other hand, I do enjoy how the Beats have a different style of heal check, with the individual mechanics hitting more lightly but combined with the heart DOTs. This is an interesting way to vary the structure of healing requirements within a given difficulty.

Centerstage Combo / Outerstage Combo

These are good.

The cast name is both thematic and quickly processed for the first hit, and the structure offers optimization for every role that has movement-dependent optimization. (Only the cross AOE that is always the second hit requires leaving melee range, the pacing is fast enough and far enough to require instant casts or healer extended slidecasts but not for annoyingly long, and the donut AOE is a healing opportunity.) Most uses also encourage the player to dodge in a way that prepositions their character for the upcoming mechanic.

Love Me Tender (11 Towers)

The fact that 11 tower spots are used randomly out of more than 11 possible locations prevents the party from fully planning out this mechanic by assigning player characters to tower positions, priority order or otherwise. The party does not have the advance knowledge to work out which remaining locations will be used.

The fact that the initial eight hearts for this Beat are assigned completely at random (outside of not giving any player character more than two hearts) prevents the party from creating a plan that sufficient players are willing to learn and execute by assigning player characters to the timing of tower spawns.

(Planning it that way is theoretically possible, most easily by having the first eight towers be taken by a fixed order of party members and then going back to the top of the list for the priority order to take a second tower, with everyone in the center of the arena when not taking a tower. But the fast debuff checking required for the priority order is more suited to Ultimate, since it must be done either before any of the towers or with the ongoing towers in mind, and with small icons that are not really meant for checking other party members' debuffs. No one really wants to be at the top of the list, since it is more work and it makes them less likely to have personal leeway on the reaction sequence, while their party members at the bottom of the list will never be reached in the priority order. That method does not care about melee range at all, and even encourages leaving melee range early to help the party count towers, so players dislike it for the sake of trying to meet the damage output requirement. And of course, it requires thinking of it at all, which is counterintuitive and well beyond most players at this difficulty level. I thought of it while doing this review, not in my many weeks completing this duty every week.)

Technically this mechanic is plannable, but not within a reasonable effort or in a pleasant way. As a result, parties resort to roughly prepositioning based on their planned clock spots or their Honey Beeline spread spots before the towers begin, and then having each player react to the appearance of towers near their character.

The problem here is not that they are reacting to the towers - the 10 seconds between a tower's appearance and its resolution is plenty of time. The problem here is that they are reacting to each other's choices, both of whether to take a tower and of potentially leaving part of the arena unattended entirely. So exploded towers and towers taken by two player characters still occur without anyone making a mistake, which is not an acceptable result in any high-end duty.

Regardless of whether you intended this to be done using that thoroughly unpleasant plan or by the party reacting to each other's choices, this is a fundamentally bad mechanic. You must ensure that a reasonable and enjoyable plan exists for every single mechanic in every single high-end duty.

Loveseeker

This is such a basic AOE that I see its role as pushing the player characters out of the center of the arena before the reaction sequence, whether that is meant to push them closer to the edge for their own benefit (away from the moving hearts emitted by the boss), to their detriment (towards the random moving hearts from the edge of the arena), or to put an endpoint to the planning method for the preceding towers.

Love Me Tender (Moving Hearts Reaction Dodging + Stack)

This is less of a visually overwhelming mechanic than it is in Normal, since the pink circle puddles are not included and the party has the opportunity to practice and plan. But that does not make it not a reactive mechanic.

Here, in theory, the party can plan to place the non-stack group (with three hearts each) between two of the fixed spiral arms from the boss, the stack group (with less than three hearts each) between a different two of the fixed spiral arms, and have them each follow behind an arm slowly at a slightly smaller radius than the edge of melee range. I have gotten parties to do this, and it significantly reduces the disruption from the randomly baited hearts coming from the edge of the arena. Frankly, in a party full of players at my skill level, and who know that fact, it would almost eliminate that disruption entirely, as the slow stutter-step movement with tight control from the party leaves only a small range of angles from which a heart baited on a group can still block that group's path several seconds later.

But even in that best case, such a plan does not entirely eliminate the disruption. So when it does happen, each player must make their own judgement on which way to dodge a stray heart and how far they have to move - the party cannot make and execute a plan that keeps each group together, because that would rely on exactly matching individual judgements of angle and distance. Those individual judgements are not themselves particularly reactive other than for hearts hidden by the stack, since the player can see each heart coming in peripheral vision and filter out the fixed spiral pattern. But once a group is forced to make those individual judgements, they must then react to each other to bring their characters back together after the stray heart passes by. As before, this is an unacceptable result in any high-end duty.

And in practice, the situation is much worse than this, because most parties do not follow this partial plan.

First, the format of the slow movement required will not occur to most players at this difficulty level naturally. The vast majority of mechanics do not penalize moving fast, so the player defaults to thinking of dodging mechanics at their character's full running speed. There are no puddle drops here, which is the usual way that mechanics enforce and suggest stutter-stepping while also providing the edges of the puddles as references to the player for their next movement. And even at the Ultimate level with those references, parties learning TOP Pantokrator usually make a mess of the puddle drops for quite a while, since one player overshooting affects their entire light party.

Second, the presentation of this mechanic pushes players away from that movement pattern. Since this starts during a raid buff window, and BLM did not have Ley Lines flexibility in 7.05, both BLM and PCT players do not want to move their characters away from their personal area buffs. And the fixed spiral arms are hidden by the randomly baited hearts, pushing the player's attention to reacting - like they did in the Normal - in early progression. Once they are in a reactive mindset, that makes it less likely for them to discover the hidden pattern in future, though it is not a complete dead end unlike Barreltender in Tender Valley.

Third, if the stack group is not already together, they must react to who gets the stack, and then to each other in how they bring their characters together. All this while the nearby hearts are obscured by the stack. (Unlike in Normal, the heart stacks here do not give more than four hearts if the maximum of five eligible player characters stand in it, though who gets the "free heart" for the remaining part of this dodging sequence is random.) This further pushes the player into reacting in early progression, and if the plan is disrupted.

Fourth, even one party member who does not follow that plan will bait several stray hearts on top of the direct confusion, dissolving the plan into every party member reacting individually. In high-end duties, one player's not knowing the plan or execution failure collapsing the plan for the whole party is perfectly acceptable, and often even necessary. But if the duty is well-designed, the feedback from the duty reinforces the importance of the plan to the party. Here, the feedback from the duty drives the party back into reacting and away from the plan. In turn, this compounds by creating more and more stray hearts until it becomes a reaction time pressure mechanic.

Fifth, this mechanic is a recipe for players getting angry at each other or quitting without noticing the possibility of planning. Those players who have low ping, good reaction times, and comfort in bullet hell games progress quickly through this mechanic and the rest of the duty, since the duty is too easy and repetitive for a second floor Savage with the reactive mechanics excluded. They do not want to hang back and make a plan, they are inclined to continue progressing the Savage tier. (Even for the occasional failures that they themselves make, they are often inclined to look at them as a personal failing rather than a structural problem with the mechanic.) The duty is not hard enough to push them into planning regardless, and frankly it would have to be harder than an Ultimate to overcome the counterintuitiveness of the partial plan.

Meanwhile, those players who struggle with this mechanic with no plan are forced into doing it in the fully reactive form by even a single party member who feels that way, resulting in them failing it frequently. And then that party member may well shame them for getting their character hit, since healing the boss and giving it a Damage Up affects the whole party. This is a very discouraging experience whether or not they come to perceive the possibility of a partial plan, and instead encourages them to respond angrily to the party member who shamed them. (Whether over the shaming itself for their reaction time, or for neglecting and/or refusing the partial plan.) Even parties with no significant differences in reaction time can wind up sniping at each other over individual failures, as it takes serious contemplation to realize that the party can never truly master the mechanic.

For all of these reasons, most parties treat this mechanic as largely reactive, with either no plan at all or only a general area for the stack group.

Again, this is a fundamentally bad mechanic.

On a personal note, the reactive nature of doing this without the full party on board with the partial plan puts noticeable physical stress on my arms, due to the party's reliance on my individual success. The towers were less so, since fellow party members would move their characters away from my glamoured-for-visibility character, but my party cannot help me in that way here. Early progression of this duty, doing this over and over again in quick succession, was not pleasant.

Alarm Pheromones (Alarm Pheromones 1)

"Grand Octet, but bad."

That is how a friend put it to me, referencing the UCoB mechanic with eight divebombs, and I completely agree.

This is the same as the Normal version's Alarm Pheromones 2, the Random Baits "pattern", except that in Savage the knockback from getting hit by a Groupbee goes further. (Making it more likely that a single hit will put a character into the death wall, and therefore making the mechanic cascade faster.) The increased harshness of the penalty is not the issue, nor is the mechanic being unsuited for Normal Mode.

The issue is that this mechanic does not fully yield to planning either.

Suppose that the party approaches this mechanic on reaction, just like in the Normal. Then it is reactive and failure-prone for all of the reasons I covered in reviewing the Normal.

Suppose instead that the party adopts the "Mario Kart" strategy, which is running along the edge of the arena as a group to stick together without having to react to each other. (This method is sometimes employed to have baited attacks pass harmlessly behind the party, and other times to create an even spacing of objects dropped on player characters for later usage.) Initially that is an improvement, but true Mario Kart does not work here, since the lack of advance knowledge of the order means that the party can find a Groupbee blocking their path no matter where they start. Once that happens, the player must again make an individual judgement on whether to continue forward or stay back, just like with the moving hearts earlier. As a result, the party becomes separated in the same way, and must either react to each other to bring their characters back together or revert to approaching the remaining divebombs on reaction. In the former case, the party can elect a member to try to stick to, usually the main tank for melee uptime reasons, but then still must react to each other in a more limited form. In the latter case, again the plan dissolves, for analogous reasons to those regarding the moving hearts.

Suppose instead that the party adopts the "box" strategy, splitting the party into groups with widely separated "boxes" that they each start in and try to dodge in. This is an improvement in the average visual processing demand, since most Groupbee baits will wind up only going through one "box" and the lines wind up less cluttered, but it is not an improvement in the worst case. High-end duty plans must be reasonable in the worst case. Further, the judgements on dodging each Groupbee are still individual, so each player must still react to the choices of the other players assigned to their box.

None of the available plans eliminate the reaction time pressure, since they all include the party reacting to each other, and operating entirely on reaction creates reaction time pressure as it does in the Normal. Yet another fundamentally bad mechanic.

That does not mean that you cannot have high randomness or gradually revealed information in divebomb mechanics. Grand Octet does both and is fine. But Grand Octet gives the party enough information in advance to be fully plannable, which is why it works. There, the player only ever needs to react to the boss's choices of random variations, and they have enough time to do so at the Ultimate level of preparation.

Adding to the annoyance of this mechanic, it is not only an uptime mechanic but also right before a raid buff window. As a result, the KOs and Damage Downs sustained from failure here have an outsized impact on the party's damage output, which matters to completing the duty here in Savage. (And moving reactively to avoid the Groupbees often disrupts the player's damage output, since that is inherently not planning.) This makes the party discouraged and annoyed over mechanic failures that are not really mistakes, and even regularly leads to parties deeming the attempt ruined and running their characters into the death wall to try again.

On a personal note, my party cannot help me much here either, so this and the moving hearts create two physically stressful mechanics in close succession. Progressing Beat 2 was really not fun for me, not because of anything about Beat 2 but because of getting there. I had to stretch and eat far more than I should have for the amount of raiding time I was putting in, on top of finding these mechanics annoying.

Honey B. Live: 2nd Beat (Beat 2)

This mechanic is nothing special, but on an individual mechanic level it is okay. Of course, it does contribute to the memory mechanic overuse I mentioned earlier.

Since there is no reason for the party not to put both heart stacks together, they generally use that to have all the 0-heart player characters move as a group and have all the 1-heart player characters move opposite them. This was a predictable result, especially as the gear advantage increases in the Party Finder and Raid Finder populations, since for pure duty completion the benefit to consistency of learning fewer "roles" and avoiding reaction to the puddles and the stacks outweighs the small damage loss of slightly more movement. For stronger players who can handle learning more "roles" and processing information from the boss faster, this can be irritating as it denies them the opportunity to keep their character still for personal optimization.

Alarm Pheromones (Alarm Pheromones 2)

Much like Beat 2, this is an individually okay mechanic that contributes to the memory mechanic overuse of the whole duty.

Having to estimate the space available from the Groupbee lines alone gets a little irritating in the tight space, particularly for the Bee Sting role group stacks at the end. On the other hand, the random selection order here is purely a good thing, since the player can plan out handling the movement for each of the four possibilities and their job without the cooldown-blocking annoyance or timeline profusion of M1S Elevate and Eviscerate.

Honey B. Live: 3rd Beat (Beat 3)

Other than even more use of the memory mechanic, this is actually pretty good.

It is mostly about assigning positions, keeping the party's plan in mind at all times, and working towards one's next needed position during the Combos. Plus stronger players can do some individual optimization even if their party is not up for the more demanding movement of the melee uptime plan, which makes it less irritating to be in a group that prefers the easier plan.

Rotten Heart

In principle, there is nothing wrong with having phases exclusive to high-end duties outside of Ultimates and final Savage floors. (So long as the full story is still available through casual play, as you learned with the Coils of Bahamut, and the phases are designed with care for the player's learning experience.)

But this is 90 seconds of boring in a 10 minute battle, measured from the end of the starting castbar to the enrage. If the player is not currently healing, all they have to do is stand in their clock spot, step into the center of the arena when their debuff has a party-agreed number of seconds left, step back out to their clock spot, and perhaps use their party mitigation. Even if the player is healing, the heal check is not that difficult as soon as the player realizes to stagger their AOE healing and mitigation cooldowns.

For comparison, E12S Terminal Relativity is 63 seconds measured the same way, with ramping damage and more frequent hits, and that in an environment of significantly more difficult jobs and less non-healer healing. Sure, that is a final Savage floor, but even Duty Finder players can handle more than "here is a striking dummy for 90 seconds, except you step into the center of the arena briefly at a specific time, step back afterwards, stand mostly still otherwise, and maybe use a mitigation tool".

(I have heard some players call this "newbie's first Curtain Call", comparing it to the final mechanic of Asphodelos: The Fourth Circle (Savage) (P4S) due to its placement at the end of the duty timeline and its successful resolution necessarily being based on having each debuff not quite expire. I call it "newbie's first Patch" based on the original O12S recurring mechanic, focusing on the partner-based debuff removal and the interaction between the fixed damage timings dictated by the boss and the variable damage timings arising from the party's plan and execution in dealing with the debuffs. Both of those had more going on, and even then Curtain Call was boring for non-healers.)

Exclusive phases should feel special and exciting through their mechanics, even if they are not all that difficult. Rotten Heart misses that mark.

To make matters worse, by the time the player can reach Rotten Heart, this is not the only boring section of the battle for them. The heavy repetition of the memory mechanic has made its teaching section rote and also boring, and that is the entire first minute of each attempt at the duty. As a result, at minimum one-quarter of the battle timeline is taken up by boring mechanics, even if the player does not reach the point of boredom during the annoying mechanics.

Sheer Heart Attack

The thematic enrage of charming the party is a very nice touch.

Overall Impression

That the bad mechanics from M2N made it into Savage is astonishingly awful - the mechanics do not yield to planning either, violating a fundamental expectation of high-end duties! And outside of those mechanics, the duty is mechanically too easy and too repetitive for a second floor Savage. This is another reason that I chose this duty and its Normal version as my redesign examples.

--------

AAC Light-heavyweight M3 (Savage) (M3S, Brute Bomber Savage)



Just as in the Normal, the floor markings here are oddly lacking in usefulness. Fuse or Foe is telegraphed the whole time. The only use of this floor geometry is the in/out boundary for Quadruple Lariat / Octuple Lariat, and that only indirectly at certain points where circles meet. This is a needlessly annoying choice after putting in the effort to give this floor internal geometry, and becomes more annoying here due to the higher penalties for failure.

Opening Phase

Brutal Impact

Here in the Savage, the player consistently gets to see this ramp up with each Doping Draught, from four to six to eight hits. Even as a DPS, they get told to mitigate accordingly, which encourages them to notice it rather than tunneling on their job. This is the main mechanic that really sells the boss getting stronger in basic power, not just presenting different and harder mechanics.

Knuckle Sandwich

While the added hits here are mostly noticeable to tanks, the ramp up has the nice effect of encouraging tanks to plan their invulnerability uses around the last two tankbusters instead of purely around maximizing uses. Some tank pairings get more out of this than others, which is an unavoidable result of the differing invulnerability cooldowns.

Quadruple Lariat / Octuple Lariat (Always Out)

Partners / cone proteans is a classic random variation, and the number of hits in this cast name is quickly processed.

The only thing I would change about this is the name; it makes mechanic explanations needlessly confusing due to the overlap with Lariat Combo. Unlike Lariat Combo, this mechanic does not match the real category of wrestling moves, and there are lots of other options.

Quadroboom Dive / Octoboom Dive (Always Proximity)

Partners / spreads is once more a classic random variation, and this is another good cast name. The boss's stance is very well animated here, clearly indicating which side he will dive to for rapid processing without relying on the targeting ring.

I see so many melee DPS get their characters KOed for being too close to the proximity AOE, and that is a good thing at this difficulty. It teaches them to learn not only the plan but the timing to execute it well.

Barbarous Barrage (Barbarous Barrage 1, ends in Murderous Mist)

The excellent visual design for these towers shines even more here than it does in the Normal, using the panels on the outside of each tower to show how many player characters need to take each. All the pieces for this small puzzle mechanic are immediately visible to the party, and it is a good puzzle.

This is almost a satisfying mechanic as well, but I think having to adjust one's character position after each knockback is what prevents that. The player has to focus on aiming the next knockback rather than enjoying the sequence. This is not a bad thing individually in demanding continued focus, but it becomes disappointing since the Savage tier as a whole lacks satisfying mechanics.

Doping Draught (Doping Draught 1)

A long opportunity to raise and heal before an almost completely open raid buff window, with a spectacle to enjoy while the player does what should be a well-practiced burst rotation. The timing of the spectacle is a treat for strong players, as they will use their raid buffs while the boss is distracted by the Refbot. (Literally - the Refbot takes top enmity briefly.) Pressing Chain Stratagem while he is punching out the Refbot is easy, but it is also funny.

Quadruple Lariat / Octuple Lariat (Always In)

Introduces the fire around both arms as an alternate form tell for this and the Divebooms, which is not particularly high contrast but serves well enough here.

Also contributes to the open raid buff window without literally doing nothing for the duration, since there is no leaving melee range and DPS traditionally have the same spots for proteans and role partners. Healers can manage with their extended slidecast windows.

Quadroboom Dive / Octoboom Dive (Always Knockback)

Again introduces the fire around both arms, which makes the clear stance animation all the more important to be seen with them.

There is enough time to move one's character to a planned position after taking the knockback to the right general area, even with a little hesitation on when the knockback ends. This timing is about right for the difficulty; not the longer leeway time of Extreme and first floor Savage, but also not the constant tight control of Ultimate.

Tag Team

Having a separate cast to spawn the clones before each Chain Deathmatch is important and correct, since it gives the player time to turn their camera to put both clones on the screen at once.

Chain Deathmatch (Chain Deathmatch 1)

A good mechanic, that would be made even better by having floor geometry to show the edges of the Lariat Combos from the clones. Being able to use floor references to go exactly as far as needed would be a good opportunity for optimization.

The concept of having to take the hit is a recurring way to ask the player to maintain focus rather than doing what is usual for the mechanic it modifies - we have Beyond Death for a reason - and the presentation here is very on-theme for staged wrestling. Even the chains are clearly magical without being overbearing. (Showing only the chains relevant to one's own player character was correct and necessary.)

The timing is correct for the memory mechanic nature, having to store which clone to be hit by as one item in working memory. Some players may prefer to store it in their camera angle instead, by prepositioning in the middle and then pointing their camera only at the other clone to dodge that clone only, but the camera turn also takes time and that strategy does not work perfectly for Chain Deathmatch 2.

The way that this can be used to practice Chain Deathmatch 2 early in progression reminds me of using Hello World 1 to practice Hello World 2 in O12S progression; it does make the duty easier to progress, but that is a tool rather than inherently bad, and it is especially Party Finder friendly on individual-responsibility mechanics like this one since the whole party does not have to be aware of the later mechanic.

Quadruple Lariat / Octuple Lariat (Random)

Now the player must look at both the castbar and the boss's arms, even once they have fully learned the duty timeline. They have the time to do this, though it can get slightly tight for the difficulty if they have a particularly long movement distance from the random variations of a given attempt. (The Chain Deathmatch directly before the first use of this form will always have the final safespot opposite from someone's assigned position, making the "out" variation have them cross the arena. Again, better floor geometry would help, since it would allow the player to shorten the movement distance by prepositioning their character just inside that final safespot for Chain Deathmatch 1.)

Final Fusedown

Here, the fuse timings being distinguished only by length gets even more annoying than in Normal. The fuses on player characters are very small, and the player must check their own fuse and fuses in the arena rapidly to identify the random variation each attempt. (There is a hidden pattern, but that mostly benefits healers and ranged DPS.) They know that the fuse lengths matter, but seeing them is unnecessarily difficult. If you want to have mechanic indicators that are only visuals around player characters, those visuals need to be appropriately clear. (The gaols in The Weapon's Refrain (Ultimate) (UWU) are not great, but they are large and clear enough for what the player needs to know, which is just who has them. The monitors in TOP are awesome for visual clarity, giving the player everything they need to know including a crisp line for the edge of the AOE they are manipulating. Do more like that.)

Likewise, the lack of floor geometry for the size of the bomb explosions is worse here than in the Normal. The central safespot to wait out the explosion group the player's character is not in is quite small for something that must be estimated every time, but would be fine if there were reference circles with which to work it out.

The concept of this mechanic is very cool, extending the fuse concept from the Normal into something the party has to manipulate. It is just the visuals that get in the way.

Quadroboom Dive / Octoboom Dive (Random)

Now the player must look at three things: the castbar, the boss's arms, and the boss's facing. The clear stance animation is much appreciated, especially given the relatively limited color palette of this duty.

Fusefield

This is "newbie's first Curtain Call", with a priority order for assigning fuses thrown in instead of healers needing to leave healing range for their tether. Unlike Curtain Call, it only occurs once, which is good for keeping it from becoming too boring.

Having a big scary "not too fast, not too slow" debuff management mechanic every so often is a good thing to teach newer raiders that skill. This is slightly too similar to Rotten Heart to be in the same tier, but I would change that by changing Rotten Heart instead since that one gets boring more easily.

Doping Draught (Doping Draught 2)

Again creates an open raid buff window, this time with a potion, though not nearly as long a breather as the first Doping Draught.

Quadroboom Bombarian Special / Octoboom Bombarian Special

Having the breather window between Fusefield and this is important at this difficulty level, since both are multi-hit heal checks and the boss is now at full power.

Fuses of Fury

While this does have the larger safespots of Normal, and is mostly a thing that complicates the opening of Chain Deathmatch 2 (while the party is taking in the needed information), it would again be better with visual clarity for the fuses and the size of the explosions.

Chain Deathmatch (Chain Deathmatch 2)

Much like Chain Deathmatch 1, except that all party members must take the Murderous Mist hit and DOT so mitigation is advised. It is important and correct that the boss face himself for this Murderous Mist, so that the player can rely on its edges lining up with the exact middle and two corners of the arena.

The player still only needs to remember one item, since the other chain is always to the boss.

Fuse or Foe

Players chose to develop strategies that ignore the different fuse timings not just for better uptime, but to avoid the hassle and inconsistency of trying to discern length from very small fuses alone.

Barbarous Barrage (Barbarous Barrage 2, ends in Lariat Combo)

Here, the reactive structure of the random Lariat Combo is more annoying than in the Normal, and not just because it is higher pressure. There is also the inherent lack of precise prepositioning in taking the knockback, combined with having to adjust for that in reorienting one's camera. It gets to the point where I try to skip this mechanic entirely, and I expect others do too, just to avoid the reactiveness and loss of consistency from it.

This sequence is a big part of why I suggested showing both hits in advance in the Normal, not just improving the floor geometry.

Doping Draught (Doping Draught 3)

A thematic warning to the party to use one last potion before the enrage sequence.

Special Bombarian Special (Enrage Sequence)

Thematic enrages are cool. Even though this does not have a true soft enrage before the forced party KO, since it does not ramp up within the sequence, it has a similar effect on the healing plan: requiring healers to keep their focus on both healing and damage output until the very end.

Overall Impression

If this duty had been visually polished and presented as a second floor (with adjusted tuning), it would be excellent. Doping Draught is used to great effect here thematically, which also makes progressing the early mechanics of the duty easier; healers will have comparatively more tools to salvage mechanical failures before the true healing requirements are presented, along with the Doping Draught casts themselves as open windows to raise and heal. Likewise, in attempts to complete the duty for loot, recovering from mechanical failures is easier before the second Doping Draught than it otherwise would be.

As with M1S, this duty inflicts mostly physical unavoidable damage to the party, which creates the same considerations that I covered there.

--------

AAC Light-heavyweight M4 (Savage) (M4S, Wicked Thunder Savage)



The arena floor is in the same odd state here that it is in the Normal.

Bewitching Flight

Has the same visual clarity issues that I discussed in the Normal, and here it is not practical for the whole party to keep their characters near the boss for a better view of the visual indicator.

Electrifying Witch Hunt

The proximity bait indicator is appropriately clear, and by this point the player should have no trouble learning to already be looking at the boss when it appears. The only annoying part is losing the indicator for the edges of the second safespot when the first lines explode.

Those seeking the perfect parse run will always want the random variation that best suits their job's uptime considerations, but that is okay.

Narrowing Witch Hunt / Widening Witch Hunt

Having half the random variations make the whole party move more would be questionable, in regards to lowering the party's damage output too much to make all possible random variations present a similar difficulty to completing the duty... except that this duty's damage output requirement is only slightly higher than M2S, and job balance is an ongoing subject of concern.

Other than that, this mechanic is a little too easy for a final Savage floor.

Electrope Edge (Electrope Edge 1)

This is primarily a memory mechanic, and something of an odd one to count out. The Sidewise Spark at the end guides the player into realizing the hidden pattern that the two small explosions must have one on the east side and one on the west side fairly easily, since otherwise the mechanic would present either no safespot or extra room.

The oddness of the counting comes from the rapidity of the displayed information. It is not inherently obvious whether the player is better off working in the shapes of the Witchgleam casts or the locations being hit. The speed helps the player use their short-lived sensory memory as a reference, but puts time pressure on converting the shown shapes into location pairs.

Consider the player's ideal categorization of the items to be stored. At the end of the Witchgleam casts, they clearly only need two items: the two safe intercardinals, or alternatively the two danger zones. (Some parties use number waymarks on the intercardinals for easier storage, much like in M1S, though here it depends on their chosen strategy for Sunrise Sabbath.) But how do they get there?

After the first Witchgleam, the player is storing two items: the two intercardinals that were hit.

After the second Witchgleam, the player is storing three items: the one intercardinal that was hit twice, and the two intercardinals that were hit once. They know there are only three sets of Witchgleams in this mechanic, so they can rule in the intercardinal that was not hit at all as a safe zone.

After the third Witchgleam, the player must compare the final hit to their three stored items and identify which of the intercardinals in that final hit was also hit before. The hidden pattern that each of the second and third Witchgleams will reveal one of the danger zones works to their benefit even if they have not noticed it.

That ideal categorization stays within the three item rule, but it requires very fast conversion of the cast shapes into locations being hit. The casts are so fast that I would not be surprised at all by some players memorizing the six possible shapes of Witchgleam casts as an intermediate storage form, or even being entirely unable to do the mechanic short of trying to follow their party.

Personally I can do this, using a mix of shapes and locations. But if someone else cannot do it and cannot reasonably improve at it, that is still a problem.

Sidewise Spark

Here this also comes with four or eight orbs, indicating partners or spreads. These are clear enough through the clutter of the sparks, which have the same problems here as they do in Normal.

Partners / spreads is a classic random variation, and the floor tiles make the tight space work by providing exact references for the edges of the safe zone.

Electrope Edge (Electrope Edge 2)

This is almost a very good mechanic.

The player only needs to remember one item (how many times their character was hit by Witchgleam). Extending the concept of Witchgleam casts expanding the resulting AOEs to be something the party manipulates is cool and thematically appropriate. And the healing requirement is just enough to make the healers think about it while contrasting the light distance heal check here with the heavy short-range heal check of the Wicked Bolt into the Ion Cannon mini-phase. The temporary 5x5 grid is very crisp and clear, the player can learn to work out the orientation of the Lightning Cage AOE pattern quickly by looking at specific sections, and the position within a square not mattering is great for skill expression.

The one catch is that it makes the player do Sidewise Spark with their character off to one side of the boss, denying them a camera angle that allows for seeing her stance in her silhouette. As I mentioned when reviewing the Normal version, this is an unacceptably obscured visual indicator. The sparks should have been much closer to the floor to allow for this to work well.

Ion Cannon Mini-Phase

Ion Cluster

Allows the player to see which debuff their character has nice and early, so they can prepare themselves for the fast pace of resolving the Electron Stream casts.

The visual indicators for Negatron and Positron are well done. The blue and yellow colors could stand to be more distinct and perhaps a little less bright, but the colors are not necessary since they are also distinguished by whether the circles are crossed or parallel. This is the same across the debuffs, the visual effects around player characters, and the cannons, making it well unified despite the three different visual design contexts.

(no castbar) Stampeding Thunder (Platform Break)

It still feels bad to have to take a hit here in Savage, but a lot less so once I realized that whether I used Sprint did not even matter. With a full plan and the party keeping their characters away from the boss's targeting ring arrow for everyone's speed, my character takes exactly one hit from this with or without Sprint.

I do plan extensively to make my practical response time just a little bit faster, not just the prepositioning my character in the middle of the arena that is visible to my party members. I also point my camera either East or West, looking at the boss's targeting ring arrow on one side of my screen rather than the center, so that I can preposition my keyboard hand fully for one movement direction and preposition my mouse hand for the other. Plus, of course, prepositioning my eyes to already be looking at exactly the boss's targeting ring arrow well before she turns.

(Remember all the way back when I was reviewing Herpekaris, the first boss of Origenics, I described splitting up movement along a straight line between both hands for speed? This right here is that usage for speed.)

Is that missing some of the cool animations? Yes, it is. But when you make a mechanic about moving fast to avoid the KO from a second hit, and you do not build in enough advance warning to prevent that little bit faster from mattering, I am going to do it anyway. Even if taking an individual KO here did not cascade into a party KO, it is still not fun for me to be told "not fast enough" by the duty, and this is the sort of thing I can actually do to avoid that. If you want me to perceive fancy animations at all outside videos, do not put mechanics like this with them.

At least party members taking extra hits for the sake of uptime does not burden the healers here.

Electron Stream

This mechanic is almost great.

It has an appropriately toothsome healing and mitigation requirement, complete with a Wild Charge on each side to involve the tanks' personal mitigation and make the whole party respect the positioning. It has a little puzzle in working out how to safely place all the added debuffs, that feels different because the available space is so small. The design within the floor tiles provides reference locations for solutions to the puzzle.

But I do not like that the Electron Stream casts (the cannon hits) apply the debuffs with only five seconds to resolve them. I would have applied them earlier, whether simply with a longer timer or in an inactive form that gets activated by the cannon blasts, and had them resolve at the same time. (As I mentioned when reviewing The Interphos, there is no reason to limit the concept behind Code Smells to Ultimate!)

Five seconds is not too short to just react to something, and the player is supposed to memorize their plan by this point in Savage. I mean, clearly I do a much larger character movement faster for Stampeding Thunder just before this. But this mechanic does not allow for the same prepositioning and pure focus on large-scale movement.

Consider the potential solutions to the debuff puzzle.

The nature of the donut AOEs (Roundhouse Conductor) and the closest / furthest cones (Proximate Current / Remote Current) dictate that the party wants to resolve this on the inner part of the central remaining floor tiles, totally aside from concerns of melee uptime or character movement speed. A party could decide to run the cones and the Collider cleanses outside the donuts, but they really do not want to. (In fact, Aether Party Finder uses a strategy that does not distinguish between Roundhouse Conductor and the point-blank Spinning Conductor at all, in part because those debuffs are not that visually distinct from each other at speed.) As a result, the character positioning precision requirement is inherently going to be quite high, in order to direct the Currents correctly and avoid hitting anyone with the donuts. Such precision strongly encourages looking at the intended destination to aim and avoid overshooting, pretty much requiring it for consistency.

Moreover, look at the arrangement of the three potential positions I could have to move my character to. Not only are they not in a straight line for hand prepositioning, there is no place I can preposition my character to get all of them at 90 degree angles from each other, or even 45 degree angles from each other. (Remember, I effectively cannot use a standard controller, since they do not allow for using one's whole arms to press keys or move joysticks. I use Legacy movement.) As a result, there is no way for me to get all three positions down to one keypress each, or even two keypresses each. At least one of them is going to involve a camera turn, which I cannot preposition my hands for in the same way, or a mix of two different movements.

So I cannot finish moving my character until I have finished moving my eyes from looking at my debuff bar to look at my intended destination. Because the movement distances are so small, I cannot even start moving my character until that point without risking overshooting, even for the potential destinations where I have prepositioned my character and camera to not require a camera turn. For those that do require a camera turn, I can move my eyes to look at roughly the right spot while turning my camera, but properly locking onto it is rough when the camera is also moving.

Let us make a list of steps:

1. The server sends the debuff to my client and my client eventually displays it.
2. See my debuff from my debuff bar.
3. Make a camera turn if necessary.
4. Look at the precise destination dictated by my debuff and the party's plan.
5. Press the keys / mouse buttons to make the appropriate movement, refining aim and length of keypress by visual tracking, while also doing my pre-planned heals and casts.
6. Look "up" to the party list to see if further healing is needed, because I do not have a static and in Party Finder someone might have missed a heal or mitigation tool. (Same with Raid Finder.)
7. Decide on that further healing, and try to get it not only received by the server but rippled out to the whole party before the debuffs expire.

Suddenly five seconds is not that long.

When I was progressing this mechanic, it did not just feel reactive to me, it was physically stressful to the point of hurting my arms to do over and over again. With a consistent cohealer and completing the duty, repeat completions went below the point of physical pain but never really got comfortable - and said cohealer is off to do FRU, so I am not encouraged by the prospect of going back in on my own.

Giving out the debuffs in advance would allow me to move the first four steps on that list ahead of that five-second window, even if they were only given by the previous Electron Stream cast (or Stampeding Thunder for the first one). I can handle getting all three at once, like E12S Intermediate Relativity does, too. Either way, that would be so much less physically demanding without changing the pace of the mechanic or the things the player needs to do at all.

Please count steps really carefully when giving short lead times between the player receiving information and needing to have used it. Or just give longer lead times like you used to.

Electrope Transplant (Phase Transition)

This mechanic is both extremely boring and very physically demanding. It is little more than an encouragement to repetitive strain injury. Why is this almost a minute of the duty?

Literally the only reason that the Duty Finder population cannot do this is the Conduction Point into Forked Fissures "protect your partner" mini-Wild Charges, and for most of the time the player does not have to remember or think about them. The Duty Finder population would figure out the Fulminous Field cones after an attempt or two even with the limited telegraphs given here. Transition mechanics are generally not meant to be particularly difficult, but this is too easy, especially since the same thing is repeated twice. And while the movement timings can be aligned with healer extended slidecasts, I expect that RDM and BLM have a much worse time of it due to Dualcast and Fire IV respectively.

The movement every Global Cooldown requires constant attention, but then it does not do anything interesting with that attention. That is why this mechanic is so boring.

As for the physically demanding nature of it?

Well, the natural way to learn this mechanic is by pointing one's camera at the boss, to learn what Conduction Point looks like and check one's understanding of the plan against the party's movements. Which makes the dodging entirely sidesteps, except for possibly one forward addition (back for melee DPS and tanks) to swap positions for Forked Fissures. Which in turn means that it is pretty much all on my keyboard hand, along with all my job actions. (I am aware of MMO mice, but I cannot offload much to one without injuring myself.) Doing that over and over and over again, every Global Cooldown with a short break for most of a minute... it hurt my hand even when completing the duty once a week for loot. Progressing this mechanic and those after it was awful.

I had to pin down which mechanics I find physically excessive and then check all of them for less demanding methods that still work in Party Finder. This one does have one, but it is only slightly less demanding and only usable after the learning process. Namely, I take the same Legacy movement split method I use for Stampeding Thunder, but here I use it for balancing the physical load between both my hands instead of for speed. And I have to specifically look counterclockwise, since in Aether Party Finder that is the direction of the dodge leading into Forked Fissures, and it is much more practical to aim into the tight space with my mouse if I have to move my character inward.

This was only viable once I made sure that my partner getting Conduction Point would still be visible on my screen and practiced seeing it rapidly while also getting the visual distance feedback to use the floor geometry references for how far to dodge the cones. Further, it can only take half the movements off my keyboard hand, since melee DPS and BLM/PCT want to stay in the same general area - for positionals and personal area buffs respectively - and that leads the whole party to do it by alternating movements. (I could try to explain starting my own character in a different place to my party, but that is confusion-prone and still would not help with the second round.)

I am sure you meant to include some visual spectacle with this phase transition. I am not seeing it, because I have to put the boss entirely off my screen to do this mechanic without hurting my hands. In fact, I have stopped perceiving the excellently done music change during this phase transition too, because I spend more effort and attention on protecting myself from injury than on doing the mechanic itself.

Plus, to avoid having the awful progression experience that I did, I would have had to know that you were willing to create mechanics like this and change how I approach duties accordingly. I would have had to use guides and timelines to screen every single mechanic of every single duty for its movement patterns in depth, flag any particularly demanding movement patterns, check videos to determine if they even have alternate options, all before even committing to the duty. And then I would still have to do the learning process for the mechanic outside the duty from videos, in order to use the physically safe method from the beginning.

That sort of analysis is now required for me to safely commit to a high-end duty, because if you will make one mechanic like this, how do I know that you will not make more? In regular duties, if I discover a problem mechanic and have to leave for my physical health, the discovery is extremely annoying for me at best and injurious at worst, but at least my party can replace me. In Ultimate progression, that is a disaster for both me and my party.

This one mechanic, by itself, would have been enough to stop me from committing to FRU on launch.

Relatively simple mechanics, appropriate for phase transitions, are just not worth this much movement anyway. Every button press or joystick tilt is a tiny little bit of effort that eventually has to give a tiny bit of reward back, and simple mechanics do not have the room to do that for this much movement. (Note that this is much worse than continuous movement in one direction, because that is one press and hold.) If you want a good "overload" phase transition mechanic, make something like TOP Wave Repeater, which requires far more thinking about how it complicates the overlapping mechanics than actual movement.

Conversely, if you are going to make a mechanic that requires this much movement, it had better at the very least be interesting to match, and hopefully naturally load-balanced too. TOP Pantokrator requires moving every Global Cooldown, mostly in stutter-steps, for most of a minute and it is perfectly fine - because it is a proper Ultimate-level mechanic and naturally load-balances itself. Almost all of the movement is in the same rotation direction, with smooth turns and no reason to look at the boss, so I can just do the whole movement with my mouse.

Cross Tail Switch

I hope you meant for parties to use a tank Limit Break 3 on this, because they sure were going to as the natural response to this design. They do not need the damage of a DPS Limit Break to complete the duty, and it is a lot more consistent for either tank to press one button at a specific time than for the healer pair to have a carefully coordinated healing plan and execute it under pressure. (Remember how the Party Finder response to P3S Life's Agonies, the heal-to-full raidwide at the end of Death's Toll, was "Macrocosmos or healer LB3"? Same thing, it can be done without the one button, but the one button is so much more reliable.)

I do enjoy that this needs some healing even through the tank Limit Break 3, and it does look cool. The short downtime is a natural place to use a Global Cooldown shield for it, which is a good nudge for healers new to this difficulty.

Sabertail (Exaflare Field + Light Party Stacks)

This is too easy, but would be fine in a lower floor. It does not even enforce that each light party agree on an initial spot to stand while looking at the exaflares!

The visual density is fine here; the exaflares have clear and familiar markers, and it is okay for the party to take quite a few attempts to notice the hidden pattern that the exaflares away from the east and west walls only ever go north and south. Once they realize that, it confirms their natural guess to split the light parties east and west for melee range access, and each light party only needs to look at the wall furthest from them.

Wicked Special

It is just an in/out, which makes its usage almost entirely a simple demand to look at the boss at a specific time and move. (Healing plans get worked around the potential for the "out" variation, but only when the party is split, and the constrained time is not long.) If the other mechanics in this phase were appropriately hard, that would be fine, but they are not so instead it contributes to boredom and repetitiveness. In context, it feels like "look and react" even though the cast is six seconds long, just because of the boredom.

Even O4S had in/out/Antilight in its second phase.

Mustard Bomb

This mechanic is relatively simple for the difficulty, but not too simple to be used as a "breather" mechanic mentally while still keeping the healing and mitigation requirements up. Between that and its short duration, its two appearances do not get boring.

Aetherial Conversion (Tail Charging, Memory Mechanic)

This requires the player to store exactly one item: which side to move their character to first. The tails retain the color of the stored element, so the player can choose between looking at the boss during the Tail Thrust, storing front / middle as a separate item, or condensing all four possibilities into a set to make one item.

Tail Thrust

Aside from releasing the stored Aetherial Conversion, this also varies the healing and mitigation requirement of the duty; the knockbacks do relevant damage to the party, while the fire AOEs are entirely avoided. I do not mind some variation in where the heal checks are, with long lead times so that the party can use their plan for the timeline, but this is varying the amount rather than the timing. Since heal checks are so inherently tied to the skill floor of the duty, this very much does affect the difficulty of completing the duty on any given attempt.

If the fire AOEs came with a light raidwide too, this would be fine.

Twilight Sabbath

The whole point of this mechanic is making the visual indicators difficult to see to force the player to react. It is not fun or funny. It is both reactive and boring.

If not for the baited puddles dropped before the first clones resolve, Duty Finder could do this mechanic. (They very nearly do, with Shadows' Sabbath in the Normal version.) And all the puddles do is prevent the fun optimizations, like sidestepping with a slidecast, or prepositioning in one quadrant and dashing to another if needed!

This design makes the player work with a bad camera angle to determine which clones will resolve first, compared to the Normal, as they all spawn at once and the height of the falling rings is a lot less clear when the clones are closer in. The player has to do the spatial reasoning for overlapping AOEs on top of watching for the clone manes (or the first part of the visual they personally can use) to appear, which is not at all interesting but adds to the time pressure. And half the time the mechanic is harder, because the south clone resolving second requires a camera turn for the simultaneous Wicked Special.

There is nothing to salvage in this mechanic. Even if the player is not pressured on their reaction time, they do not have anything interesting to do here. And on top of that, here they are more likely to be aware of the third-party tools that the delayed clone visuals encourage, or have someone in their party using those tools to do early callouts.

Midnight Sabbath

This mechanic is only saved by the fact that the wings of the donut AOE clones appear fairly early. Otherwise it would also be annoyingly reactive, on top of being too easy for a major theme mechanic.

Chain Lightning

This is entirely a memory mechanic.

In isolation, it would be fine, since it only asks the player to store three items: move their character to the first safespot, remember the other three. But there is a stored Aetherial Conversion before this, which puts this point in the duty timeline at four items.

Personally I can do this, but it is still unacceptable on principle as a violation of the three item rule. There is no further compression that the player can do here if they find themselves limited by their working memory. Further, this occurs during a raid buff window altered by the earlier downtime, so the player has extra working memory demands from their job at this point in the duty timeline.

This is why so many parties resort to writing down the Aetherial Conversion before this in party chat, since that is shared across the whole party unlike Chain Lightning itself. In turn, that encourages them to write down all the Aetherial Conversions, and possibly Chain Lightning by light parties, which further dulls the duty. (To make matters even worse, all that writing incentivizes parties to look for members who both do not use a controller and have the APM to type in combat.)

Sunrise Sabbath

The closest thing to a satisfying mechanic in the whole raid tier. It is a good idea, with enough lead time for all the random variations, but needs some more meat to it to be a proper final floor setpiece. (Notably, this is the other place you had to decouple the clones' rings from their attack resolution times, to allow the player to see what the clones will do in full.)

Very slightly narrower cannons would also be wise, to reduce the focus on character movement precision to avoid hitting other player characters with cannon baits.

Sword Quiver

The only thing suited to a final Savage floor in here is the heal check. The mental processing and movement would be fine in an Extreme, and without the role partner cones it would be fine in a regular duty.

Wicked Thunder (Enrage)

There is nothing wrong with using a powered-up cast of the familiar raidwide as the enrage, but thematic enrages are definitely nicer.

Overall Impression

"Boring and based on making things difficult to see, the fight."

Too easy for a final floor, still based on making indicators deliberately difficult to see, too memory-heavy, too much movement required without correspondingly interesting mechanics. The exclusive phase is particularly disappointing.

The duty that gave me the biggest push to worry about whether my body can handle FRU.

----------------

To be perfectly honest, even if I knew that my body could handle FRU, I would still have serious concerns about whether FRU would be sufficiently enjoyable to fight to be worth the commitment of an Ultimate. There is not a single truly satisfying mechanic in the entire set of Patch 7.0 high-end duties, and M2S and M4S both lack the necessary care for their difficulty towards what makes high-end duties possible and fun.

Ultimate is fundamentally about the intense challenge, about pushing the player to their limits but not beyond them, and it has to do that by using the duty design to create precise requirements for playing each job in the duty. I enjoyed every moment I spent in TOP because it walked that line. But if current duty design is not delivering high-end duties that walk the broader paths of Savage, how can I be confident that FRU will walk that line?

To be clear, I know that different duties are designed by different people within the duty design team, and that relatively few designers are entrusted internally with Ultimate designs. I still have a great respect for those designers. But it is clear that something within the duty design process for Patch 7.0 has produced duties with major fundamental flaws, whatever it is/was extends to the staples of raiding, and a single major patch is not enough time for feedback requiring major changes to make it through your production pipeline in general. If the length of that feedback loop were to be different for Ultimates, surely it would be longer rather than shorter; much of FRU's design would have to be completed before the release of Patch 7.0, and making design adjustments to the tremendous precision required of an Ultimate would involve careful consideration of how each mechanic contributes to the overall demands of the duty.

For a player who is completely ready for Ultimate, committing to attempt to complete a specific Ultimate upon its launch still means committing roughly 100 hours of their life to effective progression of that single duty. (Even for world progression raiders - they are exceptionally strong players, but they are also working without the benefit of guides and with little time to think about the mechanics outside the duty.) That is before counting time spent finding a group (or multiple groups), time spent ineffectively due to Earth circumstances such as illness, and time spent studying the duty outside the duty.

And they must make that commitment before getting to see the design of the specific Ultimate - purely on trust of the duty design process to deliver a journey that is worth the commitment. The many fundamental flaws in Patch 7.0's duty design, along with the relative lack of enjoyment, do not inspire that trust.

[Aurelle_Deresnels]

Now for the promised full duty example of the design style I want applied to a Dawntrail concept: redesigning the Honey B. Lovely duties - AAC Light-heavyweight M2 (M2N) and AAC Light-heavyweight M2 (Savage) (M2S). While I cannot promise perfection, as I do not have access to test servers or other design tools, I hope this is good enough to convey my intended style.

The lore and concept of the duties will remain identical. Honey B. Lovely is the queen bee, the idol songstress, the charmer who fights by enthralling even her opponents. One of the design goals is still to express this concept mechanically. It is a great concept!

I will utilize the visual changes I suggested in my mechanic-by-mechanic review earlier: for the Alarm Pheromones mechanics, the Groupbees have their AOE lines extend across their entire path through the arena, and these lines appear in black rather than green to keep with the bee theme while providing high contrast. I will also use a further visual change: having the Groupbees show the telegraphs for their AOEs for the last 2.5 seconds of their cast, to enable precise positioning beside the AOEs for certain Savage mechanics.

----------------

Redesigned Normal Mode Timeline

Even in Normal Mode, I have included some stinging surprises. To emulate the experience of discovery and learning for the first-time player, I will introduce these with the mechanics that include them.

Call Me Honey

Remains as in the original. Raidwides are a staple mechanic, and the cast name fits the duty concept. This makes a classic opener for Honey B. Lovely's performance theme.

Tempting Twist, Honey Beeline

Cast in a random order, one directly after the other, but both will always appear. Safe areas as in the original. This provides a light warm-up with easy dodges that teach these recurring attacks while players finish out their openers, the randomization prevents it from being completely static unlike the original, and strong players can do uptime optimization on repeat runs with Ley Lines placement, slidecasting, and/or melee uptime.

Killer Sting / Stinging Slash

Either one of the two tankbusters, as in the Savage original. (Killer Sting is a tank stack targeted on the player character with the highest enmity, while Stinging Slash is a pair of cone tankbusters targeted on the highest two player characters in enmity. Each cone is roughly 90 degrees wide, significantly wider than the narrow cones of Honeyed Breeze in the original. All targets are selected at the beginning of the cast.) These hit like a Normal Mode; a DPS or healer can be one of the two participants with a mitigation cooldown or a shield, though if they are close to minimum Item Level they will have very low HP afterwards.

There is no reason not to teach the tankbuster names in the Normal Mode, so as to make stepping up to Savage easier. They even keep their markers in Savage!

Alarm Pheromones (Alarm Pheromones 1)

Moved forward significantly compared to the original timeline, but with the same static "helix" pattern of the Groupbees appearing in sequence beside each other and then dashing through the middle of the arena in the same sequence. (Not including the "bowtie" pattern of simultaneous dashes at the end of the original Normal Alarm Pheromones 1.) This serves to introduce the Groupbees for later mechanics to work with. Once again, strong players can perform both melee and casting uptime optimizations based on this pattern.

Honey B. Live (begins Beat 1)

A raidwide with a long cast that transforms the arena, as in the original.

This is where players see the overhead charm gauge for the first time. Unlike the original, the gauge has four heart slots to match the Savage version, providing more leniency while learning the heart mechanics but also allowing the charm DOTs to tick higher. No hearts are initially assigned.

Filling the charm gauge results in five seconds of the original's Fatal Attraction debuff (charmed, swaying, unable to act) followed by 15 seconds of the Devoted Drone debuff - which nullifies all damage outgoing to the boss. (This does get copied to pets, just like Damage Downs and potions do. And it comes with the "Invulnerable" flying text and shield effect.) The heart buff stacks from the original appear on the boss to help clue players in when this happens, and track how many times this has happened, but they have no other effect. This penalty is significantly harsher than the original, but it also takes much more serious mistakes to fill the charm gauge. There are no mechanics where an attentive player might simply not react fast enough, and no Beat requires any individual player character to take more than two hearts - you will see why later.

(Veteran players may recall the Packet Filter debuffs (placed by Firewall) from Alphascape V4.0 (O12N), Alphascape V4.0 (Savage) (O12S), and The Omega Protocol (Ultimate) (TOP), as well as Pall of Rage / Pall of Grief from Cinder Drift (Extreme). Devoted Drone is slightly different in effect, in that it still allows players to apply debuffs to the boss. Obviously, it is also different in being used as a punishing 100% Damage Down rather than a non-punishing party split. But it is not an accident that Omega exerts a degree of control over the party via its total control of the Interdimensional Rift, and Honey B. Lovely is trying to control the party via her pheromones.)

As in the original Normal, the first time (in the current attempt at the duty) that the player character reaches each number of hearts, red text appears to help teach how the charm gauge works. The messages are the same as in the original, simply adding more to match the Savage debuff range:

• One heart: "You are growing infatuated with Honey B. Lovely..."
• Two hearts: "You are head over heels for Honey B. Lovely..."
• Three hearts: "You are hopelessly devoted to Honey B. Lovely..."
• Four hearts: "You are powerless against your undying affection for Honey B. Lovely!"

Spread Love

This is a completely basic spread, with fairly small AOEs, except that each AOE gives a heart. This serves to teach players that any mechanic with a heart on it adds a heart to their charm gauge when taken, in an unavoidable way since every player character present and not KOed gets a spread AOE. To reinforce the lesson, this will always trigger the first red text.

At this point, each player character should have one heart. If players did not spread effectively, some may have two or three hearts.

Outerstage (not a combo, this is not Savage)

This is a completely basic point-blank AOE, except that it has a heart on its telegraph and gives a heart to any player character hit by it. This serves to teach players that avoidable mechanics can also have hearts on them.

I have deliberately chosen not to use the cast name Loveseeker, which the original uses for this same AOE, in order to help the player learn the Combos if they choose to attempt the Savage version.

Love Me Tender (Moving Hearts)

Honey B. Lovely begins emitting moving hearts from herself in the same fixed 3-pronged spiral pattern as the original. (For reference, the prongs are evenly spaced, one always starts directly South, and they always rotate clockwise.) Unlike the original, no other mechanics appear, neither the puddle AOEs baited under player characters nor the baited moving hearts from the edge of the arena.

The point of this mechanic is not to be random and reactive. Indeed, the Outerstage before it is deliberately not random, to push attentive players out of the center and thus give them time to see the moving hearts spawn.

The point of this mechanic is to express "she is literally emitting pheromones to try to charm you" in a way that is consistently dodgeable. For first-time players, this solidifies their understanding of the charm gauge, allowing later mechanics to build on it. This pattern also rewards thinking about whether to slip between hearts in the spiral arms, or follow the arms at the expense of more overall movement, again allowing strong players to optimize based on their jobs.

She stops emitting hearts after the spiral has rotated 120 degrees, so every angle has been passed over by one arm. There is nowhere to stand that avoids engaging with the mechanic at all.

Honey B. Finale (ends Beat 1)

A raidwide that transforms the arena back and cleanses all hearts, as in the original.

Yes, Beat 1 is not all that hard, but it is also pretty short while still teaching first-time players how the charm gauge works. The duty is not done ramping up yet - it has only just introduced Honey B. Lovely's recurring mechanical elements.

Stinging Slash / Killer Sting

Whichever tankbuster was not used earlier. While Duty Finder does not make mechanic-specific plans and so will generally not plan invulnerability uses accordingly, this ensures that the first-time player sees both tankbusters before they can unlock the Savage version.

Alarm Pheromones (Alarm Pheromones 2)

Two Groupbees appear at once in random spots at the edge of the arena, each locking onto a random player character. (They cannot both select the same player character, but it is otherwise completely random. In the event that only one player character is present and not KOed, only one Groupbee will appear.) The selected players are marked, not only with a tether to the Groupbee locked onto them but also with an overhead symbol for which tether they have: the "Playstation markers" that were previously exclusive to Endwalker high-end duties. (Which two markers are used is also completely random.)



Duty Finder does not do the sort of planned coordination of multiple tethers that has been historically associated with Playstation markers, nor are they particularly good at remembering which marker they got for later. I do not expect them to do either. But they can learn "you have to do something specific with whoever or whatever has the matching symbol", which is the "real" underlying concept of the markers - and this duty will start teaching that right now, by combining the already-known tethers with the Playstation markers over both the player character and the Groupbee on each end.

Players then have several seconds to figure out who has the tethers - this is Normal Mode, after all, they cannot be expected to pre-spread - and move as they please. After this time, each Groupbee will set their path to go through their selected player character's position, shown by their tether and marker disappearing and being replaced with the Groupbee line. In case players were unsure of what tethered Groupbees do, this shows them and gives them time to dodge, but it is not a difficult guess since they have seen the Groupbees earlier.

As soon as these Groupbees complete their Blinding Love cast and begin moving, two more Groupbees appear and lock onto player characters, again in random spots at the edge of the arena. They still cannot both select the same player character, and this time - if at all possible - they will select player characters who were not selected last time. These two Groupbee tethers will use the other two Playstation markers, ensuring that the party sees the whole set.

Just as before, these two Groupbees will bait onto their tethered player characters, with the same timings.

As soon as these Groupbees complete their cast and begin moving, four more Groupbees appear and lock onto player characters, again in random spots at the edge of the arena. They still cannot have more than one Groupbee select the same player character at once, and this time they will prioritize selecting player characters who have not been selected by either previous set. As this totals eight Groupbees, this ensures that every player must bait a Groupbee (unless their character is KOed for the entire mechanic), forcing them to interact with the Groupbee that has the matching symbol. (If player characters are KOed or disconnected for the entire mechanic, that will just result in someone else baiting twice, it is not a body check.)

By forcing the interaction with the Groupbee, this mechanic as a whole builds the association for players between seeing the Playstation markers and expecting to interact with whoever or whatever has the same symbol. This also shows players that the entire set of Playstation markers can be active at once.

Just as before, these four Groupbees will bait onto their tethered player characters, with the same timings.

As a whole, this mechanic is fairly slow. (Unless some player characters are KOed or disconnected, each player character is only selected once out of the three sets.) This is deliberate, to allow players to focus on and process the new concept of Playstation markers until they are comfortable with it. Even the players not currently selected should still pay attention to the mechanic, to know where the Groupbee divebombs will be and save themselves from any poorly placed baits. (Notice that there are always active Playstation markers until the final set of Groupbees sets their paths.) This also encourages players to learn from each other by observation.

Meanwhile, for players who are comfortable with the concept, the high randomness creates many different possibilities to plan for and try to optimize. Want to bait your Groupbee without leaving melee range or making everyone move? You can do that on an individual level, but your Groupbee can spawn anywhere so it is not going to be the same movement every time, and that is before accounting for the other Groupbee(s) in the same set. Want to bait your Groupbee without losing casting uptime? You can do that, but you are not always going to have your bait at the same time or in the same location, so you have to plan instant casts for each possible time, bait in melee range, or do quite a lot of slidecasting if your Groupbee spawns far away from you. Coordinated raid groups can devise strategies like "always leave the dead center of the arena safe" and have a completely different experience from casual parties who bait anywhere and everywhere.

Honey B. Live (begins Beat 2)

Once again, this raidwide transforms the arena and brings out the charm gauges. No hearts are initially assigned.

Love Me Tender (Towers)

Four player characters are selected at random and given Playstation markers directly above their charm gauge. (Which is why I put Alarm Pheromones 1 before Beat 1 - to introduce and teach each overhead marker separately as they alternate. This also utilizes the fact that the charm gauges sit directly above each player character's nameplate, allowing for a second overhead marker without piling them too high.) If less than four player characters are present and not KOed, all player characters that are not KOed receive Playstation markers.

Each player character with a Playstation marker also simultaneously receives a new debuff, "Command Performance: [shape]", where the shape is that of their Playstation marker. The debuff icon will also show the marker shape. This debuff is cleansed by taking a tower with the matching shape, and KOs the player character if it expires rather than being cleansed. Here, the Playstation markers do not disappear until the debuff expires or is cleansed.

(For those who enjoy linguistic references, here is the definition. "Command performance: (archaic) A dramatic, musical, or similar entertainment performed before a monarch or other head of state, especially in a circumstance where that ruler has requested or ordered the performance." Fitting for the queen bee!)

At the same time, a heart tower spawns matching each active Playstation marker. (This is again not a body check, since it will not spawn more towers than player characters who can take them.) These towers show the heart within the base, like the original, and the Playstation marker floating at about overhead height for the taller player characters. (This positioning is to give clear visibility of both the heart and the Playstation marker.) These towers all spawn in melee range, because at this point the goal is to get players to do their specific assigned mechanic without being literally forced to, for which looking around the arena in a panic to find their tower or worries about losing uptime are counterproductive. Melee DPS may have to press True North if they cannot avoid positionals while in their tower, which is fine.

To reinforce that only the player characters with Playstation markers are meant to take these towers, all player characters without Playstation markers receive heart spread markers that are immediately visible and go off at the same time as the towers. (If a player with a Playstation marker is in the process of disconnecting or has been pulled away by an Earth emergency, a player whose character has a spread marker can step into their tower to prevent it from exploding, but that is clearly not what is suggested by the markers.) Since these spread markers are fairly small as in the original, these players can fit their spreads between the towers without leaving melee range.

Even without having just seen the baited Groupbees in Alarm Pheromones 2, or reading the Command Performance debuffs, a player who sees a marker over their head and the same marker over a tower is quite likely to correctly guess that they should stand in that tower. Intuitively, this further nudges the players with spread markers out of the towers, so as not to hit those taking the towers. (It is still possible for a tower to go off with no one in it, exploding and giving all player characters a heart, but it is quite unlikely barring disconnects and emergencies.)

Which means that here - unlike in the original - Duty Finder is actually capable of putting exactly one player character in each tower, the way the charm gauge encourages! The Playstation markers being assigned solves the coordination problem of who should take each tower for the party, which stops players from messily reacting to each other.

(Veteran players may recall that the Looper debuff appears in Alphascape V3.0 (O11N), not just in Savage and Ultimate, and requires players to take any tower in order to cleanse it and avoid KO. The use of Command Performance here is deliberately similar to how Looper is used in O11N, particularly in the fact that players do not need to notice the debuffs at all - any reasonable attempt to engage with the mechanic will cleanse the debuffs automatically. Command Performance goes one step further with its name and icon, in that players who see the name and/or icon in their flying text will tend to correctly guess what the debuff requires of them without having to hover over it for a description. This is great for controller players, or really anyone who has trouble hovering over debuffs in the middle of combat.)

This mechanic teaches players that the possible interactions when they see a Playstation marker are not limited to divebombs, or even to tethers. In turn, this prevents them from thinking that the Playstation markers are for a concept they already know. (Indeed, even for veteran raiders I have expanded the concept of Playstation markers; its prior uses always involved tethers of some variety.) If I had presented the Playstation markers only with the Groupbee tethers, players might reasonably think that the markers are a replacement for existing divebomb markers or tether types. If I had presented the Playstation markers only with the heart towers, players might reasonably think that the markers are exclusive to towers or charm mechanics. Showing both clarifies that the marker set is a pairing tool, and the player should try to work out the interaction with whoever or whatever they are paired with.

Once the towers and spreads go off, every player character has at least one heart, or is about to be KOed by their Command Performance debuff. If they did the intuitive thing, they will all have exactly one heart.

Centerstage (not a combo, this is not Savage)

This is a completely basic donut AOE, except that it is pink with hearts on its telegraph and gives a heart to any player character hit by it. For players repeating the duty, this encourages not spreading too far in the first place, and for everyone this creates an opportunity for healers to heal the whole party.

Love Me Tender (Towers)

As the previous Love Me Tender, except prioritizing players who did not get Playstation markers then to get them this time. This ensures that every player must take a tower unless their character is KOed for both Love Me Tender casts.

Once this resolves, every player character has at least two hearts, or is about to be KOed by their Command Performance debuff, or died earlier. If there were only three heart slots in the charm gauge, players would have to do it exactly right while still learning a new concept, which is why I put four heart slots in the charm gauge instead. The extra heart allows for each player to save a tower from exploding, or for one tower to explode.

This is not a hard mechanic, but it continues to teach the concept of Playstation markers while expressing Honey B. Lovely's fighting style. It creates a very evocative tension between having to take hearts in order to keep fighting and wanting to avoid filling the charm gauge. Lines like "Who's my obedient little bee?" and "Heed me well or you're as good as dead" have a lot more sting to them when each player is singled out to do a very specific thing - to play the part she dictates in her performance - or take a KO.

Honey B. Finale (ends Beat 2)

A raidwide that transforms the arena back and cleanses all hearts, as in the original.

Splash of Venom

Stores a spread for later, as in the original.

Players might not see this as gear improves, particularly with this being the first tier of an expansion and item level syncs going by level rather than by raid tier. That is okay. This is not that exciting unto Duty Finder, especially since the spreads have to be telegraphed for players to learn it in Normal Mode.

The primary purpose of this section is to be a spacer between the Playstation marker mechanics, so that players have some time to breathe and process what they are learning. The secondary purpose is to teach the AOE patterns to any players who will be trying the Savage later.

Tempting Twist / Honey Beeline

Either AOE at random, with Splinter honey blobs afterwards. Unlike the original, the honey blobs are in the Savage patterns, since both patterns require players to move after dodging the cast and familiar patterns help players make the step up to Savage. This is also more random than the original, which forces Tempting Twist to be first in order to have Honey Beeline overlap with its Alarm Pheromones 3.

As the castbar finishes, the spread markers for Splash of Venom appear. These resolve a few seconds after the honey blobs.

Drop of Venom

Stores a stack for later, as in the original. Duty Finder does not do quick partners. (Yet, anyway.)

Honey Beeline / Tempting Twist

Whichever AOE was not used last time, with Splinter honey blobs afterwards in the Savage patterns.

As the castbar finishes, the stack marker for Drop of Venom appears. This resolves a few seconds after the honey blobs.

Killer Sting / Stinging Slash

Either one of the two tankbusters, as before.

Alarm Pheromones (Alarm Pheromones 3)

As with Alarm Pheromones 2, except with two sets of four Groupbees each. Players have already had the Playstation markers on Groupbee tethers introduced slowly by this point, so they can now handle the faster pace.

Stinging Slash / Killer Sting

Whichever tankbuster was not used earlier.

Honey B. Live (begins Beat 3)

Once again, this raidwide with delayed damage transforms the arena and brings out the charm gauges. No hearts are initially assigned.

Love Me Tender (Towers)

As in Beat 2.

Love Me Tender (Moving Hearts)

As in Beat 1.

Love Me Tender (Towers)

As in Beat 2, once again prioritizing players who did not get a Playstation marker last time to get one this time. Castbar starts as soon as Honey B. Lovely finishes emitting moving hearts, since now players have seen all these mechanics. This encourages players to plan for the moving hearts pattern rather than reacting to it on repeat runs, without being too harsh on first-time players or those who have not noticed the fixed pattern.

Honey B. Finale (ends Beat 3)

A raidwide that transforms the arena back and cleanses all hearts, as in the original.

At this point, the duty loops from Splash of Venom until the boss reaches 20% HP.

Once she reaches 20% HP, she transitions into a new phase. This transition must happen without the charm gauges, so if necessary she will immediately end a Beat (and cleanse any active Command Performance debuffs) with Honey B. Finale.

Rotten Heart

A raidwide that brings with it a new arena transformation, as it does in Savage.

No, Duty Finder cannot do the Savage version of Rotten Heart. Yes, she is still going to drop the act when she gets desperate. (This is not out of any objection to high-end duties having exclusive phases, it is to create a final phase that cements casual players' understanding of Playstation markers.)

Player characters are immediately paired at random with the "get away from each other" blue arrow tethers from Eden's Promise: Litany (Savage) (E10S). Each tether pair gets a Playstation marker, which does not disappear until the tether is removed, along with a light DOT debuff that is weaker the further the tethered player characters are from each other. Casual players will mostly notice the high-contrast arrows on the tethers rather than the DOT, but that suffices to get them to intuitively move away from their tether partner.

After a few seconds, the Playstation markers for all tethers other than one's own disappear visually, to reduce visual clutter while still reinforcing that the markers are a set.

Alarm: Mass Final Sting

Honey B. Lovely then summons a batch of Groupbees, with an elaborate animation lasting several seconds and locking herself in the center of the arena for the duration of their flight. But rather than the Groupbees dashing across the arena, this time she orders them to suicide bomb the arena, stingers first. Their descent creates pairs of widely separated towers, each pair sharing a resolution time and a Playstation marker. (Since there are no hearts here, the Playstation markers are shown in the base of each tower, large enough to be seen through the tethers. They are not also shown over the towers to avoid confusion with the overhead markers on other players.) One pair will spawn at a time, repeating until four pairs have spawned. (This remains true even if some player characters are KOed or disconnected, as there are no hearts to create a body check from extra towers.) As usual for towers, if a tower resolves with no one in it, it explodes dealing raidwide damage.

At this point, each pair of players should already have spread their characters apart before or during the Groupbee summoning animation, making it easy for the players to split up their corresponding pair of towers. (Which is why the animation is so long, unlike in Alarm Pheromones.) Here, the Playstation markers do not completely solve the coordination problem for the party, but they reduce it to coordinating with one other person, and Duty Finder can manage that from previous experience with spreads and towers.

Each tower spawns just close enough for players to stay in melee range by standing in the portion closest to the center of the arena, with its partner tower directly across from it. (Again, melee DPS are rewarded for planning their uses of True North to have it for their tower.) These towers spawn at angles half-way between a cardinal and an adjacent intercardinal, much like the tower placements in the original Savage Beat 3, and all eight of these spots will be filled once all towers spawn. Observant players on non-melee-range jobs are thus encouraged to use their greater range to stretch their tethers further.

A rough diagram of the tower positions:



Taking a tower matching one's Playstation marker clears one's tether and DOT (for both tethered player characters). The tethers and DOTs do not otherwise expire. Here there are no Command Performance debuffs because Honey B. Lovely is no longer trying to put on a show, but now only to defeat the party.

(And yes, the cast name is a deliberate reference to BLU's Final Sting. While this version is not single-target in the same way, it is still bees' suicide attacks and ideally one player character matches up with each bee to soften the blow.)

Call Me Honey

Cast only starts once all towers have resolved.

Still a raidwide, which now also reapplies the tethers from Rotten Heart to any players who have not carried them over. The tethers are freshly randomized except for not reusing markers that are still active.

Alarm: Mass Final Sting

As before, except that two pairs of towers spawn at a time. If any player characters are KOed, this is a great big hint to use battle raises in a hurry, since all towers that spawn at once will resolve at once.

Call Me Honey

As with the previous cast, a raidwide that reapplies the Rotten Heart tethers.

Alarm: Mass Final Sting

As before, except that all eight towers spawn at once. Now Honey B. Lovely is quite fed up with the party's persistence, and has finally created a soft body check - avoiding KO from multiple simultaneous tower explosions is possible but requires efficient healing and mitigation. (Plus Normal Modes have even had hard enrages before - Deltascape V2.0 (O2N), for example - just with timers long enough that the party has to have performed very badly to see them.)

At this point, the duty loops from the last Call Me Honey until either side is entirely KOed. 20% might sound like a lot of HP for this phase, but DPS Limit Breaks and gear improvements are likely to shorten it even if the boss does not need to first end a Beat. AAC Light-heavyweight M4 (M4N) has a similar threshold, and strong parties often barely even see the Wicked Hypercannon after the long arena transformation nowadays. I would have put the threshold higher if the transition into Rotten Heart was longer, since I want the party to actually see the tethers between player characters even if they do not see the Groupbee towers.

--------

If I were not aiming to teach a new mechanical concept, I would not set a pace quite this slow for level 100 gameplay, especially outside the MSQ. But Honey B. Lovely's fighting style was an opportunity too good to pass up to teach Playstation markers - she is a performer who fights by enthralling her opponents, of course she wants to single out specific player characters for specific parts in her performance! (Plus, Playstation markers already facilitate high randomness.) So it is thematically appropriate for her to use Playstation markers often enough to guide the casual player into picking up the concept, without needing an allied NPC to instruct or demonstrate. And even a duty this slow can have plenty of sting to it.

Not every duty should have some brand new mechanical concept; even the most dedicated players need time and practice to consolidate their knowledge, and teaching new concepts every duty leaves no room to explore their forms and combinations. But taking opportunities to teach and reinforce new concepts could significantly expand Duty Finder's mechanical vocabulary over the course of several patches. (Especially if casual players in all roles learned to use the debuff bar.) And since mechanical concepts can combine, this would greatly expand the duty designs available for casual play.

Create a new Wild Charge marker and teach it, as I described when discussing the final phase of M4N? Bring the "[number] in Line" debuffs to Duty Finder? Perhaps even teach spinner baits after a few patches, so long as the spins are slow enough that players can dodge through a failed bait? There are lots of possibilities, especially if you continued updating the Hall of the Novice.

Playstation markers are also a good choice to teach casual players because they can then be used to present gentler versions of many mechanical structures that would otherwise necessarily be limited to high-end duties. Fundamentally, in regular duties they can solve coordination problems for the party, allowing the party to tackle the mechanic without having to specifically prepare for it. You could have dungeon bosses where every party member has an additional mob (add) to tank and position, even though non-tanks do not have the tools to get an add's attention if the tank goes for the wrong one - just tell them which add to take! You could bring true enumerations back to Duty Finder, this time without players having to react to each other. Show casual players role partners by giving them their role partners. And so on. That would get more players into high-end duties without making the high-end duties any less of an accomplishment - by instead making the regular duties better stepping stones to the higher difficulties.

----------------

Now for the Savage Mode. As a Savage timeline cannot be properly evaluated without context on the overall tuning of the duty, I shall provide the context for the design I intend first.

This is a second Savage floor. Regardless of job balance, it should not have a damage output requirement almost as high as the final floor of the same tier - especially not since second floors have an Item Level requirement five Item Levels lower than third and fourth floors of the same tier! The tuning I intend is that if all party members are at minimum Item Level, the party can make at most one major mechanical mistake (KO, Damage Down, or Devoted Drone) and still beat the enrage with otherwise perfect play. (Of course, the vast majority of groups will not have otherwise perfect play, thus leaving them no room for major mechanical mistakes at minimum Item Level.) Since crafted gear is five Item Levels above the minimum, parties would not be reliant on raid drops or tomestone gear for further leeway even in Week 1.

As for the healing and mitigation requirements, I intend to require planning but not perfection, with an overall result not that different from the original. Even though new raiders are encouraged to start with Extreme before moving up to Savage, this could be a new raid healer's second high-end duty ever. On top of that, a new raid healer is likely progressing in Party Finder with variable cohealers and mitigation from their parties, so requiring optimized healing cooldown plans is a recipe for quitting in frustration. But at minimum Item Level, mitigation from someone in the party is often required (outside the Beats) to reduce the damage taken from a single cast below player characters' max HP... and having a shield healer Global Cooldown (GCD) heal for every mechanic will not be pleasant.

That is at baseline. Gear will make things easier. But unlike the original, I will not have the heart stacks from filled charm gauges make Honey B. Lovely deal more damage. (Instead, I will add to the baseline healing and mitigation requirements in selected places.) This is for two reasons:

First, because the burden of the increased healing requirements from filled charm gauges falls primarily on the weakest and newest raid healers, who are least able to handle it. Strong players and/or those who already know the mechanics well will tend to seek out other players of similar skill and experience via forming static raid groups, creating Duty Complete parties, and setting higher Item Level requirements. (Especially since Raid Finder matchmaking is not in customary use outside the JP Data Centers.) Thus, the player population that joins parties with weaker and newer raid healers will be more likely to fill their charm gauges than average - and will need more adjustments to the healing as a result, between lower Item Levels and less effective mitigation use! Meanwhile, the strongest raid healers, who can adapt their healing plans easily, rarely see a charm gauge fill (during an attempt worth continuing) even in the original; with the reactive elements of Beat 1 replaced, they would almost never see a charm gauge fill, let alone enough in a single attempt to change their healing plans.

Second, because some players raid to learn a plan and push themselves to execute it as close to perfectly as they can, for the enjoyment of the dance... and some of those players are drawn to healers for a variety of reasons, despite the necessity of compensating for other players' mistakes in the healer role. (Going into those reasons would be a long detour, so I will skip it here.) From that perspective, having to change one's healing plan for the entire rest of the attempt because of how the boss works is an annoyance. (In contrast, Doping Draught is great in AAC Light-heavyweight M3, both Normal (M3N) and Savage (M3S), because it is a planned part of the duty.) Healers who enjoy adapting their healing plan based on how an attempt is going can still do that without the boss requiring it directly - and some recovery scenarios already require it indirectly, by forcing the healer(s) who can act to use resources they were saving for later mechanics.

(There may well be a place somewhere for failed mechanics giving the boss damage up stacks! But it is not here, and it is not where players are learning a new concept for the first time in Normal Mode.)

That context given, here is the timeline.

--------

Redesigned Savage Mode Timeline

0:05 - 0:10 Call Me Honey

Remains as in the original. While not every duty needs an opening single-hit raidwide, it is fine to have one in some duties, and both AAC Light-heavyweight M1 (Savage) (M1S) and M3S have different forms of opening party damage.

At minimum Item Level, this hits just hard enough to reliably KO Disciples of Magic and sometimes (damage variance) even Disciple of War DPS from full HP if it goes completely unmitigated and unshielded. We are in Savage now, time to bring out mitigation tools and prepull shields, or you are going to get sent back to the start 10 seconds in. On its own, this could even hit a little harder, but it comes back in Rotten Heart and I want players to learn how hard it hits here for heal planning there. (It does not come back before Rotten Heart due to the abundance of Beat transition raidwides, as in the original.)

More damage is coming, so ideally the party will use the mitigation tools that are least disruptive to opening burst here (rather than making the healers do more work) and save the rest for later. Mitigation spreading does not need to be perfect, this is only a second floor, but it does need to exist.

0:12 - 0:17 Splash of Venom / Drop of Venom

As in the original, stores a random untelegraphed spread or partner stack for later. When this resolves, it will hit just as hard as Call Me Honey; either the party needs to find some mitigation and efficient healing, or the healers will be scrambling to heal the party up after their openers.

While this is the same memory mechanic as in the original, this design uses it significantly less often - thus making its presence less repetitive and boring while making room for other forms of mechanical difficulty. In particular, the Beats will not use it at all, which helps mechanically differentiate the "enthralling songstress" aspect of the Beats from the "venomous queen bee" aspect of the other mini-phases. This mechanical differentiation in turn helps give the Beats a "wide open stage" feeling, contrasting the restricted spaces that other mechanics create.

0:23 - 0:28 Tempting Twist / Honey Beeline

As in the original, casts a random ground AOE with follow-up Splinter honey blobs that force players to move. This specific cast retains the extended break between casts of the original, to allow players to finish their openers before moving.

The Splash of Venom / Drop of Venom resolves at the same time as the honey blobs (0:33), as in the original.

0:40 - 0:44 Killer Sting / Stinging Slash

Either one of the two tankbusters, as in the original. Now that we are in Savage, these hit like it - at minimum Item Level, a tank participant will be KOed from full HP unless they use personal mitigation.

I have moved this tankbuster ahead in the timeline from the original, so as to create a space between the first and second rounds of the memory mechanic while still ensuring that players learn both possible stored damage casts and Splinter honey blobs early. This encourages healers to use their regens to heal up from the first Splash of Venom / Drop of Venom, which will serve them well in the new Beat 1 where the heart DOTs will tick for longer.

0:45 - 0:50 Drop of Venom / Splash of Venom

Whichever stored damage cast was not used earlier, as in the original.

0:52 - 0:57 Honey Beeline / Tempting Twist

Whichever ground AOE cast was not used earlier, as in the original. Once again, the stored damage resolves at the same time as the honey blobs (1:02).

Here, healers are encouraged to use burst heals before the upcoming Beat.

1:10 - 1:19 Honey B. Live: 1st Beat

A raidwide that transforms the arena, as in the original. Does not hit as hard as Call Me Honey, to prevent immediate KOs from heart DOT ticks. (As a whole, the Beats have a different style of healing and mitigation requirement: lighter big hits, but continuous DOT damage from the heart stacks.)

During each Beat, the boss centers herself facing North and remains there, since she is performing and intends to be the star of the show. This contrasts with her fairly free movement during the Alarm Pheromones mechanics and around the tankbusters, when she will follow the player character with highest enmity so long as she is not actively casting.

Just like the original, the charm gauge has four heart slots. Eight hearts are initially assigned across the party, but with the following rules not present in the original:

• One tank will get two hearts, while the other tank has none. (This encourages attentive tanks to split their incoming damage, with one tank taking the heart DOTs from the beginning and the other tank taking the auto-attacks.)
• The healers will get two hearts between them, either one each or both taken by one healer.
• The DPS will get four hearts between them, in any combination such that no player character has more than two hearts.

All player characters also get a Command Performance debuff with no shape attached; to cleanse this, they must take any heart tower. It is now up to the party to decide who takes which tower(s), but no one can sit out of the mechanic.

Filling the charm gauge has a similar penalty to the redesigned Normal: five seconds of the Fatal Attraction debuff followed by 25 seconds of the Devoted Drone debuff. (The heart buff stacks also appear on the boss just like the redesigned Normal.) This allows players to progress despite being charmed, while punishing mistakes while attempting to clear the duty, as one would expect from a Damage Down - and players care a lot more about their damage output in Savage! The length of the penalty is meant to have a similar effect on damage output to a KO (time taken to receive a raise and in the raise animation, then 25% lower damage and healing for 100 seconds) without draining one's resources or affecting the party's healing and mitigation plan. Indeed, Devoted Drone allows players to debuff the boss precisely so that they can still apply debuff-based mitigation, with the side effect that it also permits debuffs that increase party damage output.

(Filling the charm gauge could have healed the boss like it does in the original; that does not have the same disproportionate effects that the damage up does. But I find being unable to damage the boss more fitting to being enthralled, while the boss healing evokes more of an "aether drain" concept. What if the boss healing was on Wicked Thunder instead, since she is trying to take the player character's soul?)

1:24 - 1:28 Love Me Tender (Towers)

12 Fracture heart towers spawn one by one, separated by the same 2 second intervals (1:28 - 1:50) as in the original. Unlike the original, there are 12 positions for the towers, where each position will be used exactly once in a completely random order. The positions are:

• four "close" towers on the intercardinals, well within melee range, like in the original;
• four "mid" towers on the cardinals, where only the parts closest to the center of the arena are in melee range;
• four "far" towers on the intercardinals, that require leaving melee range to take.

A diagram of these tower locations:



The fixed set of tower positions allows parties to assign who will take each tower position based on the initial heart assignments, which in turn allows parties to eliminate all reaction to one's party members despite the completely random order. (Recall that this is necessary to prevent pressuring the party's reaction times.) Meanwhile, players trying to optimize their damage output have many possibilities to consider for when they will have to move to take their tower(s), including the possibility of taking consecutive towers.

Here is one solution that the party might agree on, with the tank with zero initial hearts taking the T1 spots:



(In this solution, no DPS will ever need to move twice, despite the melee DPS being marked on both priority orders. If either priority reaches the third DPS listed, that is because the first two listed both started with two hearts, and therefore they have all the initial hearts that can be assigned to DPS. That means the other two DPS started with zero hearts, and will pick up one tower each beyond the requirements of Command Performance. (Indeed, the priority ordering in this solution can be read as including all four DPS for each tower, but the fourth player will never be reached.) As a result, each individual player has all the information they need to know which tower(s) they will take as soon as they see the initial heart assignments, which are given 19 seconds before the first tower resolves, and they can take some time working through it without messing up the priority order.)

Each tower resolves 10 seconds after it spawns (1:38 - 2:00). The 10 second period between spawn and resolution will be the same for all heart towers throughout the duty.

The Command Performance debuffs expire two seconds after the last tower resolves (2:02) - slightly longer than needed to ensure that the debuffs are cleansed even by the last tower, just long enough for a player who did not take a tower to realize their mistake.

(As a result, players still engage with Command Performance differently from the existing uses of Looper, despite the former appearing without the Playstation marker shapes. In all of O11N, the first Executable in O11S, and Run: ****mi* (Sigma Version) in TOP, the whole party must cleanse Looper at the same time. In the second Executable in O11S and Program Loop in TOP, the party has the cleanse order dictated to them by the differing lengths of Looper given by the boss. Here, each player character cleanses Command Performance at a different time, but the order is up to the party.)

At this point, the party has a total of 20 hearts if exactly one player character stood in each tower.

2:05 - 2:11 Centerstage Combo / Outerstage Combo

Either of the avoidable ground AOE sequences, as in the original. (Second and third hits at 2:14 and 2:17 respectively, the same three second spacing as the original.)

Unlike the original, most of the heart DOTs have already been applied, so healers should consider taking advantage of the donut hit to heal the party despite this being a burst window. (My thoughts on the 2 minute meta aside, duty design and job design are tightly linked, and the jobs we have in Dawntrail follow synchronized 2 minute bursts.)

2:21 - 2:25 Love Me Tender (Stack)

As in the original, the four-heart Heartsick stack spawns targeting a random player character out of those with the lowest number of heart stacks among the party. It hits lightly at 2:30, with its real danger being that it forces the party up to the maximum of 24 hearts without any player character filling their charm gauge.

There are no "freebies" or "spare hearts" here, unlike the original Beat 1. Since the party can fully plan out the forced hearts and dodge all the avoidable AOEs without reacting rapidly, there is no need for lenience on the mechanics dance. The party has some degree of choice on who will take the stack - anyone who was initially assigned two hearts must get their third heart from fulfilling their Command Performance - but no room for mistakes.

Wise parties will agree on a position to take this stack, and skilled players will start moving towards / away from this position during the preceding Combo depending on whether they need to take or avoid the stack.

2:30 - 2:36 Outerstage Combo / Centerstage Combo

Whichever ground AOE sequence was not used earlier, as in the original. (Second and third hits at 2:39 and 2:42 respectively.)

Like the original, all of the heart DOTs are now ticking, so healers should utilize the donut hit out of burst to heal.

Unlike the original, there is no "spacer" between the Heartsick stack and the start of the Combo castbar, as there are no moving heart AOEs that need time to dissipate. Players can choose to take the stack in a position that leaves them set up for the Combo, especially since they know which one it will be.

2:49 - 2:54 Honey B. Finale (ends Beat 1)

A raidwide that transforms the arena back and cleanses all hearts, as in the original. Again does not hit as hard as Call Me Honey, since shields will be worn down by the heart DOT ticks.

2:57 - 3:02 Splash of Venom / Drop of Venom

As before, stores a random untelegraphed spread or partner stack for later.

This is a good time for healers to use regens to heal up from the end of Beat 1.

3:07 - 3:11 Stinging Slash / Killer Sting

Whichever tankbuster was not used earlier. This allows tanks to have branching personal mitigation plans if they so choose. In particular, a tank can guarantee that they use their invulnerability on Killer Sting either here or the preceding tankbuster, allowing them to take it alone with no further mitigation.

3:16 - 3:21 Tempting Twist / Honey Beeline

As before, casts a random ground AOE with follow-up Splinter honey blobs that force players to move.

Splinter and the stored damage resolve at 3:26. The party has a moment to set up healing before...

3:34 - 3:38 Alarm Pheromones (Alarm Pheromones 1)

Four Groupbees spawn around the edge of the arena, spaced 90 degrees apart. They can appear on either all cardinals, all intercardinals, directly between each cardinal and its clockwise adjacent intercardinal, or directly between each intercardinal and its clockwise adjacent cardinal. (These are the same 16 possible positions as in the original, divided into the sets from the original Alarm Pheromones 2.) At the same time, the closest player character to the boss is targeted for a four-player-character multi-hit Enumeration, visually marked.

2.5 seconds later, another four Groupbees spawn, adjacent to the previous ones but either clockwise or counterclockwise at random. (One randomization that applies to all the Groupbees for this mechanic.) This repeats two more times, so the entire edge of the arena is lined with Groupbees 7.5 seconds after the castbar ends. (Spawn times 3:38, 3:40.5, 3:43, 3:45.5.)

Here is a diagram of the Groupbee spawn groups, each group marked with a different in-game shape sign:



10 seconds after each Groupbee spawns, it will lock onto the closest player character to itself and set its path to go through that player character's position, shown by the Groupbee line appearing as it starts its Blinding Love cast. Thus, the first set of Groupbees will lock on 2.5 seconds after the last set of Groupbees appears. (Lock-on times 3:48, 3:50.5, 3:53, 3:55.5. Groupbee casts complete 3:54.5, 3:57, 3:59.5, 4:02.)

As each set of Groupbees locks on, the Enumeration hits once, leaving behind a venom puddle underneath it that lasts for 22 seconds (just like the player-baited puddles in the original Alarm Pheromones 2). At minimum Item Level and even somewhat above it, the four hits of the Enumeration combined will reliably KO any non-tank from full HP, and will be painful even for tanks when combined with auto-attacks resuming after the Alarm Pheromones cast completes. (So unlike the original, there is a healing requirement here even with perfect play.)

Now that I have described what the mechanic does directly, let us go over what it suggests to the party as a solution, and what that solution asks of players.

If the Groupbees appeared by themselves or with a stack, strategies could easily develop that have them baited by half the party (one player character beside each Groupbee), two players (characters positioned opposite each other at the edge of the arena, weaving between the Groupbee lines), or even the whole party (skew from the center and move as a group). But I do not want any players to wind up standing still, nor do I want the whole party moving together - hence the Enumeration and puddles, which make it difficult to leave two player characters out of everything and useless to soak the damage with the whole party. Veteran raiders will recognize that the mechanic suggests having half the party bait the Groupbees, and the Enumeration marker confirms that to them.

(It is still possible to do the other bait strategies, making this mechanic not a body check. But that is not easy or advised.)

In theory, the party can split who baits the Groupbees and who takes the Enumeration however they like. But since the Groupbees are all spread out and the boss has an appropriately small hitbox, parties will intuitively give the Groupbee baits to Disciples of Magic and physical ranged DPS. This has several effects:

• It puts the healers away from the player characters taking heavy damage, creating a distance party heal check even after getting some mitigation / healing from the tanks and melee DPS. Distance healing is a way to make the puzzle of heal planning more interesting, encouraging healers to think about what parts of their toolkit they want to use when. Yet there are lots of ways to solve this particular distance party heal check, making it suitable for new raid healers: any SCH fairy heal (especially Consolation), Holos, Panhaima, Philosophia, any "healer bubble", manual or timeout detonation of Liturgy of the Bell, any GCD party shield, any GCD regen if cast shortly before the baits (utilizing the regen ticks), even Cure 3 will work. If both healers and any tank put something on this, the party will be fine, and they really do not need to put a healer in the Enumeration to find ways to do it. (They still can put a healer in the Enumeration, especially in a single melee party, but it is not that helpful once the healers have thought about what tools work for distance healing.)
• It encourages the Groupbee baiters to think about prepositioning near the edge of the arena, in whatever quadrant the party has assigned them. (If I wanted to prevent the Groupbee baiters from prepositioning towards their quadrants, I would have the Enumeration target the furthest player character from the boss instead. But that is more appropriate for higher Savage floors or Ultimates.) Magical ranged DPS and physical ranged DPS can do this with no downside so long as they do not get hit by Stinging Slash, while healers have to weigh their prepositioning against the range and timing requirements of the healing tools they plan to use.
• Meanwhile, it encourages those taking the Enumeration to think about working in a small space and utilize the ability to move underneath the boss. Parties have the choice of whether they want the puddle baits to be done by a tank or a melee DPS (or another role), but if they want positional uptime they will have to move in lockstep regardless. And since the puddles persist for so long, they do not want to move too far when baiting or afterwards while waiting for the puddles to disappear. (The puddles disappear during the 4 minute burst window, at 4:10, 4:12.5, 4:15, and 4:17.5 respectively.) Skilled puddle baiters will also leave room for BLM/RDM/SGE to come in to melee range after baiting Groupbees.
• Both groups practice recurring movement techniques that are commonly given to their role. The process of baiting the first Groupbee in a quadrant so that it does not get in the way of the later baits - look at it, look around it for the next one, move into bait position tucked in tight, move out of the baited AOE - is very similar to the process of baiting a spinner. (I considered putting spinners here, but the Groupbees create their AOEs by moving rather than firing a beam, so spinners did not fit perfectly. Since Blinding Love is a 6.5 second cast as in the original, the Groupbee baiters still want to tuck in tight so that their first bait cannot cover a neighbor's second last bee (locks in 1.5 seconds before).) The players taking the Enumeration instead practice positioning relative to each other to maintain uptime on small hitboxes, as well as stutter-step puddle baiting.

Despite only having 2.5 seconds for each Groupbee baiter to identify their first Groupbee without working backwards, this mechanic does not pressure the reaction time of anyone who can get to it. This is because the baiters can already be looking towards their quadrants during the initial Alarm Pheromones castbar, and have lots of time to act on that information before their first Groupbee locks on. (I made the initial Alarm Pheromones cast a second longer than in the original for exactly this reason.)

In fact, the rhythm of the Groupbees locking in and the puddles dropping is deliberate, to fit slidecasting and instant casts comfortably for all but the highest amounts of Spell Speed on Disciples of Magic. (Healers' movement windows from 1.5 second base cast times will work. BLM can use a Triplecast for the three movements between their four bait positions, and then has time for a hardcast before leaving their last bait position. RDM can use a Dualcast into Acceleration similarly. You get the idea.) Lining up one's GCD with the movements should be satisfying, and the lock-on times are late in a minute precisely to make that happen for both the popular 2.50s and 2.40s GCDs. (If I wanted a different timing, I would have moved the memory mechanic and/or tankbuster to make it happen.) The point in one's GCD that it lines up with is different for healers than for other roles, but that was an unavoidable result of healers' 1.5 second base cast times compared with other jobs that can precast a spell.

Even before a player gets to that level of mastery, the whole mechanic is meant to be satisfying despite being fairly easy for Savage. It involves using the duty's recurring elements to create a smooth sequence, which players can enjoy watching as it goes off. It feels like a natural upgrade to the redesigned Normal's Alarm Pheromones 2 and 3 - which also have player-baited Groupbees - but this time it is the party's choice who baits what. And it gives players back a measure of control over the battle, contrasting against the boss trying to control their characters in the Beats.

The party then gets a relative breather of a burst window and healing opportunity while the puddles disappear, before...

4:18 - 4:27 Honey B. Live: 2nd Beat

Once again, this raidwide transforms the arena and brings out the charm gauges. As in the original, four hearts are initially assigned. One heart each goes to a random light party (one tank, one healer, two DPS). (This is slightly more structure than the original, which assigns one heart each to two random DPS and two random tanks or healers.) However, another randomly chosen light party also get Command Performance (no shape). The two light party randomizations are completely independent; each party member could get one, both, or neither.

Unlike the original, the party will want to organize quickly, both because their burst should be wrapping up and because there is no stored damage cast to give a longer movement window.

4:31 - 4:35 Love Me Tender (Multiple Effects)

As this cast ends, four heart towers spawn at once, in the "mid" cardinal positions from Beat 1. As before, these resolve 10 seconds after they spawn (4:45).

Five seconds after the towers spawn (4:40), a Heart-struck pink puddle spawns under each player character's position. (Thus players must wait before moving their characters to their towers or planned spread spots, and waiting with a plan is an important recurring skill. For healers, this is also a time to heal the party up from the previous raidwide.) Heartsore spread AOEs also appear on the light party without Command Performance. The puddles, spreads, and towers all go off at once.

Here is a diagram for one solution the party might agree on to assign towers and spread positions, using the Looper icon to represent Command Performance:



(The puddle baiting in the original is not bad, but I did not want Beat 2 to feel too much like the redesigned Alarm Pheromones 1 or Alarm Pheromones 2, hence the change to a single puddle each that can be stacked since they all drop at once. This also makes Beat 2 feel more like the redesigned Normal's Beat 2 and Beat 3, despite the redesigned Normal not using puddles at all.)

Once again, the Command Performance debuffs expire two seconds after the towers (4:47). At this point, every player character has at least one heart (from their spread or tower) or is KOed by their Command Performance. The party has a total of 12 hearts if there were no mistakes so far in this Beat.

(And players still engage with Command Performance differently than Looper, because only half the party gets Command Performance here.)

4:44 - 4:48 Love Me Tender (Stack)

Creates another four-heart Heartsick stack, spawning on a random player character with the lowest number of hearts. Brings the party up to a total of 16 hearts when it hits at 4:53.

Players with one heart will want to bring their characters into the stack, while those with two hearts will want to stay out of the stack. Since the light party that initially got 0 hearts is the stack group now, the natural place for players to place the stack is in the middle of the arena, giving the other light party access to melee range if they are careful.

4:55 - 5:00 Blow Kiss

Unlike the original Normal, Blow Kiss is a cone protean with moderate damage that inflicts a heart on each hit. (For those who are not used to old raiding terms: one cone on each player character, do not hit anyone else with yours.) Blown kisses are not exactly avoidable on Earth, and this boss is blowing pheromones around trying to control the party.

Proteans have a classic resolution: everyone stand in their preassigned "clock spot" angles. And since everyone is guaranteed to get hit once and take another heart, this forces the party to distribute the earlier 16 hearts evenly or take KOs / filled charm gauges.

(While Blow Kiss is inherently limited to the Beats, and so does not allow many opportunities to use the protean, that is okay. Parties are likely to assign tower and spread positions related to their chosen clock spots throughout the Beats, helping players remember their spots in that party.)

Since this is a cone protean, not a line, the party can stand quite close to the center of the boss. This allows healers to reach the whole party with AOE heals both before and after - while Blow Kiss itself only deals moderate damage, the whole sequence and the heart DOTs are more than enough to leave non-tanks at low HP and get them KOed by Honey B. Finale.

This is not difficult for Savage as an individual mechanic - nothing in Beat 2 is - but the pacing punishes players for hesitating too much. (In 20 seconds, each player drops their puddle, moves for their spread / tower, moves in/out for the stack, and may have to move again for their clock spot depending on their planning.) It is not an Ultimate pace, or even a final floor Savage pace, but with the heavy randomness it is enough to trip up players who do not know their part well. (The Combos here and the Cycles from Eden's Gate: Descent (Savage) are faster at the same difficulty, but they specify the entire movement pattern from the castbar, so players can execute those sequences without having to think about random variations within them.)

As a whole, the redesigned Beat 2 is the fastest "song" out of all the Beats. And it rewards players who map out their movements, since all necessary information about the randomness for Beat 2 is given at the start of the Beat!

5:05 - 5:10 Honey B. Finale (ends Beat 2)

As before, a raidwide that transforms the arena back and cleanses all hearts. Has a shorter wait after the previous mechanic than Beat 1's Finale, since the party has already had the opportunity to be in healing range and the shorter wait reinforces Beat 2's "fast-paced performance" feel.

5:15 - 5:19 Killer Sting / Stinging Slash

As before, a random one of the two tankbusters.

If a tank used their invulnerability on the immediately preceding tankbuster, it is not available here, as this is less than four minutes later. However, if the first set of tankbusters put Killer Sting first, a WAR player can choose in that branch of their mitigation plan to use Holmgang both at that time and again on a Killer Sting here. (This sort of thing is an inherent result of designing the tank jobs with different invulnerabilty cooldowns.)

Of course, the tanks can choose to tank swap in advance; even if one tank used their invulnerability on the previous Killer Sting, the other tank has the opportunity to use their own invulnerability on a Killer Sting here if they have prepared by having the highest enmity when the cast starts. New raiders will generally not accomplish this immediately, as it requires remembering that the tankbuster is coming before the castbar appears, but it provides an opportunity for stronger players to express their skill by mitigating more effectively.

5:24 - 5:29 Splash of Venom / Drop of Venom

As before, stores a random untelegraphed spread or partner stack for later.

5:31 - 5:35 Alarm Pheromones (Alarm Pheromones 2)

As in the original, except that the Groupbees replay the pattern that the party baited in Alarm Pheromones 1, slowed down to half speed to match the five second pace of the venom puddle drops. (The Alarm Pheromones castbar itself is also one second longer than the original, to match the redesigned Alarm Pheromones 1.)

(As a reminder, one DPS and one tank or healer are selected completely at random for the first set of puddles, while subsequent sets select one DPS and one tank or healer completely randomly out of those who have not yet been selected. If any player characters are KOed, disconnected, or otherwise unavailable, there will be repeat selections after going through all player characters present and able to act, which will KO those selected a second time due to the lingering vulnerabilities. If any player character is KOed after being selected, the puddle bait will remain on them.)

While the original mechanic is fine as an individual mechanic, I made this change to reinforce the idea of the party taking back a degree of control over the battle, even while dealing with being chosen in a random order (within their role group) for the venom puddle drops. Most obviously, the Groupbees have been baited by the players earlier. (And they may have left themselves a mess if they were salvaging Alarm Pheromones 1!) But also, the tight space that the players must work with for the eventual stacks is now created by the players themselves (dropping the puddles) rather than the Groupbees, giving the party more agency in how much space they have and how they arrange it.

As a result, strategy designers seeking to optimize damage uptime will gravitate to having tanks and melee DPS drop their puddles at or close to max melee distance, with the melee DPS working near the "positional walls" between the rear and flanks. The other roles can then drop their puddles well outside melee range, leaving open space to take the role stacks either North and South or East and West.

These choices will become relevant to later mechanics, as the puddles once again persist for 22 seconds each.

Groupbees spawn at 5:35, 5:40, 5:45, and 5:50, along with the overhead markers for the puddle drop selections. They immediately start their Blinding Love casts, finishing at 5:41.5, 5:46.5, 5:51.5, and 5:56.5. These latter times are also when the puddles drop, almost perfectly matching the original timings.

(Here, there is no separate Poison Sting castbar. From a mechanical standpoint this is fine, as players still see the overhead markers for the random selection, and have been primed to expect puddles from the redesigned Alarm Pheromones 1. From a technical translation standpoint, bees are venomous rather than poisonous - the danger is in getting stung, not eating them - and players will get a damage name from the text accompanying the light AOE that drops their puddle anyway.)

The puddles disappear at 6:03.5, 6:09.5, 6:13.5, and 6:19.5 - well into the 6 minute burst window where many players will want to use potions. As in the original, skilled players are encouraged to plan their rotation for every possible time they could be selected to drop their puddle.

6:02 - 6:07 Bee Sting

As in the original, stack markers appear on one random DPS and one random tank or healer at the beginning of this castbar. These role stacks resolve at the end of the castbar, wrapping up Alarm Pheromones 2.

Just like the original, the timing of this heavy damage (hits about as hard as Call Me Honey when taken as two groups of four) encourages healers to think about healing well before it, well after it, or with limited oGCDs, so as to avoid losing damage output during raid buffs. However, the next mechanic will encourage pre-healing even more than the lingering potions alone in the original do.

6:14 - 6:19 Tempting Twist / Honey Beeline

As before, casts a random ground AOE with follow-up Splinter honey blobs that force players to move. This timing dictates that the uptime strategy for Alarm Pheromones 2 leave the open spaces for the role stacks at East and West, so that players can reliably dodge Honey Beeline even though the last puddles have not yet disappeared. I have placed a few extra seconds of breather here, to ensure that the puddles do not get in the way of movement for Splinter while having them matter to positioning for Honey Beeline and the 6 minute buff window. Let players feel the confined space for a moment!

Splinter and the stored damage resolve at 6:24. Yes, this will sometimes mean leaving melee range and moving large distances during raid buffs - thinking about uptime does not always mean it will be easy! Tanks and melee DPS can leave melee range for only part of a GCD and then gap-close back in, and those with frequent cast times can plan out how to get in an instant cast and/or use a movement tool. Or eat the damage loss for one worse GCD; it is not that big a deal for clearing, and I do not think duty design should be warped around always facilitating the perfect parse run with no randomness from the duty or thought about where to put buffs.

Ideally, healers will have set up their healing such that the party is back to full HP from Bee Sting without having to lose damage in raid buffs, so that no one is KOed here. However, if they have not done so, they do have 17 seconds for regens to work between Bee Sting and the stored damage.

6:28 - 6:32 Stinging Slash / Killer Sting

Whichever tankbuster was not used earlier. Again, this allows tanks to have branching personal mitigation plans if they so choose.

If the first set of tankbusters put Killer Sting first, a WAR or DRK player can choose in that branch of their mitigation plan to use Holmgang or Living Dead both at that time and again on a Killer Sting here. If the first set of tankbusters put Killer Sting second, no tank can use their invulnerability both at that time and again here. As before, the tanks can swap in advance, guaranteeing each tank a productive usage of their invulnerability.

This time also allows healers to regen the party between the last stored damage and the start of Beat 3, unlike the original.

6:36 - 6:45 Honey B. Live: 3rd Beat

Once again, this raidwide transforms the arena and brings out the charm gauges. As in the original, no hearts are initially assigned.

Also as in the original, every player character gets a debuff that will eventually explode in a large "defamation" heart AOE that is only slightly smaller than the arena, with the timer based on role groups. (For the sake of technical translation correctness, I am renaming this Venomous Pop, but it is the Poison n' Pop from the original.) At random, either DPS will get the "short" timer and tanks and healers will get the "long" timer, or vice versa, just like the original. The actual durations of "short" and "long" are different, since there is no memory mechanic cast, but the concept is the same.

There are no Command Performance debuffs this time. The party will still want every player character to take a tower - the original Beat 3 is a fine mini-phase and I am only changing its gameplay to replace the memory mechanic - but those who enjoy blind progression get to figure that out rather than being told by the debuffs. In Beat 1 and Beat 2, Command Performance placed restrictions on the party's options, while here it does not so there is no need to use it.

6:43 - 6:49 Centerstage Combo / Outerstage Combo

As before, either of the avoidable ground AOE sequences. (Second and third hits at 6:52 and 6:55 respectively.)

Near the end of this sequence at 6:53, the first set of four heart towers appears half-way between each intercardinal and one cardinal axis: either North and South or East and West at random. (These are the same positions as in the original.)

A reminder of what these positions look like, with the two possibilities in different colors:



The "short" Venomous Pop timers expire and release their AOEs at 6:59, four seconds after the Combo finishes. The heart towers resolve another four seconds later at 7:03. This is the same relative timing as the original, encouraging but not requiring players with Venomous Pop to preposition towards their chosen spot at the edge of the arena during the Combo.

On a mechanical level, it is up to the party where they will create a safespot from the Venomous Pop AOEs to avoid excess hearts, and whether the towers will be taken by the role group that just had their debuffs expire or the role group that was waiting in the safespot. If they want to put in the effort of finding and using precise positions and Sprint to give tanks and melee DPS uptime while dropping the Venomous Pop AOEs, so be it.

But the healing is easier if the heart towers are taken by the role group that was waiting in the safespot, since that will distribute the necessary 8 hearts evenly across the party for even DOT ticks and AOE healing. (Doing it the other way is possible, but annoying for the healers and not advised unless it is to prevent a missed tower, since the Venomous Pop AOEs deal over half a non-tank's HP at Minimum Item Level and stacking higher DOTs on top of that leaves them not far from KO.) All this is well and good from the original.

7:03 - 7:09 Outerstage Combo / Centerstage Combo

As in the original, whichever ground AOE sequence was not used earlier. (Second and third hits at 7:12 and 7:15 respectively.) As in the original, the reverse of the earlier randomness plays out here with the AOE timers and towers as well. Even the 20 seconds between the first and second sets is just like the original.

The second set of four heart towers appears at 7:13, half-way between each intercardinal and whichever cardinal axis was not used earlier. The "long" Venomous Pop timers expire and release their AOEs at 7:19, followed by the heart towers resolving at 7:23.

At this point, the party is now up to at least 16 hearts, with every player character having ideally taken one Venomous Pop AOE and one tower.

7:28 - 7:35 Take a Bow

When this cast completes, player characters are paired completely at random with the Supporting Cast debuff, which doubles their hearts taken from any source while they are too close to their partner. To aid players in interpreting this debuff, the tethers between paired player characters are in the the "get away from each other" blue arrow style from E10S and come with Playstation markers. (Conveniently, the redesigned Normal ensures that all players who can enter this duty have seen both of these, even if they are new to endgame!) The arrows fade and get smaller whenever a tether pair is sufficiently far from each other to not receive double hearts, providing a further visual cue akin to tethers to an object or NPC fading when sufficiently stretched. The necessary distance is almost the full diameter of the arena.

(Experienced raiders may look at this and think "Remote Glitch but with hearts". Yes, that is what this is. And while TOP Party Synergy is an Ultimate mechanic, "stay away from your partner" is a second floor Savage mechanic as demonstrated by E10S Shackled Apart, and "find your partner via Playstation marker" is already in Storm's Crown (Extreme) - so this is entirely viable for second floor Savage as long as players are not asked to do anything too complex or fast with the tethers on. Do not worry, it is nothing too difficult.)

Seeing this, players will want to not only see their own Playstation marker, but also assign positions to each "side" of a tether to keep them apart for whatever subsequent attack is going to inflict hearts. And the established way to do this is for the party to line up in a "conga line", allowing everyone to see their own Playstation marker and where their partner is. The result looks a lot like the theatrical practice of ending a play by having all the actors line up on stage and bow to the audience... as the name of the cast alludes to. This furthers the evocative tension from Normal in Savage style - in order to avoid filling the charm gauge, players will want to do as she says and find out their specific assigned part!

For healers, the conga line is also an opportunity to heal the whole party up (from the ticking DOTs and the Venomous Pop damage) before everyone must spread back out for the next attack. They can also apply shields for upcoming damage and DOT ticks should they choose, though it is not needed even at minimum Item Level.

7:44 - 7:49 Blow Kiss

As before, Blow Kiss is a cone protean that inflicts moderate damage and a heart on each hit. The Playstation markers disappear at the start of this cast.

This time, the hearts will be doubled (filling the charm gauge) unless players stretch their tethers to manage Supporting Cast. Accordingly, the clock spots must be assigned to tethers and sides, not to player characters. This is not a difficult assignment. Since the tethers must always be stretched, parties will simply take their preferred ordering of the Playstation markers, set that order around one half of the edge of the arena, and repeat it around the other half of the edge of the arena.

Players must remember to go to their new position, and what that position is. But the length of the Take a Bow cast and the time between it and Blow Kiss are deliberately generous, to allow players to scan over the conga line even if they hesitate or put substantial attention on their job. (For a higher Savage floor or an Ultimate, I would set a faster pace to demand that players more tightly control their own attention. But this will very likely be a newer raider's first conga line and first exposure to Playstation markers in the high-end style of "make a plan that accounts for all possible pairings", so a gentler pace is suitable here.) Each player has nine seconds to check at most four markers, all of which are in close proximity.

(For those who are not familiar with scanning through a conga line for Playstation markers: Each player must identify their own marker and their own side of the tether. If their tether partner is to the left of them, then they are on the right side of the tether, and vice versa. Since their tether partner must be on a side of them, they need only check one side, and can choose the shorter one for speed. That shorter side has at most three player characters on it - for this not to be the case, both of their sides would need to have at least four player characters, for a total of nine player characters in the instance. So each player must check at most three markers other than their own, for a total of at most four markers, and they are all in an uninterrupted line that allows for smooth planned eye motion.)

From a mechanical standpoint, this gives every duty in the Savage tier its own twist on proteans: M1S has Quadruple Crossing, M2S has this, M3S has Quadruple / Octuple Lariat, and AAC Light-heavyweight M4 (Savage) (M4S) has Electrope Edge 2.

From an uptime standpoint, full uptime requires effort for anyone with significant constraints here. Yes, tanks and melee DPS are going to have to leave melee range briefly. The end of the cast is positioned late in a minute and thus moderately late in a slow GCD so that players can hit their GCD, run out, and then gap-close back in if they want to put in the effort to maintain uptime. (Which is not easy, especially since failing the timing fills the charm gauge on both the player character attempting it and their partner!) Meanwhile, those with frequent cast times must contend with the possibility of having to go almost all the way across the arena from their conga line spot, and plan instant casts and/or movement tools accordingly - there are only two spots in a conga line (the edges) that can guarantee which side of their tether they will be on, and the presence of any magical ranged DPS other than SMN in the party ensures at least three jobs with frequent cast times. And even those who are on the edges can still have to go to any of four spots around the edge of the arena, so they will want to get moving quickly (and set up healing accordingly) if they plan to slidecast their way there.

From a thematic standpoint, Honey B. Lovely is ending her performance by simultaneously thanking the player characters and making one final attempt to control them. (The debuff is called Supporting Cast because she wants to be the star. "Nobody steals the spotlight from me" and all.) Definitely a sting hidden under that sweet surface, especially to spectators in-setting who cannot see the tethers or markers!

7:57 - 8:02 Honey B. Finale (ends Beat 3)

As before, a raidwide that transforms the arena back and cleanses all hearts. Has a longer wait after the previous mechanic than the previous Finales, to allow the party to come back into healing range from the very edge of the arena. While this gives the party a moment to refocus after having to find their new spot, it is not entirely a kindness - the heart DOTs are still ticking.

As a whole, the redesigned Beat 3 is the slowest "song" of all the Beats, compared to the fast Beat 2 and moderate Beat 1. The slower pace enables the high randomness combined with large movement distances, creating a sweeping final performance before Rotten Heart.

8:10 - 8:14 Killer Sting / Stinging Slash

As before, a random one of the two tankbusters.

Consider what happens if this tankbuster rolls Killer Sting: If the first set of tankbusters put Killer Sting first, any tank player can choose in that branch of their mitigation plan to use their invulnerability both at that time and again here. If the first set of tankbusters put Killer Sting second, a WAR or DRK player can choose in that branch of their mitigation plan to use Holmgang or Living Dead both at that time and again here. Only the PLD+GNB tank pairing loses out on the opportunity to get a third productive invulnerability use out of a third Killer Sting.

(Again, this sort of thing is an inherent result of designing the tank jobs with different invulnerabilty cooldowns. Preventing that in the duty design would require delaying this tankbuster by almost a full minute, thus delaying Rotten Heart and distorting the battle overall.)

As in the original, this tankbuster placement creates a relatively open raid buff window where non-tanks can focus on their burst rotations. Players who dislike the slightly disrupted 6 minute burst window may choose to place their second potion here instead of there, but in this version that is something to think about rather than using a potion every time it is available for a burst window. (M4S has the early potion to avoid getting cut off by its transition, but that is about it. I would like to see that more often when it suits the duty design.)

This is the last random tankbuster, each of which has two possibilities, creating a total of eight possible timelines for tankbuster order and therefore tank mitigation planning. This number is on the high side relative to expected duty completions, since a player needs one to two small armour pieces and one to two accessory augments from this duty to complete a Best-in-Slot set for a role, but it is workable because the player does not need to have multiple mitigation plans to complete the duty without burdening their party even as a tank. ("Share every tankbuster with a fixed order of personal cooldowns" will work just fine for the tankbusters themselves, and the randomization does not change the timing of any mechanics.)

Branching timelines that change mechanic order have tighter limits, as the player - regardless of their role - is effectively forced to make a plan regarding their job for each timeline or else have their plan not function in some attempts. Here, it is optional skill expression even within the context of players choosing to attempt the duty, and so tanks who will be frustrated by not getting to use plans for every timeline can simply just not make them. Meanwhile, tanks who expect to go through many duty completions, or simply enjoy the planning, have the timelines there to enjoy.

8:25 - 8:30 Rotten Heart

As in the original, this raidwide transforms the arena and applies the Beeloved Venom debuffs. (It hits as hard as Call Me Honey, too. Hopefully the party has a mitigation plan by this point!) Honey B. Lovely also locks herself in the center of the arena facing North for the remainder of the battle, now focusing on getting rid of the party using her venom and Groupbees. (There is a mechanical reason for this too.)

I am adding to the mechanic though, since the original is rather easy - and boring - for a full 90 seconds of a duty, as I mentioned in my review of the original.

As in the original, there are four different debuff timer lengths, each of which is given to one player character for Beeloved Venom Alpha and another for Beeloved Venom Beta. These assignments are completely random, except that each player character gets exactly one Beeloved Venom - including KOed player characters. (Should these expire without being cleansed, they apply a heavy paralysis and a KO respectively. While they are present, they include a light DOT, comparable to a single heart during a Beat.)

Unlike the original, the order of the timers is marked for players with the First in Line through Fourth in Line convenience debuffs, to facilitate doing more than just mixing the Beeloved Venom types in a controlled fashion. (For those unfamiliar, the [number] in Line debuffs do not have any mechanical effect of their own, only serving to show players the order the boss has assigned them for the "core part" of a sequential execution mechanic. Using them here also provides a gentle introduction to this tool for new raiders, as here they have the time to realize what it does by looking at the debuff timers.) I did not use these in Beat 3 since it does not have a clear "core part" to read the sequence from; the towers and large AOEs are both equally important, even though the large AOEs are the only ones directly dictated by the debuffs.

Also unlike the original, all player characters receive a Contact Poison debuff lasting for the rest of the battle, which makes any contact at all between two player characters cause a Big Burst explosion without removing the debuffs. (From the original, Big Burst deals moderate magical raid damage that applies a seven second vulnerability to further magical damage, including Call Me Honey. There, it is caused by mixing Beeloved Venom types instead.) The two player characters who made contact receive five seconds of Poison Immune, allowing them to finish casts and move away without further explosions. Contact between the two types of Beeloved Venom is still necessary to cleanse them, and also to create the new Beeloved Antivenom debuff, which lasts for 30 seconds after its creation.

(Since the heal check here cannot be increased by heart stacks, Big Burst hits a little harder than it does in the original. Not a lot, the main danger is still timing the strong magic vulnerability, but about 10% more damage. While this is roughly equivalent to three heart stacks at 3% damage up each, Call Me Honey is not getting buffed at all and it is the bigger hit. The resulting overall heal check of Rotten Heart should be roughly equivalent to the original when the boss has one heart stack, but with a more even damage profile.)

(And yes, from a technical translation perspective, Contact Poison is correctly named. Poisons are passive, relying on the action of those affected, and Contact Poison does not do anything until the players act to make it explode.)

In turn, Beeloved Antivenom is needed to soak the Groupbee towers, which return from the redesigned Normal Mode. The towers have the same possible positions as in the redesigned Normal, and still spawn in pairs, but the pairs are no longer constrained to be across from each other. The only constraint on the random position selection is that each position will be used exactly once. (And this is why the boss is locked in place. I do not want tanks to find themselves moving the boss for momentarily leaving melee range and unable to move it back because of the Contact Poison debuffs around, especially since both tanks can have the same timer length and the melee DPS are also stuck respecting the debuffs!) A reminder diagram of the tower positions:



Without Beeloved Antivenom, player characters cannot neutralize the sting and so cannot affect the towers. As a visual cue to this, the towers do not light up from player characters without Beeloved Antivenom standing in them. (Yes, I am using the visual cue from TOP's towers requiring Looper, it is a good cue and does not need to be restricted to Ultimates.) If a Groupbee tower goes off without a player character with Beeloved Antivenom inside, it explodes for high raid damage (the same as Call Me Honey) and inflicts 30 seconds of the Stung debuff on all party members. Stung is a stacking, heavy DOT - a single stack hits about twice as hard as having three hearts during a Beat. Healers might be able to salvage one missed tower, but considering the ongoing damage, the party may not have the HP to give them the opportunity.

When a Groupbee tower is taken with Beeloved Antivenom, it does no damage at all, just removes Beeloved Antivenom from any player characters standing in it. (This is a second Savage floor, not an Ultimate; I am not making the healers do Program Loop spot healing on top of an AOE heal check. Spot healing the player characters with the longest Beeloved Venom timers on top of the AOE heal check is enough.) This makes logical sense for the creation and use of an antivenom.

As in the original, players must space out the Big Burst explosions around not only each other, but four Call Me Honey casts. These occur at 8:45 - 8:50, 9:01 - 9:06, 9:17 - 9:22, and 9:33 - 9:38. (This is not the same pace as the original, which has less time to the first raidwide but more time afterwards. The changed timing is deliberate, to allow players to check their [number] in Line and mentally prepare themselves.) Each [number] in Line's Beeloved Venom debuffs expire one second after the start of the matching Call Me Honey cast, so if players forget their timing they will get caught out by the magic vulnerability.

A pair of Groupbee towers spawns at the start of each cast and resolves 15 seconds later, at 9:00, 9:16, 9:32, and 9:48. As such, at most one pair of towers is on the field at any time, so players do not have to distinguish between towers about to resolve and towers freshly spawned. (Again, this is not TOP Program Loop.) These towers give players an extra five seconds compared to the heart towers, to help them deal with the random positions and move around everyone else.

Now that I have described what the mechanic does directly, let us go over what it suggests to the party as a solution, and what that solution asks of players.

Most obviously, player characters need to remain spread out somewhere for an extended period. To avoid accidental collisions when taking towers, those locations should be out of all the towers and discourage meeting near the towers to create Beeloved Antivenom. For the sake of uptime, strategy designers will want to put the tanks and melee DPS in melee range, and try to give melee DPS access to the positional walls.

At that point, it is easiest to put everyone well within melee range inside the ring of towers, so that no one tries to run through the towers in a panic or makes contact with someone taking a tower by accident. And to give players fixed locations with clear reference points to avoid touching, it is convenient to use the clock spots from earlier on the inner layer of the boss's targeting ring. (Traditional clock spots even put the melee DPS on the positional walls.) Players should already remember the clock spots they agreed upon from the earlier and easier proteans, even if their strategy for spreading Venomous Pop and assigning heart towers does not use the clock spots.

The party can then use the very center of the arena to cleanse Beeloved Venom and create Beeloved Antivenom. So far, this is much the same strategy that is popular in North American Party Finder for the original; the only difference is that the cleanse timing must be more precise to prevent Beeloved Antivenom from wearing off early, rather than precise timing simply being helpful for the healers.

But now, rather than simply returning to the boss's targeting ring in their clock spots, each pair of players must agree on who will take which tower in their pair. Since both the tower spots and the player character pairs are random, the whole party must agree on and remember a priority system for splitting up the towers. (Or have voice chat, but for strategies that are doable in Party Finder / Raid Finder.) Players are free to devise whatever priority systems they would like, including ones that aim to preserve specific jobs' uptime, but the simplest will be along the lines of "Venom Alpha looks at the ring of towers from North going clockwise and takes the first tower they see, while Venom Beta looks at the ring of towers from North going counterclockwise and takes the first tower they see".

(Some players will try to go without a priority system and say "yolo" or "use eyes", and that will go poorly for them. It was unavoidable that players would try, given a long time to see the towers, but the center of the arena is not safe to adjust through. Not only is there the ring of those waiting, but the next pair needs to create their Beeloved Antivenom while the current pair is getting to their towers.)

Optimization is thus a puzzle on both a party level - devising uptime-preserving priority systems the party can consistently execute - and a personal level - planning for every possible [number] in Line around the uptime and healing considerations of one's job. The Fourth in Line players can even pre-locate their towers by paying attention to all the previous tower spawns. Have fun!

On top of that, two pairs of player characters will often be outside the hitbox at once: one going to their towers, and the other returning to their clock spots from their towers. The party must therefore agree on and execute a system of "lanes" or other priorities to prevent collisions, which also encourages those who can do full damage at range to use that fact and create more room. (Some players will also try "yolo" / "use eyes" here, to slightly better effect, but getting stuck in a loop of reacting to each other is still deadly.)

This teaches players to stay still far more strongly than the original does. In the original, players are free to move their characters within their clock spot wedges so long as they only go to the center at their assigned time, and can even move further once their neighbors no longer have Beeloved Venom. (Players mostly do not use that freedom of movement because there is no need to.) In this version, players who are waiting their turn have their characters confined on all sides: in front is the central meeting spot, to each side is another clock spot, and behind are two lanes for dealing with towers! The message is clear without using any AOEs or puddles - stay the heck still, and especially do not touch outside of creating Beeloved Antivenom.

Staying still and not touching are themselves foundational to handling debuff passes and tether passes, which are recurring mechanical elements in higher Savage floors and Ultimates. (M4S has both in Mustard Bomb!) Before a player can pass a debuff or tether with the expected control, they must learn to stay still, both to not pass when they do not want to and to provide a clear target for the other player in the pass to work with. (As both players and designers, we work with the netcode we have got.)

Thematically, this does not use any ground AOEs at all, nor the puddles from Alarm Pheromones, but it sure feels related to the latter through the tight space. And it is related - the towers that make the space so tight are from Groupbees suicide bombing the party! Rotten Heart has become a twisted upgrade to Alarm Pheromones, where Honey B. Lovely has dropped both the pretense of caring for her Groupbees and the performance of the Beats to KO the party at any cost. (The towers can even be seen as a lingering hint of her performing skill from the Beats, while feeling different due to the longer timer and different context.) Players can enjoy the theme when it is not their turn to move.

And players do still have time when it is not their turn to move, to stand still and deal damage. But the longer period of movement, along with needing to find their tower (and for some priority systems, notice their timer partner's position), makes the time spent standing still a breather to a high-focus mechanic that would be too harsh for a second floor otherwise. (It is scary and precise, but players have ample time if they avoid panic and maintain focus. It would be a disaster if the whole party had to move at once.) This version is actually 10 seconds longer than the original, but it does not feel like it, between adding more than 10 seconds of movement and requiring more focus during one's movement.

Yes, this makes the duty as a whole harder - not just in making a mechanic harder, but with mechanics late in a duty being more time-consuming to progress due to the time taken to get there each attempt. But that does not make it wrong to do, especially when the concept of the duty suggests it. The original duty as a whole is too easy for anyone with a good reaction time, and it should be terrifying when a charmer and performer finally drops all their acts. All the rules they were keeping to for the sake of their acts no longer bind them, and all the energy they were spending on pretenses they now have free to use.

I also made sure that there are no "boss-assigned roles" that have to do very different things, keeping down the number of practice attempts a player needs to learn Rotten Heart - they only need to practice the nuances of the one thing they will do every single time they see it, with at most a different timer and different tower priority. (Putting a "boss-assigned roles" mechanic with individually difficult "roles" this late in a duty would be too harsh for a second floor, and more so the more "roles" there are.)

Yes, players will attempt to skip Rotten Heart. Players attempt to skip every mechanic they perceive as difficult late in a duty - unless the damage output requirements are so high as to prevent them from doing so - it is inherent to the incentives created by requiring mechanical consistency. "Skip Soar or disband" is still a meme from Heavensward. That is not a reason to make all final mechanics easy.

10:00 - 10:10 Sheer Heart Attack

As in the original, this is the effective enrage, bringing out and immediately filling the whole party's charm gauges upon completion. Thematic enrages are fun and should be kept.

I have added five extra seconds before this cast starts and therefore ends, to reward players who think about how to front-load one last partial raid buff window rather than autopiloting their rotation loop. (Not every duty should do that, but the mechanical timing suggested it here.) This also allows the Fourth in Line players to return to their clock spots to take full advantage of the last moments of the attempt - they have the same amount of time between their towers resolving and the enrage cast as there is between the original last raidwide and enrage cast.

10:14 - 10:19 Honey B. Finale

As in the original, this is the raidwide that actually KOs the party.

Since the party cannot attack through Devoted Drone, she takes her time to give one last flourish to the audience before the party KO - unless DOTs KO her first, pets KO her while their "owners" are unable to act entirely, or the party decides to go out on their own terms using Contact Poison. (The nine second tense wait guarantees exactly three DOT ticks after the charm gauges fill, though the party can choose to end it after five seconds.)

Should budget and voice acting constraints allow, there is room here to add a special line or sound effect for the enrage, and even a brief cut-off line for the party choosing to interrupt her. Not necessary, of course, but it would spark even more memes.

----------------

Not only does this redesign of Honey B. Lovely keep her lore and concept, I have even kept the highly random nature of the mechanics. In fact, Beat 3 and Rotten Heart are both significantly more random than their original versions, and Beat 2 forces the whole party to deal with the randomness rather than allowing the 0-heart group to ignore it with the "braindead" strategy. (And knowing where the Groupbees will be in Alarm Pheromones 2 comes from paying attention in Alarm Pheromones 1, not from "oh there is a hidden pattern that the first set always has safespots clockwise of each cardinal.") But the duty no longer pressures reaction time, whether to the boss itself or to fellow players, making it consistently doable by players who choose to put in the effort to learn it - even though the redesign is harder!

It is not an accident that I have heavily used forms of randomness that are common in Ultimate, it is by design, because those forms both force the party to deal with high randomness and ensure that they can learn to manage it every time. Randomness is fine, and can enhance a mechanic, even some fast-paced mechanics that require players to learn to efficiently process the information they have been given. Handing a player a failure that they cannot do anything about - they cannot change the boss's random choices or their own reaction time - is not just unpleasant but demotivating.

It is also not an accident that many parts of the design reward players for digging deeper into their jobs and the duty. (Tanks can always use their invulnerabilities if they make a branching mitigation plan for the tankbusters, because of the hidden pattern. There are multiple selection order mechanics for everyone with uptime constraints to map out all possibilities. And so on.) Pushing for greater mastery of a duty and one's job is a fun thing to do once players can consistently do the mechanics at all, it is a form of skill expression, and it should be rewarded rather than frustrated.

I have cut the occurences of the memory mechanic down, but not removed it, since memory mechanics are fine as a light seasoning with care not to let them get boring or crowd out other forms of difficulty. I want to demonstrate what an appropriate amount looks like in a duty timeline, with the understanding that not every duty (or even most duties) should use them. Even though in this case that means just cutting it from the Beats, that makes a big difference - it is four uses of the mechanic total rather than six, and two of those are the opening ensuring that players have seen all possibilities. (Indeed, if the Normal could be relied upon to teach the Splinter follow-up patterns, the opening pair of occurrences could potentially be cut down to a single one, forcing Drop of Venom since it is not a partner stack in Normal. (Much like how Alphascape V2.0 (Savage) (O10S) opens with the one animation tell AOE that is not demonstrated in the Normal, and expects the party to know all the patterns thereafter.) But there is not enough room in the Normal to reliably teach both that and Playstation markers, so I prioritized the concept that is interesting to casual players in the Normal.)

Unfortunately, I cannot demonstrate with a single duty design the appropriate balance between testing and rewarding tanks' skill at positioning a boss, and allowing for duty concepts and mechanics that indicate that the boss should position itself. First, that is a matter to be weighed over an entire Savage tier or even an entire major patch, not a single duty. Second, Honey B. Lovely's concept as a performer indicates that she largely should be positioning herself on her stage for her audience. (For an example where adding more positioning skill tests would fit a duty concept, albeit with reworked mechanics, M4S could have had the boss's hitbox gradually get smaller as she feeds her own body into her electrope.) Third, Tempting Twist and Honey Beeline both require precise dodging with floor references when combined with the memory mechanic, so to leave that in, I had to keep her positioning herself for those as well.

While no single duty design can demonstrate that duties need not and should not all feel the same mechanically, Honey B. Lovely's concept is great to demonstrate leaning into a duty concept as a way of creating mechanical variety. Not only does a charm-based enemy suggest different mechanics than a more head-on battle, but she has two "modes" within herself: the charming songstress and the venomous queen bee. I have deliberately created mechanical contrast between her modes - the Beats as performances on a wide-open stage, while almost everything else has movement restrictions from her venom and her Groupbees - to make the duty better express her concept. The contrast and the chosen mechanical styles create a push and pull between the boss and the party for control of the battle.

She has an excellent concept, really, it has just been overshadowed by the duty design issues. I hope this redesign example has helped demonstrate how to avoid those issues and make the game more fun for everyone. If Dawntrail had been designed like this, not only would players not have complained en masse about Honey B. Lovely, but I would be in a FRU static rather than having to sit out of its launch entirely.

You have promised to improve job design for Patch 8.0, and players have been complaining about job design for a long time. (Indeed, I myself am a systems-oriented player, hence my prior writing about job design.) Strong job design can and would prevent much of the boredom players experience in the Endwalker and Dawntrail duties. But none of that will matter if players are driven from the game by duties they cannot improve at, or have too many annoyances from duty design in the course of playing their jobs. You must get both designs right, individually and interlinked.

Give us challenges we can all rise to meet and aspire to master, not barriers we cannot do anything about.

[Aurelle_Deresnels]

I must humbly confess that I do not speak Japanese; for your convenience I have attempted to translate the above letter via Google Translate. Please pardon any mistakes so generated. In case of any confusion, please refer to the English text if at all possible, as I cannot verify the accuracy of the machine translation.

正直に申し上げますが、私は日本語が話せません。皆様の便宜を図るため、上記の手紙を Google 翻訳で翻訳してみました。間違いがありましたらご容赦ください。機械翻訳の正確さは確認できませんので、ご不明な点がありましたら、できるだけ英語のテキストを参照してください。

--------------------------------

吉田PとファイナルファンタジーXIV開発チームの皆様へ

まず、フィードバックをもっと早くお伝えできなかったことをお詫びします。グラフィックアップデートで健康と安全上の問題が発生したため、Dawntrail早期アクセス開始から3週間以上経ってから、安全にゲームを見ることができるポストプロセス方法を見つけるまで、Dawntrailのコンテンツをまったくプレイできませんでした。その結果、パッチ7.00のメインシナリオクエスト（MSQ）をパッチ7.05とAACライトヘビーウェイト（サベージ）のリリース前日まで完了できなかったため、まずサベージティアを完了し、パッチ7.0のコンテンツデザインをまとめて徹底的にレビューしたほうがよいと判断しました。

特にエンドウォーカーのコンテンツデザインに関するフィードバックに応えて、プレイヤーが楽しめるコンテンツを提供するために一生懸命取り組んでいることがわかります。私は、エンドウォーカーの任務設計に戻ることを主張しているわけではありませんし、ゲーム全体を簡単にすることを主張しているわけでもありません。実際、私はパッチ 7.0 で利用可能なすべての任務を完了しましたが、そのどれもが 3 回かそれ以下で私を飽きさせました!

パッチ 7.11 で登場する Futures Rewritten (Ultimate) (FRU) などのより難しい任務に挑戦して完了させたいと思っています。実際、私はエンドウォーカー中に The Omega Protocol (Ultimate) (TOP) を完了したので、パッチ 7.2 のリリース前にパッチで FRU を完了することを目指すのが論理的な次のステップです。

しかし、私はそれを実行できず、FRU をまったく完了できない可能性があります。そして、それはパッチ 7.0 の任務設計のせいでもあります。

ご存知のとおり、私は障害のあるプレイヤーです。医学や生体力学については触れませんが、特に翻訳では読者にとって難しいかもしれませんが、私の筋肉は「普通の」人間の体よりも反応が遅いです。うまくプレイできるだけの速さで入力するには、両腕を肩まで使って入力しなければなりませんが、それでも反応時間が少し遅くなります。もちろん、TOP はできるので、それほど遅くなるわけではありませんが、進行中 (ハイエンドの任務のメカニクスを練習中) は、最も速いメカニクスをもっと勉強して、効率的に処理する方法を学んでいます。「リーダーに従う」やコールアウトに頼るのを避け、代わりにすべてを自分で解決することを好むほどです。なぜなら、他の誰かがメカニクスを処理するのに反応することで余分な遅延が発生すると、他の全員がセーフスポットに到着する間に私のキャラクターが KO される可能性があるからです。私がすべての作業を費やしたにもかかわらず、単純な老化や高遅延によって動きが遅くなった人のように動いています。

Duty Finder のプレイヤーの大半は、私と一緒にプレイしても気付かないでしょう。 (私はデューティファインダーで「リーダー」として、パーティに仕組みを教えることが多かったです!) レイダーの大半は私と一緒にプレイしても、私が言わない限り気付かないでしょう。ただし、自分の体にとって入力パターンが悪いためにレイドを避けているジョブに切り替えるように求められたり、怪我を避けるために設定したレイド時間制限を超えるように求められたりすると、レイドグループに伝えることもあります。

なぜ時間制限があるのでしょうか? 他の 7 人のプレイヤーが私の入力を十分速く行うことに頼っているということは、私が自分自身に高い基準を課していることを意味します。私の体は健康な状態でそれを長く維持することはできません。覚えておいてください、私はすでにプレイするために両腕をフルに使っています。ゲームをプレイし始めたとき、徐々にスタミナを鍛える必要がありました。レイドのベースラインを超えると、頻繁にストレッチしたり、食事を増やしたり、特別な栄養バランスをとったり、身体に回復時間を与えるためにレイドのタイミングをより戦略的に考えたりする必要があります...アスリートが集中的にトレーニングするときにそうしなければならないのと同じです。(私も、ベースラインを超える時間を数週間以上維持することはできません。) 健常者と自分との違いは確かにわかります。なぜなら、プレイできるように舞台裏ですべての努力をしているのは私自身だからです。

(地球上で私に会っても、ほとんどの人は、高い身体能力や筋力を必要とする作業が発生しない限り、私に気づきません。オフィスが従業員全員に重いものを持ち上げたり、非生産的な残業をしたりすることを要求していない限り、私はさまざまな仕事をすることができます。医師に相談すれば、フィットネスのためにできるスポーツがいくつかあります。車の運転もできます。無意識のうちに補償するスキルがそれ自体で十分に優れていたため、障害があることを知らずに路上試験や緊急事態のトレーニングをすべてパスしました。(たとえば、ほとんどのドライバーは、車が死角にあることを最初に知るために肩越しに確認するのであって、周囲の交通を継続的に追跡して確認するのではないことを知ったのは、何年も経ってからでした。) 障害のせいで私よりもパフォーマンスが悪い人はたくさんいます。)

Dawntrail 以前、私のレイド時間は週 9 時間が基準でした。Endwalker の最後の方まで、週 12 時間を超えることはありませんでした。Dawntrail の早期アクセスの前に TOP を完了するために、Party Finder で進めていたにもかかわらず、週 14 時間までレイド時間を延長しました。当時は、そのためにやらなければならないことは信じられないほど集中的だと思っていました。インスタンスの外で完了ビデオ映像や打撃ダミーを使用して練習した時間は除き、毎日 2 時間という厳格なスケジュールで、休みはありませんでした。(誤解のないように言っておきますが、Party Finder ではそう簡単にはいきません。各パーティーでの時間を毎日集計する必要がありました)。各セッションの直前、セッション中の 1 時間経過時、直後だけでなく、1 日を通してさらに数回ストレッチしました。ガツガツと食べながらも、タンパク質、脂肪、微量栄養素をすべて食事に取り入れるよう注意深く計画しなければなりませんでした。手の負担を減らすために、パーティー チャット以外ではほとんどタイピングしませんでした。地球のスケジュールではこれらすべての対策が講じられていたにもかかわらず、私が体をここまで酷使しようとしたのは、Dawntrail のリリースとそれに伴う MSQ で 1 週間 (必要なら 2 週間) 自然に回復できるとわかっていたからです。

AAC ライトヘビー級 (Savage) の進行に週 9 時間費やすのは、あらゆる面で体に負担がかかりました。ストレッチや食事、睡眠だけではありません。Dawntrail は、私が自分のケアのためにあらゆることをしているにもかかわらず、ゲームをプレイして初めて手が痛くなったときでした (痛みを感じたらすぐにやめることはできませんでした。痛みは後でやってくるので、やめるのに丸 1 か月かかりました)。Dawntrail は、レイドだけでなく通常の任務に時間制限を適用することを検討しなければならなかった最初の拡張です。Dawntrail は、運動で徐々に増加するのではなく、私のスタミナを効果的に低下させ、それに合わせて時間制限を下げることを真剣に検討するようになった最初の拡張です。

パッチ 7.0 の任務設計のこれらの結果を考慮すると、任務全体を個人的に詳細に分析しなければ、FRU を完了できるかどうかはわかりません。もちろん、リリース後かなり経って、メカニクスのランダム性から生じる多くの可能性を適切に理解できる大量の完了映像が利用可能になるまでは、分析できません。同様に、たとえ FRU を物理的に実行できるとわかっていたとしても、さらに詳細な分析を行わなければ、少なくとも週 9 時間の FRU 進行を継続できるかどうかはわかりません。(私は、TOP や Dragonsong's Reprise (Ultimate) (DSR) のリリース前に喜んで取り組みました。Endwalker の開始時には週 9 時間の基準値があったからです。)

そして、週 9 時間未満では、リリース日からパッチの残りの期間を通じて効率的に時間を使用する静的レイド グループ (多くの場合、「静的」と略されます) であっても、リリース パッチで Ultimate をクリアすることは統計的に非常に困難になります。 (なぜそうなるのかを検証したスプレッドシートはありますが、レイドの一貫性の計算は重要ではありません。) Ultimate が要求する一貫性の高い基準を満たすメカニクスを適切に学ぶには、十分な時間がありません。

これを知っているので、良心に従って FRU を完了する意図で静的にコミットすることはできません。また、複数の友人が FRU の静的に興味があるか尋ねてきました。そうすることはグループに対して不誠実であり、私自身の健康にも害を及ぼします。Live Letter 83 で FRU に挑戦するときは健康に気を付けるべきだと皆さんが言う前から、私はそのことを知っていました。また、ローンチ パッチでパーティー ファインダーを使用して Ultimate を進めるには、DSR で経験したように、1 週間あたりさらに多くの時間が必要です。パーティーの明示された目的に対して準備が整っていないグループで無駄に過ごした時間を補うためだけでなく、任務を迅速に完了するために 1 週​​間に 30 時間以上を費やしている強力なプレイヤーに追いつくためです。彼らに遅れをとると、パーティーは良くなるどころか悪くなり始め、そこから悪循環になります。

そのため、非常に悲しいことですが、FRU から遠ざかることを余儀なくされることが分かりました。少なくともパッチ 7.2 の後半 (AAC Cruiserweight (Savage) の後にプレイヤーの関心が戻るまで)、そしておそらく永久に。私は難しい任務に興味があり、熱心に取り組んでいます。私は SCH の完全な最大アイテム レベル ベスト イン スロット セットを所有しています。これは、単に最大ダメージ出力のためではなく、FRU の進行のために設計されており、必要に応じてセットを調整するための本も持っています。(毎週 Savage ティアを繰り返しているので、必要に応じて他のジョブの武器を入手できます。) Eden Savage への懐かしささえ感じています。しかし、パッチ 7.0 の任務に飽き飽きしているのと同じくらい、私の体は現在の任務の設計方向の物理的な要求に耐えられません。

これまでの Dawntrail の全体的な設計方針、つまり義務設計とジョブ設計との相互作用の両方の結果として、現在の義務は精神的には非常に簡単で、肉体的には非常に困難です。 これは、運動の形として設計されていないゲームにとっては非常に悪い状況です。そして、そのようなゲームは、特定の形式と運動の強度を求めるニッチなプレイヤーに限定されることを受け入れています。幅広く永続的な魅力を求める MMO にとって、これは適切ではありません。この手紙の残りの部分では、この問題の両側面を修正することを目指して、より詳細なフィードバックを提供します。

私自身だけでなく、Strayborough 人形と Honey B. Lovely の義務について不満を述べた多くのプレイヤーのためにも。これらの義務は、そのメカニズムが非常に反応性が高く、若くて健常なプレイヤーでさえイライラさせるため、広く不満を集めました。 AAC ライトヘビー級 (サベージ) を 10 時間未満でクリアしたことに失望しているワールド プログレッション レイダー、および、ほとんど苦労しないタスクが興味深い難易度を圧迫していることに気付いた一般的な熟練レイダー向け。加齢によって反応速度が遅くならざるを得なくなったプレイヤー向け。(このゲームはかつて「格闘ゲーム プレイヤーの引退ホーム」と考えられていました。このジャンルは、最高レベルのプレイヤーが素早い反応に依存しているため、トップ プレイヤーは年齢を重ねてジャンルから完全に脱落します!) Dawntrail を始めて 1 か月か 2 か月で、まったくの退屈さから登録を解除したプレイヤー向け。戦闘デザインは、拡張のローンチ メジャー パッチで無料ログイン キャンペーンを実行するのが適切だと判断するほど登録数が急激に減少する唯一の問題ではありませんが、間違いなくリストに含まれています。 (確かに、World of Warcraftは独自の拡張パックであるThe War Withinをリリースしましたが、それはパッチ7.05のほぼ1か月後のことでした。Dawntrailはグラフィック、ストーリー、エンドゲームを最初に公開したので、全体的なパフォーマンスが良かったら、もっと多くのプレイヤーが残っていたでしょう。) 「これは難しすぎる」と言わなくなったプレイヤーは、適応したからではなく、身体的または作業記憶の限界に達した場合は適応できないため、他のプレイヤーに怒鳴られたり、イライラしてやめたりしたからです。 (あなたがそのことを言及したインタビューは、Dawntrail 早期アクセスの開始から 2 か月以上経っていたことに注意してください。タイム カードでサブスクライブしているプレイヤーでさえ、その時点ではサブスクライブを解除する機会があったため、ここに投稿することはできなくなりました。) 本当に、すべての人に。

(この段階で FRU のメカニカル デザインを変更することを期待しているわけではありません。すでに確定しているはずです。また、Ultimate のデザインは非常に精密で相互に関連しているため、パッチ 7.05 のリリース時にフィードバックを提供したとしても、FRU に間に合うように完全に対応することはおそらくできなかったでしょう。(Ultimate の任務デザイナーには大きな敬意を抱いています。彼らは私たちを限界まで追い込む任務を引き受けますが、それを超えることはありません!) しかし、パッチ 7.3 以降、あるいは AAC Cruiserweight (Savage) などのパッチ 7.2 の任務でもそれを活用できることを願っています。)

徹底のため、この手紙の残りの部分を 3 つの主要なセクションに分けました。まず、現在の任務設計が不十分な点に特に重点を置きながら、設計の原則と全体的なスタイルについて説明します。次に、パッチ 7.0 の繰り返し可能なインスタンス化された任務を私の視点から分析し、良い点と悪い点の両方を取り上げ、私がメカニクスをどのように体験しているかについて多くの例を示します。退屈だと感じる読者の方は、2 番目のセクションを飛ばして 3 番目のセクションに進むことをお勧めします。これは、Honey B. Lovely のノーマルとサベージの両方の任務の完全な再設計であり、Dawntrail コンセプトに適用したいデザイン スタイルを示しています。

ゲームの歴史全体にわたる任務の仕組み、および敵の背景にある伝承との関係について広範囲に説明しますので、他のプレイヤーの皆さんは注意してください。この手紙の残りの部分は、MSQ 以外の任務を含む、パッチ 7.05 までの完全なネタバレです。