Graham1

Why not? I wouldn't expect a barrack or stable to offer such a service. As the enemy, you take the chance of being healed or converted. It's just an idea.

How about making Temples a neutral zone for any player (only units, not siege) where ever you are on the battle field. For an enemy unit to be healed, they will need to go inside the temple whereas allies can still heal around it or inside. To make things more interesting, the owner of the temple is able to see who is garrisoned inside and if any enemy is identified, is able to convert them to his side.

This is the same issue I have on Fedora 37 (also posted on this forum). Apologies if this has already been mentioned (quite a bit to take in above). I have noticed that the area accessible via the mouse is more, if Fedora's default driver is used (in my case NV138). Nvidia's driver restricted the area quite a bit in that I couldn't get to some parts of the menu. For me, this is only an issue with Wayland, Xorg is fine. When in Wayland, pressing Alt+Tab makes the full screen accessible again, so at least there is a workaround.

Thanks for pointing out the obvious. . Please ban me for my stupidity but before you do, thanks for the fix .

Hi wraitii Please see attached short video. 1048968678_0ADError.webm

Tested with persist and hero garrison but still crashing with 0.26.2 I'm afraid.

No problem. Looking forward to the release.

I agree with what you have said above and was expecting a future release to fix this, so was surprised when the games started working with that release. Having tested again, I can confirm that since installing this mod, I had since changed the settings to conquest and had been playing future games with this setting. Having reverted back to hero, the error is re-occuring . I apologise for my post above as it is misleading and will delete that reply. Now, I'm gutted that I have to keep setting up each game again or I can just leave as conquest.

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.