252 replies to this topic

[dreamer2007]

Okay, thank you . So, it seems that if I want to play with the new characters, I am forced to play without BWP .

[The Imp]

Okay, thank you . So, it seems that if I want to play with the new characters, I am forced to play without BWP .

Well you can still use the BWS to do a BG1:EE compilation... but that's it.

[Jenavee]

Some additional issues:

Mages can put a proficiency point into any weapon, yet all the mages kits cannot use any weapon.

Wild Mages revert back to vanilla mage on game start.
"W_MAGEsw=2" appears over my character's head a an unkitted mage at game start.

 

Some research led me to this:
http://www.shsforums...dritch-phantom/
 

I'm fairly certain this is the same/similar issue I'm having and that Psionics Unleashed is the culprit. 

Also jc whats the mod that asks with a dialogue at the very beginning what difficulty you want from easiest to insane? And what does it effect, because it doesn't move the usual difficulty slider.

This sounds similar to what I've reinstalled three times now for. My Wild Mage PC keeps being created with kit 0x41130000 (Unknown) instead of 0x00008000 (Wild Mage). Oddly enough, when I Ctrl+Q'd Rhialto into my party, he had L30 Wild Mage (instead of Mage, like I was showing), yet his kit ALSO revealed itself as kit 0x41130000 (Unknown) in Shadowkeeper. This means no Wild Mage (not even Rhialto) can use ANY of the Wild Mage-only gear, and also limits the 'Wild' Mage from certain Mage-only items. I'll try booting Psion class from Fighters to see if it'll fix it, then, or make a separate install with just WMA + Psion mods to test it.

 

EDIT: Half-solving locally for now by editing Wild Mage-only gear to be usable by this 'kit'.

 

If anyone cares to double-check my logs, just lemme know.

Edited by Jenavee, 19 December 2013 - 09:24 AM.

[The Imp]

This sounds similar to what I've reinstalled three times now for. My Wild Mage PC keeps being created with kit 0x41130000 (Unknown) instead of 0x00008000 (Wild Mage).

The reason for this is that one of the mods cheeses the kit.ids file.... the Psion kit making mod is one of them... I noted this and it will be fixed in the next version after the v0.3

[Jenavee]

Oh, awesome! Does this mean a reinstall without Psion will fix it completely?!

 

Edit: OH, you just answered the other question I've been trying to figure out all day, which file the Kits are in. Knew there was a reason I loved you so much, lmao: the almighty Imp has all answers, even if he doesn't know your question yet

 

Edit Edit: Looks like it borks Barbarians, too, now that I'm examining the Kit.ids

 

Edit Edit Edit: Alrighty, looking everything over, I'm gonna yank Psion + Refinements (who the hells wants HLAs anyway) and change up a couple options I'd borked up in my last install (like getting changed to 9 rep after leaving Candlekeep: my poor Paladin...last thing I want is to lose status upon leaving, lmao...and I can always cheat some gold to lower my rep if needed later at Friendly Arm Inn).

Edited by Jenavee, 19 December 2013 - 10:49 AM.

[dabus]

Just a note: BWP checks and possibly adjusts Action, Animate, Stats and Kit.ids every time it installs something.

If you want to know when something gets twisted, adjusting that process to check if there's some change to the kit.ids  would be the best thing to track things down, wouldn't it?

[Jenavee]

A good idea, and one I hadn't been able to consider earlier, as I was having no luck googling where the Kits were (or at least the kit list and values). Guess I should figure out how the BWP does that then, lmao. Mebbe I'll work on it while it's reinstalling.

Edited by Jenavee, 19 December 2013 - 11:51 AM.

[The Imp]

Just a note: BWP checks...

Nope, you mean either the BWS or BWInstall.bat, as the BWP is the project which is not installable by itself as... ... I would not recommend either of the installers to actually do this as the changes are meant to do good and not going with the mainstream can have cheesing effects all over. And yes, the install errors actually tell us that things go wrong and thus correcting them at the source is the best option. AKA, the BWFixpack can patch the .tp2 code to not screw up the install.

