5286 replies to this topic

[agb1]

* BWS:  Select-GUILoop.au3 and Select-Helper.au3 - Fixed 'load selection from weidu.log' option in selection tree (now works on quick-log format weidu.log too)

* BWS:  Select-Tree.au3 - Added check to make sure sub-components in Select.txt have the same theme as the full component that precedes them

* BG2EE:  Corrected sub-component answers 0?2_1 and 0?2_2 for Ascalon's Breagar NPC (German language only)

* BGT:  Corrected sub-component answer 11?1_3 for EET Tweaks

[vanatos]

Hi,

 

Apologies accidentally made the Imoen Romance a .rar file, put it back as zip.

[dady977]

Hey there, I just downloaded the latest update and did a fresh install, but everytime I click on the "Choose mods and components" option I get this error:

 

 

I'm using BG II: Enhanced Edition, if that matters.

 

PS: The update before this one worked perfectly with me.

Edited by dady977, 12 January 2016 - 03:04 AM.

[agb1]

* BWS:  Select-Tree.au3 - Fixed mistake in previous commit that prevented customization of BG2EE selection

 

* Imoen Romance download link changed from .rar to .zip

Edited by agb1, 12 January 2016 - 05:13 AM.

[agb1]

I noticed the new mod by kulyok Reunion is not yet included in the BWS. Is there a reason for this?

Two reasons:

 

1) Until now, no one has actually submitted a request for the mod to be added

2) It does not have a "static" download URL that will not change for new versions, and we are hoping that Kulyok will provide one soon

 

Regarding #1, you are welcome to submit a request.  See http://www.shsforums...quest-template/

 

Regarding #2, having to update BWS manually every time a new mod version is released is not an ideal situation.  With the availability of free hosting on sites like GitHub, for new mods we prefer that authors host them with "static" URLs so we don't have to keep the links up to date.  We have posted on the Pocket Plane Group forums asking Kulyok to consider hosting Reunion on GitHub and offering to help.

[Lollorian]

Yes.  Eventually I want to move all of the custom workarounds out of BWS and into the original mods or BWFixpack.

It was added temporarily, until you add the appropriate fixes in BWFixpack, and stayed there for just one day. 

As for the rest of workarounds I can say that they were either taken from BWInstallpack or added to BWS in days when Yellow and Round was inactive on SHS (or not yet engaged BWFixpack, not remember).

 

I don't mind that you're even now removed all these workarounds from BWS, but on the condition that they will be corrected in any other way (there certainly all hope for BWFixpack), and not just for the sake of their there was not (especially it concerns mods that are no longer supported by the authors).

Yeah we'll have a look at them one by one But whenever we do, it might help to have documentation about why a particular workaround was done (so any prior discussion about it is accounted for )

Only record keeping is what's needed - no need to remove the workarounds yet if they allow stuff to be installed.

 

About the RPG-KP workarounds in particular, I think that kind of workaround should not be done by BWS. Instead we should just change the Type of the problematic mod to 'E' in the mod.ini. Since one of my recent changes, just changing the Type will automatically mark all of its components red and put them in the Expert pre-selection (no need to modify Select.txt).

And here I disagree. Expert we must mark mods that after installation (which implies that they should be installed through BWS under any conditions) may cause problems in the game. If mod or component for some reason cann't be installed (as it was in the case of installation Infinity Sounds after RPG-KP), we need to add corresponding conflict or dependence for prevent the occurrence of errors during installation (at least temporarily, until this issue is solved in any other way).

I agree with Quiet about this - if there are workarounds that enable installation we should use them (just make sure it's logged somewhere ) Expert mods IMHO should contain stuff that hasn't been looked at/unusable in its current state - not stuff that has workarounds (considering that the BWPFixpack is itself a giant collection of workarounds )

Edited by Lollorian, 12 January 2016 - 07:39 AM.

[Lollorian]

I noticed the new mod by kulyok Reunion is not yet included in the BWS. Is there a reason for this?

1) Until now, no one has actually submitted a request for the mod to be added

There was a request - I tried...

[Ser Elryk]

So what about mods that are in the BWS but are not currently EE-compatible? I've seen a lot of them trickle over one by one, but how does the transition work? Is it solely up to the original mod author to make it compatible? What if the mod author has been inactive for years? Could some kind soul explain how it works?

[subtledoctor]

@agb1 does this mean BWS is pulling from the latest release, instead of from the latest commit?

Can I safely upload new versions of my stuff and make pre-release links, without affecting BWS?

