Seems that's all you pro parsing people can ever resort to.
Nah people really want to believe you need parsers for this.
If it wasn't for parsers we would never notice those players that disconnect constantly during fights.
All we can resort to? I specifically broke down why the example you gave was terrible but you just go ahead and disregard my totally relevant points, they probably went over your head anyways.
Although I am neither for, nor against parsing, there are some misconceptions about these facts I'd like to point out.
The TOS says something about third-party tools, a broad spectrum in which parsers fall under.
Square-enix has not formally authorized the use of any third party software that I know of.Originally Posted by FFXIV Terms of Service
2.2.5 Data Mining. You may not intercept, mine or otherwise collect information from the Game using unauthorized third party software.
Square-enix policy revolves around the collected evidence during in-game practices. Talking about using a parser is not the same as catching someone using a parser. Square-enix only pursues the latter.
I already addressed the issue with regards to forum posting. As for in-game punishment, I can attest to the fact that they do suspend accounts if enough evidence arises. Although Square-enix will never share the results of any investigation directly, I was lucky enough to see the result first-hand. I had reported someone after they admitted to using a parser during a dungeon run. To be honest, I wasn't really expecting much since I knew only 3 of us were around to witness it and the likelihood of SE taking any action seemed slim. To my surprise, a thread popped up two weeks later on these forums where someone who, acting as a proxy, was pleading some case to get their friend's account back after he/she was "wrongfully banned."
Granted, if said player hadn't said anything, he/she would have gone unnoticed. However, the fact of the matter is that Square-enix will take action when warranted.
This is what he does. He immediately went to say "Seems that's all you pro parsing people can ever resort to." which falls into the "You guys never get what I say anyway" type of stuff he always bring sup when you corner him with a good argument.
That's not always the problem though. For example, when you're tackling turn 8 or 9 everyone in your party may look to be doing pretty well based on your hate meters. The tanks outstripping everyone nicely so they are holding hate fine, and everyone in the party is right in line with one another (exceptions going to hate reduction moves), but in the end you just aren't even coming close to the DPS check of the fight. The team sits stumped. Wondering "Why can't we beat this? Everyone's hate meters seem to be properly in line!" but once a parser gets thrown at the battle it becomes clear. Everyone in the group is equally below the thresholds required to win the battle. Everyone needs to step it up because no one is succeeding.
See the entire "threat meter" argument assumes that if you are all equal then you're all doing alright, but that's a flaw. It only works when at least 1 person is absolutely killing damage so that everyone else has a baseline amount of threat to strive for. When you all fail the entire system falls completely apart. It is a flawed method. Perfectly fine for low end content, but completely useless for end game content.
Last edited by Tiggy; 08-12-2014 at 05:03 AM.
because you can't proc your buffs on mobs...right you sure told me. Especially when I mentioned it before that in regards to testing w/o buffs.
Again you've proven to try real real hard to justify your pro parser argument and there's no shame on it but seriously stop trying so hard to justify it and say you desire your QoL.
Parsing log files isn't data mining. The log files aren't even in the game installation folder. They're in your documents folder. Go look for yourself. They're .txt files you can open them up in Notepad. In fact I posted some of my own in this thread and I haven't been warned or banned for it.
I'm going to wager he was speaking about the parsers that had 'other' features involved with them. If they didn't want parsers to be allowed at all, they'd patch the game to turn off log files. Especially when they are in the SAME folder as the screenshots.add in the fact Yoshi-P has said on at least two occasions (I think it was two) that they are not allowed. Even going as far at one point to tacitly admit they exist and there isn't a lot they can do about it.
Again go look at the threads. They are posting the results of the parses. So anyone contributing has used a parser to give the information they've discussed. Its not different than saying in chat "my parser says you're underperforming."Having a discussion about it is not against the ToS and also isn't a valid way to determine if this is against the rules or not. Having a conversation isn't using third party tools to extract data from the game.
I'm not talking about lack of proof, I'm talking about calling a bluff. As in challenging the other side of the argument to prove their conviction to their own argument. So far they have lacked it. Which leaves me to believe, they don't even believe in their own arguments. Seriously, why nitpick it? Why go "ooh its against the rules, you -might- get into a tussle with a GM if they ever find out!" Instead of reporting them. I mean at this point the discussion is pointless otherwise. It hasn't gone anywhere except this loop in like 3 days.Lack of proof is not proof of the contrary. Just because you haven't personally seen it doesn't mean it does not happen. There are over 2 million accounts in this game. Do you think you've played with enough of them to even know?
No, you can't accurately recreate how your Dots work on T9 versus a Doblyn outside of Camp Bluefog that dies before the DoT timer finishes. Is that a simple enough way to put it for you? This still isn't including all the other factors I mentioned like foe req, accuracy, DoTing before phase changes and all that good stuffbecause you can't proc your buffs on mobs...right you sure told me. Especially when I mentioned it before that in regards to testing w/o buffs.
Again you've proven to try real real hard to justify your pro parser argument and there's no shame on it but seriously stop trying so hard to justify it and say you desire your QoL.
Everything you said is true. It only becomes a problem when the "Pro" players are just chortling or kicking these players instead of teaching them how to be better (given they are willing to listen). This is how we cultivate a healthy and friendly community. Sadly, this is not the norm found anymore.The crazy part is, we don't need a parser to see you are terrible.
When your threat is below someone of the same class, whom has worse gear, and using quelling. You are bad.
When you casting spells/abilities for reasons you should never have to, like blizzard 1 because your oom. We know you are bad.
When you have penta-melded gear with melds that give +0. We know you are bad.
When you can't beat turn 5 / titan / turn 6-9 /ramuh / levi. We know you (or your group) is bad.
Last edited by Tygg; 08-12-2014 at 05:19 AM.
Yes I can, yes I have, and yes I did.
yup because that "pro" player behavior gets transferred to "casuals" player base.Everything you said is true. It only becomes a problem when the "Pro" players are just chortling or kicking these players instead of teaching them how to be better (given they are willing to listen). This is how he cultivate a healthy and friendly community. Sadly, this is not the norm found anymore.
Last edited by Gormogon; 08-12-2014 at 05:21 AM.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.