03/09/14, 11:26 AM | #1 | |
Join Date: Feb 2014
Posts: 7
|
Cheating Addons
Hi dear Eso LUA-Fans, Contributers, Publishers and Managers,
did you hear about an Addon which could be harmfull, and how Zenimax Online Studio / Bethesda (ZoS) or EsoUI should react on? I mean addons for e.g. which + do in PvP automatic blocking + do aggresive guild-autoinviting + do IP-Sniffing or more + steals performance because of ++ syncing between raid-/campain members ++ unlucky LUA Programming ++ unintended side-effects What dou you think how should ZoS or EsoUI handle this? Did you have found some kind of malicious solutions? BR, Oz4u Last edited by Oz4u : 03/09/14 at 12:07 PM. |
|
03/09/14, 02:42 PM | #2 | |
It is upto the game developer to prevent "cheating."
If an addon can be done to partially automate the combat for example, it will be made by someone and it will be used by some. Personally I do hope that they will restrict the API quite a bit so stuff like that can't be made. I've not heard any harmful addons yet but I guess this is somehow related as one of the PTS testers have said:
|
||
03/09/14, 02:49 PM | #3 | |
Join Date: Feb 2014
Posts: 24
|
I believe its up to everyone...
User: To find such addons and report them. Also to not use them afterwards. Dev (ZOS): Take action on said addons and alter the API or break functions on their side. Dev (Addon): To not make such addons and to report possible misusage of API functions to Dev (ZOS). Everyone has to do their part to make/maintain/upload/download Addons for ESO and to allow ESO to be a great game. |
|
03/09/14, 03:11 PM | #4 | |
Join Date: Mar 2014
Posts: 4
|
The effect of addons
A big concern right now with addons is the amount of information the ESO API allows for them to see. The default UI has a very minimalist design to it which doesn't show on-screen a large amount of the data available at any given time.
For instance, here is a function from the API which an addon could use to see a lot of information about a unit casting a spell in the vicinity... GetUnitCastingInfo(string unitTag)Some of the most important information this function returns includes:
The addon could then take some action(s) based on this information it has received... However! It is incredibly important to realize.... By and large, the ESO API does not allow an addon to issue combat or movement commands for the player. So by itself, the addon is only capable of notifying the player of this information. In theory this prevents "cheating" or "botting". Access to this kind of information does, however, make botting a fairly trivial task using an outside application. For example, you could make an addon which uses the above function to detect whenever a certain interruptable spell is being cast nearby and do something non-combat related in the UI, say place a 1 pixel pink square at a specific location on the screen. A program external to the game could be setup to look at that one pixel and enter some keypresses automatically whenever that pixel turns pink. Voila, you have an auto-interrupter. This is cheating and could very easily get you banned. The two most obvious ways to prevent this are to...
or
The former would preserve access to those API functions for legitimate uses, but is much more difficult and invasive to pull off (the game would need detection algorithms and/or a sniffer application that can look at what is running on your computer outside of the game). The latter would solve the problem for good, but deny a great deal of functionality to addons which would use the information legitimately. Zenimax has stated that they will be taking a pretty firm stance on exploits of the API. They are very much against the idea of players feeling forced to get a certain addon in order to stay competitive in the game. To address some of your specific concerns....
Addressed above
Definitely possible with the API unless there is some sort of internal cap on invites/time
To my knowledge, nothing in the API has access to anything regarding your system information, so no worries there
Addons run locally on the client's computer reactive to "events" (player opened a vendor screen, player looted something, etc.) in the game. As far as I know, there are very few (if any) API functions that create events that are not local to the client and would need to be sent to the server. Even if there are and an addon was made to maliciously spam the server with events, it would probably take a lot of people all using the addon at the same time in one place to notice any effect on latency due to the enormous bandwidth the servers have. |
|
03/09/14, 03:19 PM | #5 |
A number of the things you've listed aren't actually possible using the Lua programming language. Some of the others are, it all depends on the amount of leeway Zenimax gives us.
My hope is that they will continue to let us have a robust API and that they will do like other companies have done - judiciously lock down certain very specific parts of the API if and when it becomes necessary. I would also like to see them give us an "AddOn Policy" of some form. Give us a list of the things that they categorically do not want us doing. It's a lot easier to police things when there is a clear statement of what isn't acceptable. Honestly, if I were to say what I really wished, it would be that people not create/use things that they bloody well know ZOS won't like in the first place. But I also know damn well after all these years that there are going to be some folks out there that will push beyond the 'acceptable' limit and, in the process, spoil it for the rest of us.* [edit]* And that's the point at which the community (users, addon devs, ESOUI, etc.) should be going "hey, not cool, I'm not going to use/write/host that". One thing the OP and others new to our sites will discover, and hopefully be reassured by, is that we have some pretty firm guidelines of our own and our standards are very high. As others that have known us and used our sites for years can also attest to is that we have great communities. When something is just not copacetic, folks make it known and it gets dealt with. Last edited by Cairenn : 03/09/14 at 03:51 PM. |
|
03/10/14, 10:58 AM | #6 | ||
Join Date: Feb 2014
Posts: 7
|
enviroment/UI integration ease of configuration ease of using support quality spoiling factor errorness ... Only rough first brainstorm-ideas... But perhaps with something like that the community can rank the addon in different ways. And this in return can help developers make nicer, faster, easier addons *g* Last edited by Oz4u : 03/10/14 at 11:01 AM. |
||
03/21/14, 01:45 AM | #7 | |
|
What the star system does is the following:
|
|
03/21/14, 09:29 PM | #8 |
|
Until Zenimax patch things out -- all things are fair.
They introduce a bug -- they fix a bug -- problem solved (if there ever was one, usually it only exists in peoples mind..) People should focus more on creativity than trying to hinder or prevent it. Re: Stars: Based on Blackberry/Google storefronts, its either 1 star == "I have no idea" or 5 stars == "I have no idea". |
03/23/14, 10:50 AM | #9 | |
|
Amazing post. |
|
03/24/14, 02:12 AM | #10 | |
Join Date: Feb 2014
Posts: 7
|
||
ESOUI » AddOns » AddOn Help/Support » Cheating Addons |
«
Previous Thread
|
Next Thread
»
|
Display Modes |
Linear Mode |
Switch to Hybrid Mode |
Switch to Threaded Mode |
|
|