[Lollorian]

@Ser Elryk:
If author is inactive
- BWPFixpack a patch and inform author
Else
- ask author/provide working patch for incorporation. If author allows, BWPFixpack until new version is out

Edited by Lollorian, 12 January 2016 - 09:38 AM.

[Roxanne]

So what about mods that are in the BWS but are not currently EE-compatible? I've seen a lot of them trickle over one by one, but how does the transition work? Is it solely up to the original mod author to make it compatible? What if the mod author has been inactive for years? Could some kind soul explain how it works?

It might be as easy as applying a patch to make a *simple* mod EE compliant or it may be a complex execise - it really depends on the mod content and the type of game resources that are affected.

[Ser Elryk]

@ Lollorian & Roxanne

 

What about those of us who have the technical expertise of a lima bean, but would still like to see a currently non-EE mod be implemented, lol? What's the best way to put our requests out there so that the people who know what they're doing might consider it? And how do the BWS people or modders determine which mods are popular or requested enough to consider doing the work for making it EE-compatible?

 

One example is the Weimer's Solaufein mod which was only recently made EE-compatible. What brought that about?

Edited by Ser Elryk, 12 January 2016 - 09:52 AM.

[The Imp]

The ony issue was that the installation of Generalized Biffing failed for me ..

This could be cause the BWS updated the soucre file to be from GitHub's most recent, instead of the G3's.

Edited by The Imp, 12 January 2016 - 11:57 AM.

[agb1]

Genralized Biffing is distributed in an archive where the path to the TP2 file is:

generalized_biffing-master.zip\generalized_biffing-master\generalized_biffing\generalized_biffing.tp2

 

I had to manually move the TP2 up a directory level so that:

Black Isle\BGII - SoA\generalized_biffing\generalized_biffing.tp2

Thanks for the report and your warm remarks.  This issue should now be resolved:

 

* BWS:  Extract.au3 - Special treatment for Git master branch archives: for mods that have a 'Save=' filename in MODNAME.ini ending in '-master.zip', move sub-folders up a level after extracting and delete original folder (e.g., move BG2\generalized_biffing-master\generalized_biffing to BG2\generalized_biffing, then delete BG2\generalized_biffing-master)

 

* BWS:  Extract.au3 - Helarine mod special extraction logic (rename "Helarine Mod" folder, if present, to "JklHel" folder) enabled for BG2EE (for future EET installs) in addition to BG1EE

 

* Teleport mod:  added compatibility note regarding Sandrah NPC to explain the conflict rule

[subtledoctor]

FYI, NPC_EE has been updated to v2.0.  I've PM'd the .ini and select.txt info for BWS to agb1.  Please note that, while v1.2 worked on the old engine, v2.0 is EE-only.  Sorry, couldn't be avoided.  It relies on a feature of kitlist.2da in the EE engine that isn't present in the old engine.  On the bright side, if you're playing TOB or BGT you can use the ever-excellent "Level 1 NPCs."  And also on the bright side, NPC_EE v2 is an order of magnitude more flexible and fun than v1 was.  You can do really wild and fun stuff, like make Montaron a berserker/thief, or make Neera a Wild Sorcerer.  And the kit-changing part of it now happens in-game, instead of in Weidu, so you can have NPCs use different kits in different playthroughs, without reinstalling anything.  It's cool.

[Quiet]

* BWS:  Extract.au3 - Special treatment for Git master branch archives: for mods that have a 'Save=' filename in MODNAME.ini ending in '-master.zip', move sub-folders up a level after extracting and delete original folder (e.g., move BG2\generalized_biffing-master\generalized_biffing to BG2\generalized_biffing, then delete BG2\generalized_biffing-master)

Uh... This function has long been included in BWS and works fine.

 

Version of BWS was b692bec (~17:08 on 27/11/2015).

No one but me didn't bother that it was a version of almost two months ago? And since no one reported about such errors (despite the fact that mod has been fixed)? And that link to mod since then has not changed? And it's not the only mod that BWS downloads from github, but neither about one of them there were no such reports? So maybe the problem in something else? Because I tested without the latest commit and mod installed fine for me.

 

The ony issue was that the installation of Generalized Biffing failed for me (and the download of WeiDU was corrupted somehow, I needed to manually re-download).

And would like to clarify what failed: installation or extraction of mod? Because if failed installation, it is very strange that there were no reports from BWS about failed extraction.

 

@agb1

I'm not saying that your corrections bad, just don't see any reason hasty correct something that already works well.