Short summary: GW2 Event Explorer is a desktop GUI program for viewing the events on a server. The current release is bare-bones and is not terribly good, but it will be enhanced later to include desktop/smartphone/tablet notifications for events. Unfortunately, it’s for advanced users only, as it’s a ruby script. It should work on windows, OS X, and linux, although it’s only been tested on windows.
This is not intended to replace the GW2 event timer sites. In fact, if you want event timer information, I recommend the awesome GW2Stuff.com site.
Get it from github (current release is 0.1). See the README.md for usage info.
NOTE: when starting this program, nothing may happen for 10-15 seconds. Please be patient. Also see the README.md file for more information.
Current minimal features:
- Seeing the available events on a given server. You can choose from any of the available servers.
- You can see all events on a server, or you can limit the events to a particular map.
- You can filter the display by event status: active, failed, success, warmup, or preparation (I’ve yet to see any event in the “preparation” state, though).
- The events automatically update every 5 minutes (this will be configurable in a future version).
- Your settings are automatically saved when you quit the program, and are automatically restored when you restart.
- The settings and the event database are stored in the current directory (the directory from which you started the program).
I’ve written this program for my own needs. If others find this useful, great. I’m open to suggestions.
- Ruby 1.9 or later, with the “tk” extension (e.g., “require ‘tk’” must work).
Windows users can download the latest Ruby 1.9 rubyinstaller (“Ruby 1.9.3-p429” as of May 24, 2013.)
- You must have installed the following gems:
gem install ruby-growl gem install sqlite3
- (Windows) You need to obtain the SQLite DLL. Go to the sqlite download page and download the ZIP archive that contains the SQLite DLL. Open the ZIP archive and copy the contents to the “bin” directory of your Ruby 1.9 installation. Example: if you have installed Ruby1.9 in “C:\Ruby193”, copy the SQLite DLLs to the “C:\Ruby193\bin” directory.
- Config files and the event database are stored in the current directory.
- Yes, “database”. The backend uses sqlite to store the event data, and can store arbitrary amounts of historical event data. Data mining, anyone? The GUI, however, periodically trims and vacuums the database, as the GUI has no real need for historical data, except for the previous event snapshot.
- In the future, notifications will be handled by sending growl messages, which means:
* You need a program to handle growl messages, and you might have to buy such a program. On windows, you need Growl for Windows (free). On OS X, you need to buy Growl. Linux users are on their own, although mumbles might work.
* For smartphone or tablet notifications, you have to buy one of the apps supported for growl message forwarding (this is supported only for windows and OS X). See the above websites for Growl for Windows or OS X Growl for supported apps.
- NOTE: while it is possible to convert this script into a windows .exe, there are no plans to do so. This is because the resulting executable is often incorrectly flagged as a virus, trojan, or other malware, due to the ruby script to .exe conversion methods.