View Single Post
12/05/18, 03:44 PM   #4
sirinsidiator
 
sirinsidiator's Avatar
AddOn Author - Click to view addons
Join Date: Apr 2014
Posts: 1,578
Originally Posted by Drakanwulf View Post
This would let ESO tell developers what the current version of their loaded add-on is. For example, add-on developers could use the return value to detect and deny duplicate or "out-of-date" add-on load requests caused by unnecessary add-on folders that have been embedded in poor (or bad or lazy) add-on packaging.
What you are saying is plain wrong. The game uses the AddOnVersion to prevent multiple instances of the same addon from loading. Authors don't influence that with their packaging and don't have any need to "detect and deny" it.

Originally Posted by Drakanwulf View Post
Right now, for example, the LibStub add-on, which many library add-ons use to bootstrap their loads, has to "guess" at what any add-on's latest version number is because ESO provides no internal reference to those values.
LibStub has nothing to do with the AddOnVersion and won't ever use it. It's an old and deprecated system that did in the past what the game now does with the AddOnVersion and loading nested addons, so it's better to not use LibStub for new libraries anymore, since it cannot do it as well as the game itself.

Originally Posted by Drakanwulf View Post
Add-on developers know when the ESO API has been changed because they can invoke "GetAPIVersion()" to get the latest version. I think we should be able to get similar version information about any loaded add-on.
Addon devs also know which version of their addon is loaded if they have specified an AddOnVersion. It's always the one with the highest number, which you implicitly know in your code.