Results -9 to 0 of 807

Threaded View

  1. #10
    Player
    Aiselia's Avatar
    Join Date
    Feb 2015
    Posts
    437
    Character
    Shandraya Heavenswind
    World
    Famfrit
    Main Class
    Dark Knight Lv 60
    Quote Originally Posted by Lyrica_Ashtine View Post
    I gave you the objective benefits back at page 47 and 49
    You gave objective benefits of seeing the information, which I've not disagreed that seeing the information can be important in the right situations. You did not give objective benefits of forcing the information to be public over being optional to be public, particularly for content where DPS doesn't make a difference outside of saving a few minutes.


    Quote Originally Posted by Elazu View Post
    This again.
    Hey, I asked you a question about you making things up back on page 50. Could you answer it, please? I'm honestly curious.

    Quote Originally Posted by Aiselia View Post
    Shortcut to question
    Quote Originally Posted by Sleigh View Post
    Mainly because sometimes total DPS isn't as important as what someone does in a particular phase or up to a particular spot, when learning. It's good to have a timeline as you see it, basically; the end result number isn't always one you can analyze and get some info out of, especially if someone dies or does a mechanic wrong which would destroy your results when otherwise you could get some info out of them during the fact.
    Okay, so it's basically just so you know where a specific problem may happen, for example, if they strangely popped a CD just before a phase where they wouldn't be able to really use it to its full extent (for example, boss goes invulnerable and they're only 5 sec into their cooldowns)?

    But, I mean, if we assume that a forced-party parser is going to show you in-depth information into their CD usage or when/where they died, couldn't an end-result parser also show a timeline? Like, select a player, then it opens up a window that shows a more in-depth information timeline, while the standard UI view of the parser would be limited to more limited information.

    Alternatively, what if the optional part was only who it shows to, but still would show real-time data if you selected to make it public? In which case, literally the only difference would be that instead of the party being forced to be able to see it even in content where it largely doesn't matter, one can choose whether or not theirs shows up on someone else's sheet. When doing savage content, you could still set rules to have it set to public for the run.
    (1)
    Last edited by Aiselia; 09-18-2015 at 01:26 PM.