Click the "Scan Folder" button (or type Alt+S or Ctrl+o) and browse to your test folder.
Put mods for testing into the test folder. Create a test folder as a subfolder of the Downloads folder. DON'T add acceptable conflicts to the Known Conflicts list Resolve any reported conflicts as necessary. Click the "SCAN" button - this will perform a full conflict scan on the Downloads folder. Click the "Downloads Folder." button (or type Alt+D or Ctrl+D) and browse to The Sims 2 Downloads folder. This makes checking for conflicts in newly added mods a lot easier. Version 1.1 and onwards of HCDU Plus permits mods in a specific folder to be checked for conflicts against themselves and those already in the Downloads folder. The HCDU Plus application is my attempt to remedy these. it reports conflicts at the resource (BHAV, BCON and STR#) level and not at the package level (it's usually enough to know that "InTeenimater_FlavorPak_BackToSchool.package" conflicts with "InTeenimater_B.package" without giving the eleven resources that conflict). it can't be told to ignore known conflicts (eg all the InTeenimater flavour paks). it can't be told which folder to start in. 
it doesn't consider STR#, OBJD, OBJf or other resources.The Hack Conflict Detection Utility (HCDU) is an essential tool when using mods, but it does have some shortcomings
0 kommentar(er)
