Obelix

Hello @BluetrashPanda and welcome to the community! Now that you've managed to get your game installation working, I wish you very nice matches!

FYI Pull request #8784 has been merged.

Thanks for your replies! Every open Issue has a Milestone now, the ones formerly without one got backlogged. In the next step, all Issues with Milestone "Backlog" and the priority label "1: Release Blocker" have been set to Milestone "Release 29". Right now, I have set all backlogged Issues that have the priority label "2: Must have" to Milestone "Release 29". For me, this case is now closed.

FYI Pull Request #8881 (Persians to Achaemenids) got merged 11 hours ago (5268cb62a6).

Like some people might have noticed I worked on some janitor tasks in the last weeks. Now every open Issue has a Type label (some 35 closed ones are still lacking: current state), a Priority label (some 24 closed ones are still lacking: current state) and countless tickets have gotten a Theme label. As of today we have 112 open and 181 closed Issues lacking a Theme label (current state). I probably opened everyone of them, but have no more clue on how to label the last ones. Therefore I call for support! I you have the corresponding user rights on our bug tracker, please consider working on before mentioned list - and when opening a new Issue, please remember to use at least the three important label categories and a milestone. Why is this label important? If bug reports arise on the forums, it's not always possible to check on Gitea for the existance of already opened Issues by using the search function. We have no semantic search function, so it's sometimes just luck to find something if the words are matching. Then the search by Theme labels really helps. But if tickets haven't such label, we might open duplicate Issues which leads to problems in the future like redundant work etc.

Currently we have 97 Issues without a Milestone listed on Gitea. The oldest one has been opened 4 years ago, but it seems to me that new Issues without a Milestone increased since the migration from Trac to Gitea. Shall all Issues without a Milestone be backlogged? If yes, I'd proceed.

There's already an issue for that: #7454 (Incorrect Unit Classifications for Idle Worker Hotkey).

I'm able to use the bug tracker right now.

I'd be banned as well ... Let's guess the server admins are already notified.

I'd like to bump this^ answer as well ...

I need to correct myself here: #7166 (Option to only allow signed mods for multiplayer games) by @Dunedan.

I like that suggestion and couldn't believe there isn't already an Issue for that on Gitea—at least, I didn’t get any positive search results.

Hello GufraMirtol and welcome to the community! Thank you for sharing this bug report with us! This includes Issue #8875 you already opened on Gitea.

Thank you for sharing your game experience and welcome to the community, Luigi! Unfortunately the game crashes sometimes. In the future, if you'd like to share your error logs with us, you can follow the instructions here. Maybe it's a problem with Athenian Civilization, but in my games with current game version I can garrison Archers on top of Walls. Would you like to explain the situation a bit more, please?

Thank you for reporting this defect! You'll find more information on that matter in the following thread, where we already got a similar report:

For the record

i.e.

merged

I really like the idea and would test it out in a (community) mod! May I request to have this and all related messages from 2026-03-23 moved to a proper thread?

While reading through the pinned thread I came to the position that it should be moved to 0 A.D. -> General Discussion. Guess most people will search it there ...

Lacking typeface may be related to sorry, no idea

Only 35 Issues themed AI open on Gitea: https://gitea.wildfiregames.com/0ad/0ad/issues?type=all&state=open&labels=20

Acknowledging that following call is not relevant to 1v1 and no-team matches: Don't forget the impact of Alliances with strong Team Bonuses.

Yesterday, Gitea user stydxm opened related Issue #8847.