Keep in mind when we create a custom config valid for several different game ID's we still need to create a specific config file for everyone of them... because all the databases we use (managunz, webman, etc) works with individual config files that uses the game ID in the filename
Is happening since beginning, when we was able to extract the official configs from GX and SOFT emus there was a bunch of them that are identical, the only difference is the filename
And since that point has been added some more custom configs that are also identical to others
This is a problem we never worried about, is a bit messy and is not efficient, the solution is to create a single "config database" file using a structure similar than the official used inside GX and SOFT .self's
The concept is very easy... we need to separate the "game ID" and the "config data" in 2 different tables... this way we could create "links" in bewteen multiple "game ID" to the same "config data"
But.... this is going to "obfuscate" the configs itself... with this i mean they are going to become less "human readable"

You know... when you get used to how the config structure works and some config commands you start recognizing them just by looking at the hex view (and with the help of some documentation in psdevwiki), is what we use to do in this thread... someone posts a config and others are able to "review it"
The point is... is we create some kind of database with them in a single file we are not going to be able to "play around" with them so easilly :P
Anyway... i think is better to add the game ID always at the end of the config, especially when this configs are added to the databases we are using actually
But when we are talking about them in forums is not needed though, it can be removed to simplify it
Emulator read bytes after 00 00 00 00...
...after 00 00 00 00 there is multidisc support config in some games.
Really ?

i never saw a config like that