jb said:
On my system and most of the teams is fine. However on a few systems we had to have to hack to get the mod to show up after it was activated by the mod menu. One we had to hack in the paths to the main UT2004.ini before our mut or gametypes would show up. Another we had place the game .Us in their main system dir before the games would show up. Then on another system our mods UCL file was getting over-writen by UT2k4 so by setting that to ReadOnly was the fix to get our mod to show up. So for most of our testing team it went fine. But I have at least 3 people that we had to hack with no good reason why.
And for the log are you saying after you activate your mod and play you get valid updates to the log file? I just checked any my loq stops after the mod was activated....
If you suspect a caching related issue, you can try removing the Suppress=RecordCache line from your .ini - this allows the cache manager's status logging to be written to the log, though it may or may not actually help you.
You can also try removing Suppress=DevSave to see exactly which file & sections variables are being loaded from (warning: serious log spam with this removed!!).
Additionally, you can use the console command 'dumprecords' (see ExtendedConsole for additional info) to see exactly which cache records are loaded during the game.
Notes:
CacheRecordPath is the path where .ucl files are located (i.e. where the game will look for .ucl files, and where the game will create .ucl files). The Paths array is where the caching system will look for valid packages to export. If you have modified the CacheRecordPath, but are still including the standard Paths= entries in your mod's ini file, then when your mod loads, the caching system will generate a new CacheRecords.ucl file in whichever directory is specified by CacheRecordPath...however, this CacheRecords.ucl file will only contain map entries. That is pretty inconvenient, but other than a pretty long first run startup-time for your mod, it shouldn't prevent any of your items from appearing in the GUI/webadmin lists.