What you are saying sounds very much like an automated function that if not done correctly will lead to very much to the situation above, which could be corrected with better at the source... aka the Refinement ALWAYS block, instead of this giant idiozity:

    // Corrections to KIT.IDS. Translates in WeiDU the corrections originally
    // made by Dyara	
COPY_EXISTING     ~KIT.IDS~                  ~override/KIT.IDS~
		REPLACE_TEXTUALLY ~0x00004000 TRUECLASS~     ~0x4000 TRUECLASS~
		REPLACE_TEXTUALLY ~0x00000001~         ~0x4001~
		REPLACE_TEXTUALLY ~0x00000002~         ~0x4002~
		REPLACE_TEXTUALLY ~0x00000004~         ~0x4003~
		REPLACE_TEXTUALLY ~0x00000008~         ~0x4004~
		REPLACE_TEXTUALLY ~0x00000010~         ~0x4005~
		REPLACE_TEXTUALLY ~0x00000020~         ~0x4006~
		REPLACE_TEXTUALLY ~0x00000040~         ~0x0040~
		REPLACE_TEXTUALLY ~0x00000080~         ~0x0080~
		REPLACE_TEXTUALLY ~0x00000100~         ~0x0100~
		REPLACE_TEXTUALLY ~0x00000200~         ~0x0200~
		REPLACE_TEXTUALLY ~0x00000400~         ~0x0400~
		REPLACE_TEXTUALLY ~0x00000800~         ~0x0800~
		REPLACE_TEXTUALLY ~0x00001000~         ~0x1000~
		REPLACE_TEXTUALLY ~0x00002000~         ~0x2000~
		REPLACE_TEXTUALLY ~0x00008000~         ~0x4007~
		REPLACE_TEXTUALLY ~0x00010000~         ~0x4008~
		REPLACE_TEXTUALLY ~0x00020000~         ~0x4009~
		REPLACE_TEXTUALLY ~0x00040000 MAGESCHOOL_GENERALIST~   ~0x4000 MAGESCHOOL_GENERALIST~
		REPLACE_TEXTUALLY ~0x00080000~         ~0x400B~
		REPLACE_TEXTUALLY ~0x00100000~         ~0x400C~
		REPLACE_TEXTUALLY ~0x00200000~         ~0x400D~
		REPLACE_TEXTUALLY ~0x00400000~         ~0x400E~
		REPLACE_TEXTUALLY ~0x00800000~         ~0x400F~
		REPLACE_TEXTUALLY ~0x01000000~         ~0x4013~
		REPLACE_TEXTUALLY ~0x02000000~         ~0x4014~
		REPLACE_TEXTUALLY ~0x04000000~         ~0x4015~
		REPLACE_TEXTUALLY ~0x08000000~         ~0x4010~
		REPLACE_TEXTUALLY ~0x10000000~         ~0x4011~
		REPLACE_TEXTUALLY ~0x20000000~         ~0x4012~
		// Added by the_bigg, further corrections by Littiz. Some installations have a
		// different (and still wrong) version of KIT.IDS, so they require a different patch:
		REPLACE_TEXTUALLY ~0x00004000 BARBARIAN~         ~0x40000000 BARBARIAN~
		REPLACE_TEXTUALLY ~0x0000 BARBARIAN~         ~0x40000000 BARBARIAN~
		REPLACE_TEXTUALLY ~0x00008000 WILDMAGE~         ~0x80000000 WILDMAGE~
		REPLACE_TEXTUALLY ~0x0000 WILDMAGE~         ~0x80000000 WILDMAGE~
		REPLACE_TEXTUALLY ~0x40010000~ 	       ~0x4001~
		REPLACE_TEXTUALLY ~0x40020000~ 	       ~0x4002~
		REPLACE_TEXTUALLY ~0x40030000~ 	       ~0x4003~
		REPLACE_TEXTUALLY ~0x40040000~ 	       ~0x4004~
		REPLACE_TEXTUALLY ~0x40050000~ 	       ~0x4005~
		REPLACE_TEXTUALLY ~0x40060000~ 	       ~0x4006~
		REPLACE_TEXTUALLY ~0x00400000~ 	       ~0x0040~
		REPLACE_TEXTUALLY ~0x00800000~ 	       ~0x0080~
		REPLACE_TEXTUALLY ~0x01000000~ 	       ~0x0100~
		REPLACE_TEXTUALLY ~0x02000000~ 	       ~0x0200~
		REPLACE_TEXTUALLY ~0x04000000~ 	       ~0x0400~
		REPLACE_TEXTUALLY ~0x08000000~ 	       ~0x0800~
		REPLACE_TEXTUALLY ~0x10000000~ 	       ~0x1000~
		REPLACE_TEXTUALLY ~0x20000000~ 	       ~0x2000~
		REPLACE_TEXTUALLY ~0x40000000 TRUECLASS~ 	       ~0x4000 TRUECLASS~
		REPLACE_TEXTUALLY ~0x40000000 MAGESCHOOL_GENERALIST~   ~0x4000 MAGESCHOOL_GENERALIST~
		REPLACE_TEXTUALLY ~0x40070000~ 	       ~0x4007~
		REPLACE_TEXTUALLY ~0x40080000~ 	       ~0x4008~
		REPLACE_TEXTUALLY ~0x40090000~ 	       ~0x4009~
		REPLACE_TEXTUALLY ~0x400A0000~ 	       ~0x400A~
		REPLACE_TEXTUALLY ~0x400B0000~ 	       ~0x400B~
		REPLACE_TEXTUALLY ~0x400C0000~ 	       ~0x400C~
		REPLACE_TEXTUALLY ~0x400D0000~ 	       ~0x400D~
		REPLACE_TEXTUALLY ~0x400E0000~ 	       ~0x400E~
		REPLACE_TEXTUALLY ~0x400F0000~ 	       ~0x400F~
		REPLACE_TEXTUALLY ~0x40130000~ 	       ~0x4013~
		REPLACE_TEXTUALLY ~0x40140000~ 	       ~0x4014~
		REPLACE_TEXTUALLY ~0x40150000~ 	       ~0x4015~
		REPLACE_TEXTUALLY ~0x40100000~ 	       ~0x4010~
		REPLACE_TEXTUALLY ~0x40110000~ 	       ~0x4011~
		REPLACE_TEXTUALLY ~0x40120000~ 	       ~0x4012~
		REPLACE_TEXTUALLY ~0x401F0000~ 	       ~0x401F~
	BUT_ONLY_IF_IT_CHANGES

