Leaderboard

Hello everyone! We are now in Feature Freeze for A27. With the new git workflow, a few things have changed (improved, we hope). The nightly-build tracks the state of A27 and can be used to test the new version. It is generated daily, and you can get it using SVN. Detailed information can be found on the wiki if you try to build the game on Unix, please note that the build process has slightly changed. you need to run first libraries/build-source-libs.sh, then build/workspaces/update-workspaces.sh, then make as usual Mock Release Bundles are also generated daily, from the nightly build. They can be downloaded from our Jenkins build system. Future RCs will be taken directly from here. For now, we have a few bugs to fix, you can find them on the Alpha 27 Milestone of our bugtracker. A higher overview of the release process can be found at [RELEASE PROCESS] Alpha 27 Contrary to previous releases, we are able to use a git branch for preparing the release. Thus, the contribution workflow is not stalled during the process. We are still merging the work of devs and contributors into the repository, for inclusion in the future releases. The preparation of Alpha 27 is made in parallel, and not blocking. That said, most of our energy is dedicated to the release, and you will experience delays in us reviewing contributions. Please make sure no mods are enabled when testing the game. Note that the "spirv" mod for Vulkan shaders is obsolete. The nightly build and bundles already contain the shaders. You can delete all trace of this spirv mod from your computers. It will not be needed anymore. What should I test? Everything What should I report? Not everything. We must fix regressions (stuff that used to work, but doesn't work anymore) and critical issues that would prevent the users from playing. We cannot reasonably fix all the existing bugs in the release. Critical issues include crashes and multiplayer OOS. How to report them is detailed in the ReportingErrors wiki page. With the new daily generation of testable game versions, it is absolutely necessary to check you use the same nightly build (version is displayed in the main menu) without any mods when testing for OOS. Happy testing!

I edited the previous post: the Mock Release Bundles are now signed on macOS, and should not require workarounds to be tested. Thanks to everyone who gave feedback and reported bugs already! We are steadily progressing towards the first RCs.

I'd like to get the default stance of new units as "defensive" when they are created. Is there a way to define the default unit stance'

Officially I mean. There are a lot of things those mods offer that I want to see in the game.

I also think that the default attack mode when creating units should be that or that it can be changed in the game settings.

Free open source, Linux friendly, low system requirements, CnC Tiberian Sun like game. But has new features and very good gameplay:

I think it's a great idea. I was originally not planning on teaching the player the diplomacy system, but this is a nice opportunity to do so. We could make scenario 3 focus on fortifying the city and repelling an assault. But in the end actually negotiate an alliance with the attackers: For instance, gifting them some food to help with a current shortage (and maybe arranging some intermarriages). And in exchange the player gets access to the Iberian embassy building in the next scenario (therefore the ability to hire mercenaries) to use in the large attack in the end (against some Roman target).

Wildfire Games would like to send you its best wishes for 2025! May you have a prosperous New Year!

Merry Christmas everyone.

I made some new tip images: I still have the full-res, uncropped images in case anyone wants them. Also, can someone tell me how to enable rendering the sky? And how can one rotate the camera up and down in Atlas?

Greek Theater 4k

I never noticed these guys before on Lion's Den.

Based on my 4-5 years of experience playing 0 A.D., I have noticed that many players are either overrated or underrated, with some claiming their skill level is higher than it actually is. To address this, I propose the following ladder to categorize players' levels: Iron Level (1200 or below): These players are beginners with limited experience in the game. They are still learning the mechanics, and progressing beyond this level may take a few months to several years, depending on the player. Bronze Level (1200–1500): Players at this level excel at booming but are weak in combat and often struggle against rushers. Many prefer defensive playstyles and are not as active in offensive strategies. Silver Level (1500–1700): These players are "eco-bots" with excellent economic skills and strong armies. However, they rarely rush and lack proficiency in advanced rushing tactics. When they do rush, it is often infantry-based. They primarily prefer playing on mainland maps and are less skilled on low-resource maps. Additionally, they are vulnerable to early attacks. Golden Level (1700–1900): These players are aggressive and knowledgeable about rushing strategies. They excel at disrupting the economy of silver-level players and often dominate early engagements. Diamond Level (1900+): These players are highly creative, capable of devising new strategies for both combat and economy. They often serve as role models, with others learning from their gameplay. In my opinion, among last year’s active players, only Vali, Borg, and Vinme belong to this elite level. Note on Cheating: Some players use tools like ProGUI auto-train, hacked auto-civilization selection, or multi-click mice. While some may argue these are not cheats, in my view, anything that provides an unfair advantage is cheating. These tools can artificially elevate a player's level. For example, a bronze-level player using cheats might appear to be at the silver level. Therefore, players using such tools should be demoted by one level in their ranking.