Leaderboard

Nothing has thwarted the migration project, so it will happen as planned during the upcoming two days Here are the final improvements performed over the past weeks: Added missing "Patch By" credits in a number of commits Set up issue templates Set up code owners Devised an alternative way of tracking a release process (using issue templates) fixed issue search after the Trac import

Those are migration period and viking era art:

Dear contributors, We plan to perform a long-discussed migration to git as our version control system. We have been very happy with SVN for a long time, for its simplicity and its ability to handle our game assets. But we yearn for the collaborative features of git and for the many git-based tools that would allow for a more efficient development process. We managed to keep using SVN and to collaborate efficiently on Phabricator for the past 6 years, but unfortunately all good things must come to an end, and Phabricator is now unmaintained. We thus decided to take the plunge and to migrate to git, and we have chosen Gitea as our self-hosted git forge. Our historical Trac bug-tracker will become read-only, and its contents (tickets, wiki) will be entirely migrated to our Gitea instance. After some time, Trac will be stopped, and links to Trac will be redirected to Gitea. Access to our Phabricator instance will be restricted so that our contributors can port their open work to Gitea. After some time, all sensitive user data will be deleted from Phabricator, which will become read-only. Please keep in mind that, even though Phabricator holds a meaningful history of important discussions, it constitutes a security liability. We cannot guarantee to keep it online indefinitely. No ready-made tool exists, at this moment, to migrate Phabricator discussions to Gitea. The migration is planned to happen on the 19th and 20th of August (European hours). During these two days, the aforementioned services (Trac, Phabricator) and the SVN repositories will be down. Development progress will be halted. We plan to provide a functional git-based development environment immediately after the migration. Most CI/CD systems are ready to be launched, and user documentation is ready. But the transition to a new development flow will, of course, take some time. We hope that this transition will allow us to make swift progress on the long-awaited release of the next Alpha.

One of my friends used to play a lot of Age of Empires and he started searching for an alternative and eventually found this game. Then he introduced it to our friend group. It was basically just word of mouth.

Sounds like something for @wraitii

Works for me

I was going to report that Trac is down right now... So is this people doing it one day early, or is Trac going to not leave without a fight?

Goth barrack

The shields the enactment soldiers use in this book look pretty nice: https://books.google.com/books?hl=en&lr=&id=7aBGEAAAQBAJ&oi=fnd&pg=PT7&dq=teutobod&ots=bJbD6ZUQYm&sig=F_tjU-wjjn3xLHFOG7HyG4niQEU#v=onepage&q=teutobod&f=false

<p class="warning">WARNING: there is a required technology</p> <p class="warning">WARNING: there is a required technology</p> <p class="warning">WARNING: false</p> <p class="warning">WARNING: there is a required technology</p> <p class="warning">WARNING: true</p> Ok, so it does work, its just the tooltips that are not accounted for. So I think the solution at least for now is to just use some text to indicate that a tech is needed for the aura to take effect.

When you say it does not work, do you get errors, or does CanApply ignore the requiredtech ? From this line of code, it seems it should still be supported https://code.wildfiregames.com/source/0ad/browse/ps/trunk/binaries/data/mods/public/simulation/components/Auras.js$144

More designs

Some examples