Reasons why a COR should not pull in merit parties
- Our fastest gun sacrifices our WS and QD damage potential
- Almost any other job can equip a ranged attack weapon without sacrificing as much as a COR would have to
- /NIN again sacrifices our DD potential while some jobs natively sub NIN
- We have no method of sleeping multiple links, 2 light shots, on a 50-60 second timer does not cut it
- It further pushes the mentality that COR is only a support job and their DD potential gets completely ignored for any other part of endgame
- Despite other arguments that a COR has "quick" buffs, sometimes they can be extremely slow. Double-Up has an 5 second recast timer. If you have to double up three or four times in a row you've effectively used 20 seconds trying to get a single buff on the party and it might not even be a decent roll without doubling up further. The party can sometimes demolish a bird within that time. Not to mention that we only have 45 seconds to get our roll up to a decent number making it sometimes difficult to start a roll, pull, then try and get our roll to an acceptable level
- Further to rolling, maintaining a -decent- 4 roll rotation is almost always out of the question when having to pull
- We have the ability to out damage melees who do not gear properly (which does happen on occassion!)
Reasons suggested by others or attitudes I've come across why a COR should pull in a merit party
- There are no BRDs seeking - This is the number 1 reason we are asked to pull
- We natively use ranged attacks and are always using one
- The other members of the party shouldn't have to roam
- The other members of the party shouldn't have to sacrifice Acc+2 Attk+4 or some other mediocre stats so they can equip a ranged weapon
- Other members don't have access to any form of sleep - This one is legitimate
- We are invited for our rolls, not our DD
The only real reasons a COR should be pulling in a merit party
- The COR trusts the party he is with to keep him alive when %@^& hits the fan
- The COR doesn't mind fulfilling the pulling role for whatever reason
- The BRD in your party left or DC'd and a replacement BRD is on the way
- The COR is not well equipped for Melee TPing, Ranged Attack TPing, or does not have a good WS build, or just overall sucks apart from pulling
One thing I've noticed, before there were many CORs at 75, merit parties never left town without a BRD and most parties would disband if they lost their BRD. I believe there is a few reasons for this:
- They lost the party member who was pulling and no one else wants to step up
- They lost their buffer and refresher
- They would now have to rely on their healer for all sleeps - which can be tricky without any additional support
As CORs, I too believe we can fulfill the above but not as well as a BRD. We can pull, but not with the efficiency of a BRD. They have fast songs and can recast them very quickly if they are interrupted. We can buff, but not to the extent of a BRD - our rolls are based on randomness and we don't have a duplicate of any of our rolls. We can sleep, but not as easily as a BRD. What would you do if you had to pull a Mamool that had a pet and another one with a pet links with him only because you had to wait for your shot to go off? Thats 4 mobs. A BRD can cast one instant song and all of them would be asleep. As a COR, you can sleep 1, take the time to target another and sleep him, the melees start attacking one, and then unless your one of your melees provoke the last one off of you or the healer sleeps it, you're screwed. Then you also have to worry about one of the melees attacking the wrong one that you've just slept but you have to wait 50-60 seconds to sleep him again... Then what happens if you link on your next pull too and you still have 30 seconds till your next light shot? I've had BRDs who have had a tough time with links, and I've saved them many times by providing my extra sleeps.
So if a party was willing to disband or not leave town because of BRD issues, why do people think that CORs can replace a BRD? Simply put: We cannot. Asking a COR to pull is a bandaid solution and your party would probably be better off having the COR DD and just roam, and the COR can sleep when necessary.
If anyone out there wants to pull as a COR, be my guest, thats how you want to play. I am not trying to attack anyone with my post other than those who would not take a COR because they don't want to pull or forcing a COR to pull based on their ignorance of the capabilities of the job.
So based on all of this, and realistically BRD and COR are the only two jobs that are looked at for pulling, I think my argument still stands... COR is the absolute worst job for pulling in merit parties.
Locrotien wrote:
HAHAHAHA!!! What the hell are you smoking?
I pulled a chain 107 with Coffinmaker /nin in Merit pts. The chain could have went higher but one of the DD's left.
Pulling can get boring but since we are RA, people expect it. I think you should suck it up and work on getting merits. With all the pts you probably turned down, you could
have had a crap load more merits.
No need to be rude, I was simply voicing my opinion. My COR is 20/20 on merits, and while yes, I have other things I still have to merit I've never regretted putting {fisherman} {No Thanks} in my search comment as every merit party I've been in always had a BRD and at worst I've had to wait maybe 30 minutes for an invite. Every single party was more than capable of breaking C100 and going higher apart from AFKs or washroom breaks etc and every single one was 20k+/hour without Corsair's Roll.
The real problem is people see all these crappy CORs out there and think that pulling is all we are good for and thus they think all other CORs are just as equally terrible and expect all the rest of us to put up 2 or 3 rolls, pull, then pick our noses till we have to pull or put rolls up again. Sadly I have seen CORs in merit parties like this. This mindset propegates to all other endgame aspects and people don't think we can DD at all.