All that is needed is this:

COPY_EXISTING ~kit.ids~ ~override~ //Kit fixes (CamDawg & the bigg ETC.)
/* snip */
  REPLACE_TEXTUALLY ~.*\bBARBARIAN\b~			  ~0x40000000 BARBARIAN~
  REPLACE_TEXTUALLY ~.*\bWILDMAGE\b~			   ~0x80000000 WILDMAGE~
BUT_ONLY
APPEND ~kit.ids~ ~0x4000 TRUECLASS~ UNLESS ~\bTRUECLASS\b~
APPEND ~kit.ids~ ~0x40000000 BARBARIAN~ UNLESS ~\bBARBARIAN\b~
APPEND ~kit.ids~ ~0x80000000 WILDMAGE~ UNLESS ~\bWILDMAGE\b~

For every mod that tries to cheese the kit.ids file.

Yep this solves the original mod install without the Throne of Bhaal -situation which is the sole reason why the mods introduce the whole freaking thing in the first place.

And yes, I posted about this in the Refinements forum too, but no one replied.

[Jenavee]

Well, if they refuse to acknowledge and fix it, push a hotfix through for the fixpack? Then it'll be fixed whether they like it or not, and they'll be left, as they say, gnawing their boots in impotent frustration. Or, hells, why not just make a general fix that can be thrown into a BWP install at a certain time manually or something, or replaced by hand in their scripts? I'd try it myself but I'm in the middle of a reinstall and gotta cut the grass.  

 

Edit: Gah! Death and the dark, I just realized that I'd started the BWP install on Minimum (since I always load my selections from a custom, saved file). Now I gotta restore my install and start all over...

 

