Twintania conflag bug

Time: always
Frequency: always
ISP: At&t Uverse
World name: Ultros(all)
Class/level: bard/50
Party or solo: party
Area: Bahamut's Coil turn 5
Steps:
1. Get to Twintania phase 2
2. Twintania casts conflag on random raid member
3. Cast sleep on the newly created conflag
4. Conflag timer ends and conflag disappears, not killing the character it was put on


This mechanic is meant to be killed before it explodes killing the character put inside it, it does not seem right to be able to completely bypass a core mechanic so it does not have it's intended affect.

Please Square, this turn has been brought down twice now for 2 weeks total. If this needs to be brought down again to fix this issue please make sure all mechanics in the fight are working as intended before it is brought back up. You guys have already said twisters are working fine but it's hard to believe even hardcore guilds have not figured out how to take the rng out of it. Please if you fix this issue take a look at the fight in it's entirety before bringing it up again just to take it down a day later because another issue came up. Please get a new team of testers and review the entire fight until everything is fixed.

Confirming this bug in our raid as well.

Confirming this as well.

This is getting sad now.

Heard about it on a stream. They refused to do it.

It's not even the only bug in the instance right now, this is ridiculous. Adds and Divebomb are broken too.

This is pathetic, can confirm.

It is borderline asinine that it took 2 weeks to remove a single exploit and yet all other problems with this fight remain along with newer ones. It does not bode well at all if this is the quality we have to look forward to in future content if the current team of testers can't even figure out a single fight. How many fights will be in Crystal Tower? We're getting extreme primals, 2 hardmode instance, king mog, and all the content that will come after 2.1. I do not wish to play any of it if the problems going on with Twintania are what we have to look forward to on anything beyond it.

Please fix your problems whether they be with the testing team or dev team. I enjoyed the game up to 50, I enjoyed what little content there has been at max level so far. I would like to keep enjoying the game as patches come out, but if we have nothing to look forward to because of problems that can't be worked out in a timely manner then what reason is there to continue on when they will just get worse as more and more content comes out?

More specifically, it would seem that any mob or entity that has a special effect on death (small snake adds spreading debuff, conflagration exploding) are affected by this. If they are disabled in some way (stun, sleep, etc) they do not properly die.

In the case of conflagration, if it is slept or stunned when the timer expires, it will not explode properly and once it awakes it simply disappears. In the case of the snakes, if stunned before they explode and complete their death animation, they become invulnerable and do not die.

Quote:

---

Originally Posted by Pellegri

It is borderline asinine that it took 2 weeks to remove a single exploit and yet all other problems with this fight remain along with newer ones. It does not bode well at all if this is the quality we have to look forward to in future content if the current team of testers can't even figure out a single fight. How many fights will be in Crystal Tower? We're getting extreme primals, 2 hardmode instance, king mog, and all the content that will come after 2.1. I do not wish to play any of it if the problems going on with Twintania are what we have to look forward to on anything beyond it.

Please fix your problems whether they be with the testing team or dev team. I enjoyed the game up to 50, I enjoyed what little content there has been at max level so far. I would like to keep enjoying the game as patches come out, but if we have nothing to look forward to because of problems that can't be worked out in a timely manner then what reason is there to continue on when they will just get worse as more and more content comes out?

---

Honestly though, this is how you fix bugs. No dev team can find 100% of bugs in content by themselves; it's only after hundreds of people going through the content and running into things that bugs get discovered and fixed.

not sure if this is a bug aswell

http://i.imgur.com/CLgcCmI.jpg

this is without benediction - bendiction if you see on the side is still on cooldown and only 4 minutes had pass since that timestamp, while benediction still had a good 2minutes on its cooldown.

Basically I healed Cure II none crit for 6172 x.x im still perplexed about this.

Have you considered that CC effects are part of a legitimate way to beat the instance? Why have CC in the game at all if it works on nothing?

This just seems like you're mad someone was doing it in a stream earlier and that they might legitimately beat the instance before you.

Quote:

---

Originally Posted by Churchill

Have you considered that CC effects are part of a legitimate way to beat the instance? Why have CC in the game at all if it works on nothing?

This just seems like you're mad someone was doing it in a stream earlier and that they might legitimately beat the instance before you.

---

I consider cc effects to be a legitimate way to beat an instance by disabling adds on a fight whether it be boss or trash to take them out of the equation while dealing with everything else. I do not consider cc effects as a way to completely bypass boss mechanics when it's clear as day the intended way you are meant to deal with said mechanic especially when it is a spell that is being used and not a mob.

