Quote from xureathWhen using the "Prefer NoLib" option the updater still chooses curse over wowace regardless if the package on curse is nolib or not, even if they have the same version numbers.
This is using the latest (a4) client of course.
Edit: Actually, after further investigation it seems that the "problem" lies with the "Site Priorities" ordering. It just picks the one from the site which has a higher priority regardless if it's nolib or not.
Hum true, I do set Site Priorities according the ordering, no matter what else is set. Maybe I should warn the user if he sets the NoLib Option or use wowace/curseforge always if nolib is set.