EmperorFool
Deity
Both of these problems are likely caused by BUG not finding its "BUG Mod.ini" file. I have just committed what should nail down both of these problems.
SVN has this new code, and I'd love for people to try it out. It no longer relies on the Windows registry to locate the install folder or the .ini file. Specifically, it will now search five directories for .ini files:
Note that it will search the two mod folders above even if you are not playing BUG as a mod. There is no way to tell whether or not the mod was loaded as such or is in CustomAssets. However, I can't imagine this being a problem. Besides, the first .ini found is taken, from top to bottom in the above list.
If you don't want to grab the latest code from SVN, we'll be doing a release in about two weeks.
SVN has this new code, and I'd love for people to try it out. It no longer relies on the Windows registry to locate the install folder or the .ini file. Specifically, it will now search five directories for .ini files:
- C:\Documents and Settings\<user>\My Documents\My Games\BUG Mod
- C:\Documents and Settings\<user>\My Documents\My Games\Beyond the Sword\Mods\BUG Mod
- C:\Documents and Settings\<user>\My Documents\My Games\Beyond the Sword
- <install-folder>\Mods\BUG Mod
- <install-folder>
Note that it will search the two mod folders above even if you are not playing BUG as a mod. There is no way to tell whether or not the mod was loaded as such or is in CustomAssets. However, I can't imagine this being a problem. Besides, the first .ini found is taken, from top to bottom in the above list.
If you don't want to grab the latest code from SVN, we'll be doing a release in about two weeks.