quantumstate

I agree, I don't see the reason for diminishing returns if we lower the gatherer cap.

Locking this for consistency with the previous lock on the other thread.

I think towers, civil centres and fortresses. When calculating damage each type is done individually and then the three types are added together to give the final damage. So pierce armour only affects pierce attacks. The way armour works is that each point reduces damage by 10%. So a unit with 5 pierce armour will take 10% less damage vs a pierce attack than a unit with 4 pierce armour. The damage reduction percentage is shown in the tooltip.

I don't think we are getting anywhere. The decision to change farms to infinite resources was made recently and is unlikely to be reversed, though feel free to keep debating here if you wish. (AoM had infinite farms, also Warcraft 3 != WoW)

Thanks, but I am a native speaker. Perhaps you could reword it to help me understand . How is a strategy good for an AI but not for a human? If an AI can play a strategy then so can I. (unless it has very high micro management requirements, but infinite farms clearly don't). By this am I to understand that you want to remove that from the game on the same grounds? If not then I don't see the problem with arguing that since one form of non realism is acceptable then this form of unrealism is acceptable because it is actually more realistic. I disagree that the other games suck. Here are some examples: AoM, AoE3, AoE Online, C&C Generals, Warcraft 3 (night elves and wood). I might not say all are great games but I think some are (AoM, Warcraft 3). You are free to hold a different opinion of course but since many other people agree based on reviews I think infinite resources are ok from this point of view.

Sorry, I don't understand this sentence. Can you reword it? I fail to see what is especially unrealistic about infinite farms. As other people have mentioned real farms do have a tendency to be infinite as long as you keep a bit of last years crop to replant. They definitely don't continuously consume wood. We have to sacrifice realism in a very large number of ways in order to make a playable RTS game. (glaring examples are gathering some berries in order to have a woman magically appear after 30 seconds). I was arguing in my previous post against your argument that infinite farms are unbalanced. The strategy you mentioned in the first post is not viable vs a skilled opponent. Infinite farms are not unbalanced, many other games have implemented infinite resources.

What you have done sounds correct. It is the problem with having different civs not having exactly equivalent buildings.

I thought that scripting engines were allowed as long as it is not possible to run any code that is not in the original package. So as you didn't allow mods to be installed it should meet the requirements. Also for those interested this source linked from the wikipedia article gives a clear explanation of the possible legal issues with the GPL and the app store http://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement

Infinite farming is a completely sensible mechanic. The gather rate is lower than other resources and trading through the market is inefficient (though the rate change might need some balance as suggested above, that needs playtesting to decide). If two people are playing and one controls the whole map and the other is just farming and buying resources at the market the one controlling the map will have massively superior income (at least 1.5 times). This means they can easily win the game because they will be able to train more troops. There is an argument that it is too easy to cluster the farms very close to the CC currently. I think that increasing the obstruction size a little more is better, maybe so they barely overlap. Having ton place them a long way from the CC makes them very vulnerable early on.

The load does not affect building speed.

That looks really nice, both are good. As a small bit of nitpicking I think the wavyness of the thatch is slightly too much, if stands out a lot against your black background.

GIMP will work fine for textures as long as you understand what is happening. The issue is that the game does the player colour in an unusual way. What I think you are expecting to happen is to have a background of the player colour with the texture over the top so the player colour shows through in the alpha sections. It works slightly differently though. First with images you need to understand that each pixel in the image has 4 channels. 3 colours (red, green, blue) and the alpha or transparency channel. When you make part of the image transparent you only change the alpha channel, the colour components stay exactly the same. To see this in gimp you can use the layer mask as Enrique mentioned to show the alpha channel as a black and white image. You can disable the layer mask (from the right click menu of the layer) to see what the image looks like without the alpha channel. Now what 0 A.D. does with the player colour to create the final texture: 1. Multiply the texture by the player colour and discard the alpha channel. So if the player colour is white then the image will be left as it was (multiplying by 1 leaves things unchanged). If the player colour is black the whole image will become black, if it is blue then the image will become blueish. You can test the multiply in gimp using layer modes, just create a layer with the player colour and set the mode to multiply. 2. Take the original texture with the alpha channel and place it on top of the new multiplied image. Then the multiplied image will show through in the transparent regions giving the final texture. You can replicate this in gimp to preview what your texture will look like. 1. Open the texture, there should be a single layer. 2. Duplicate the layer. 3. Remove the alpha channel from the bottom layer. (Now you can see the colours "underneath" the transparent sections). 4. Create a new layer and put it in between the two existing layers. 5. Fill the new layer with the player colour (e.g. #0000FF for blue players). 6. Set the mode of the new layer to multiply. Now you should see an image which will look like the final texture in game. So it is important that you are aware of what the image is like "underneath" the transparent areas because it will affect what the texture looks like. This is why layer masks are useful so you can easily disable the transparency and see the colours in the transparent areas. (create the layer mask using the "Transfer layers alpha channel" option).

That looks really nice. One thing I am not keen on is the wood plank roof. Firstly it is flat, flat roofs are really bad at keeping water out, making them slope a bit is pretty easy so I would assume people in wet areas wouldn't make them flat. Also the lengths vary a lot, whever I have built something I tend to cut things to be the same length, everyone in the modern world does that so I woud have thought the gauls might have as well (producing wooden planks was a lot of effort back in those times so you wouldn't use them in a quickly thrown together structure you didnt care about).

Those maps look nice. You do just need to zip the pmp and xml files to share them. You shoud be able to atach zip files to a forum post.

I've seen this problem before. It is from the code which is detecting which unit is under the cursor. I think it happens more on linux because the mouse events come at a faster rate. There should be a way to speed up the code but it isn't a straightforward piece of work.