DependsOn in Manifest not working when addon is out of date

[CrazyDutchGuy]

If you use DependsOn in your manifest file, and the addon you depend on is marked out of date, your addon will still load.

Looks imo a bug. Anyone else encountered this behavior before ?

[zgrssd]

Are you certain it is actually loaded/excuted? The checkbox only implies an intention to execute it.
Easiest way to check that is BugEater+PreInitDebug+OptionalDependency+d() in the .lua file.

I once had an issue where I was missing a Dependency. Dependant Addon was not loaded and for some reason the name of the dependency did not appear either ("Depends on: ").

Could it be that you misswrote in the Manifest?
Like the XML, errors while processing the manifest are silently ignored. It could help if you post the manifest.

[Garkin]

I have tested how it works and even if addon manager (on character selection screen) does not show dependency error, addon is not loaded.

If you are talking about your ATLAS Logger, you have typo in the manifest:

## DependsOn : ATLAS

This command is not recognized because of space between DependsOn and the colon.

Also addon name is case sensitive, so you should use:

## DependsOn: Atlas

[CrazyDutchGuy]

Zzzz it was working fine before but somehow a space was added so it didn't work anymore

Wrong
##DependsOn : yourAddon
Right
##DependsOn: yourAddon

[CrazyDutchGuy]

hmm the case sensitivity i didn't notice even. That resolves all the problems.

[CrazyDutchGuy]

Took the opportunity to update the wiki http://wiki.esoui.com/Addon_manifest_(.txt)_format

[zgrssd]

Wait, the list is space seperated?
Then I am wondering if my optional dependecies has ever been working like this:

## OptionalDependsOn: LibStub, timer, LibAddonMenu-2.0, LAM-1to2-Interface, libDebug, BugEater

If they are ignoring comma's it would propably work out. If not then this line never did anything (but the only one that really matered was BugEater anyway).

[Garkin]

Originally Posted by zgrssd Wait, the list is space seperated? Then I am wondering if my optional dependecies has ever been working like this: ## OptionalDependsOn: LibStub, timer, LibAddonMenu-2.0, LAM-1to2-Interface, libDebug, BugEater If they are ignoring comma's it would propably work out. If not then this line never did anything (but the only one that really matered was BugEater anyway).

To be honest I have never tried to separate dependencies with commas, but try to separate saved variables with commas and you will see what happens.
http://www.esoui.com/downloads/info5....html#comments

[farangkao]

Originally Posted by zgrssd Wait, the list is space seperated? Then I am wondering if my optional dependecies has ever been working like this: ## OptionalDependsOn: LibStub, timer, LibAddonMenu-2.0, LAM-1to2-Interface, libDebug, BugEater If they are ignoring comma's it would propably work out. If not then this line never did anything (but the only one that really matered was BugEater anyway).

The Answer is simple, their code checks for a string that starts with "## OptionalDependsOn:" ,the rest of the string is then processes accordingly, the spaces don't matter then.

[zgrssd]

Originally Posted by farangkao The Answer is simple, their code checks for a string that starts with "## OptionalDependsOn:" ,the rest of the string is then processes accordingly, the spaces don't matter then.

Since according to the wiki it is a Space seperated list, the spaces do matter.
At worst it might actually count the comma to the addon name, so it was trying to load the addon "LibStub," instead of "LibStub" - wich it would never find.

Luckily the only one that really mattered ws BugEater/LibDebug because those are needed for the error output. And since they always were at the end of the list, thier names were propably parsed correctly.
The rest was only thier for minor efficiency reasons (stand alone copies more likely up to date, so better to load them before embedded copies are loaded so LibStub get's the highest first).