[showdax]

Originally Posted by flyingmongoose I wrote it out seperately (at least cleaner) It'd be simpler keeping it within the <mod> directory because the <mod> is the base where most plugins and files are called from in the engine (last I checked)

Okay, so the mod pulls mod-specific files from the mod directory? What does that have to do with metamod? How is it simpler to have seperate installations of the same damn thing for each mod you have?

so you exec server.cfg it execs cfg/server.cfg or cfg/server.cfg and the exec /../../addons/metamod/plugin/cfg/whatever.cfg won't work, nor will ../../addons/metamod/plugin/cfg/whatever.cfg Try it.

You can't "exec" any files outside of the mod's cfg directory anyway, so your idea isn't going to work period. I never suggested cfg files should be outside of the mod directory, but where the files go and what the files are is up to the plugin and isn't necessarily prone to this limitation so it's irrelevant. I think it's pretty obvious that mod-specific configuration files should go in mod/cfg or perhaps mod/cfg/plugin, and non-mod-specific configuration files go in the metamod directory though.