I tried coming up with a good logo the last two days but i didn't really succeed. This one is like the small one in my signature, the axes took me quite a while to get them look good. I don't really like it but right now i can't think of something better.

And yeah, really nice work accounthack this should be good to use.

Another try, i like this one better but i am not so sure if the WAR part is actually readable. I guess many would read it as KRH or something.

Please consider removing the timer for attacks that fail because the selected spot is not adjacent to your land, and for evacs on land you don't own.

Also, if you do leave the global-ish geo eff recalc and go with the much-more-efficient local updates to face/tile count, consider removing or seriously reducing the timer on evacs generally.  Partly, players are happier grinding out time to expand, compared to spending time to contract; partly, spending half your time evac'ing to advance your scouting party across the plain is tiresome; and partly, there are tactics that leave you utterly crippled and unable to do anything but abandon unless you spend a large chunk of time on evac, which is likely to drive away players who would otherwise tough it out, and we'd rather have them around.

@ZuckeR
Very nice, i like it.
Reminds me of the good old game classics.
 

Quadrants are a 25x25 area, one entire map's view.

The inherent problem is the speed of database transactions.  I'm still working through how I want to handle this. I'm thinking of a few different options.  All of them end with making the map "static".  That is, only load one screen, change the individual parts on that screen, etc. instead of moving to a new screen on each point.  The old game did things that way, and it worked out very well.

1) My first thought on speedings things up is to throw a compiled array into memcache and maintain it.  I'd need a 27x27 array for this, as I'd need a 1 tile ring around the map for display purposes only.  I'd need to swap data in and out of the memcache array just to be safe.  It does lead to an issue with writes though.  The DB isn't async, so the response would still hang.

2) To build on #1, scrap the memcache thought, and add a memory table to the DB for "queued updates".  Have a php job that runs in an infinite loop, looking every few seconds to see if there's anything in the memory table, and if so, process and update the DB.  This would separate the business logic from the display and would drastically speed up game play, with the down-side of non-immediate responses.

3) Combine the memcache & memory table scenarios together.  It'd be extensive and memory intensive, but it might work...

Any other ideas?

I think you could get some aspects of the map completely static. So you could put those infos in a simple php array rather then putting it in the database. This of course would only work if you do not plan on changing the map too often.

Map cell data could be static and if quadrants are pre-rendered you would only need to send the cell type for each one visible.
$map[x][y] = array(
 'type' => 1,         // ground/water/??? determines if you can walk/attack a tile.
 'color' => '#ffffff' // not needed on pre-rendered quadrants or if the cell type would have a color assigned to it.
);

Landmarks / Orbs could be static if you do not plan on changing them on a regular basis.
$landmark[x][y] = array('type' => 1);
$orb[x][y] = array('type' => 1);

Now you would still need to get who owns which cell and how many forts are placed from the DB. But that way you would only need to improve those requests rather than getting all the other infos as well.

Yeah, you are right databases are pretty damn efficient for searching. You would need to split the data into several arrays and files you could include when needed so only having the quadrant you are on in memory. It could work but would also be pretty messy. I guess your async idea should be more efficient.

A few 'would be nice' enhancement ideas:

1) have the keys E/A/F/M set the next action type, so we don't have to go down to the picklist
2) have the coordinates appear in the, hmm, status line updates (Attacking could be [2,494] Attacking, etc.)
3) have the status line updates spawn/stack from the lower right instead of the upper right, so they don't overlap your xp in Stats or the recent actions in Log.

None of them are showstoppers, but they'd be good ROI, I think.