File in Addons folder is not an add-on (?)

Shadowshire · March 2022

@ZOS_Bill
Yesterday (29 March 2022), after I ran the Repair option on the Launcher's Game Options menu, I discovered that the following folder has been added to the top of the folder C:\Users\Player\Documents\Elder Scrolls Online\live\Addons :: _MACOSX

My computer has an AMD microprocessor and runs Windows 7 Pro as the operating system. The folder name implies that it pertains to the Apple MacIntosh OS X, so there does not seem to be any reason for it to have been created.

On the face of it, the contents are loaded by the game client, just as it loads the source code for each of the other add-ons in the folder .../Addons. The underscore at the start of the folder name likely ensures that it will be processed first.

(1.0.0.0) The folder .../_MACOSX contains the following sub-folder:

(1.1.0.0) C:\Users\SYSOP\Documents\Elder Scrolls Online\live\Addons\__MACOSX\TEC contains one sub-folder and six files:

folder .../Lib
file ._Bindings.xml
file ._Lib
file ._LICENSE
file ._README.md
file ._TEC.lua
file ._TEC.txt

(1.1.1.0) C:\Users\SYSOP\Documents\Elder Scrolls Online\live\Addons\__MACOSX\TEC\Lib contains two sub-folders and two files:

folder .../LibAddonMenu-2.0
folder .../LibStub
file ._LibAddonMenu-2.0
file ._LibStub

(1.1.1.1) C:\Users\Player\Documents\Elder Scrolls Online\live\Addons\__MACOSX\TEC\Lib\LibAddonMenu-2.0 contains one folder and three files:

folder ... /controls which contains 14 files of .LUA source code
file ._controls
file ._LibAddonMenu-2.0.lua
file ._LICENSE

Note: The library folder LibAddonMenu-2.0 is also separately installed in .../Addons and supplants the previous LibAddonMenu versions.

(1.1.1.2) C:\Users\SYSOP\Documents\Elder Scrolls Online\live\Addons\__MACOSX\TEC\Lib\LibStub contains the following file:

file ._LibStub.lua

Note: LibStub is a deprecated library, which nonetheless might be included in the folder tree of an add-on which depends upon it (e.g., Dolgubon's Lazy Set Crafter).

Question:

Is the folder _MACOSX and its contents the result of a bug in the Launcher installation Repair feature??