Bard - they broke my job

[Arrik]

Alexander patch notes would like to have a word with you.

Casting times are no more mate.

That's casting time to put up WM, not the casting time on every WS under WM. Probably part of the reason you aren't being taken seriously by anyone but me. And before you reply to that, yes I answered every one of your posts, and broke down what I want from the Job unlike the "STFU you don't have Bard lvld" people. I typically pre-read for a job I intend to start, so I can join in the conversation before lvling it, so that argument isn't a good one if you have researched. I don't like attacking people like that, so I instead talked about every point you made.

Off-topic Edit: While we're on casting times, I'd very much like the animation changed to actually nocking an arrow and drawing the bow back, and getting rid of the hiss.

[MercureXI]

Snip

Yeah misread his comment as "casting times" as in "downtime to put up WM", which is no more as of today's patch. 5:43am, cut me some slack, but quick to react on this anyway.

I don't worry about being "taken seriously", the whole community kinda thinks the same as I do :

Essentially, most bards are complaining because the game is giving you an incentive to stand still rather than run around pointlessly. You can now turn WM off easily whenever you have to move to dodge or handle mechanics and continue dps'ing in the 2.0 style; which is still more than other classes can do. How does this affect the way you play Bard unless you played it redundantly to begin with; running around aimlessly for no reason ?

[Arrik]

Yeah misread his comment as "casting times" as in "downtime to put up WM", which is no more as of today's patch. 5:43am, cut me some slack, but quick to react on this anyway.

I don't worry about being "taken seriously", the whole community kinda thinks the same as I do :

I am cutting you some slack but not dismissing it as you not lvling the Job, it's something the wiki's could have told you though if you had bothered. And not everyone hates WM, a lot of us hate being considered second rate DPS because "muh support" or "muh mobility" when other threads clearly show that's a crock or it's being taken away somewhat with WM. I will admit, some do just want to delete WM from the game, and I kinda argued with one pages back. But, I think today's patch clearly shows that's not the direction SE has for the Job.

lol there is so much hate and negative energy going in here you can almost summon an angry bard primal with it. This wasn't even as bad as smn threads...

/just passing by don't kill me pls

You live, for now. Nah, I'm not really mad so much as frustrated, FFXI had a lot of these Hybrids poorly balanced and SE had the golden opportunity to learn from it, especially with more clearly defined roles. And they haven't. Makes me shudder to think how they plan on doing a RDM, BLU, or other Hybrid jobs. At this point I'd rather they don't.

[ChloeGrace]

(further)

2. Heavy Utility + token dps: nerf potency to be on par with healers' DPS, and give bard songs to buff all the secondary skills (SkS SpS, Acc, Crit, Det, Attack Power, and Defense), along with TP regen, MP regen and requiem. Cap groups to 2 songs TOTAL. This basically forces every group to have 2 bards - no more, no less - in order to be maximized. Yeah, I know. Snowball's chance in hell of SE ever going for this.

[MercureXI]

snip.

Bards had that kind of buffs in FFXI, and they were mandatory for most events for double songs with their 2hrs skill. No way SE is gonna make that mistake ever again.

2.0 BRD was "100% uptime, great DPS, easy to play, away from close range AoE" style with added unique utility.

Isn't it a bit too much ?

3.0 BRD seems more balanced, since you need to plan your "WM dps phases" accordingly to mechanics (like MNKs do with GL3 for example), to ensure maximum DPS output. You still can use 2.0 style the rest of the time, when the fight needs you to move and evade shit. Still having 100% uptime, while moving, from afar (where melees can't do anything, and BLMs will have to stop casting from time to time).

[Arrik]

Bards had that kind of buffs in FFXI, and they were mandatory for most events for double songs with their 2hrs skill. No way SE is gonna make that mistake ever again.

2.0 BRD was "100% uptime, great DPS, easy to play, away from close range AoE" style with added unique utility.

Isn't it a bit too much ?

3.0 BRD seems more balanced, since you need to plan your "WM dps phases" accordingly to mechanics (like MNKs do with GL3 for example), to ensure maximum DPS output. You still can use 2.0 style the rest of the time, when the fight needs you to move and evade shit. Still having 100% uptime, while moving, from afar (where melees can't do anything, and BLMs will have to stop casting from time to time).

2.0 BRD was great dps, 2.1-2.2 (first brd nerf) was ok dps. 3.0 was a lot worse and 3.01 is a bit better. More and more monsters are actually targetting ranged or the whole party, negating a lot of the far away from AoE we once had. And as buffs today have shown, 2.0 BRD is going to be more and more of a dps loss, and less and less of an option for those who do not like it.

Learn to read. Told you I thought he was talking about "casting times" for entering WM. Which was a DPS loss.

That's funny, learning to read would have helped that too. S/he clearly talks about the oGCD and timing them inbetween shots.

Evidence that YOU cannot read, and that you STILL have no idea what you are posting about.
Go troll somewhere else.

[MercureXI]

snip

2.0 style is less dps, that's for sure, but still solid dps if you are among the only dps that can actually dps from that range, evading shit at the same time.

Having huge dps + 100% uptime and full mobility would make you rockstars again, like in 2.0. Along with half the server playing BRD because of the "easy dps" style (I remember early Garuda EX being "no melee, BRD yes please").

If the job gains dps to catch with melee jobs, BRD needs either positioning bonus / malus (I can live with that) or movement restriction like mages do have, and SE chose that.

Why BRD should be free of all "problems" that DPS should face during a fight (100% uptime VS melee being out of range, no positioning, and being able to move without altering dps) ?

[Arrik]

snip

2.0 style is less dps, that's for sure, but still solid dps if you are among the only dps that can actually dps from that range, evading shit at the same time.

Having huge dps + 100% uptime and full mobility would make you rockstars again, like in 2.0. Along with half the server playing BRD because of the "easy dps" style (I remember early Garuda EX being "no melee, BRD yes please").

If the job gains dps to catch with melee jobs, BRD needs either positioning bonus / malus (I can live with that) or movement restriction like mages do have, and SE chose that.

Why BRD should be free of all "problems" that DPS should face during a fight (100% uptime VS melee being out of range, no positoning, can move without altering dps) ?

3.0 Mechanics are not all the same as 2.0 Mechanics. Not everything is melee range only. And I've never stated I want to move without altering my dps. What I said was "as a dps, doing damage the way as a caster, I should do around the damage of one" that means fulltiming WM, and standing still. WM buff today proved 2.0 is not what they want, and will be more and more of a dps loss (which I personally am ok with). I don't think my WD should scale like crap, I don't think my support capabilities should double dip into my already low dps (which could either be fixed by raising my base dps or by removing the penalty attached to them, idc), and I don't want to parse like a melee, just the caster I'm "pretending" to be w/ WM on. I've also said this is if I remain a DPS. If they don't feel like treating me as a DPS, they need to move the jobs to a role more suited.

[MercureXI]

That's funny, learning to read would have helped that too. S/he clearly talks about the oGCD and timing them inbetween shots.

Just meaning it's both our problem it seems I'm tired, I won't lie. You must be too I guess.