578 replies to this topic

[Jarno Mikkola]

The BG1(the Icewind Dale should have that too) had a feature in the CHARNAME's character creation that set the pre-memorized spells so that when the game was started the clerics and mages had spells they had memorized and were able to cast them without the need to sleep at the in at the start of the game, the BGT has lost this feature, and so they start without any spells in the memory; now I was thinking that:
Would it be horrible stretch to make such a feature to be there ? I ask this here, cause there are several other TC's that can benefit from it too, and it would make the BGT's last night sleeping in the 3-kegs tavern ~[insert a fancy word].

[Ascension64]

Why don't you just RestParty() in a new game?

[Vonburen]

Everything worked great for a week or two, and then suddenly it started doing this whenever I use the TobEx Loader, (regular BG2 .exe works fine, though).



After I close that, this pops up:



Restarting my computer doesn't help, and I closed all my background programs, (Diskeeper, Steam, Pidgin).

Happened to me once or twice, I assume you're using Windows 7.
Try closing apps, disabling any antivirus, run the game under admin, if push comes to shove reinstall the game under x:\ instead of x:\Program Files.

I usually had this problem whenever I had two copies of BG2 running at the same time (don't ask me why)

[Ascension64]

TobEx beta 0013 released. Seems like a lot of changes but not really. As usual, check TobEx_ini.txt for more details.

New version information in a nutshell
TobEx beta 0013 sports some new hacks and some important installation changes. The core needs to be installed first (Setup-TobEx.exe). Core has all options disabled, but installs all supplementary files and will enable you to install the configuration mod (Setup-TobExConfig.exe). TobExConfig configures the entire INI and modifies supplementary files for tweaks, but is massively tedious (over 70 components). I can't say that this is convenient, but let's see how it goes. For mod compatibility, users will actually have to fully configure TobEx before installing dependent mods that check on TobExConfig components, meaning that TobEx should be installed and configured before installing dependent mods. However, if you run into issues in the game later, you can still manually edit TobEx.ini and disable hacks.

The other massive change is for people who don't like TobExLoader.exe. A TobExConfig component will patch BGMain.exe to load the DLL statically, removing the need for the loader. Should fix up issues with Classic Adventures and all.

That's pretty much it. Now some commentary on the change log itself.

Core changes
-Class/structure updates
-Added: Remove Dependency on TobEx Loader (probably the most significant change of all, no more reliance on TobExLoader.exe; modifies the EXE; if installed, you can still launch using TobExLoader.exe and shouldn't cause any problems since you cannot LoadLibraryA() twice)
-Condensed WeiDU components for more convenient installation
-Split core and configuration installations (this will stuff up BWP all over again; I am not entirely convinced this hack-per-component thing really is the most convenient, but hey, here you can have a go and give feedback)

Tweaks
-Added: Allow All Races to Dual Class
-Added: Dialogue Greeting Subtitles (somewhat in the style of BG1, but the text shows up like dialogue at the moment)

Effects
-Added: Apply Effect Item Fix
-Added: Apply Effect Itemtype Fix
-Added: IWD Style Cat's Grace Dexterity Mod (thanks to FlameWing)
-Added: IWD Style Mage Spell Slots Mod (thanks to FlameWing)
-Added: IWD Style Priest Spell Slots Mod (thanks to FlameWing)
-Added: IWD Style Strength Mod (thanks to FlameWing) (since the effect opcode params are reserved for IWD and I got sent code, it was easy enough just to pop FlameWing's stuff in)
-Added: Remove Projectile Mod (the externalisation beyond CLEARAIR.2DA)

Engine bugs
-Added: Disintegrate Fix (thanks to Avenger for the tip)
-Added: IWD Animation Attack 3 Fix (thanks to Avenger for the tip)

Beta stuff
-Added: Disable Duplicate Effect Stacking (this globally stops identical effects being applied, which probably doesn't have much use at the moment)

Debugging
-Added: Custom Dialogue Bar Buffer Size
-Added: Log Dialogue Bar
-Added: Log File Mode (essentially, an option to overwrite (default) or append to, the latter used to the default but can bloat up the log a bit)
-Added: Verbose Logging (not much yet, but would help me if the people with difficulties with scrollbars posted their logs after using the scroll bars and this option)

Existing hack fixes
-Externalise Class-Race Restrictions: Fixed a bug where the standard gnome and dwarf multi-class options were swapped
-Magic Resistance Mod Fix: Fixed a bug with non-instant/limited timings (timing != 1) using increment (param2 = 0) type
-Scrollable Level Up Mage Spell Selection: Fixed a bug with selecting high-level abilities

[Igneous]

TobEx beta 0013 released.

Thanks, Ascension64.

What's the rationale behind splitting the core and config installations? Is it a way to keep needed changes to game resources self-contained to their respective hacks? I suppose it'd allow dependent mods to detect them individually, too.

The setup process is, indeed, massively tedious. It seems most hacks don't need to be installed via WeiDU this way, though, correct? Only 'Remove all race-class restrictions' and 'Remove Dependency on TobEx Loader' seem to require it.

One very small thing I've been meaning to report. Regarding the soundset subtitles, I'm pretty sure the .tra reference @4166 should be "Ooh, you wily bastard", not "Ooh, you whiny bastard." (Makes more sense that way, too. It's the critical miss sound.)

Edited by Igneous, 29 December 2010 - 06:41 PM.

[Ascension64]

It allows mods to check which hacks are enabled via WeiDU. It was requested by modders for this purpose. If WeiDU implemented some equivalent of C++ GetIniValue() then it would simplify things a bit.

[the bigg]

It allows mods to check which hacks are enabled via WeiDU. It was requested by modders for this purpose. If WeiDU implemented some equivalent of C++ GetIniValue() then it would simplify things a bit.

I use FILE_EXISTS ~tobex.ini~ && FILE_CONTAINS ~tobex.ini~ ~Configurable Backstab Every Hit=1~ in tb#tweaks (although REQUIRE_COMPONENT is faster and slightly more reliable). One component per tweak is mostly for ease of use: you can [R]einstall tobexloader without losing your .ini selection and lusers won't complain that the mod doesn't work because they forgot to add required files for each tweak.

Edited by the bigg, 30 December 2010 - 05:07 AM.

[Ascension64]

If it makes things a little easier, I may be able to add the 'recommended' and 'compatibility' installs again to the config so that you don't have to go through all that tedium.

Update: WeiDU gets really angry if I AT_EXIT --force-install-list and try to AT_UNINSTALL --force-uninstall-list for a quick config component. Any way to make this friendlier, or an alternative to quick install/uninstall components via another component?

I have currently grouped the quick configs in one group and the manual config in another. The users is implored not to show both groups in an installation.

Edited by Ascension64, 30 December 2010 - 10:48 PM.

[the bigg]

Code plz? Offhand, I think you want AT_UNINSTALL_EXIT rather than AT_UNINSTALL. However, this is a very flimsy solution: if the user has installed some other mod on top of TobEx and then re-installs TobEx (for whatever reason), the AT_UNINSTALL_EXIT will then kick in (removing ToBExConfig and re-installing again all mods) and then TobExConfig will be re-installed as the last mod. Aside from wasting people's time, mods that detect TobEx will not find it when being re-installed and thus not install components and/or mis-install.

Qwinn does it like this in PST-UB:

BEGIN ~Do you want to install all recommended tweaks?~
FORBID_COMPONENT setup-mymod.tp2 100
FORBID_COMPONENT setup-mymod.tp2 101
FORBID_COMPONENT setup-mymod.tp2 102

INCLUDE ~mymod/lib/component100.tpa~
INCLUDE ~mymod/lib/component101.tpa~
INCLUDE ~mymod/lib/component102.tpa~

BEGIN ~Component 100~
DESIGNATED 100
FORBID_COMPONENT setup-mymod.tp2 0
INCLUDE ~mymod/lib/component100.tpa~

BEGIN ~Component 101~
FORBID_COMPONENT setup-mymod.tp2 0
INCLUDE ~mymod/lib/component101.tpa~

BEGIN ~Component 102~
FORBID_COMPONENT setup-mymod.tp2 0
INCLUDE ~mymod/lib/component102.tpa~


BEGIN ~Not-recommended Component 103~
INCLUDE ~mymod/lib/component103.tpa~

However, doing this means that you lose the modder advantage of writing REQUIRE_COMPONENT ~setup-tobexconfig.tp2~ "Tweak X" (they actually need REQUIRE_PREDICATE (MOD_IS_INSTALLED ~setup-tobexconfig.tp2~ "Tweak X") OR (MOD_IS_INSTALLED ~setup-tobexconfig.tp2~ "All Tweaks") OR ... or you could drop a marker file for each component in the override and let mods write REQUIRE_FILE). Of course, the user advantages (which are probably more important than modder convenience) are still there.

[Ascension64]

I am doing something stupid:

BEGIN ~Some quick config~
AT_EXIT ~Setup-TobExConfig.exe --force-install-list <list>~
AT_UNINSTALL ~Setup-TobExConfig.exe --force-uninstall-list <list>~

The AT_UNINSTALL stuffs everything up. But if I don't have it, all the mods installed by --force-install-list will get re-installed if you uninstall the 'Some quick config'. If I use AT_UNINSTALL, everything does get uninstalled, but WeiDU chucks a psycho, and then doesn't uninstall properly the 'Some quick config' component. Obviously, I shouldn't be doing something like this.

So, is there a way to have a config in the same tp2 that you can install other components, such that when you uninstall the config, the other components are uninstalled and not re-installed?

[the bigg]

As I've said, take a look at AT_UNINSTALL_EXIT rather than AT_UNINSTALL.

That said, the closest to what you're trying to do might be PST_UB's tp2 structure.

[Ascension64]

Cool, seems to work a bit better - although the uninstall of the quick config A (which includes B, C, D) causes all the subsequent components (B, C, D) to be installed again, and then AT_UNINSTALL_EXIT uninstalls those components (B, C, D).

FORBID_COMPONENT won't work for me because I use AT_EXIT to install the other components. This does not remove the modder advantage of REQUIRE_COMPONENT because both the config (A) and other components (B, C, D) show up on WeiDU.log. The only glitch is the above and what you mentioned.

Edited by Ascension64, 01 January 2011 - 03:04 PM.

[Mike1072]

If you want WeiDU.log entries to show up properly, it might be easiest to just package a .bat that would --force-install-list the recommended components (or a more advanced one that asks "do you want to install group X, group Y, or do it manually?").

[Ascension64]

I considered the .bat option. I would need to enlist some Linux expertise to make a said-OS-compatible version. If we can solve this by WeiDU, it would be easiest. My method does shows the WeiDU.log entries correctly, but it would have re-install glitches.

[Ascension64]

TobEx beta 0014 released. Fixed the crashes and we have a quick config you can try.

Change log:
-Custom Dialogue Bar Buffer Size: Fixed a dialogue crash bug when this hack was disabled (set to 0)
-Log Dialogue Bar: Fixed a crash bug when trying to log text larger than 256 characters
-Soundset Subtitles: Corrected a typo in the FEMALE2 soundset subtitles
-Modified config installation to allow quick and manual configurations
-Reviewed TobEx_ini.txt

[Ascension64]

I don't know if someone reported this before me, but with the "dipel formulae fix" active, in my game dispel magic and remove magic always work, no matter what. I have version 12, but i checked the revision history of version 14 and i didn't find any mention of this bug.

I cannot confirm this. Works as intended with vanilla TobEx. Are you using a mod that modifies the way that Dispel Magic works? You could test this by CLUAConsole'ing in a very high level creature (such as Sendai, for example) and using some low-level char to try and dispel some of the buffs that she puts on.

[Ascension64]

I'm not familiar with the exact details of Spell Revisions, but whichever you installed TobEx doesn't make any kind of difference at all. You can try disabling the hack in TobEx.ini and see if it fixes things.