Well, i can see the UserID in every mails i receive.AngersRevenge wrote: »... the only people that can see your UserID as apposed to your character name is the people on your friends list and in your guilds. If you are worried about gold spammers or account hackers then you should review your friends and guilds that you are in.
nzblustone wrote: »Bots always find a way. Though I haven't encountered any in ESO yet. And if you don't want an addon showing you where all the nodes are, then don't use it. I don't and I have skillpoints in all the Keen Eye skills which I prefer. Just because it exists and some people can save a skillpoint or two as a result it doesn't mean you have to as well, be an individual, play your own way.
In the case of the alchemy one If you don't like an addon don't use it, it's quite simple.
The third one is countered by the player taking responsibility for their account security. Not downloading keygens, not using the same password as they use on any website or their email account. A new email specifically for ESO. There are so many things a player can do to ensure their account security that despite the fact that I would prefer my character name being shown/used ingame I have no concerns about my account safety as a result.
TLDR: Gamebreaking is such an exaggeration. Relax and enjoy the game.
Then I shouldn't have to spend skyshards to have the in-game highlighting should I? Since other players are allowed to highlight all nodes at any range for free yes?
There is somnething Called Concern Trolling listed on the WIkipedia Page for Trolling. Everytime somebody says the words "ESO is doomed because of X" I am thinking of that is my first reaction.ragamerb16_ESO wrote: »After reviewing the API, I think ESO Devs still need to deactivate some more features. Before going in, I just want to point how I define a "Game Breaking" addon... In reality it's very simple, when the pressence of a given modification disables a basic gameplay mechanic... Following this simple definition here go my suggestions:
Nothing that cannot be done with a Webbrowser. And cannot be just memorised/copied into a database.ragamerb16_ESO wrote: »- Map Location Additions. Like nodes, skyshards, etc.... This work by creating a high precission coordinate system. This is the prerequisite needed for automated navigation (ie bots). This information in game basically removes the needs to invest into some Skillpoints. Create Serverside checks to allow ONLY players that have invested skillpoints into node visibility to access "extended" information (And rework this "visibility" to offer variety for ppl dedicated to gathering... And establish limits on how much info a given set of Skillpoins yield). This is a very important decission as the "rate of gathering" have a lot of impact on the Economy of a game... And anything that eases the creation of Bots needs to be removed from any game ASAP, IMO.
- Dynamic Recipes. Alchemy discovery gameplay is atm disabled completely by another in game database addon... Devs should decide if they want to keep this aspect of gameplay or simply put all properties of plants visible.
ESO uses a default "Accoutn Guard" System. Everytime you try to log in with from a different Computer* a one time code is send to your mail adress. No one time code, no interaction with the gameworld. So they already need to crack two account data (and find your mail adress under hundreds of mails servers).ragamerb16_ESO wrote: »
- Player Handler Visibility. This is not strictly game-breaking but a concern about security... Due to the poor decission of Zenimax to make publicly visible part of your login information (The account handler) coupled with how easy for an addon is to gather massive ammounts of player handlers, this will have an impact in the frequency of security related events. This is better handled by doing what any company concerned about the security of their custommers would do, which is having a username for login independent of the public handler any1 else sees but... As I think it's already too late for that, maybe controlling how addons access player handlers could help at diminishing this effect (It's hard to do... Because handlers are visible at very different points into the API, and the info is required for basic features to work, like invites, chat & guild functionality).