Results -9 to 0 of 16

Threaded View

  1. #1
    Player
    Liander's Avatar
    Join Date
    Sep 2013
    Posts
    32
    Character
    Dyne Liander
    World
    Hyperion
    Main Class
    Conjurer Lv 50

    A Binding Coil review and discussion

    Now that all of the current Binding Coil has been cleared and things have calmed down I wanted to take a moment to look back and review the instance from the standpoint of a hardcore raider. What I'll attempt to do in this review is give a rundown of the pros and cons of each turn and ways I can think of to improve them for instances in the future.

    Before we start breaking down each turn though I'll have to address the dungeon and raiding as a whole. Binding Coil is the first raid dungeon in Final Fantasy 14 and is going to be a multi-turn/zone instance where Free Companies of eight member can tackle bosses in most zones for glorious loot. Currently there are five such turns, four of which contain bosses, which drop ilvl 90 loot and was stated that it would be so difficult that they did not foresee more than 100 people completing it before the December patch. That is all of the true raid content in the game at the moment. Another raid instance, 24 man Crystal Tower, is slotted to be introduced in December but will drop ilvl 80-85 gear. Along with extreme primals though I'm not sure at what gear level they will drop, presumably at or below ilvl 90.

    These details are critical in understanding the first basic problem with Binding Coil, it is simply under tuned. That is all bosses either do not hit hard enough or the mechanics of the fight do not press the players hard enough to account for having lower than intended gear levels, in most cases it is a combination of both. Currently at the end game content outside of raiding the average player has access to two sets of gear, Ampador Keep greens which are ilvl 60 and Darklight token gear which is ilvl70. This means most guilds walked into Coil in a mixture of 60-70 gear yet were easily able to challenge and defeat the first three bosses and progress much in to the last boss, Twintania, with the sprinkles of ilvl 90 that were picked up. This presents a problem since we have our next raid content coming out next month and it is supposed to bridge the gap in gear and help us down coil more easily. Essentially what this mean is Coil, which should have been tuned to push the limits of ilvl 80-85 gear, was beatable in i70 gear thus allowing a large jump in power for raiders. This leaves Crystal Tower in a horrible spot and will end up being a large waste in development time.

    Raiders are now faced with a large problem. Geared in i90 we'll be too powerful for Crystal Tower and left to sit for six months with very little to do as raid production cycles happen. Unfortunately, I don't see a way to fix this outside taking Crystal Tower and quickly retuning it to be higher than i90, which I suspect won't be feasible, thus SE can only take it as harsh lesson on the importance of tuning and raid production cycle as most raiders will probably drop their subscriptions. As I hope to have illustrated that there was a large miss in their tuning for this instance. It was listed at not a 100 people completing it but likely more than 500 will before December.

    Another huge point in the overall design that needs to be addressed, at least for 8 man, is whether or not bringing at least one bard is required. Right now with a bard healing is fairly trivial with infinite mana. The problem is do you design fights with mana song in mind and require a bard or not require mana song and for those who have it healing is easy to manage. Personally I feel mana song should probably be removed from the game and healers given access to other sources of mana and bards a different type of song to play. It's too much of a design headache to force a class on raids or have it be trivialized.

    Well that got a bit wordy but I feel it's a very important piece to take to heart as we look into each turn.

    Turn 1: Caduceus

    When delivering great content in any environment the first area of a zone has a large job of setting the tone of an instance. Turn 1 does so in both an amazingly great way and then in an amazing horrible way. How is that possible you might be asking, being able to do both so amazingly? When you first set foot into Coil you're surrounded by crystal and metal a fusion of science and the more magical aspects. As you walk through the area you the area breathes to you that evil stuff is going on and I applaud their work on the environment. As you progress you run into the murder ball himself ADS. ADS is such a fantastic start to the instance I can't praise it enough.

    ADS is a science construct in the form of a large ball that sets the tone of the instance as it is the first block many had on their first night in Coil as there is a few things to learn before being able to down him. ADS' abilities are those of a boss many abilities to get of in a tight hallway before they kill you, an ability that needs to interrupt or it severely damages and paralysis the raid, and adds to deal with that will buff the boss. So most raiders who were feeling this out I'm sure were in the mind set that ADS is the first boss of the instance. All those abilities, the boss lockout wall, everyone was really pumped to see our first pieces of loot when we first downed him. Then the reality set in, ADS was no boss. ADS was merely a really strong piece of trash and while bummed over getting no loot it set out expectation of the instance really high. This place was going to be no joke, we were going to have to slog through who knows how many strong mini bosses to get loot. That thought was exciting.

    But then you turned the page. The rest of the turn you wade through an odd assortment of beast type monsters in aoe packs with zero challenge. It was a pretty large let down in my opinion and really changed to the tone of the instance to being something great to being something badly routine. This theme sadly follows the rest of the instance, a little bit of good and behind the curtain a lot of mundane and bad.

    Now the boss of the floor, Caduceus, is a large snake and that's about it as far as looks go. Not everything has to be about looks though so I'll give them a pass on it. What really shines on this fight is some pretty neat mechanics. The first thing free companies will find out about our snake friend is he hits like a truck. A truck which through the rest of the fight gets bigger and bigger then grabs his 18 wheeler friend to truck over you some more. The core mechanic behind the fight is Caduceus gets a stacking buff which increases his damage and about around four to five stacks is supposed to be unhealable. To counteract the stacks through the fight parts of the floor will light up, those standing on the lit up parts will spawn a slime which you then run into the snake in order to get him to eat it thus lower his stacks. The problem with the slimes is they have to be kited to the snakes carefully, get too close and they hit you pretty hard and apply a long slow. Get too far and they blow up and kill anyone close. Then even if you do all this correctly the slimes will heal Caduceus for about 10% of his hp bar unless you dps down the slime to low hp before it is eaten. A pretty fun mechanic which can cause positioning to get a bit tricky if the floor which gets lit up is on two platforms that are up a ramp and the lights don’t last too long.

    At 60% or so Caduceus presumably calls his cousin to come wreck your day. These two snakes have to be pulled far apart or they'll fusion dance and start gaining the damage buff every couple of seconds which can't be removed by slimes any more. Then the rest of the fight is dpsing down both snakes and feeding them slimes till finally killing both at about the same time or they enrage and gain super buff mode. Great fight on paper, really fun the first time. Now when you peel back the curtain what's wrong with the fight.

    Most notably, and it's been mentioned by SE that they don't like how it turned out, is after the split phase (or the whole fight if you got some good dps) you can't ignore the slimes completely and dps the boss down. This is mostly due to the boss just having too low of an hp pool that you can kill it but it also stems from what else is wrong with this fight and that is that there is nothing keeping the dps off the boss. The only other two abilities that Caduceus has is an acid spit and a tail whip. Acid spit is a roughly 700 damage nuke on a target that leaves a puddle on the ground which I presume does damage but you simply sidestep it and continue on your merry way. Tail whip is a cone attack from a snakes tail that will only trigger if someone gets behind them.

    Thus you see the problem. The fight is devoid of any challenge besides tank damage. If things were implemented to keep dps off the snake the feed the slime mechanic works really well. Say acid spit instead of leaving a damage puddle either put a large ticking dot on the person it hit which has to be healed through so you can't allow snakes to stack up. Another idea is some sort of character disable, perhaps a smaller snake randomly chooses a dps and constricts them and it has to be killed. Really anything to drag the fight out longer will make slimes work. Tail whip is also pretty nonsensical, while the cone is pretty large it does little to affect the fight beside be a nuisance to melee dps. Changing it to another mechanic, perhaps Caduceus will charge up in throw out his tail in a line direction across the room. Something to avoid, people may mess up and spawn a slime that has to be delt with, you get the general idea. Mechanics need to have some meaning in what they do and raider generally don't enjoy standing in a spot and shooting a boss. We like having things to avoid and controllable havoc being thrown at us. There are lots of ways to improve this fight, I liked where they were headed with it but it needed some extra to make it a real challenge.

    Turn 2: Super ADS

    Turn 2 takes a different approach than Turn 1 when it comes to level design. Instead of having any trash you are given what basically amounts to a choose your own adventure boss. What lay before you is 7 tiny ADS the each have a different buff and ability. After killing one of these mini ADS the boss gains the buff of the killed add. Also through the fight the boss eats the remaining mini bosses left alive and take on their special ability. So you kind of get to create a boss fit for your raid. I find this to be a pretty fun mechanic, it adds a lot in terms of player interaction.

    The major problem though is each mini ADS is the same monster with a different attack. These different attacks barely affect the raid in any meaningful way besides two special cases which I'll discuss in a moment. The problem when learning the fight is it is a pretty tedious task of reclearing each of these mini bosses with their mostly weak special ability and pretty large amount of life. The reason you have to reclear them is when you start the encounter and clearing the adds you're on a timer. Fail to kill the boss for before the timer expires and you all die. Interesting if the timer wasn't so lenient that even in the worst of gear I never saw the timer tick all the way down. I'd like to see some more meaningful abilities given to the adds, so some thought is given to avoid certain abilities instead of just the passive buffs.

    The only exception to this are two certain adds, one which give allagon rot and the other chain lightning. Allagon rot is an ability given by the special out of the way add that places a debuff on a random player. After 15 seconds or so the debuff expires and explodes killing everyone. The way to survive this is to pass the rot to another player but you can't just pass it back and forth between to as you gain a debuff not allowing you to regain the rot for quite a while. So your raid must spread out and pass the rot through several members. Now general you're always going to have this for the boss fight as killing the mini ADS that has this ability gives the boss haste which is pretty soul crushing in the fight. To my knowledge no one has killed ADS with the haste buff, if there is extra to be gained for making the boss harder I'll give a lot more credit to this fight but doesn't quite fit SE's encounter designs. Anyway, you'll almost always have rot, to deal with rot you need to spread out to avoid making everyone immune to rot pick up. Doing this makes chain lightning, the only other ability that isn't trivial, useless. So they designed the fight in a way to counteract their own mechanics by doing another mechanic.

    There isn't a whole lot that needs to be done to this encounter to really fix it. Some stat adjustments and a bit better ability selection could really push this fight to another level. The beginning mini ADS phase could probably be cut a bit in time as it is a bit tedious and given a bit tighter timer on the boss itself or make each ADS a bit more unique instead of clones with only one ability difference.

    Turn 3: Why?

    It was stated they were happy with how Turn 3 is. Remember that for the rest of this. Turn 3 is a zone where you work your way down through packs of random beast type monster in aoe packs with zero challenge at all with a random golem thrown in for kicks. Sounds familiar? The kicker of Turn 3 is there is no boss. There is no story. For all free companies it is a 4 minute annoyance as they run through the zone bypassing all the monsters. I ask why are you happy with how Turn 3 is when you're capable of so much more SE. This is development time, art assets never used anywhere else, and nothing gained from having Turn 3 in the game. Sadly there was at least conspiracy theories and mystery behind Turn 3 but that was quickly killed off devs on the forums. Gamers love a mystery, having that empty zone begged for a hidden boss. It got down on its knees and pleaded for something more. Adding something special for a lucky group to find definitely would have spiced things up. Don't leave areas unused in raid content!

    Turn 4: Elevator Boss

    Like Turn 2 there is no trash in this Turn, but instead of a true boss you're given waves of mechanical monsters to fight in a single room as a timed event before the room starts to blow you up. There's not a ton of strategy involved in Turn 4. Hit the things you do damage to and aoe the rest. This is mostly a gear check fight. Its hard to consider this a boss fight since there really isn't many mechanics worth mentioning. Once you've beaten this fight once there’s little room for improvement or much to pay attention to. Turn 4 suffers in such way that Turn 1 does, you're just attacking the monsters around you without much thought. The fight needs to breathe and keep the players engaged, not just hit attack buttons.

    I wont go in depth in to this fight since there isn't much to analyze but I'd like to see more wave interaction such as mobs in wave 2 dropping something on the ground that wave 5 can't be allowed to get to or each wave destroying a monster drops a void zone that limits the area you have to fight in. At the very least each wave should have an ability that needs to be dealt with beyond not letting spiders get near the big guy, which is a good mechanic in itself but the fight demands more. Wave fights can be interesting and fun but you can't really leave the raiders with nothing to think about or the fight becomes nothing as it has become now.

    Turn 5: Twintania

    A large wyvern dragon, who looks pretty awesome I might add, and his three buddies there to ruin your day. A quick rundown of the fight is in phase 1 you punch his adds till they die as they fire fireballs (heh) that leave a puddle under the feet of those hit. After the adds die you move over to Twintania, who uses an ability called death sentence throughout this phase dealing very high damage, and punch her down 75% or so where his tail ring will break off and leave a visible area on the ground. After this Twintania gains three new abilities, the first a incredibly high damage fireball that has to be split between several players to survive but for each player hit by the fireball Twintania gains a stack of Waxing flesh which causes his next ability to blow up more quickly, the second ability is a disable called firestorm or conflag which locks a player and any others that are too close in a swirling vortex of fire that last for a certain amount of time depending on how many stacks of waxing flesh Twintania has gained and has to be destroyed to save the players inside before it explodes, and last his death sentence gains a debuff that cuts healing by a large amount for a while.

    After punching Twintania to 50% another ring breaks and leaves behind another puddle. Twintania then flies into the air and begins to divebomb plays in an attempt to push them into the sides of the room which will immediately kill the player. After three sets of divebombs three snakes will spawn, 2 small 1 large, which must be dealt with. Above all else killing the small snake near the large one to apply a damage increase buff to be able to cut through the large snakes massive hp pool. After a minute or so Twintania will divebomb three more times and spawn an additional two small snakes. All that needs to be cleared up quick and players stack into the dropped rings before Twintania decendes and explodes dealing massive damage to anyone not inside the circle and hitting those inside for a hefty amount.

    Phase 3 involves three mechanics, death sentence which is the same as before, summon dreadnaught which will summon an add down in the center of the room who you focus on to a person stunning them in place, if the add reaches this person they die, and the last ability is twister which summons an invisible vortex of death under your character which must be moved out of to survive. Surviving these and punching Twintania down to 25% will cause the last phase will begin.

    Phase 4 Twintania continues to death sentence but gets two new abilities to use. One is to fire five of the fireballs used by the adds in the beginning of the fight at a single player. Second is to summon a doom orb which will lock on to a player and fly to them and deal deadly damage to anyone that gets caught in its path and not standing in a dropped ring puddle. Repeat these mechanics and punch Twintania down to 0% to win the fight before too much time passes and she enrages and one shots everyone.

    A pretty complex and on paper a really great fight. Unfortunately what was given to us to deal with was an extremely bugged, poorly tested, and under tuned encounter with several game breaking bugs. So lets go down the list of most of the bugs that plagued this fight for months at a time.

    The major bug, which most are probably familiar with, was the dc bug which would cause Twintania to stop all movement and attacks which allowed for some early kills.

    Phase 1: Sometimes the conflag graphic wont show up - The tank can step in to the conflag and cause twintania to stand still and only use attacks - players could sleep conflag and cause it not to explode and bypass having to dps it down

    Phase 2: (Personal opinion with lots of evidence)Divebomb not being able to consistently dodged without near exploit - snakes that went to 0% hp while stunned would not die - snakes that went to 0% while stunned would pulse several stacks of the debuff

    Phase 3: Players could become perma-stunned if dreadnaught was killed at a certain time - dreadnaught could be bugged to not move from the center of the room - (personal opinion with lots of evidence) twister not being able to be consistently dodged

    That's a pretty large collection of bugs for a single encounter when there is only four raid bosses to have tuned before release. This fight is also pretty underwhelming in what it asks of players. Twintania doesn't really hit that hard outside Death Sentence, which is dropped heavily by debuff rotations, and the mechanics themselves are simple and not really going to kill anyone on their own. This is a fight took two months to down only because of the bugs to Divebomb and Twister.

    Now Divebomb and Twister are a hotly debated topic and I'll give my opinion on that matter. Divebombs currently strategy is to stand in the edge of the room and cause Twintania to fly off the screen. This position causes probably 80% of her hit box to never come on to the battlefield thus this near exploit strategy allows players to move out with little effort by using .01% of the room. This would be viewed anywhere else as a pretty large bug, but it is the only strategy that allows players to dodge divebomb with any consistency. Standing anywhere else in the room and trying to dodge the mechanic in a more logical way will 50/50 be able to get out in time with how it's currently coded. It definitely needs to be rewritten of fixed to be dodgable as it feels it should be.

    Even after spending two months on this encounter people are still in the belief that Twister was not bugged. It confuses me, after spending dozens if not hundreds of attempts on the mechanic and seeing the widely varying outcomes, how people see it as so. Many point to the dev posts about Twister but not once is it said it was working as intended and not bugged only it is called not random. Certainly it's not random, it picks four players every time and they must move to survive. What is random and was able to be proven with countless hours of video footage was weather you survived or not. Given the behavior of the ability after the fix, unless they completely rewrote the mechanic which is a much larger problem to talk about if true, the intended mechanic was always to move when twister is being cast. The bug being the game was updating your position and whether or not you were moving correctly at odd times and killing you when it shouldn't have. Eventually players found ways to semi consistently force update that you were indeed moving but was never reported as being 100% consistent. At which point it was less about dealing with the mechanic and more about dealing with the game's general unresponsiveness and updates. Its fairly obvious to me and others that the twister mechanic was never functioning properly and the fix took much too long to get out.

    So what can be improved to make this fight over all besides bug fixes? Not whole lot needs to be done in the first three phases of the fight. I would call each of these pretty solid mechanic wise besides fixes to Divebomb to make it an actual ability in the fight instead of using .01% of the battle floor to deal with it, and twister which after the changes to it went in function like a real mechanic. Phase 5 is what needs to most work. There’s almost no threat from the fireball attack and the doom orb can usually be absorbed by your off tank and take very little damage. The last 25% of a fight, especially of and end boss fight, should be truly epic and interesting. A good start would be requiring healers to quickly be able to switch and heal those targeted by fireball. Right now the fireball does a very small amount of damage and is generally ignorable by having the person target kite. Another good step would to have the doom orb spawn in more random locations forcing those targeted to be on their toes and not just mindlessly eaten by the off tank. Another small change that maybe be interesting would be to have the outside fire ring slowly creep in to make the area smaller for less kiting room, give the fight a sense of impending doom. Dealing with mechanics and affecting players emotions is a pretty important aspect of raid design that needs to be kept in mind.

    So I apologize for those who stayed and read the whole thing. It got a bit rambly and poorly constructed but I think does a fairly good job at pointing out key weakness in the current raid design and what should be avoided in the future. Of course SE may be happy with what they have on the floor now and continue to make content for more of the casual raiding crowd and that's perfectly alright. But from a hardcore raiding standpoint I can only give the Binding Coil a C grade and only on the potential that I can see under the lack of experience in creating true raid encounters. Thank you for reading and feel free to discuss what is written here if you have questions, have your own ideas on how to improve design, or disagree with any of my points. I'll be happy to respond as I can.
    (13)
    Last edited by Liander; 11-03-2013 at 03:45 AM.