Concerning recent developments of third party addons, and SE's DADT stance

[Saranade]

Please stop. You are doing more harm than good here. I am very much against parsers being included in the game by SE as I firmly believe they would used to harass people. But if individuals use them now and keep quiet about it, Yoshida has said himself that is okay. You have been attacking these raiders who use parsers throughout your posts. But suddenly you're telling Hyomin to stick to the topic when you haven't stuck to it yourself?

You've been aggressive and unpleasant throughout, and you're really not doing your argument - that parsers should be banned because they're toxic - any favours because YOU clearly don't need a parser at all to be toxic

My argument is simple. Currently, there is a "Dont ask, don't tell, don't harass, and parsers are okay." - As far as the Terms of Service go - it doesn't say that anywhere, and does not corroborate it either. I am sorry that you are all misinformed by some live letter you watched, but third party programs are against the TOS, period. A ban wave is extremely unlikely - since so many of you use this add on. What is more likely is a patch to render it useless, much like the add on that was rendered useless a few years ago that called out hunts. Looking forward to this add on now being rendered useless because its reaching too far, and becoming too advantageous. If this offends you, or you think its toxic, well I don't really care.

[BristolRuss]

What is more likely is a patch to render it useless, much like the add on that was rendered useless a few years ago that called out hunts.

Uhhh SE can't prevent someone reading memory information, which means they can't 'stop' programs like parsers. I'm assuming the hunt add-on you are referring to was the guildwork plugin. That plugin wasn't "rendered useless" by anything SE did, the programmer stopped updating it because he was too busy working at his job at Discord.

[Saranade]

Uhhh SE can't prevent someone reading memory information, which means they can't 'stop' programs like parsers. I'm assuming the hunt add-on you are referring to was the guildwork plugin. That plugin wasn't "rendered useless" by anything SE did, the programmer stopped updating it because he was too busy working at his job at Discord.

...sure they can't 'prevent' someone from reading memory information. Do I need to link you to the ToS? It goes over this very specific topic.

[BristolRuss]

...sure they can't 'prevent' someone from reading memory information. Do I need to link you to the ToS? It goes over this very specific topic.

I'm well aware of what the ToS states. It's never stopped anyone making programs that read memory information so far though, has it? My point was that you stated SE could release a patch which wound render them useless, and I'm saying they cant because it's not possible.

[HyoMinPark]

My argument is simple. Currently, there is a "Dont ask, don't tell, don't harass, and parsers are okay." - As far as the Terms of Service go - it doesn't say that anywhere, and does not corroborate it either. I am sorry that you are all misinformed by some live letter you watched, but third party programs are against the TOS, period. A ban wave is extremely unlikely - since so many of you use this add on. What is more likely is a patch to render it useless, much like the add on that was rendered useless a few years ago that called out hunts. Looking forward to this add on now being rendered useless because its reaching too far, and becoming too advantageous. If this offends you, or you think its toxic, well I don't really care.

The TOS can say whatever it wants—but, at the end of the day, it’s up to the developers to actively enforce it. They don’t actively enforce the “no parsers” (or even, the “no third-party tools” rule) unless it crosses the line and results in griefing or harassment (as it did with Arthars recently). The director/producer himself has said that he understands some raiders like having the program and analyzing their own numbers. If they use the program responsibility, then the developers will not seek to punish them. That’s the stance of those who head this game. You don’t have to like it, but it’s their choice not to blanket ban every single player who parses. The TOS means nothing if it’s not actively being enforced. If anything, it’s more of a way for SE to cover themselves should they ever act upon it.

Most major patches tend to break things like the parser you so hate. It only takes anywhere from a couple hours to maybe a day to actively fix it. For the developers to break this specific add-on, they’d likely have to break the parser itself. Which, they have never been able to do. It’s always patched to start working again very soon after any major update. It’s unlikely that they would start reprogramming fights to hide the data it’s rendering visible.

That said, I don’t think that Ellasie was offended by your “argument”, or that it was what was “toxic” about you. I think they were referring to your attitude and the tone of your posts.