Deicide4u

It's a general technology not unique to any civilization. So, yes.

Name: Logistics Effect: Civilians carry +10 more resources, gather stone and metal 100% faster. Cost: 400 Wood, 300 Metal, unlocked after Hand-Cart in the City phase. The intent of this late-game tech is to make Civilians still useful after the population boom slows down and you start to replace them with more CS. Also, this makes Wheelbarrow and Hand-Cart technology more useful in the long run/worth getting. It could also be one way to test if any more changes to the Civilians are useful or not.

Why, though? I think giving melee units pierce damage makes no sense. It's also much easier to balance when you know that melee = hack and ranged = pierce. But, people chose to give "trash" (w/o metal cost) melee units high pierce damage, to artificially nerf them against buildings, thus promoting the capture mechanic.

Armor penetration created a bunch of balance issues in AoE2. Armor shouldn't ever be ignored, but we do need to correct the damage reduction formula to not give so much reduction at lower levels.

Use masses of ranged units, preferably ranged cavalry. Once the blob of Spartan death comes close, simply run away until you're at the safe distance. Nothing worse than dealing with annoying hit and run attacks, trust me. Keep up with the upgrades as Spartiates have a lot of base armor.

It makes the most sense to give javelin throwers the damage multiplier, but that would severely nerf an already underused, slow unit. The decision to retain damage multipliers against cavalry for spearmen was purely based on balance, to counter the cavalry's naturally greater speed and higher stats. Otherwise, we got rid of counter units in A17, if I recall correctly.

Micro. Your APM is better spent elsewhere.

It's not the standard type of latency lag there. Only some sluggishness during a long match with many, many units. It's gotten much better since A27.1.

You said, "the people who actually play the game", as if the only ones playing the game are the people you met in the lobby from your narrow social circle. I will not discuss anything with you anymore, as you're clearly got something personal against me if you've bothered to read my post history from that far.

Ah, so the "real players" are only players on the lobby for you? You do know that vast majority of this game's player base is outside of the lobby, do you? This game cares not for your ideological feelings. Take that somewhere else, please. Now you sound like you're arguing about something that this change tried to correct. If you'd read the release statement, you'd know this. EDIT: On topic, thanks for the mod @Atrik. We should correct the voices in the next release.

Such a strong argument. You should be a game developer, I'm sure many would love to play your games. Who cares how people call them in the lobby, there's so many players who don't care about the lobby. Or who don't even know that the game has a lobby, for that matter. Now, this is written in bad faith. It was called "woman", because that's what it looked like. You could argue that original developers should have gone with the standard gendered villager unit, but people wanted to try something different. AoE is a great franchise, but it doesn't need yet another clone. Almost no one used men to gather crops in the fields. Only the AI and some dedicated Sparta player with a lot of Helots. I really struggle with understanding your opposition to this change.

Congratulations to the team on this milestone release! I have been playing a few games and already noticed some big changes. Especially in the AI, it has gotten much better. It can be a challenge even on Medium difficulty. Gendered Civilians is such a major change. I remember suggesting this change some time back, and I'm glad it was included in the game. It helps some players who like to distinguish between economic and military unit roles. It is also logical to have civilians (or pure economic units) of both genders in the game. GUI scale sharpness is also a great fix. As for the Germans, I had a such a surprise when I sent my clubmen to chop wood I don't think I'll like playing with them, but they're nice. Someone mentioned better performance. Maybe in multiplayer, I didn't feel the increase in performance in my SP matches. Here's to many more great releases!

I can see only a small flame, but maybe there's a bigger arson on a different frame.

A German and an Italian enter a bar. Perfectly normal conversation ensues.

Some things to think about for release 29 or 30. 1) Only buildings that can be captured are production buildings and Civic Centers. Any other building cannot be captured, including Houses that have "Fertility Festival" researched and Fortresses. 2) To compensate, introduce three levels of building armor classes. "Civic" or "Civilian" structures will have ~30% hack resistance. "Military" structures (Barracks, Stables, Arsenals, Elephant Stables) will have ~60% hack resistance. "Fortification" structures (Walls, Towers and Fortresses) will have a highest ~80% hack resistance. Pierce and siege resistance doesn't have to be changed, except for structures belonging to the "Civic" class. This should massively simplify game balance and solve the Capture and Delete meta once and for all.

@wowgetoffyourcellphone Careful, you might actually make me like AI.

Cavalry was always at the fore-front in every major historical battle. So, cavalry first, then infantry. Champions are tougher, so they maybe should be in front of CS in a formation. Another logic would be that CS are a good fodder, so we should place CS in front of champions. This is also more historically accurate, as many armies reserved their elite troops for later engagements, when the enemy was exhausted by "fodder".

Hippocrates is in a league of his own.

Big population cap = macro eco boom fest. You shouldn't do tactics with an abundance of available resources and population space. It's a trade-off that's not worth the extra APM. In short, this isn't Warcraft 3. It's beyond even the StarCraft's level of macro.

Hey, I wanted to create a new topic, but it seems like someone already mentioned utilizing branches. So, the question is, why don't you use Git branches for development?

Now, this is why I still think that someone needs to 'modernize' Slackware. In my opinion, what you're just described would be a daily routine for someone using that behemoth of a distro. Which is both its main strength and weakness. We need a distro with strong base for all userspace programs. Slackware (and maybe RHEL) fit this use case perfectly. You almost can't break it because almost all applications would be compiled manually or by some automated script, inside your userspace. The distro is designed to be used like that. Anyway, I just wanted to thank you for dispelling the FUD around Franken-distros, at least for people who know what they are doing.

Ah, yes, Rust. Such a wonderful and safe language, I'm sure. Too bad it's just an unreadable mess to me. Why would the game need a Rust library for C bindings?

Happy New year guys

I didn't really forget that. I've just assumed that those library versions were backwards-compatible (as they should be) and that he would need fewer libraries anyway since it's an older alpha release. But yes, that is one issue you inevitably hit while learning to compile. And this knowledge ia quite valuable in today's world.

Hello, you mentioned that you don't know how to compile, but that may be the only option if you want Linux native older 0 A. D. And it's not too hard to do. First, get the a23b tar source and data archives from this link: https://releases.wildfiregames.com/ Then, follow the build instructions for Linux on this page: https://gitea.wildfiregames.com/0ad/0ad/wiki/BuildInstructions Obviously, instead of the latest source and data archives, you would use the a23b ones. Good backup practices apply before compiling any large software from source.