Forums

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.

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.

Thanks for the tip, Deicide4u! I didn’t realize the “Call to Arms” could be hotkeyed either, assigning it now. That sword icon showing up is a good visual cue. One thing I’ve noticed: sometimes after issuing the command, some units still lag a bit before dropping off resources. Do you all wait a second or two before the attack-move, or just go right away? Also, thanks @Atrik for the ‘Y’ key reminder, super useful for a quick transition back to economy. These little workflow improvements really add up mid-game.

There is a "rate limiting" to avoid spam, but newcomers don't have a maximum number of posts. Once they post enough (in quantity, but not too fast), they obtain normal limitations.  

The limit is lifted when the limit is reached??? Anyway, was there a change? I remember a number of new members being stopped cold when posting too often (five posts in three days?)...