All Activity

Then you need to take account of his true level when balancing.

Unfortunately we were both pockets, but I did manage to fully 1v2 my side, as well as 1v2 his side multiple times. However, it was not enough

Well played Barcodes, impressive performance in carrying your team. This game was just simply imbalanced. To survive with DoctorOrgans, you must glue your army with his army at all times and follow him closely. The two of you will win by numbers. Since he is Spartan, he will be mostly javs and melee, therefore you should focus on longer ranged units such as slingers archers. If you are his pocket, bring cavs as well. He will be doing the main melee damage and meatshielding and you can be the sniper / taking care of the flanks.

It is very annoying and inconvenient, you would have to do a lot of micro.

There are many variations of the crash errors. I will put the issue onto Gitea. This RC gives a different error to the A27-0 version.

Maybe the sentry tower.

Is it already a known issue? If not, please open a ticket on Gitea, if yes we'll try and take a look.

In the bottom of the main menu, it should display (release-a27.1, 68d99) instead of (release-a27, 8c96b)

I am currently playing on the RC. It feels much much smoother than A27 and I have experienced no random crash / stuttering so far. The minimum fps has always been very high. Good improvement! However, Atlas crash still persists, especially on Wayland.

Congratulations to everyone on the team for the new update, I'm happy with this new approach!

How can I check if it installed correctly?

Hey guys, This is my 158th attempt to complete DoctorOrgans challenge, but unfortunately no avail! However, this is probably my closest game by far, but it wasn't good enough this time. If anyone could give me any tips for future games, I would greatly appreciate it!

It's clear there's a lot of room for balance improvement, but please don't remove CS. It's one of the few most distinctive features of the game. Let's not revert everything to the existing standard. Let's not turn 0ad into yet another RTs

P.S. i have one more sub-idea: move Eco upgrades from Storehouse/farms to Blacksmith. I didn't think a lot about that, but I guess it'd make some earlier timing pushes more viable. Tho idk if you will be able to do enough damage to pay off delaying eco upgrades?

It's kinda weird mechanics, but why not try since we want to be weird (different to classic RTSes/AOE). Question is just technically how complex is that to implement for programmers. Ofc, time is to be discussed and tested. Eventually time can be different in each Phase if needed.

The skirmisher of the gauls get a cape when they promote to rank 2. During the attack animation this cape stays in position while the body moves forward and backward during throwing. See attachment gaul_cape.mp4

This is a great suggestion, and it's not the first time I see it proposed. I wouldn't make it 30 seconds, 10 seconds is already enough. 15 seconds max.

Congratulations development team for their commitment and dedication.

Yeah CS is kinda annoying and gameplay in 0ad is not that dynamic as it could be. I have 3 brainstorm ideas for this (1) Have you guys ever discussed to increase eco difference between CS and Women/Villager? What I mean is now we have situation that CS has better Wood/Metal/Stone gather rate then Villager. Why not make Women like 1.5-2x faster gather rates then CS (that is nerf all gather rates for CS by 1.5-2x). (2) Allow building Towers anywhere on map, even on enemy's territories. (3) Add some Upgrade/downgrade buttons to CS so they need like 30s to be turned into fighting unit. In theory, you can moveout with CSs and click on "Upgrade to soldier" and when you arrive armors will be ready and opponent will need same time to upgrade so it will also damage his eco. After attack, you click "Downgrade to Worker" and by time you return back to your base, your soldier will become worker.

Hi. Guys. I didn't follow this forum for a while. What's new in this Mod in 2025? And is it still alive at all?

Hi everyone, We are preparing the first "patch release" of 0 A.D., now that our workflow allows us to do that. We need your help testing it! What is a patch release? A patch release is a minor release of 0 A.D., bringing a few selected fixes from the development version into the latest release of the game. All fixes of the patch release are already present in the development version (the future Release 28). There are two important aspects to a patch release: Patch releases are OOS-compatible with major releases. If your friend has not heard about the patch release, or cannot install it for whatever reason, they should still be able to play multiplayer with you. This limits the kind of fixes we can include in a patch release. Patch releases are prepared on the side, and do not take precedence over our work towards the next major release. We prepare and provide patch releases as our resources allow. This limits the scale of the fixes we can include in a patch release. What is the current status of A27.1? We have setup all the infrastructure for generating patch releases, and a first testable version is ready for you. It is still incomplete, and thus labeled as "Release Candidate Zero" (RC0). In A27.1, we wish to include, but those are not yet in RC0: a fix for the flood on non-flood maps reloaded from a save a fix for modifying your lobby password when you have an uppercase letter in your username In RC0 are included: a fix for the large performance issue observed by some players on older hardware several small performance improvements in the calculation of simulation hashes (related to multiplayer stuttering) a fix for the distorted 3D models with GPU Skinning fixes for crashes with Vulkan and/or with GPU Skinning a fix for the game crash on pressing Fn key a fix for a crash in Atlas when the map generation fails fixes for multiplayer port forwarding package fixes for Linux desktop environments various build fixes for Linux (some sent by package managers) A27.1 will not include: any modification of simulation hashes: it could remove stuttering entirely, but it would make A27.1 incompatible with A27 (against rule 1 above) incremental simulation hashes: those improve stuttering as well, but are too complex to backport (against rule 2 above) How can I test it? You can download the release bundles of A27.1-RC0 at https://releases.wildfiregames.com/rc/ Please report below any crashes or new issues (that weren't already present in A27, unless they are listed as allegedly fixed above). Thanks for your help and support!

Alright, that's what I'll do, likely starting with the parchment overlay. There's some other stuff I have to finish first, but I will get to this soon.

haven't given them the Numidian cav yet, but the Cretan Archers and Balearic Slingers are there, along with Samite spearman and skirmishers.

the romans have auxiliary units through a tech