-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Randomly installs classic versions #79
Comments
hi, not a maintainer of lcurse, but the issue lies about here: Lines 192 to 201 in 4a22aa1
it's because curseforge relatively recently allowed 'classic' releases of their addons, as well as alpha/beta/alternate releases that lcurse already seems to do. This is really bad form on my part, but there are other addon managers that support classic here: https://github.com/ogri-la/wowman#other-addon-managers |
I do have it working in my version, I PR'ed my changes in #80 in case that helps. |
Since #80 is merged, I think this is solved and can be closed. |
I've taken a look at the code changes and read the commit messages and I'm still not clear on whether lcurse actually supports the installation of classic addons from curseforge or is just ignoring them ... I ask because my data may be wrong ;) |
It supports Classic as well. It should even work for PTR as well, provided if it's installed in the same WoW directory.
|
Using the latest version of lcurse it is randomly chosing to install "classic" versions of mods rather than the live versions. It has done this to, among others, AdvancedInterfaceOptions, DBM Voicepack VEM, Details! Damage Meter, GTFO and Prat 3.0
The text was updated successfully, but these errors were encountered: