incompatible or missing mods error is shown on every game start

[pat]

I am using Arch Linux and installed 0ad from pacman (0ad a26-6 and 0ad-data a26-1). When I start the game the 'Incompatible mods' warning is shown. In the 'Enabled Mods' section is one red mod with name 'This mod does not exist'. I disabled the mod and enabled the '0ad' mod from the 'Available Mods' section. I Saved the Configuration and restarted 0ad (quit and start) and the same message is shown again. The mod '0ad' is not enabled and 'This mod does not exist' is back again in the enabled section.

When I use the 'Save and Restart' button the game starts, but all configurations are empty and the game behaves wrong.

So, I think there must be some problem with storing my configuration. I reinstalled 0ad but the error persisted.

I had an old version installed, which worked without errors. After updating to version a26-6 the error occurred.

[pat]

incompatible mod message on startup

[phosit]

Hi pat

I also use a26-6 from the arch repo and don't have that problem.
The settings are stored in .config/0ad/config/user.cfg there should be a line like: mod.enabledmods = "mod public"

0ad might not have permission to write to that file or the path/your username does contain characters outside "Basic Latin".

[Stan]

Someone also reported this bug to me on Endeavor OS. He said downgrading the package worked for them. It seems that the last update of (Boost?) broke it.

[pat]

removing the ~/.config/0ad directory solved the error for me temporarly (until I start a match)

[phosit]

Interesting...

Is the line (mod.enabledmods = "mod public") in the user.cfg?
What happens if you start the game with pyrogenesis -mod=mod?

[pat]

The line was there before removing the directory, after that the file was created without the line. Adding the line (mod.enabledmods = "mod public") to ~/.config/0ad/config/user.cfg seems to have no effect

When running pyrogenesis -mod=mod, the same dialog appears (without the message at start), but there is no mod with name 'This mod does not exist'.
The '0ad' mod is not in the enabled section, but the available section.
The behavior is the same as when starting 0ad directly (configuration save is ignored, save and restart works for the restart, but does not save)

Removing the directory does not change pyrogenesis -mod=mod (it displays 0ad not as enabled).

Replying to phosit:

Interesting...

Is the line (mod.enabledmods = "mod public") in the user.cfg?
What happens if you start the game with pyrogenesis -mod=mod?

[phosit]

I can reproduce it now. But only with a26 and not with the SVN-version.

[Silier]

Running just pyrogenesis -mod=mod is not enough to start 0ad, it will only launch pyrogenesis engine.

You need to include "public" into the arguments for -mod

[phosit]

Replying to Silier:

Running just pyrogenesis -mod=mod is not enough to start 0ad, it will only launch pyrogenesis engine.

You need to include "public" into the arguments for -mod

I know. I tryed to find out if "mod" alone does started correctly (which it does).
If i run pyrogenesis -mod="mod public" there is the same error as if i run 0ad.

[phosit]

I oped a "task" at arch: ​https://bugs.archlinux.org/task/78474

[phosit]

It is fixed in version a26-7.

[Vladislav Belov]

I confirm, I'm not able to reproduce the issue with a26-7 as well.