Bustikated

The Window

All of the action takes place in the window.

• Map – Where the action is
• Cash and income
• Inspector
  
  1. Name & Description of currently selected (hovered) terrain or unit
  2. The current unit is strong against these units
  3. The current unit is weak against these units
  4. The current unit can’t be used to attack these units
  5. Terrain effects on this unit
• Chat Window
• Player List

The point of WeeWar is to build an army and destroy your opponents.
To do this, you need to build units.
To build units, you need money.
To get money, you must capture bases.

Only bases generate income. The amount varies from map to map. This cash will be deposited every round.

Bases also build ground units and hovercraft.
Airports can build helicopters, and planes.
Ports can build hovercraft and ships.

Repair patches aren’t capturable. Repairing a unit on a patch totally repairs that unit!

Most units can either
1. Repair increase 1 or 2 HP
2. Move and stay
3. Move and attack

• Infantry & Hovercraft can capture if they are on a building. Infantry are a LOT weaker during capture.
• The Light Artillery, Heavy Artillery, and DFA units can not attack after moving.
• Planes can move, attack, and move again.
• Air units can’t be repaired.
• The Battleship can move and then attack twice.

Most units can only attack adjacent units, that is units they are right next to. Indirect units can fire on units in their range.

Terrain

• Different units move differently over the different types of terrain.
• Some units can’t cross certain terrains.
• Some units get bonuses or penalties in combat if they are on a certain terrain.

If you haven’t already, see parts 1, 2 and 3

This script checks your HQ and prints out a list of games. You can see the returned xml data here.

Example Output

Active Games
One if by land
Someone else’s turn for the last 2 hours

It’s been brought
Someone else’s turn for the last 8 hours 12 Minutes

WAR 2
Someone else’s turn for the last 10 Minutes

Go Baby Go
Someone else’s turn for the last 1 hours 35 Minutes

Lobby
Moo, This Means War

more

If you haven’t already, see parts 1 and 2

This script will request information about a game, and output it nicely. You can see the returned xml data here.

Example Output

Game Info
map => lakes1187102532212
type => Pro
pace => 1 day
cbp => 150
round => 14
credits => 100
name => One if by land
started => Mon Feb 25 02:54:46 UTC 2008

Players
BM5k, bowerman4875, sbowerman’s turn

more

If you haven’t already, see Part 1

I’ve thrown together a script that requests my player info, and outputs it to the screen. You can see the returned xml data here.

Example Output

About Me
name => BM5k
online => true
id => 10908

My Stats
wins => 9
losses => 4
draws => 1
credits => 103350
points => 1523

Friends
sbowerman, bowerman4875, spacecadetjuno

Games
56945, 56698, 56939, 56992, 57266, 57641, 57639

more

As a ruby newb, I thought that I’d document my first trek into API development.

Lately, I’ve been quite taken to wasting hours in front of WeeWar, to the extend that it’s interfering with my normal goofing off. Among other things, WeeWar has a relatively simple API. An introduction can be found here.

There are only a few API accessible objects, Players, Games, All Players, and the HQ. Click on the preceding links for sample of the data returned by each.

These URLs are pretty straight forward. The key thing to realize is that while games are selected by numerical id, players are selected by name. (Names are NOT case sensitive, i.e. Bert is the same as BeRT.) Also, accessing your HQ requires both a user name and an API token. You can find your API token on your account page.