As an example, we have broken down buffs and debuffs into a few key effects. We have worked to keep many things off the screen that were not absolutely necessary. You might ask why?įirst, we feel a clean and unobtrusive UI is a key part of The Elder Scrolls Online. However, it is certainly true we don’t natively add icons to show buffs and display timers. Our changes to the API were exclusively about keeping the playing field as level as we could in a competitive environment, not about keeping the game immersive or trying to make sure people could not see numbers. We do not want players writing scripts that play their character for them, and that was the direction ESO UI modding was headed. If later we feel changes or additional functionality is a good thing without damaging the overall game, some features may be re-enabled. We left as much of the API open as we felt we could. In order to keep the playing field as level as we could for competitive PvE and competitive PvP at ship, we removed the ability of the API to access this functionality. For example, it was trivial to create an add-on "listen" for a debuff, and be able to remove this debuff automatically - or to create an add-on that allowed group members' adds-ons to report their status through chat allowing party members with the same add-on to automatically cast heals. But we also found that certain events could be used to allow add-ons and macro programs, used in conjunction, to do many things which otherwise should require player skill. When we made the changes to restrict our API, our goal was to make sure you couldn't see more information about your enemies than we intended. We saw things which necessitated that we change the API. The initial release of our API was intentionally wide open in order to test the boundaries of what could be done - which is exactly what happened. To reiterate, our goal was: to keep the playing field level for our competitive environments.
As you are probably aware, we recently publicly clarified our overall UI modding strategy, and our reasons for making changes to the API. As many of you know, there has been a lot of discussion over recent changes to the API.
0 kommentar(er)
