Time to bring back 1.23 multi-job relic style dungeons

[Velhart]

Also needed for cross-class abilities, like Quelling Strikes on BLM.

Needed is not the correct word, you are not restricted from the content simply because you don't have one ability. More like it is less efficient to not have it.

You are more then welcome to come up with suggestions.

Why make a suggestion when we are satisfied with product as it is? People didn't like switching between jobs in 1.xx either. Let me ask, what exactly do you want to become out of a dungeon that you would have to switch jobs in between? This game isn't like 1.xx. In 1.xx, you would switch from one job to a BLM simply because bosses had a certain elemental weakness. While play style is different between each job in ARR, overall all jobs go off potency on their DPS and not some elemental wheel or weakness to a certain thing like piercing or slashing. You are not switching jobs in ARR necessarily, you are switching roles. If it went by your request, SE would have to make it that you have to switch between DPS, healer, and tank. Which comes back to segregating or forcing people to play roles they do not like. I highly doubt SE would ever do anything that would make you feel forced to play more than one role.

The idea is just plain bad.

[Magis]

Needed is not the correct word, you are not restricted from the content simply because you don't have one ability. More like it is less efficient to not have it.

I'd say that Swiftcast is "needed" for WHM if you are doing raids. Your chances to raise players are shot except for rare "breaks", and you lose an important "oh shit" button.

[Cynric]

I'd say that Swiftcast is "needed" for WHM if you are doing raids. Your chances to raise players are shot except for rare "breaks", and you lose an important "oh shit" button.

It's not really. I've played with a few people who didn't have swiftcast and they performed just fine. Thing about raising is that while of course we all know deaths happen. The way content is designed currently if you're playing your best no one should be dying at all anyway. And if someone does die, due to dodging and the cooldowns we have,(mantra, Tank CDs, healer CD's) it's not very difficult to create an opportunity for the second healer to raise. If it's 4 man most of those bosses can be kited in case of tank death or handled with regen/aldo shield long enough to raise.

Content is designed without the use of Cross Class and Limit break in mind. So while they're more optimal they aren't gamebreaking.

[DurtiMonkeyToe]

I'd say that Swiftcast is "needed" for WHM if you are doing raids. Your chances to raise players are shot except for rare "breaks", and you lose an important "oh shit" button.

I still agree with Velhart on his post. Their is no fight in the game where dieing is a mechanic required to beat a boss, therefore Swiftcast is NOT 'needed' if a fight goes the way it 'should.' I realize that fights don't always go that way. I would say having Swiftcast would help a skilled group 'recover' better in a fight, but it is not specifically 'needed'.

[Cynric]

I still agree with Velhart on his post. Their is no fight in the game where dieing is a mechanic required to beat a boss, therefore Swiftcast is NOT 'needed' if a fight goes the way it 'should.' I realize that fights don't always go that way. I would say having Swiftcast would help a skilled group 'recover' better in a fight, but it is not specifically 'needed'.

There are points during turn 7 where in order to recover properly someone will have to die.

[DurtiMonkeyToe]

There are points during turn 7 where in order to recover properly someone will have to die.

But again, that is to recover in a fight where players have already failed. It is not meant to be a mechanic of the fight from start to finish.