A Python-based GuildWars2 helper tool.

This project is unsupported. It is/was mostly functional and usable, and I think it provided quite a bit of help. However I'm no longer playing GW2, so I don't expect to do much, if any, work on this project. If anyone wants to take over development or maintenance of it, please open an issue...

gw2copilot is a browser-based "helper" for Guild Wars 2, to automate manual tasks that players currently perform out of the game.

It is developed for either native Windows or Wine/PlayOnLinux and interfaces with both the official ArenaNet GuildWars ReST API (for both general information and account-specific data) and also makes use of the MumbleLink memory-mapped file to retrieve realtime character location from the game.

This aims to automate manual tasks that players currently perform, including looking up zone maps online, tracking ToDo's, etc.

This project is not a game overlay; its runs as a standalone webserver, intended to display data in a browser on a second monitor. It also does not, and will not, incorporate anything that violates the User Agreement or Rules of Conduct; aside from the documented ReST APIs which it uses to communicate with ArenaNet servers, the only way this software interacts with the game is by reading information from the documented MumbleLink memory-mapped file to determine current character and location.

• Store a list of ToDo items/reminders per-zone, and display them when you're in that zone
• Track zone completion percentages.
• Displaying an interactive map of the current zone, including your location as well as waypoints, POIs, etc (with links to the relevant wiki articles).
• Using manual input (i.e. clicking on hearts/waypoints/etc. that you've already gotten), track what you haven't completed in each zone.
• Possibly showing gathering node locations on the interactive map.
• Tracking a list of crafting recipes that you want to make, and what materials you have vs still need.

See the Waffle.io board for development tasks and status: https://waffle.io/jantman/gw2copilot.

This is very alpha software. I wrote it for myself and a small number of friends. If it's useful to you, great, but I don't intend on doing a whole lot of development on it. The codebase is pretty rough, and I'm probably not even going to write tests for it, let alone the rest of what goes along with real released software; sorry, but I have too many personal projects, and I just want the end result of this.

Note that running natively under Windows is not currently functional, as I can't get GW2 to login under VirtualBox.

• Python 2.7 (for Windows users, get it here) with pip
• Guild Wars 2
• Windows, or Linux and GW2 running via wine or PlayOnLinux

It's recommended that you install into a virtual environment (virtualenv / venv). See the virtualenv usage documentation for information on how to create a venv.

pip install git+https://github.com/jantman/gw2copilot.git@master#egg=gw2copilot

If you're running under Linux (wine/PlayOnLinux), you'll also need to install Python2.7 in the same WINEPREFIX as GW2.

1. Download the Windows Python 2.7 installer linked above; GW2 is usually run in a 32-bit WINEPREFIX, so be sure to use the correct installer.
2. Under plain wine, just run the installer with wine. Under PlayOnLinux, click the game in the main PoL dialog and then click "Configure". On the Miscellaneous tab, click "Run a .exe file in this virtual drive" and browse to the Python .msi installer.
3. Complete the installation with defaults.

You'll need an API Key for the GuildWars2 API; log in to your account and generate one, and then either export it as the GW2_API_KEY environment variable, or pass it via the -k / --api-key command line option. The key you generate must have at least the account, characters and inventories permissions. It is recommended for security that each application you use have its own API key.

@TODO this.

gw2copilot is built on the shoulders of giants; it makes use of the following Free or Open Source tools:

• drant's gw2timer.com (github.com/Drant/GW2Timer) for data on resource node locations and some other items not accessible through the GW2 API.
• bootstrap and html5boilerplate for the UI, downloaded via initizlizr, which themselves include jquery and modernizr.
• The twisted event-based asynchronous framework at the heart of the app (reading the MumbleLink file, serving HTTP and websockets, and timer-based actions).
• The Klein microframework for serving HTTP, with user-oriented pages templated using Jinja2.
• The python psutil package, which greatly simplifies finding the running GW2 wine environment.
• Crossbar's autobahn Python websocket server.
• leaflet for rendering the interactive maps, greatly helped by the example on the GW wiki and an example from Cliff Spradlin.
• The leaflet.contextmenu plugin for context menus.
• bootleaf to integrate Bootstrap and Leaflet.
• jqueryui-bootstrap-adapter to make jQuery UI and Bootstrap play nicely together.
• jquery.appendGrid for the editable Zone Reminders form.

If you're running natively under Windows, it simply reads the memory-mapped MumbleLink file.

If you're running under Linux (wine/PoL), it's a bit more complicated and involves some "magic", as the memory-mapped file can only be read by other programs running within the same wine server.

1. Look at the running process list, and attempt to find the Gw2.exe process.
2. Find the correct WINEPREFIX from Gw2.exe's environment via the /proc filesystem.
3. Look for Python2.7 at the default install location of WINEPREFIX/drive_c/Python27/python.exe.
4. Find the correct wine binary by searching for it using the PATH of the Gw2.exe process.
5. Execute a small helper "shim" script, with GW2's wine binary and environment, that reads the memory-mapped file and writes all changes to it as JSON to STDOUT.
6. The main script reads that process' STDOUT to retrieve the information.

Bug reports and feature requests are happily accepted via the GitHub Issue Tracker. Pull requests are welcome. Issues that don't have an accompanying pull request will be worked on as my time and priority allows.

To install for development:

1. Fork the gw2copilot repository on GitHub
2. Create a new branch off of master in your fork.

$ virtualenv gw2copilot
$ cd gw2copilot && source bin/activate
$ pip install -e git+git@github.com:YOURNAME/gw2copilot.git@BRANCHNAME#egg=gw2copilot
$ cd src/gw2copilot

The git clone you're now in will probably be checked out to a specific commit, so you may want to git checkout BRANCHNAME.

• pep8 compliant with some exceptions (see pytest.ini)
• 100% test coverage with pytest (with valid tests)

Testing is done via pytest, driven by tox.

• testing is as simple as:
  • pip install tox
  • tox
• If you want to pass additional arguments to pytest, add them to the tox command line after "--". i.e., for verbose pytext output on py27 tests: tox -e py27 -- -v

1. Open an issue for the release; cut a branch off master for that issue.
2. Confirm that there are CHANGES.rst entries for all major changes.
3. Ensure that Travis tests passing in all environments.
4. Ensure that test coverage is no less than the last release (ideally, 100%).
5. Increment the version number in gw2copilot/version.py and add version and release date to CHANGES.rst, then push to GitHub.
6. Confirm that README.rst renders correctly on GitHub.
7. Upload package to testpypi:
   • Make sure your ~/.pypirc file is correct (a repo called test for https://testpypi.python.org/pypi)
   • rm -Rf dist
   • python setup.py register -r https://testpypi.python.org/pypi
   • python setup.py sdist bdist_wheel
   • twine upload -r test dist/*
   • Check that the README renders at https://testpypi.python.org/pypi/gw2copilot
8. Create a pull request for the release to be merged into master. Upon successful Travis build, merge it.
9. Tag the release in Git, push tag to GitHub:
   • tag the release. for now the message is quite simple: git tag -a X.Y.Z -m 'X.Y.Z released YYYY-MM-DD'
   • push the tag to GitHub: git push origin X.Y.Z

11. Upload package to live pypi:
    • twine upload dist/*

10. make sure any GH issues fixed in the release were closed.

This software is licensed under version 3 of the GNU Affero GPL. The gist is this means you can't build a publicly-accessible service using this code unless you release your complete source code to all of your users under the same license.

This software does not, and will not, violate the Guild Wars 2 User Agreement, Rules of Conduct or Terms of Use.