Edit Edit: FOR THE LOVE OF THE LIGHT! AAAAAARGH! Bloody BiG World Setup earlier borked mid-restore due to Shadowkeeper being opened, see... which crashed the GUI but kept on randomly deleting things in my BG II folder.... among which was several gig's of downloaded mods!

Edited by Jenavee, 19 December 2013 - 12:37 PM.

[dabus]

It's not random and I doubt having files opened would have any effect but Shadowkeeper-files that didn't get deleted.

The restore asks you:

This will affect all files that were created after the backup.

Should these files be deleted or moved?

 

So what it does is deleting stuff from data-dir by comparing files to a predefined list.

The original files/folders present in your Backup-folder will be "listed" and the possibly modified files/versions will be removed from the BG2-folder .

During Backup, a list of files that were present in the BG2-root-folder is saved as BWS_Backup.ini. into the Backup-folder.

The restore gets it now. There are a few exceptions but every file / folder that is missing in that list will be removed from your root-folder.

Then it copies the files from your Backup-folder to your BG2-folder.

 

So if I had to pick, I'd guess that those files were either put in after creating the backup or something really screwed up.

Haven't heard about those things lately though.

[Jenavee]

Looking at my logs, I think I know what happened: I'd had to completely reinstall BG II / ToB from scratch, along with BiG World Setup (after I moved my downloaded mods folder). Then I must have run the setup on Minimum by accident instead of using my custom selection, which meant...when I hit remove the unneeded mods, it booted everything non-minimal.

 

Edit: Hadn't been literal about that 'random' earlier, either. I'd meant more that by the time I managed to find and crash all related processes, it'd erased enough from my BG2 installation that I couldn't restore the uh...um........ my brain just stopped functioning properly.... oh! Right, Shadows of Amn / ToB clean install files. Hence why I had to uninstall what was left and reinstall it all from scratch.

Edited by Jenavee, 19 December 2013 - 03:30 PM.

[dabus]

Ok. Can't help myself but being fussy sometimes. And as you said, you can look at the logs what happened. And maybe you could use move before deleting the files manually to prevent those things. I did shoot myself in the foot more than a few times while creating the script, so I can understand your feelings though.  

Edited by dabus, 19 December 2013 - 03:51 PM.

[Jenavee]

Heh. Actually, Shadowkeeper was holding a bunch of ITM's in memory since I'd been searching through them while modding up the finalized ITMs with NearInfinity, hence why BWS was complaining about the files being in use.

 

...urk. Another error, this one a new one from the past two installs. Looks like Mur'Neth's conflicting with BG1NPCs now; can't find the dialogue between Edwin and Mur'Neth, so Mur'Neth won't install. On the bright side, I'd only planned on killing Mur'Neth anyway....not much loss there.

[Lollorian]

All that is needed is this:

COPY_EXISTING ~kit.ids~ ~override~ //Kit fixes (CamDawg & the bigg ETC.)
/* snip */
  REPLACE_TEXTUALLY ~.*\bBARBARIAN\b~			  ~0x40000000 BARBARIAN~
  REPLACE_TEXTUALLY ~.*\bWILDMAGE\b~			   ~0x80000000 WILDMAGE~
BUT_ONLY
APPEND ~kit.ids~ ~0x4000 TRUECLASS~ UNLESS ~\bTRUECLASS\b~
APPEND ~kit.ids~ ~0x40000000 BARBARIAN~ UNLESS ~\bBARBARIAN\b~
APPEND ~kit.ids~ ~0x80000000 WILDMAGE~ UNLESS ~\bWILDMAGE\b~

For every mod that tries to cheese the kit.ids file.

Yep this solves the original mod install without the Throne of Bhaal -situation which is the sole reason why the mods introduce the whole freaking thing in the first place.

And yes, I posted about this in the Refinements forum too, but no one replied.

 

The refinements block also intends to fix a broken KIT.IDS because it's installed almost at the end (and the mods before it are stupid) - I'll have each value mapped to their identifier so the REPLACE_TEXTUALLY doesn't bork shit up further Thanks Imp for pestering me giving me a heads up

 

