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.

[tymora]

played SCH for Coil, played BLM for ST, played WAR for Roulette, played BRD in Ramuh, played WHM doing hunts.

crafted and gathered, all within the last week. not seeing any shaft here.

only thing limiting me from playing more jobs in more places is my iLv and Coil lockout. i don't need or want to change jobs within a single piece of content.

Not talking about using different jobs for different instances. Talking about using multiple jobs in one single run of an instance.

[Reokudo]

Only way that'll work is there's no lockout on endgame dungeons so you can gear your other jobs to the same level as your main. Otherwise you're just going to have a bad time. Aside from that, sounds good on paper but you think SE would make that work correctly? Naaah.

[Nalien]

So by catering to the specific group of people who likes to play only ONE job, the people who likes to play MANY jobs should get shafted?
Discrimination much there?

I don't think you know what discrimination is...

I have everything leveled (don't bother checking this account). I am being anything but shafted; I can gather everything I need for crafting myself. I can craft everything myself. With the exception of required iLvs, I can pretty much get a spot in any content.

The game rewards me more than enough for leveling everything. You're absolutely insane if you think we're getting shafted for leveling more than one Job. If you don't like playing the same Job over and over, switch to one of the other ones you've leveled and play that for a bit. How short must someones attention span actually be to get bored of a Job while in an instance? None of the instances in this game take that long. If you want to play your many Jobs, don't queue as the same thing over and over. Problem solved.

This game does not discriminate against people who leveled multiple Jobs. A system where you require multiple Jobs, however, does discriminate against people who'd rather just play one. Even if you ignore all the advantages of having multiple Jobs that I just listed, it still isn't discrimination. You are not discriminated for having multiple Jobs while another person has one; you're treated exactly the same.

[DurtiMonkeyToe]

This game does not discriminate against people who leveled multiple Jobs. A system where you require multiple Jobs, however, does discriminate against people who'd rather just play one. Even if you ignore all the advantages of having multiple Jobs that I just listed, it still isn't discrimination. You are not discriminated for having multiple Jobs while another person has one; you're treated exactly the same.

I agree with everything you said, but wanted to emphasize this because not only does it discriminate against players that only want to play 1 class, it discriminates against new players. I would be shattered to get my first class to 50 and start looking for a group for end game just to be told "No 50 BLM,SCH, AND PLD? No group for you noob!" That is just plain ridiculous.

When did strategy become "finding the quickest and easiest way to beat something"? It seems to me that it takes way more strategy to require a group to use a standard makeup than "bringing a group of 8 blackmages and nuking something to death."

[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.

[SarcasmMisser]

Provoke is the only absolutely necessary cross class as there are fights with tank switch mechanics that would be close to impossible without it. It's a complete newbie trap to not give warriors their own taunt.