I like this idea. Of course, you wouldn't want to use "*" as your wildcard character in a file name because it would cause all kinds of trouble. I'm not sure what a good candidate for the wildcard would be. Maybe "@" would work. Windows disallows "\/:*?"<>|" and linux would complain about the same. You could just not have a wildcard, but that would sacrifice some flexibility. With a wildcard you could even do things like:
[email protected] -- For all fy maps.
[email protected] -- For all fy maps starting with "joe."
Without a wildcard, you lose this flexibility, but you can still do what was originally described:
fy_.cfg -- would do all fy maps
(You would not want fy_joe.cfg to do all fy maps that start with joe, because you could not guarantee that fy_joe and fy_joecity should have the same cfg.)