Current BIS for Bard

[LenTsani]

What kinda deeps do you put out on Twin? Do you have a detailed parse screenshot with that set? Cuz I call BS. I keep SS as low as I possibly can to not risk going TP dry.

Parsers don't, and CAN'T, give an accurate output on "deeps." Until the combat log is updated (which it probably won't be) they are extremely rough estimates at best, and CANNOT (not should not) be used as proof of anything in game right now because of those flaws.

Just stop.

Stop what? Stop testing things for myself instead of taking the word of random people on the internet? Crit has decreasing returns, Skillspeed has increasing returns. Simple math, folks.

[Bardo]

How exactly does crit have decreasing returns when we can't even hit 50% with max gear/food/straight shot buff/Internal Release?
And how does skillspeed have increasing returns when it runs you out of TP faster as well as eventually causing on-globals to clip the animation lock of off-globals?

[BrandoH]

Parsers don't, and CAN'T, give an accurate output on "deeps." Until the combat log is updated (which it probably won't be) they are extremely rough estimates at best, and CANNOT (not should not) be used as proof of anything in game right now because of those flaws.



Stop what? Stop testing things for myself instead of taking the word of random people on the internet? Crit has decreasing returns, Skillspeed has increasing returns. Simple math, folks.

Except I consistently parse the same with my set. Were you to give me some comparable logs (logged damage done over a fight, extremely relevant in the case of testing extremely high skill speed), and accuracy over the course of the fight given the few points under cap, and general idea of how TP starved you feel over the course of the fight, people could take you a bit more seriously.

[LenTsani]

Except I consistently parse the same with my set. Were you to give me some comparable logs (logged damage done over a fight, extremely relevant in the case of testing extremely high skill speed), and accuracy over the course of the fight given the few points under cap, and general idea of how TP starved you feel over the course of the fight, people could take you a bit more seriously.

Parsers don't work. I just ran the 3 big ones side by side and got 3 COMPLETELY different outputs against training dummy (one said 107.4, one said 212, one said 486. Good thing they're accurate, right?). They estimate, and aren't worth the time they took to set up. Also, I never miss. But hey, you all keep thinking that you need 483 acc, it really makes me smile.

[Skull_Angel]

Parsers don't work. I just ran the 3 big ones side by side and got 3 COMPLETELY different outputs against training dummy (one said 107.4, one said 212, one said 486. Good thing they're accurate, right?). They estimate, and aren't worth the time they took to set up. Also, I never miss. But hey, you all keep thinking that you need 483 acc, it really makes me smile.

I too would like to see data and a detailed layout of your testing methodology; simply taking raw test data on statistical values and their perceived changes at different levels without understanding how they effect the mechanics of the specific job/class can and will lead to false conclusions.

[Bardo]

one said 107.4, one said 212, one said 486

But what about total damage done?
DPS can vary quite a lot because parsers have a difficult time knowing the exact amount of time you're actually attacking.

However, you should be seeing consistent total damage numbers between parsers (as I do.)
And you can use those total damage numbers to easily compare gearsets.

By the way, if you're not using a parser to back up your claims, then what kind of testing ARE you using to come to your conclusions?

[LunarEmerald]

I do think people put too faith in parsers. With dots being guesstimated, they aren't really reliable.

[BrandoH]

Parsers don't work. I just ran the 3 big ones side by side and got 3 COMPLETELY different outputs against training dummy (one said 107.4, one said 212, one said 486. Good thing they're accurate, right?). They estimate, and aren't worth the time they took to set up. Also, I never miss. But hey, you all keep thinking that you need 483 acc, it really makes me smile.

I never attack Hygeia, so I sit at 473 and never miss. You're pretty darn stupid if you think I asked for a detailed parser screenshot to look at the dps numbers. Specifically, I'd like to see damage done to each mob and accuracy on asclepius on a kill. I have app, act, and logrep so I could compare to any of them and how each of them guesses on dots. Only a kill attempt in which you don't die or get dread knighted please, so we could see optimum dps. :3

[Satsui]

Parsers don't work. I just ran the 3 big ones side by side and got 3 COMPLETELY different outputs against training dummy (one said 107.4, one said 212, one said 486. Good thing they're accurate, right?). They estimate, and aren't worth the time they took to set up. Also, I never miss. But hey, you all keep thinking that you need 483 acc, it really makes me smile.

Parsing training dummies is tricky unless you know how to work the parser as sometimes the encounters don't stop or start early based off people fighting in the zone. Parsers are much more accurate in instances (given some of the inaccuracies you already stated).

Your SS BIS list is intriguing. Worst case, people should try it out before knocking it which I intend to do.

[rweezy]

Is there an established BiS for bard?