I'll have a patch up in git by tomorrow morning... please don't hurt me

 

@Jenavee: Please post pics/the error lines for any errors you get If it's in the code, it'll be fixed! kthxbai

Edited by Lollorian, 19 December 2013 - 05:23 PM.

[Jenavee]

I would, normally, but after running into a couple parse errors later in the install during components which, the last two installs, patched in just fine, I decided to throw away my old selection list, which was heavily modified from the one I used the first two times, then went through BWS component by component and stripped out the ones I knew had problems with some of my other selections (Refinements, Song and Silence, Rogue Rebalancing, and Psion, for instance) then saved my new selection for this reinstall.
 
Also, at this point of trying to get this working for the past ...two weeks?... I'm much less interested in fixes I'd have to reinstall for (AGAIN) and much more so in simply getting a workable install (much like the first two were, but with Wild Mage fully functional). Well, actually... I guess it was more like a week or so of planning so I wouldn't bork the first install, but that failed...and of course it takes around twenty hours to install the BWP on my craptop, so that's a day per install...

Edited by Jenavee, 19 December 2013 - 05:56 PM.

[Jenavee]

 

Alright, that's it. I'm getting tired of this...

 

Mur'neth and Item Revision are both refusing to install properly. Mur'neth's complaining about BGBEDWState or something like that, and Item Revision's whining over a parse error. I don't dare continue BWS with these kind of errors so early in the install, lest everything else breaks over the loss of Item Rev. I REALLY want to play BG again, but with the kit problems surrounding Wild Mage, guess I'll have to wait. Might as well get these fixed in the meantime. I did remove Refinements from my install list (to fix the Wild Mage problem) but ever since this crap's been happening. Not sure if it's the reason, but maybe related?

 

 Setup-Mur'Neth.debug   38.68K   293 downloads

 

 SETUP-ITEM_REV.DEBUG   26.24K   187 downloads

 

------------------------------------------------------------

 

