All Activity

He didn't get the memo.

Well instead of making people do the extracting and installing, they can just drag and drop the mod on the running game in windowed mode it will install the mod correctly on all platforms.

Sparta has no eco bonus and the buildings they use to train those champions are expensive. If you find a way to attack early with other civs that can boom faster such as gauls or germans or ptolemies then you might have a chance of not needing to fight the hoplites.

They get armor but not dmg from the forge. Also the splash buff and unit preference behavior change they received in a28 is quite significant. In my opinion they can be very strong in this alpha.

This is true, at lease by checking the stats in-game. Only Will to Fight affects Elephant melee attacks.

soldier_attack_melee_0X.json "affects": ["Soldier !Elephant"], Test it out in-game. edit: Has been so in 0.27 as well, so that melee elephants are not affected by melee upgrades has been in the game for a while.

One of the frustrating things about modding is how difficult it can be to get the mod to work with other people. I'm currently using git hub (kinda a newb) i share the git link: Emacz2/classical-warefare-aea and i have them download the zip, they extract to their mod folders, it shows up, they host games but still grayed out. I am aware of the naming issue. For example if one is called: Classical-Warfare-AEA and the other is classical-warfare-aea you cant join games.... but what if they are exactly the same and you still can't?!? What other issues could be causing it? Any help would be greatly appreciated.

Since I've learn the power of coding I'll go pull request to nerf your elephants, their hp is set to 1 but their evasion stat is 99.9% with 10 damage with area of effect of megameters also they spawn smaller elphants that moves like a car and punches like a bee but only to allies.

????? they do receive all bonus of forge upgrades and will to fight as well seriously, who's been spreading misinformation about my lovely cute eles? deadly too :3

P.S. I am also currently facing a problem with adjusting the normals. As you can see, it creates some strange-looking shadows. Maybe someone here has more experience with this and knows what might be going on.

Hello everyone I’m currently working on a new olive tree model for the Erechtheion and the olive mill. It’s still a work in progress, but here are the first results. I attached the blend file down below! For the foliage, I modeled an olive branch, textured it, and turned it into a foliage card to use for the tree. This is my first time working on a project like this, so please don’t hesitate to give feedback, I would really appreciate it! Have a great weekend! - Emma OliveTrees.blend

That melee elephants don't profit from melee upgrades does not help, either.

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.

i don't know, but attack take the bonus forge

Spartain Hoplites are a bit overtuned at the moment. Swordsmen should be a cost-effective counter to spearmen, but due to the Spartain Hoplites haveing an 11% faster rate of fire it makes them already almost as good. And with then either the +10% health or the +10% damage upgrade they become a cost-effective counter to their counter. So the default strategy is to not fight them head-on, but to build lots of defenses, destroy their Rams with cavalry and / or swordsmen, raid them, and eventually win a battle of attrition. If your Civ has access to them you can try Elephants, but then they can do the strategy to avoid them and raid your economy instead.

Can it be that the health bonus and damage bonus of promotions are calculated differently? It seems for the elite promotion the health bonus is HP*1.25*1.25 while the damage bonus is Damage*(1.1+1.1). Or to phrase it differently, health bonus affects the current HP, while the damage bonus affects the base damage.

Elephants are currently not that great, so it would be bad to let spear units counter them.

Oh, bonus damage / counters were removed from the game? Sad.

From different civs. So e.g. Mauryas Swordsman have the same stats as Romans Swordsman. But they can still be different. E.g. Romans Swordsman are P1, Mauryas Swordsman are P2, and Mauryas deal +20% in P3 thanks to their final melee damage upgrade. edit: Also flavor. Instead of going to the approach like AoE2 where the many units look identical across Civs in 0AD many units have a Civ-specific look.

That was fast, @Tapothei! Thanks for putting in the effort to learn how to create a PR. You could get a source-code editor like Visual Studio Code to make things easier for you. Also, when creating a PR that solves an issue, you normally want to include this in the PR message like this: "Fixes #8781" I'll try to explain the basic Git workflow as simply as possible. I'm still learning myself, so there may be a few details I’m overlooking. The usual workflow is to fork the repository, clone your fork locally, and create a branch for your changes ( You don't want to work directly on the website for practical reasons). You commit your work and push the branch to your fork. Each contributor works on their own fork. Once the changes are ready, you open a pull request from your branch to the upstream repository, where the maintainers can review it. Also, right now your changes are on the main branch of your repository. `Check this: Normally main should not be used for development. Instead, it is kept in sync with upstream (the official 0 A.D. repository), and new changes are developed in separate branches. Pull requests are then opened from those branches. This is an example of a PR from another contributor, notice his PR comes from another branch, called "lazy-actual-size": This way your main branch always stays clean and can be used to create new branches. Otherwise, if main contains previous work that wasn’t merged, those changes could end up included again in future pull requests. An if you later want to work on something else and sync your main branch with upstream, you may run into problems because git will detect local changes that don’t match upstream. By creating separate branches from main, you isolate each set of changes. This makes it easier to keep main clean, revisit your work later, and work on multiple things in parallel. I also noticed that your PR contains many separate commits. Like this: In these cases, it is usually recommended to squash (git command) them into a single commit. This makes it easier for maintainers to review the changes and keep a clean history of the proposed modifications. I know this might seem completely confusing right now. But if you plan to keep contributing, learning it will make things much easier in the long run.It can take months and plenty of frustration to get comfortable with the basics of git. So if you decide to learn it, be patient with yourself. It gets a little easier every day. Well, I don’t want to overwhelm you any further. You’ve already made it this far, and that’s worth recognizing. Thank you!

NO. KEEP MY ELEPHANTS AWAY FROM THIS! ELEPHANTS ARE NOT CAVALRY

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.

What is the point of having two units with the same stats ?

And how do you do that ?

Thx for the push, also I don't use either of them, I just have my default text editor. This took me awhile to understand(somewhat a partial comprehend)... and now after that it request for checks... man I'm so exhausted...