Itms

They're at the tip of the branch, 173100c5c3. The RCs are based on the nightly build.

The Unix bundles are used by package maintainers, they still need to be compiled following the Build Instructions. You'll need unix-build to build the game and then unix-data to play it.

The first Release Candidates are available for Alpha 27 You will find them at https://releases.wildfiregames.com/rc/ Please report any issues in this thread! We are preparing the announcements, hoping to deliver this new release soon if no breaking bugs are found. Thank you to everyone who has already tested and provided feedback on the mock bundles.

This is now fixed!

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.

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!

Done

Hi, thanks 2. would be fixed by 7. but you're right, that doesn't work in the nightly SVN. Instead, if you version of subversion is recent enough, "svn cleanup --remove-unversioned" would do the trick. 5. 6. ah, you're correct. those are fixes that are in place in our CI configuration, but on on the build instructions. 9. The SPIR-V mod is not needed anymore, you can delete it from everywhere. All the SPIR-V shaders are already included in the nightly build.

and the vast amount of underpaid workers from developing countries

I'm not an artist but I'm amazed by what they can create and very proud of participating to a project that is so visually appealing. I would be very sad to see this work from humans replaced by generated contents copied over from someone else's work (because "generative" AI creates from plagiarized content, for now). Jason, the content you sent is beautiful, but knowing that no one spent time on it, demonstrating their skills through it, removes all the value in my eyes. I'm on 0 A.D. to do something selfless, spend much time on something for the love of it. The end result is not by far my main metric of satisfaction. Similarly, genAI could generate documentation and increase our metrics on this front... but without real added value. If an AI can deduce what the code does, maybe documentation was not absolutely necessary at this place. Worse, it can generate low-quality comments which mask the need for detailed information written by competent developers. And, my main concern, regardless of the very personal input I'm giving above, is the carbon footprint of these tools, which is ridiculous. If we're accelerating the catastrophe just to splash shiny images on a hobbyist game, we're being very careless. That also includes using genAI for inspiration.

As long as it's still relevant maybe it would be good to test and have reproduction steps on the nightly build.

Hello zyli, thanks for the report and the useful feedback on the build system. This is currently being fixed, in PR-7323 Unfortunately, Rust 1.66 is a requirement from Mozilla to build SpiderMonkey, we cannot decrease that. However, you can install Rust 1.66 or later using Rustup instead of your package manager. This is the recommended Rust install method. On our CI this allows us to build and test 0 A.D. even on Debian Bullseye.

I don't care much, but from the (very) few games I played with this new system, I feel like it's closer to a traditional RTS experience while still retaining that realistic and original feature of capturing, which allows players to diversify their strategy and turn a game around. I quite like it. I am not sure it's possible to reach a consensus here on the forums, but what about trying a release with that change, and see how the wider community reacts? It's always time to switch that back in the community mod and A28...

It does not look like it, the missing files are not LFS files. Moreover the user reports using the nightly build, so there is no need to pull anything. @superserioussam I think that your download of the nightly build is incomplete. In the nightly build folder, right click somewhere and choose "SVN Update". If you get error messages, try a cleanup first: "right click > TortoiseSVN > Clean up...", then check all the boxes, let it finish, then retry "SVN Update". The update process should complete with the message "Completed - At revision: 84" (or a higher number than 84 if you try this in the upcoming days)