You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 17, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+33-9Lines changed: 33 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,18 @@
2
2
3
3
This utility provides an alternative to the Twitch/Curse client for management and updating of addons for World of Warcraft. The Twitch/Curse client is rather bloated and buggy, and comes with many features that most users will not ever use in the first place. This utility, however, is lightweight and makes it very easy to manage which addons are being updated, and to update them just by running a python script.
4
4
5
+
_Now supporting both retail and classic addon management!_
You must have a version of [Python](https://www.python.org/) 3.6+.
12
+
13
+
This utility has two external dependencies:
10
14
11
-
* A version of [Python](https://www.python.org/) 3.6+
12
-
* The [requests](http://docs.python-requests.org/en/master/) module
15
+
- The [requests](https://pypi.org/project/requests/) module, for making HTTP requests
16
+
- The [BeautifulSoup4](https://pypi.org/project/beautifulsoup4/) module, for HTML document parsing
13
17
14
18
The install should be managed by [`pipenv`](https://github.com/pypa/pipenv). All you need to do is run the following:
15
19
@@ -26,19 +30,39 @@ After performing the setup steps, `pipenv run` is used to execute the utility. T
26
30
pipenv run python -m updater
27
31
```
28
32
33
+
More advanced usage includes specifying the configuration file, which is detailed in the next section.
34
+
29
35
## Configuring the utility
30
36
31
-
The `config.ini` file is used by the utility to find where to install the addons to, and where to get the list of addons from.
37
+
The `config.ini` file is used by default to find where to install the addons to, and where to get the list of addons from.
32
38
33
-
The default location in Windows to install the addons to is `C:\Program Files (x86)\World of Warcraft\_retail_\Interface\AddOns`. If this is not the location where you have World of Warcraft installed, you will need to edit `config.ini` to point to your addons folder.
39
+
It requires that some properties be set, if you do not want to use the defaults such as:
34
40
35
-
The standard addon location on macOS is `/Applications/World of Warcraft/Interface/AddOns`
41
+
-`WoW Addon Location`
42
+
- The WoW application files addon directory
43
+
- (The standard addon location on macOS is `/Applications/World of Warcraft/Interface/AddOns`)
44
+
- (default `= C:\Program Files (x86)\World of Warcraft\_retail_\Interface\AddOns`)
36
45
37
-
The default name of the addon list file is `addons.txt`, but this file will not exist on your PC, so you should either create `addons.txt` in the same location as the utility, or name the file something else and edit "config.ini" to point to the new file.
46
+
-`Addon List File`
47
+
- A file specifying which addons to install and/or update
48
+
- This file will not exist at first, so you should create `addons.txt` in the same directory as the utility.
49
+
- (default `= addons.txt`)
38
50
39
-
The `Installed Versions File` property determines where to store the file that keeps track of the current versions of your addons.
51
+
-`Installed Versions File`
52
+
- A file which tracks your installed addon versions
53
+
- (default `= installed.ini`)
40
54
41
-
The game version that you would like to target addons for must be specified in the `Game Version` property. The two options are `retail` or `classic`.
55
+
-`Game Version`
56
+
- The game version (either `retail` or `classic`) that you would like to target for addons
57
+
- (default `= retail`)
58
+
59
+
### Multiple configurations
60
+
The module supports a command-line configuration for maintaining multiple set of addons. For example, a set of addons for retail, and a different set of addons for classic.
61
+
To use a different configuration file, specify it with the `--config` flag (or `-c`) e.g.
62
+
63
+
```bash
64
+
pipenv run python -m updater -c my-custom-config.ini
65
+
```
42
66
43
67
## Supported addon hosts
44
68
The following hosts are supported as download targets. The URL specified should be to the main page of the addon, or in the case of GitHub, to the root of the repository.
Copy file name to clipboardExpand all lines: changelog.txt
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,8 @@
1
1
Changelog
2
2
3
+
* 8/31/2019
4
+
Add command-line argument for specifying a configuration file. Now multiple independent configurations can be used i.e. one for retail, and one for classic.
5
+
3
6
* 8/31/2019
4
7
Enhance support for Curse classic-only addons. Now those addons can download if the page only supports one release, and that release is the classic game version.
0 commit comments