Edit: Alright, I ditched Psion, fixed Refinements (I think, using Impy's code from above), tweaked a few little things, unchecked Item Revision's buggy masterwork weapons and item revisions, and murdered the Mur'neth mod. Got nearly halfway through BWP install now without errors, until THIS happened.

Luxley Family component won't install, getting a parse error (like everything bloody else). UGH!

[Faren/crossmod/luxley/fhflux.d] PARSE ERROR at line 41 column 1-14
Near Text: @21
    syntax error

 SETUP-FAREN.DEBUG   189.88K   202 downloads

 

Too impatient to wait, going to go ahead with the install for now without this component, ensure there's no other unrelated bugs.

 

EDIT EDIT: WOOHOO, fixed it (I think). The @21 lacked a space and = sign before it. Adding them and saving it made it install without errors.

 

--------------------------------------------

 

Annnnd another error.

ERROR Installing [Revised Shield Bonuses], rolling back to previous state
Will uninstall   0 files for [ITEM_REV/ITEM_REV.TP2] component 10.
Uninstalled      0 files for [ITEM_REV/ITEM_REV.TP2] component 10.
ERROR: Sys_error("item_rev/lib/descriptions.tpa: No such file or directory")
Please submit a report regarding this problem, including the information contained in SETUP-ITEM_REV.DEBUG to Demivrgvs and Mike1072 at forums.gibberlings3.net
Automatically Skipping [Revised Shield Bonuses] because of error.

 SETUP-ITEM_REV.DEBUG   2.37MB   398 downloads

 

There IS an item_rev/lib/descriptions_update.tpa, however. I'll attempt to fix by renaming it. Turns out, the latest Item Revisions, the beta 3, DOES have that correct file. I think the BWS is thinking it's installing v3....but then WHY THE HELL is it downloading and extracting v2?!

 

No idea if this is the right thing to do, but I'll completely uninstall Item Rev v2 and try installing v3 manually with the options I'd picked.

 

Edit: If this works, I'm calling out this project (and install) as a load of ----.

 

Edit Edit: It half-worked...sort of, anyway. On the bright side, everything else installed just great, and I can, frankly, live without this tweak for now.

ERROR: cannot convert b_0_1 or %b_0_1% to an integer
ERROR: [chan19.itm] -> [override] Patching Failed (COPY) (Not_found)
ERROR: Not_found
Allow Thieving Skills in Armor -> Stealth is Penalized by Armor and Shields (Item Revisions) was not installed due to errors.

Here's the latest debug (for v3 beta)

 

 SETUP-ITEM_REV.DEBUG   6.42MB   258 downloads

 

Going to download the v3 beta hotfix (September) now (I only just found out it had one), uninstall v3 beta, then patch it and try again.

 

GAAAAH! DEATH AND THE DARK, it bloody worked without stopping after I patched Item Rev v3 beta with September's hotfix

 

 

-------------------------------

 

Am beginning to have a sinking feeling I shouldn't have updated the BWS with its update button. If all else fails, I'll need instructions on how to undo the updates to BWS so it'll revert to its downloaded state. It appears that simply restoring BG2 to its default state, minus all BWS files, isn't enough to do so, since BWS is not giving me the option to update when I copy it from its zip file back to BG2 SoA folder, which is giving me the impression it's using the latest changes.

 

--------------------------------

 

And now Sword Coast Stratagems is stuck in an infinite loop. This is beginning to get really depressing. Everything was (apparently) going great....

 

--------------------------------

 

 

It finally happened. This bloody updated BWS drove me insane. Rolling back to pre-update, which suffered NONE of these issues under my near-identical configuration.

Edited by Jenavee, 20 December 2013 - 11:55 PM.

[Lollorian]

Ok small update

 

Refinements patch is up

Mur'neth's patch was already up (but I tweaked it a bit because I'm a dick )

Faren's patch was already up

 

ItemRev's case is a bit different- the BWS should probably not try to apply the hotfixes itself but let the BWPFixpack apply them From what I gather, the BWS downloads v2 and applies v3.1's hotfixes on it?

 

The next version BWPFixpack should be way more updated and awesome than anything you've seen before

[Jenavee]

My hero as ever, Sir Smiley! And just in time for the (hopefully last) install! However, you're mistaken somewhat. After reverting the BWS to its default, un-updated state, it was in fact asking to download Item Rev v3 beta, rather than the uh... the other one, the v2. I had to manually download it, even, since it was having problems finding the v3 beta link. Further, I then (not knowing if it would or not), copied its hotfix directly to it once BWS extracted the files.

 

Those fixes are pushed through now, and won't have to be manually installed? Never mind, I'll just check it myself to see if they are. Heh, added them locally for now since it's a hassle to redownload anything. Then thought better of it and simply left it as it was, since it occured to me I wasn't using the latest version anymore, and they had installed without errors the first two times when doing so. Further, turns out the version of BWS I'm using is downloading both the v3 beta and the hotfix for Item Rev already, hence no need for my localized Item Rev.

Edited by Jenavee, 21 December 2013 - 07:34 AM.

[Marvin]

Hey there,

 

what about the Textpatch fixes for non-English users? Any updates?

 

Greetz,

Marv

[Lollorian]

@Jenavee:
The fixes being pushed into git won't affect you because the BWS doesn't use it for the moment. More on that in a bit...

@Marvin:
Leonardo mentioned a few weeks back that he's regenerated all the textpack patches so it shouldn't be long now I've also mailed him updated patches for the english and spanish textpacks

I'd like to explain that the long delay in the next BWP update is partly my fault (who am I kidding... it's probably entirely my fault) because I pushed a lot of patches into the BWPFixpack that essentially broke the BWPTextpack (because the textpack gets applied after the fixpack)

So Leonardo had to recreate all the BWPTextpack patches so they're compatible with my BWPFixpack patches Hence the delay, but like I mentioned, Leonardo's said that he'd updated everything so it shouldn;t be long

After the texpacks get updated, the BWS can switch over to the git master branch and the BWPFixpack will literally be updated in real-friggin-time baby