Graham1

Thanks for the instructions but it looks like the community-mod 0.26.1 has resolved this issue. Settings had changed (hero to conquest) since 0.26.1 had been installed.

I would love to see a Star Wars take of 0 A.D. I remember playing Galactic Battlegrounds many years ago. I guess Disney wouldn't be too happy though.

I've noticed that the community mod is already available. Will this fix my issue (error on starting games) or do I need to wait for the next release?

Regarding the community mod, will it update itself (once downloaded) or do you need to update manually on each release?

I've not used mods before, so could you explain how these work. For example, this mod is going to fix an issue I'm having with the game crashing on startup. Are these mods configurable? What I am concerned about is that there seems to be a lot of changes going into this mod, but will this alter the original gameplay or does this just fix issues? (like a service pack).

Just tested. As soon as you re-enable and start a game again, it errors.

Thanks for the tips guys :). I can play 0 A.D. again :D.

Is that mod just for this issue or does it include the balancing mod that I have read elsewhere in the forum?

No problem, that's good. Multiplayer seems to play without any issues. Edit: Spoke to soon. This error occurs in Multiplayer too

Yes, when selecting "Single-player" and "Matches". There is also a matchsettings.mp.json. matchsettings.json

Now the RPM version of 0 A.D. is causing this error (updated from Gnome Software). It seems that closing and re-opening 0 A.D. causes the error. I have attached the mainlog.html. mainlog.html

No worries. Having re-installed the Flatpak version, I'm unable to reproduce this error now.

Fedora have just released an RPM for 0 A.D. a26, so I'm back on that at the moment. Luckily, the Flatpak files were still in the wastebasket, so I have attached mainlog.html. The map was Harbour. mainlog.html

This is the same error I am seeing. For me, it occurs after selecting "Single-Player" and "Matches". Previously, it occurred straight after selecting the same combination. 0 A.D. was installed from Flatpak (flathub) using Gnome Software. I then uninstalled and re-installed the RPM version (a25) which plays without any issues. After clearing out the remains of the Flatpak, I tried again (re-installed) and managed to play 1 game yesterday (as the Huns ). Just tried 0 A.D. now and got the same screen after select "Single-Player" and "Matches" again. I'm using a similar setup as valdiusryb, myself against the AI (x3) with no mods installed. Like yesterday, if you close 0 A.D., logoff or restart computer, this error appears straight away. The error message doesn't appear for long and scrolls off the screen quickly.

Thanks Stan. Didn't realise there was an appimage. Will use this until the RPM is updated.

Yes, noticed a snap setup for Fedora but really trying to get away from Snaps (and Flatpaks if I can). I prefer RPMs and DEBs but thanks for your reply.

Hi All Looking forward to playing the new version of 0 A.D. a26 on Fedora 36. Does anyone know when it will be released via RPM? Have tried the Flatpak version but it seems to be getting stuck during the game setup. Even after closing 0 A.D., logging out & restarting OS, this screen is still displayed :(. EDIT: Maybe it's just me but would have loved to have seen Hans's Island as one of the new maps. Some of you will know what I mean.

I think one of the civ's had/has this feature. If I remember, it was in one of those large round docks. It would seem more realistic to repair this way, rather than any villager/militia having the tools on them to do this.

How about being repaired inside the dock (similar to units).

Coming from Ubuntu, I've been used to Snap. I'm tempted by Flatpak and if like Snap, will work on any version of the Fedora so for a packager, this has to be better (if I understand this correctly).

I can confirm that the window issue is caused by wayland as I am unable to reproduce the problem under x11.

Which is the preferred method of installing 0 A.D? (rpm or flatpak). Does one release sooner than the other or better supported? Edit: Btw, the window issue doesn't occur in the flatpak version.

Looking forward to it.

You've got to be kidding . I'm a very basic user . Tbh, it's not really a big issue for me but just thought I would mention. Just a couple of clicks of the Windows keys resolved this issue.

Still the same I'm afraid.