I do not find a problem with cc being used on adds in the fight(other than the fact that it makes them invincible if it's used too close to their death). What is a problem is the fact that conflag is a spell that is used by the main boss to disable a player and needs to be dps'd down to prevent said player from blowing up. Using sleep completely voids this mechanic when it's clear the intent was to have players actually kill it before it blows up their party member.

I'm sorry you came in here and got mad because someone reported your "clever use of game mechanics" because you feel you need the crutch to defeat this encounter. Square has touted this fight as being the hardest in the game so far again and again. If difficulty can be bypassed by cheap exploits or unintended uses of game mechanics then do you honestly feel like you accomplished a kill when it was handed out because of said cheap tricks?

Quote:

---

Originally Posted by PkFire

Honestly though, this is how you fix bugs. No dev team can find 100% of bugs in content by themselves; it's only after hundreds of people going through the content and running into things that bugs get discovered and fixed.

---

This is how things are fixed the vast majority of the time as players give a much larger sample size as to any problems that may be wrong in a fight. The problem is though is this fight has been worked on by players for almost the last 2 months and it feels like it is largely untested by any amount of devs. Some of the the issues that have come up in the last 2 months have for the most part been widely known and while some(like this) have never gotten bug reports posted on them, any amount of research could have shown the results players have come up with.

Most mmos with pve worth mentioning actually have a way for devs to watch a fight as players do it making adjustments as they make attempts(this goes for any high end content that is not tested on ptrs). It feels like that is just not here though when they have to bring down the turn every single time a problem comes up and even with all the info out there nothing has been fixed over the course of the past 2 maintenances other than a widely known exploit that was the only way to down the fight.

CC doesn't work on adds though, CC works on almost nothing. The only time CC works is when the fight is specifically tailored for that one(ish) CC effect to work. We've been using Stun since our second day in Turn 5 and it never once occurred to us that it might be illegitimate because its use made sense given all the data before us. You can break the conflag normally and lose a player once in awhile due to the rotation of Conflag/Fireball or use a CC effect that actually works and by god if you do it right you don't lose anyone.

This isn't the hard part of the fight, not that there really is a part that is difficult because it is difficult. This is the tedious part that we've done hundreds of times to get to the parts that definitively have not been tested.

A lot of people assumed this was not an exploit considering it's been known since the start and has survived every Twintania shutdown.

I figured if SE doesn't want them to be slept in this way, they would have made them the same as Rocks in Titan. [You cannot sleep/etc the rock bombs in Titan.]

I don't consider it an intended way to defeat a fiery conflagration with a sleep or stun.... it is most likely a byproduct of the current mechanics.

Quote:

---

Originally Posted by Churchill

CC doesn't work on adds though, CC works on almost nothing. The only time CC works is when the fight is specifically tailored for that one(ish) CC effect to work. We've been using Stun since our second day in Turn 5 and it never once occurred to us that it might be illegitimate because its use made sense given all the data before us. You can break the conflag normally and lose a player once in awhile due to the rotation of Conflag/Fireball or use a CC effect that actually works and by god if you do it right you don't lose anyone.

This isn't the hard part of the fight, not that there really is a part that is difficult because it is difficult. This is the tedious part that we've done hundreds of times to get to the parts that definitively have not been tested.

---

I highly doubt sleeping conflag is a legitimate mechanic. It doesn't make sense to me that you can stun/sleep a fire sphere, and just because you've done it hundreds of times doesn't make it a correct mechanic. The alternative way of doing conflag makes much more sense and seems more intended to for last boss fight of the game than to sleep a ball of fire and have it go away 5 seconds later with minimal effort.

All that being said, I think SE should seriously attempt to do twintania and see if they're able to successfully do it before releasing the content back into the game.

Edit: CC works on plenty of mobs. Just not most of the raid mobs.

Well, as they said themselves, they designed the fight to be beaten by less than 100 people by 2.1, so every broken thing works in their favor here. I can only speculate why T5 wasn't properly QA tested, but my best guess is, they assumed twisters RNG will wipe everyone anyway, so no point debugging the fight in-depth. Seems like the dungeon is very low priority on their list for some reason.

This isn't the last boss fight of the game though, it's a boss fight that wasn't tested and was put out the door because without it and a lack of Crystal Tower there would be even less to do. If you take out the bugs, this fight was beaten 4 weeks ago and by now would be an extra 15 minutes to the 35 minutes it takes to do Turns 1-4.

Quote:

---

CC works on plenty of mobs. Just not most of the raid mobs.

---

So it's useless then? The only time CC works is when it's part of the strategy. Without those few instances where it's necessary to defeat something, you could get rid of every single CC ability and the game wouldn't be any different. You don't need stun to beat Ifrit, you need to not suck at dodging. You don't need silence to beat ADS, it just makes it easier. Knockbacks, gravity, blind, none of that shit works or even exists. When something works, I take it to mean it's intended to.

Greetings,

Thank you for posting your concerns about this issue. I have made sure to submit all of your information to the development team and they will thoroughly investigate this matter, based on your report. Unfortunately, I cannot guarantee that a direct response will be posted on this thread, but I do recommend checking Here or Here for any details regarding the development team's investigation. Thanks again for your report!

Thank you for the report.

We are currently investigating this issue and will look into what adjustments need to be made based on the overall balance.

We plan to release a comment about this early next week. We don’t plan on closing Turn 5 again in order to address this issue at the moment, and there are no problems if you would like to continue to challenge this content.