Results -9 to 0 of 196

Threaded View

  1. #11
    Player
    Bourne_Endeavor's Avatar
    Join Date
    Sep 2015
    Location
    Ul'Dah
    Posts
    5,377
    Character
    Cassandra Solidor
    World
    Cactuar
    Main Class
    Dragoon Lv 90
    Quote Originally Posted by NinjaTaru72 View Post
    While some people may use it "for good" more games than not it's seemed to be a cause for issue. I just wish SE would make up their mind...the whole "don't ask/tell" thing is annoyign imo. Either fully disallow it and ban people, or allow it and say that's that.

    I think something that would make a settlement between both parts (from my perspective) would be to make a world dedicated to people who want to use/have parsers used on them.

    Wanna parse you and/or others? Transfer to this world(or even 2 or 3 worlds depending on population.

    Allow it there. And only have party finder/duty finder work for that world(s) . That way parsers can stay in there little area, and non parsers can be in our area. Lol.

    It's about the best solution for both groups imo
    This has to be among the most absurd overreactions to parses I've seen, which is a considerable feat. Who cares if someone runs ACT provided they aren't screaming profanities about your numbers. Honestly, you make it sound like you have something to hide and only want parses bannable because that way people won't see your poor performance. Whether that be the case or not, it is the impression you leave by overreaching to this extent. Demanding segregation because someone dares to use a tool is ridiculous. You have not a single shred of evidence supporting the notion people who parse are nothing more than jerks yet you've repeated spoken in absolutes. Have you even dealt with harassment from parse users? And no, being told you're not doing enough DPS isn't harassment. If you have, how often?

    Regardless, Yoshida could come out tomorrow and ban parse usage. No one will care because they can't properly detect it. Even when the battle logs were changed, an update was done within a day to work around it.
    (14)
    Last edited by Bourne_Endeavor; 09-06-2017 at 06:11 PM.