Each of the CMD lines in Select.txt gets written into Tmp.bat (replacing whatever was there before) one by one and executed. So it was undoubtedly something different at the time.
The IF EXIST in the line you pasted is a condition for the rest of that line. So no harm done. However, we could add some dependency checks to skip running more of those types of batch commands unnecessarily, just to clean up the installation a bit more.
I've found some code that I'm suspicious might cause a random hang, but I haven't been able to reproduce the problem locally. I will keep looking into this over the next few days.
BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)
BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)
To say more, baldur.bcs would be required - however those warnings appear harmless, mostly DVs that are not in your game or other resources that do not trigger. Should not cause any issue in your game. (I have more than 300 warnings in my baldur.bcs but no issue so far.)
Hey people, I just got this error in my current installation, how can I fix it, because I really want to use Randomised Items, Weidu's version:
Is this with Item Randomiser v7 ?
If ... well wait until it gets updated.
Yep, Jarno Mikkola. my Mega Mod FAQ. Use of the BWS, and how to use it(scroll down that post a bit).
OK, desert dweller, welcome to the sanity, you are free to search for the limit, it's out there, we drew it in the sand. Ouh, actually it was still snow then.. but anyways.
I'll update the BWS link to use the new version of Item Randomiser for new installs; for her current install, Dady can use the workaround of moving amtgen01.cre unless the differences between the versions seem significant enough to warrant a full reinstall of that mod.
BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)
BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)
Dady, find amtgen01.cre in the override folder and move it out temporarily, install item randomiser, then move it back in.
Thank you very much for the help and the quick reply.
I'll update the BWS link to use the new version of Item Randomiser for new installs; for her current install, Dady can use the workaround of moving amtgen01.cre unless the differences between the versions seem significant enough to warrant a full reinstall of that mod.
How can I reinstall/update the mod, since I continued through the mod and finished my BWS installation, is there anyway to update it? Or can I just download the latest version and install it again on my own without using BWS?
Hey people, I just got this error in my current installation, how can I fix it, because I really want to use Randomised Items, Weidu's version:
Is this with Item Randomiser v7 ?
If ... well wait until it gets updated.
I really don't know... I just used the version BWS provided me with, but I think it's version 7.
You can't install it at the end of the installation if it was already installed in the middle of the installation. Since you already finished the installation, you'd have to unwind all the way back to Item Randomiser to make any changes to it. It would be easier to just start over with a fresh BWS install if you wanted to do that, but it is probably not worth it for your current game because there is no game-breaking problem with the version you currently have installed.
BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)
BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)
* Mods: Updated Item Randomiser download link to latest dev release (7.160110)
* BWS: Select-Tree.au3 - minor bug fixes
* BWS: Depend.au3 - Added validity check for whitespace in rules (shouldn't be any)
* BWS: Implemented support for dependency rules of the form D:xxx|yyy (without any '&') -- at least one of the listed mods/components MUST be installed, if any are in Select.txt for current game type
* Added new dependency rule -- either Lolfixer #4 or Miloch's Creature Fixer must be installed
* BWS: All dependency and conflict rules can now be right-click ignored, but rules that are not marked as notice/warning ('CW' or 'DW' in Game.ini) will require two things: click-properties must be set to Expert (under Options menu at the top left of the selection-tree view) and user must click the "yes" button on the confirmation message box
BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)
BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)
* Mods: Updated Item Randomiser download link to latest dev release (7.160110)
* BWS: Select-Tree.au3 - minor bug fixes
* BWS: Depend.au3 - Added validity check for whitespace in rules (shouldn't be any)
* BWS: Implemented support for dependency rules of the form D:xxx|yyy (without any '&') -- at least one of the listed mods/components MUST be installed, if any are in Select.txt for current game type
* Added new dependency rule -- either Lolfixer #4 or Miloch's Creature Fixer must be installed
* BWS: All dependency and conflict rules can now be right-click ignored, but rules that are not marked as notice/warning ('CW' or 'DW' in Game.ini) will require two things: click-properties must be set to Expert (under Options menu at the top left of the selection-tree view) and user must click the "yes" button on the confirmation message box
Is there any link to where Expert install is now defined - or is there any file in the BWS download where I can find the definition?
Do you mean that you want a complete list of which mods and components are classified as Expert?
It is determined by a combination of all lines in Select.txt containing the pre-selection bit sequence ;0001; and additionally every component of any mod whose ini file in Config\Global contains 'Type=E'. The latter overrides the pre-selection bits in Select.txt.
BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)
BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)
Do you mean that you want a complete list of which mods and components are classified as Expert?
It is determined by a combination of all lines in Select.txt containing the pre-selection bit sequence ;0001; and additionally every component of any mod whose ini file in Config\Global contains 'Type=E'. The latter overrides the pre-selection bits in Select.txt.
No. I meant what was the final outcome of a recent discussion about criteria to say a mod is expert (testing was not agreed as category if I remember well).
With the latest feature there will now be a new class of expert installs, that are created by overwriting known incompatibilities and thus mixing it with installations that contain expert mods.
If I find some issue in an expert mod I can report it to the modder or the forum and it may be corrected.
If I find issues because i have ignored the warnings about known incompatibilities - i assume that is my very own problem and I cannot expect any assistance from the mod makers of the mods involved in this case.
If I find issues because i have ignored the warnings about known incompatibilities - i assume that is my very own problem and I cannot expect any assistance from the mod makers of the mods involved in this case.
I wonder if BWS could add some statement on the prominent place in WeiDU.log that this certain install was done with safety overridden? Could reduce irritation of mod developers and streamline debugging.
If I find issues because i have ignored the warnings about known incompatibilities - i assume that is my very own problem and I cannot expect any assistance from the mod makers of the mods involved in this case.
I wonder if BWS could add some statement on the prominent place in WeiDU.log that this certain install was done with safety overridden? Could reduce irritation of mod developers and streamline debugging.
Good idea, this would be really helpful, otherwise there could be a lot of wasted effort chasing ghosts.
Good idea Creepin. Already I coded it so that expert-ignored rules like will be logged to BiG World Debug.txt in BWS\Logs... Which should also be included automatically in the Upload.7z.
Roxanne, I wrote a definition of expert mods in the "why are these mods expert mods?" thread. Haven't updated it recently.
BiG World Fixpack (community collection of mod fixes and compatibility patches, with user-friendly cross-platform script)
BiG World Setup (tool to automate best-practice installation of Infinity Engine mods on Windows, with conflict analysis)
Good idea Creepin. Already I coded it so that expert-ignored rules like will be logged to BiG World Debug.txt in BWS\Logs... Which should also be included automatically in the Upload.7z.
Roxanne, I wrote a definition of expert mods in the "why are these mods expert mods?" thread. Haven't updated it recently.
Thanks - I knew it was somewhere but could not find it.
* BWS: Added a couple of newlines to BWS GUI messages in Config\Translation-EN.ini
* BWS: Select-Helper.au3 - Fix typo in expert/warning mods message box that could result in the same mod being listed more than once
* BWS: Install.au3 - Disabled WeiDU quick-logging so incomplete installations still show components names in WeiDU.log
* BWS: Install.au3 and Depend.au3 - Setup-BWS.tp2 will add lines to WeiDU log with following information as appropriate:
1. If user chose Expert click-properties, this will be logged (this might not be logged if BWS was restarted)
2. If user ignored any rules (by right-click, ignore this problem), each rule will be logged (rules with DW or CW prefix indicate notice/warning)
3. If user selection included any Expert mods or components (MODNAME.ini Type=E or component pre-selection bits = 0001 in Select.txt), each will be logged