zoot

1. Foundations do not show up on the minimap. Having nearly lost, the enemy can build a foundation some silly place and remain nearly invisible and thus drag out the match needlessly. 2. Destroyed civ center foundations count towards civ centers destroyed in the match statistics:

When you select a group of units including battering rams, you will often be able to set the stance of the whole group (e.g. to "Standground"). However, when you then later select just the battering rams, you will be unable to change their stance again (e.g. to "Aggresive") because they do not have the stance UI.

Yep, that works. Can you do it for the production queue too?

When any of you experience these 'black' issues, can you please try disabling and enabling shadows (from "MENU -> Settings") and see if it makes any difference? It sounds a lot like issues I've had with the minimap when shadows are enabled.

Indeed, that was what I meant. Perhaps a check could be made when the button is clicked ("sufficient resources? if not, ignore click")?

I think there is a small bug/lack in this feature: if several buildings of the same type (e.g. fortress) is selected, the icon will not show as red if there aren't enough resources to build the given unit from all the selected buildings, even though that is what will happen if clicking the icon. Also, it would IMO be nice if in addition to turning the icon red, it actually disabled the button - it's annoying to Shift-click the icon 10 times, see it turn red, accidentally click it another time, and then get the "not enough resources" message and having to start all over.

In a similar vein to this, it would be nice if generic names showed up in the tooltips of garrisoned units.

For all the reasons that have been listed previously: - People seem to be having a lot of trouble making SVN accept patches from their Git repos. - SVN working copies don't carry their history around like Git working copies do, hence every time someone begins working from an SVN working copy, they break the Git side of the equation.

Why retain SVN? Git can easily act as a 'blessed' repo.

Welcome to the forum! Cool idea, but note that 0 A.D. covers the time period from 500 B.C. to 500 B.C. The Mosteiro de Santa Maria de Seiça seems to be from the Middle Ages, but of course it could always be part of a cool medieval mod.

IMO units that are stuck should be given license to pass through obstructions to get out of the way.

Is it a bug in a particular variant perhaps? The unit seems to have the same hair in both shots. quicksave-0008.0adsave.zip

quicksave-0003.0adsave.txt

I have encountered a similar issue, though in my case at least, it seems to have nothing to do with the terrain, but rather that a unit got stuck within the foundation (the piece of wall under construction). (I would have attached a savegame of the situation, but "You aren't permitted to upload this kind of file".)

I wasn't making an argument - I was pointing out the flaws in yours

Then I propose using the Lighthouse of Alexandria instead IMO, the lighthouse is the obvious choice for a wonder. The library would work well as a "special building".

This bug is well-known, but I haven't seen it reported anywhere: Territory borders form weird 'islands' on steep terrain. This shot is from the map 'Miletus', but it happens everywhere.

Red player's spearman decided to wear blue uniform into battle:

The units in this screenshot were not findable with the "Find idle worker" button:

Yes. I just can't speak to the performance, because I haven't tried it. That doesn't imply it's bad, though.

Not yet, but this close to a release new builds are going in fairly frequently. You can check what is going into SVN here. At the moment, new builds usually have a log message saying "Manual build".

Please see: http://trac.wildfiregames.com/wiki/GameDataPaths

Sorry for sounding like a broken record, but - normal maps! It's designed to enhance that kind of features.

Another advantage of Git is that it has no single points of failure. Say you decide to host the main branch on a Git server of your own on git.wildfiregames.com and set it up so it automatically pushes all commits to Github for backup purposes. If the main server on git.wildfiregames.com crashes, no problem - everyone just begin pushing to a branch on the Github mirror while the outage lasts. When the main server comes back up, Git can easily figure out how to merge all the intermediate commits back into the main branch. The same goes for build automation. Instead of having a single autobuilder set up, any trustworthy person can set up an autobuilder of their own and have it push the new builds to their repository. When the main autobuild is down, people can just begin using one of these secondary autobuilds until the outage is resolved.

http://www.wildfiregames.com/forum/index.php?showtopic=16189