Think this is a new one in UT3, been putting mine all in its own ini since its already rather long just for a small mutator pack. Personally I would recommend to people to put their muts together in packs to keep ini settings for that set in one common *.ini which is why I went the way I did so I didnt need a *.ini per *.u. Then again theres nothing saying you cant use the same config(ini) in all your *.u's to keep them together.
* This function can be used to parse the command line parameters when a server
* starts up
function InitMutator(string Options, out string ErrorMessage)
if (NextMutator != None)
Passing options can be done via batch or something, whatever the server admins use to execute the game then they can do $mutator=suchandsuch and the options. Not sure entirely how it works yet but its certainly cleaner than messing up UTGame.ini since its already larger than most of the uscript classes in file size.
I can understand what people are saying about easier server configuration but hey I prefer not to mess up epics ini's because in 2k4 Ive seen first hand what the joys of doing that does to the mod directory and other mods, actually breaking them fairly badly in somecases.
Im inclined to add options to the command line for the server if need be then it shouldnt matter what the config file says if its overriden, as I said Im still not sure on the details