Leaderboard

Wildfire Games is proud to announce the release of the Patch Release A27.1 for 0 A.D. Alpha 27: “Agni”. This is the first patch release of 0 A.D., made possible by the new development environment put into place last year. Easy download and install Download and installation instructions are available for Windows, Linux, and macOS. 0 A.D. is free software. This means you can download, redistribute, modify and contribute to the application under the same licenses: GNU Public Licence version 2 (GPL v2) for code and Creative Commons Attribution Share-Alike 3.0 (CC-BY-SA 3.0) for artwork. Although you might find some people selling copies of 0 A.D., either over the internet or on physical media, you will always have the option to download 0 A.D. completely gratis, directly from the developers. No “freemium” model, no in-game advertising, no catch. 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. Changelog Here are the changes included in A27.1: 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) fixed support of Windows 7 a fix for modifying your lobby password when you have an uppercase letter in your username a fix for the distorted 3D models with GPU Skinning fixes for crashes with Vulkan and/or with GPU Skinning a fix for changing player perspective in replays a fix for an out-of-memory crash in the JS engine when generating random maps a fix for the game crash on pressing Fn key a fix for a crash in Atlas when the map generation fails a fix for a memory leak in the renderer fixes for multiplayer port forwarding package fixes for Linux desktop environments various build fixes for Linux (some sent by package managers) Thanks to all the community for your continued support and enthusiasm, which allow us to deliver these updates! Reporting issues If you experience a technical problem with the game, please report it at gitea.wildfiregames.com. This is also the first address to visit when you wish to dedicate some of your time to help patch the code. Got any further questions or suggestions? Discuss them with other players and developers at the forum or talk with us directly in the IRC chat rooms: #0ad and #0ad-dev on QuakeNet. Subscribe See our LinkTree. For press/media inquiries, please DM @play0ad on Bluesky or webmaster at wildfiregames dot com.

Let's wrap it up with a classic for now.

In a rush situation or playing on the border, 10 soldiers before upgrading wood and farm. In a situation where you're certain you won't receive a rush, upgrade wood before the barracks, then a barracks and farm upgrade. Of course it's very situational, but in general this is how I do it.

You can even see in his glasses he is pausing while a ally is about to rush

okey, here's my take

Well, as borg said, it depends on the situation you're in. If you are doing a boom, get level 1 woodcutting as early as possible. Get level 1 farming once you transition to farms. If you are being rushed, priority is to defend yourself, so make soldiers. Get level 2 as soon as you hit the town phase.

Yes there are some imperfections for sure. As well the graph smoothing make the first minutes inconclusive, since everybody will have a point at 100% and it takes until fcking min 5 for the smoothing to wear it away.

Also probably makes sense to only clock idle time when a player is below max pop. Anyways, these are cool graphs.

It's total idle time / total life time of buildings, while the time in seconds is just total idle time. So burrito had more buildings, or that were alive longer. Basically it tells you the efficiency (or downtime) of your production buildings.

Thats cool data to have on the summary. How is percentaje calculated? tabasco has 280 seconds idle time and burrito has 573 seconds. and yet both has 54%

1) Download the source files from play0ad.com 2) Check the requirements for building from source for your distro. 3) Build a game somewhere on your Games drive. 4) After that, run the pyrogenesis executable.

Right. I read a bit too quickly and didn't realize when you said idle time you were referring only to barrack idle time

My go-to is 1. Ranged Damage Upgrade 2. Pierce Resistance Upgrade 3. Hack Resistance Upgrade 4. Melee Damage Upgrade but it does depend on which units you are planning to go for; with athens/sparta, you might opt for melee first, against rome you might make the hack resistance upgrade first.

It's getting danker.

No names have been mentioned.

Of course. But as long as we dont have a button to jump to the next idle building, the same cant be said about buildings, which is why a graph with the cumulative building idle time would be nice.

Obviously, this makes you a better player because it masks your flaws. Being better or worse than another player requires several evaluation points, and one of them is the ability to manage everything that happens on screen, especially in an RTS game. If you use a script that does these things for you, it's obviously an advantage and shouldn't even be discussed. Your analogy exemplifies exactly what I said. A manual car may not be faster than an automatic, but there's a chance of shifting into the wrong gear and breaking gears in a manual car, which isn't possible in an automatic. That's exactly what you do when you use scripts to mask your mistakes.

After the nerf of champion cavs, Naked Fanatics will become the next brokenly OP unit. This unit is already highly OP in non-champ-cav TGs; it deals insane damage in P2 and is hard to defend against, then in P3 it can be spammed en mass as a melee + meatshield. Most importantly, they counter the cavs to well. There are already very few infantry units which can beat it in a direct frontal 1v1, then if you factor in the cavalry-matching speed, it makes Gauls too OP. The cause of this situation is that the unit has double the health of a spearman and the same armour. It is also affected by all upgrades, including armour ones, which means it's not naked at all: Suggestion: in order to live up to their name, they should have no armour at all and be unaffected by the armour upgrades. Also the cost might need to be reconsidered. You can't have 200 health and full melee armour and near-cav speed and no weakness against spearman.

It is Zagros Mountains, and it seems to be consistently doing it now. Really weird issue since it didn't a few times. Restarted the game too. Edit: Yeah this just decides to do it completely randomly.