My point is that it can just as easily happen again regardless of you saying that it's not okay to me. I don't see why it wouldn't.
“You Can’t Believe Most of the What You Read on the Internet” - Abraham Lincoln
If someone like Nitrous or Byrth can jimmyrig a Lua plugin overnight, I fail to see how someone can't just write a plugin like ASE and sneak it around.
It's also not like most of the things trying to be kept hidden are not publicly downloadable on ffevo anyways.
Stuff like allseeingeye still don't have any public downloads afaik, however you can find stuff with a decent google search.
You'd be surprised. c.c
Oh, and I might as well add that several of them have also gotten their respective developers banned. These aren't undetectable happy little plugins. They're dangerous to use.
Care to share some examples just for fun?
Please Help! I cannot get the addons to load. I downloaded the aoebgone lua and put it in the addons folder. However when I type //lua l aoebgone in game, it says file does not exist!
btimers updated to include altbuff tracking. this is toggled on/off with btimers showalt
http://goo.gl/pKoAx -- btimers.lua
http://goo.gl/Y7R0Q -- dependencies
I'm... not 100% on this update as i couldn't test when i had more than just my 2 characters. Also, I couldn't figure out how to track perpetuance between accounts, so it will only track base timer on other accounts. I apologize for this but i tried for a good 2-3 hours to figure it out. If you can manage it i'd be glad to fix it sometime.
I also updated byrth's aoebgone to include cor roll support. Please let me know if it's not working as specified. It has commands now as well type //aoe help to see them. The reason i'm reposting this one is because i had accidently left some open variables that was causeing weird issues
Fix awaiting push to windower/lua on github for aoebgone. in the meantime if you want it here it is: https://github.com/nitrous24/Lua/tre...ddons/aoeBgone
I think Cairthenn's argument is correct on this issue. I don't think closed side distribution is entirely accurate. This issue aside, prior distributions were so limited that users should know the risk associated with such plugins.
What argument, exactly, Yugl? That it could theoretically happen again? OK. So... what? I'm not seeing any argument being made.
If I understand Aureus correctly, he's saying plugin distribution "on the side" (Meaning plugins only accessible to a select few) and risk are the reasons he's not enabling backwards compatibility. Cairthenn is saying distribution may happen "on the side" regardless of v3.4 or v4.0 version. That this hasn't happened to v4.0 yet is a temporal fact, not an absolute one. Furthermore, access to the unofficial ones is limited, so players using them should understand there is an even greater risk when using them. I understand that he wants to keep the playerbase safe by preventing such plugin's functionality, but given the obscure means of obtaining such plugins (And the fact that Windower isn't distributing them), I doubt that's an issue. In short, I don't see a fully substantial reason not to include backwards compatibility, but if he doesn't want to (Either too much work or simply doesn't like the idea of enabling such plugins) that's fine.
Backwards compatibility can't happen for purely technical reasons -- the interface changed, the old plugins don't implement it.
My reasons are for why we're not releasing new copies of the leaked plugins for 4.0.