5.0 Job change wishlist

[Bourne_Endeavor]

Did you even read that first sentence. Who knows how the game works? The dev's do. Do the devs QA everything for every possible meta possible ? No. Not unless you want content spaced 2 years apart. If we played like how the dev's intended, casting the HoT's would rip enmity from the tank every single time if not followed up by Lucid Dreaming. Instead the healer may as well not even exist since all the easy content can pretty much be handled by the tank alone.

Did you? If the developers knew everything, why did they twice re-balance Ninja after outright citing the players found a superior rotation? Likewise, why can I heal more efficiently while simultaneously contributing 3,000 DPS when the intended way to play healers is to scarcely DPS at all? And if we played as the dev's intended, tanks would never leave Tank stance, thus there isn't a chance in hell HoT ripping aggro. Warrior generates so much enmity, you switch to Deliverance on your second or third GCD.

(Unchained) -> Tomahawk (Equilibrium) -> Heavy Swing (Deliverance)

With a Provoke+Shirk, that will hold off everyone, assuming they use their own aggro utility properly.

You are also overgeared for the content in normal mode.

I ran all of Sigma normal in i340. It remained a complete joke that never required two healers.

Please go read the developer of the ACT plugin's reddit posts and forum posts, you will find out just how inaccurate the thing is. Pieces of the source code to it are also scattered across various github's. You know what destroys the accuracy of it the most? Having anything else running (Eg youtube, netflix, spotify, etc.) Also one of the overlays is just a full blown web browser overlay, so no wonder it kills low-spec machines.

https://www.reddit.com/r/ffxiv/comme...quc/?context=1

This post says otherwise. And you are flat out wrong regarding ACT's impact with things running in the background. I frequently have thirty tabs open and/or have Twitch playing while I run content. The numbers have never changed. Regardless, logs are adjusted accordingly when uploaded to account for any discrepancies. Of course, all knowing Kisai understands parsers better than the actual developers and raiders.

Without parsers, people would figure out the best rotation and such by trial-and-error. The drama starters are the people who aren't hiding the fact that they are parsing. You're trying to justify data-mining as if it was ever a good thing. I like knowing how things work, but not before I play it. A small portion of the playerbase is responsible for "the MSQ cutscenes" incident, and a small portion of the player base is responsible for the Koike incident. A small portion of players is what ruins things for everyone because they can't just be nice.

And how do they know? Trial and error requires an objective error conclusion, which cannot be reached without data to rule out that valuable. This is why you see Monks who Tornado Kick on cooldown, Warriors who prioritize Fell Cleave over Upheaval when the latter is always better. Or they don't know pressing Inner Release too early will deny you five Fell Cleaves. Data-mining necessitates digging through files that aren't readily available. ACT uses the battle log itself and calculates what is relayed there. The Koike stemmed from sexual harassment and verbal abuse. Blaming parsers for that not only shows your immense bias but minimizes the vile behavior of people who did far worse than say "your numbers suck."

Now look at all the snark in this thread. This could have all ended with one post, but because certain forum users must get their burns in, it's now derailed the thread.

Nice try, honey. No, you came into a thread about brought up parsers entirely unprovoked. Don't attempt to shift the blame onto everyone else. You derailed this thread and you alone.