The Chimera, the Monk and the Guard

[DoctorMog]

Don't change the MNK class though.

Keep it as king of single target DPS.

Change the CONTENT to work around MNK. Let's see more fights where monk can beast down single targets/semi offtank.

I would like to see evasion tanking (with actual stacked evasion, not utsusemi)

[Grudgebringer]

Our LS is now switching over to Melee on the Princess... MRD's and Lancers can destroy it a lot faster than BLM and ARC. Legsweeps and Steel Cyclones destroy the adds and Guard pops.. then back to single target WS's on Princess.

[Yves]

I really do agree with the post. HOWEVER...

This is FF. One of the biggest gripes I had with XI and XIV has been that certain classes will be excluded from certain content. I didn't want to play RNG or SMN in XI but guess what? If you wanted the ACP win you were pretty much stuck with a certain setup (pre-uber patch.) It shouldn't be this way but it is and will likely always be. If you want to experience more success then you need to branch out and have multiple classes - THIS IS WHAT THE ARMORY SYSTEM WAS DESIGNED FOR. Again, I'm not knocking the validity of the post - I just don't see it being probable that single-class players will get very far in this game.

Just watch - Garuda will end up being melee-centric and then suddenly BLM is going to be neglected and we start getting the same issue with another class.

Yes, part of this is a function of the community but I don't think anyone can blame people for wanting to be more efficient. While it is true that people can experiment and explore other options, it seems that the OP is not in this position since they are waiting for /sh groups (generally a dangerous predicament to begin with!) To ask these people to potentially forgo hours of gameplay to test a theory is uncool as the investment will exceed the reward in that you will gain very little (if anything) from practicing 10 runs before getting it down. That would be about 6 hours of total time invested to possibly shave 2-3 min from a run, meaning that, well...you can do the math. The return on investment would take far too long to make any sense.

Yes, it sucks. No, it shouldn't be this way. Yes, it is probably going to stay this way. Yes, you need to level other jobs or find a game that doesn't require this kind of flexibility.

[Rogue]

Don't change the MNK class though.

Keep it as king of single target DPS.

Change the CONTENT to work around MNK. Let's see more fights where monk can beast down single targets/semi offtank.

I would like to see evasion tanking (with actual stacked evasion, not utsusemi)

the only problem is tho 90% of situations in this game is with 5+ mobs.. untill that changes blm and their fire aoe will be prefered... because they are most efficient in 90% of situations.

and when mnks might be usefull in a single mob situation guess what.. its a boss fight and there are 3k dmg flying out every 10 seconds.. so then were back to good ol blm.

unless single target dps is buffed hugely or conversly AOE dps is nerfed.. so if fire does 500dmg each to 3 mobs a mnk should do 1500 single target.. but then why have single target attacks just for the sake of it?. just give each DD job equal potential in situations that occur regularly.

im not saying nothing can/cant be done with any job, im saying why go with anything that isnt the most efficient/easiest.

[DoctorMog]

the only problem is tho 90% of situations in this game is with 5+ mobs.. untill that changes blm and their fire aoe will be prefered... because they are most efficient in 90% of situations.

and when mnks might be usefull in a single mob situation guess what.. its a boss fight and there are 3k dmg flying out every 10 seconds.. so then were back to good ol blm.

unless single target dps is buffed hugely or conversly AOE dps is nerfed.. so if fire does 500dmg each to 3 mobs a mnk should do 1500.. but then why have single target attacks just for the sake of it?. just give each DD job equal potential in situations that occur regularly.

im not saying nothing can/cant be done with any job, im saying why go with anything that isnt the most efficient/easiest.

Magic resistant mobs, resistant to fire damage, in smaller quantities, Monk = teh winsauce.

(Edit: Would like to see some of the above since none exists,)

[Geo]

Our LS is now switching over to Melee on the Princess... MRD's and Lancers can destroy it a lot faster than BLM and ARC. Legsweeps and Steel Cyclones destroy the adds and Guard pops.. then back to single target WS's on Princess.

WAR Burn is easily the most efficient way to kill Princess. We usually kill Princess before 3rd guard pops. (sub 2mins).

[fusional]

the community cries for class/job identity, and they get it. Job X performs better than Job Y in situation A. Job Y performs better than Job X in situation B. and it makes sense. except...

then they cry for everything to be homogenized again, because they want to be able to do alllllll the things every other job does just as well as those other jobs, in every single situation.

nice vicious cycle the community is perpetuating. because it just keeps happening.

WAR Burn is easily the most efficient way to kill Princess. We usually kill Princess before 3rd guard pops. (sub 2mins).

it's also entirely easy to accidentally kill the marshal before princess with all that faceroll aoe. DRG does better single target dps and also has two solid aoe WSs to choose from, so when it's geared and played correctly, DRG also easily capable of 200+ dps on the encounter and you're generally at much lower risk of accidentally owning marshal too soon.

you don't have to do any kind of awkward damage control like dragging him out of range to make sure he lives, and yes, you can still very easily grab sub 2min kills just the same.

anyway, point is- i'd be careful about calling it "easily the most efficient way" when there are actually other ways that are as good or better. (ie: 2-3 wars and 2-3 drg)

[Relic]

I agree, but have you considered a different way of fighting princess instead of camping in a corner and AoE? Why not have the tank kite the princess when guard pops, then heavy/bind the guard to separate him from the princess and kill it. If it isn't within range of healing the princess then you're buying more time to kill it.

[Geo]

the community cries for class/job identity, and they get it. Job X performs better than Job Y in situation A. Job Y performs better than Job X in situation B. and it makes sense. except...

then they cry for everything to be homogenized again, because they want to be able to do alllllll the things every other job does just as well as those other jobs, in every single situation.

nice vicious cycle the community is perpetuating. because it just keeps happening.



it's also entirely easy to accidentally kill the marshal before princess with all that faceroll aoe. DRG does better single target dps and also has two solid aoe WSs to choose from, so when it's geared and played correctly, DRG also easily capable of 200+ dps on the encounter and you're generally at much lower risk of accidentally owning marshal too soon.

you don't have to do any kind of awkward damage control like dragging him out of range to make sure he lives, and yes, you can still very easily grab sub 2min kills just the same.

anyway, point is- i'd be careful about calling it "easily the most efficient way" when there are actually other ways that are as good or better. (ie: 2-3 wars and 2-3 drg)

Didn't say it was the best way, however leaves a lot less risk for WHMs dying because of lack of AOE on soilder Ants.

Regarding Marshall, it is quite true that you can almost kill it before princess with just AOEs.. (Usually @5% by princess death)

I agree, but have you considered a different way of fighting princess instead of camping in a corner and AoE? Why not have the tank kite the princess when guard pops, then heavy/bind the guard to separate him from the princess and kill it. If it isn't within range of healing the princess then you're buying more time to kill it.

Sorry, but this is just silly. Lol.

[Aistaraina]

the community cries for class/job identity, and they get it. Job X performs better than Job Y in situation A. Job Y performs better than Job X in situation B. and it makes sense. except...

then they cry for everything to be homogenized again, because they want to be able to do alllllll the things every other job does just as well as those other jobs, in every single situation.

nice vicious cycle the community is perpetuating. because it just keeps happening.

ilu

10charnsh*t