AW tools index

greenbird's AW Tools manual page

tactical

tactical shows 12x12 pixels per system with each line representing a planet and our status with the owner. See legend for their meanings. A little red bar on the right means, that the planet is sieged.
Find your coordinates by counting the brighter lines (each 10 squares) or by looking at the status bar (works at least with IE and mozilla). By clicking on a position you get to the system-info There is also a larger version (redrawn every 6h) which adds planning status color on the right half. If you want to see a map from current relations data you use tactical-live

system-info

system-info shows all available data about a system. population, starbase, plans and color-coded relationship with it's owner. Red background-color indicates a siege
Click the edit-planet-icon edit planet to get to the planet-info.
Click the relations-icon edit relations + intel to get to the relations of that player.
public profile and private profile will bring you to the public or personal AW profile of that player.
system-info also shows all current fleets which are automatically added by brownie or muffin tools (described below). It can also show 24h of fleet movement history.
There is a BB-export option to post plans in forums and an anonymous-export option which allows you to give access to your view of a single system to someone outside (e.g. for good coordination). Such an access link can be set to expire after a few days at the time of creation.

planet-info

planet-info displays information on one planet - especially about plans about which other alliance members will need to know.
Add your next expansion as "planned by" and change it to "targeted by" with ETA and fleet when you launched. And to "taken by" (or "lost") if you were (not) successful
Nowadays, the change from planned to targeted to sieged/taken is done automatically when you feed your fleets with brownie. Hint: as relative measures of time do not make much sense in plannings, the tools try to automatically convert them to ISO date strings. Following things are converted: "yesterday", "today", "tomorrow", "in 3 days", "in 4 d", "in 27 hours", "in 36 h"

relations

relations (which should rather be called player-info) displays information on one player (TAG, status, uid and all his planet's locations, maybe intel reports) and allows you to change the relation status with him. Setting a relation for an alliance tag (e.g. TZAR) automatically counts for all official members that have no overriding entry.

alliance

the alliance tool shows most public information about players. The "need" column shows free culture and this is colored in red if some culture is free. The "intel" column will show races and age of intel reports. If available from feeding a player's science page, there will also be an estimated time to culture(ETC, red if ETC<24h).

feedupdate

feedupdate you can input HTML files from the game here. Currently player/profile, map/detail, fleet, news and alliance/detail pages are supported. It will produce more or less informative output, but the real important info is "automagically" added to the plannings or player databases. The modified entries are linked in the output.
in mozilla you can: But the preferred method of feeding the tools is to use brownie or old muffin's AWUpload or AWMangle

muffin

this part is outdated. see
brownie below.
My muffin is a filtering HTTP proxy, copylefted under GPL and originating from http://muffin.doit.org.
I added two plugins to it: AWUpload and AWLink.
Notice: this section is obsolete now. See brownie below.

setting up muffin

first, you need a working java runtime environment (jre) installed on your local machine. You can download a jre from SUN
Next you download the muffin.jar (448 KB) which you then doubleclick in MS Windows or run with java -jar muffin.jar in *NIX(Linux, FreeBSD) or javaw.exe -jar muffin.jar in Windows. If you are a developer, you can get the sources here (288 KB) and modify them at will.

In it's filters menu you find my plugins:
AWLink includes some useful links to my AWTools into astrowars pages ... and it counts your clicks on the top right - when you are at 300 you should logout to avoid flooding warning.
AWUpload uploads every astrowars page you view to feedupdate.
You have to configure it with your user-name and your proper timezone (including daylight saving) as seen on the AW settings and of course you must tell it your account to the AWTools replacing "user:pass" with your actual login and password (AWTools, not for AW game). After changing click apply and save. The 5 fields are: AW-server, AWTool-server, user:pass, username (e.g. to know whose news/science/fleet page is submitted, should be autodetected as of 2006-01-05) and timezone (this can be autodetected now usually on the server side).
Put the AWUpload on top of your filter list and the AWLink below. Then save to store your settings in the Muffin/default.conf file.

Next you need to setup your browser to use muffin as proxy. In mozilla/firefox this is easiest by specifying this http://aw.lsmod.de/muffin.pac proxy autoconfiguration file. See the proxy-configuration tutorial for details
Otherwise you can always use manual configuration using localhost:51966 as HTTP-proxy, but then you can't surf the web while muffin is not running.

Finally log in to AW to check, if you got the AWTools link at top right.

An additional tool for our MS Windows NT(2000,XP,2003) users: muffin-win-wrapper.zip (108 kB) - see it's README for details.
As of 2006-01-14 last changes were done for muffin, but as brownie is better in nearly all aspects, brownie is now the recommended proxy to use and future development on muffin code will only include bugfixes.

brownie

brownie usage instructions:
configure your browser to use proxy auto-configuration file http://aw.lsmod.de/brownie.pac
as described in the proxy configuration guide
end of instructions ;-)

As hinted by the name, brownie and muffin are alike to each other... result of this being that you only need to use one of them. Some of the features (data feeding, color-coding, ETC display) will not work before your user-name is associated with an alliance - either automatically by official alliance tag or manually by the AWTools admin (i.e. greenbird).
If you can't use the brownie.pac for one reason or another there is one more method of how to use it. Just click here for AW 2.0.

How does it work

For the people interested in technology, here is some background info.
The hyper text transfer protocol (HTTP) allows for browsers to use a proxy to relay a request for a resource (identified by a Uniform Resource Locator (URL)). The proxy usually forwards the request to the server (some have caches and can answer right away). This design allows for the proxy to inspect and modify both, the request and the response, which is what muffin and brownie code do.
To let proxies work properly with AW it requires another thing: it must not be an anonymous proxy, i.e. it must tell the destination about the original IP. This works by adding the X-Forwarded-For HTTP header to the request with this information.

Tools Access Policy

Sometimes members of other alliances come to me (greenbird) and ask if their alliance can have full access to the tools.
As you can imagine, coding all these great things took me some months and even after it is written, running and maintaining it costs me some more (both time and money).
So if you want to have access, here is the deal:
In any case I promise to keep confidential and not pass on alliance-internal data (e.g. fleets, relations, intel), even if we were at war.

Sharing tools with another alliance

Often enough you are closely cooperating with a nearby alliance (like AF+IS) or your two alliance are in fact one (like NIAI+Seux), so you wish to increase the benefits of my AWTools by sharing information directly within it.
This sharing is generally supported. It is possible to share all or only part of information. The parts are:
  1. fleets (including incomings, movements and defending fleets),
  2. plans (the ones next to planets)
  3. and relations plus gathered intelligence reports about players.
The path to get such sharing is as follows: first, all sharing alliances must qualify for normal AWTools access as detailed in the "Tools Access Policy" section above. Then I (that is the AWTools admin = greenbird) need confirmation from all sharing alliances that (and what) they want to share with whom (so one party saying they want to share with XYZ is not enough). This should suffice for me to set up sharing.

Sources

You can download many of my sources from the code dir.

More Tools

see ChangeLog

Valid XHTML 1.0!