Error in Command-line-interface

Ask for help with ScummVM problems

Moderator: ScummVM Team

Post Reply
Krampus
Posts: 14
Joined: Sun Oct 04, 2020 10:45 am

Error in Command-line-interface

Post by Krampus »

Hello!
I am currently in the process of re-inputting my entire collection into ScummVM! I am also adapting the descriptions of the individual games to my own system! For this I edit the config.ini manually.

Recently, when starting ScummVM, regardless of the version used, I get the following messages in the command line interface: “WARNING: Game domain xxx already exists in ConfigManager!”

ScummVM starts normally and works perfectly. However, this circumstance is very annoying and delays the start!

Can you help me further or come up with a solution to the problem?
User avatar
eriktorbjorn
ScummVM Developer
Posts: 3580
Joined: Mon Oct 31, 2005 7:39 am

Re: Error in Command-line-interface

Post by eriktorbjorn »

Krampus wrote: Mon Jan 27, 2025 7:27 am Recently, when starting ScummVM, regardless of the version used, I get the following messages in the command line interface: “WARNING: Game domain xxx already exists in ConfigManager!”
The "domain" is the identifier within brackets and is supposed to uniquely identify one installed game. E.g. I have a Macintosh version of The Secret of Monkey Island. When I added that game to ScummVM, it got the domain name monkey-mac. I don't think it has to reflect the actual name of the game at all, because underneath it goes on to specify that the engineid is "scumm" and that the gameid is "monkey". So far, so good.

But I have a second Macintosh version of The Secret of Monkey Island. As far as ScummVM is concerned, they're the same game (even though the files are different). When I added that, it was assigned the domain name monkey-mac-1 with the same engineid and gameid as the first one. If I were to change the second one from "[monkey-mac-1]" to "[monkey-mac]" I would get a "WARNING: Game domain monkey-mac already exists in ConfigManager!"

So my guess is that you have two (or more) lines in your scummvm.ini that read "[xxx]".
Krampus
Posts: 14
Joined: Sun Oct 04, 2020 10:45 am

Re: Error in Command-line-interface

Post by Krampus »

That's exactly what I have - my collection contains several version numbers of different games (for example of KQ4SCI v1.000.106, v1.000.111, v1.003.006, v1.006.003 and v1.006.004)

The domains in the brackets are usually kq4sci, kq4sci-1, kq4sci-2 etc. This became too confusing for me with so many games, so I defined the domains according to my own system.
For example, kq4sci-dos-v1000106, kq4sci-dos-v1000111, etc.

Is there no way to suppress this? As I said, this is very annoying, as many of these warning messages appear when ScummVM is started and delay the start!
However, this does not affect the functionality of ScummVM or the games!
User avatar
criezy
ScummVM Developer
Posts: 980
Joined: Sat Sep 23, 2006 10:41 am
Location: West Sussex, UK

Re: Error in Command-line-interface

Post by criezy »

Using your own convention for naming the game domain (the string between brackets in the config file) is fine, as long as they remain unique.
The warning does affect the functionality of ScummVM since it indicates that part of your config file is ignored and not all games defined in it will be listed and usable in ScummVM. In short it indicates that you are using the same game domain name (e.g. [kq4sci-dos-v10000106]) multiple times. The only way to remove the warning is to rename (or remove) the duplicate game sections.

Note that having [kq4sci-dos-v10000106] and [kq4sci-dos-v10000111] is not an issue and should not trigger the waning since they are different names. Having the same engineid and gameid for multiple game domains is also not an issue. And in case that got you confused, note that what is called ID in the game options in ScummVM is not this gameid, but is actually the game domain.
Krampus
Posts: 14
Joined: Sun Oct 04, 2020 10:45 am

Re: Error in Command-line-interface

Post by Krampus »

Shame on me!

I looked through the config.ini again and discovered that numerous profiles were stored twice.....

After cleaning up the duplicate entries, there are no more error messages!

Thank you for your support!
Post Reply