5286 replies to this topic

[Lollorian]

* BG1EE:  Fixed lolfixer(7) TobEx dependency rule (TobEx not needed for BG1EE)

If I'm not wrong, there is no hard ToBEx dependency in the lolfixer - it will just do more stuff IF it finds ToBEx in the installation It should translate to ToBEx is recommended but not mandatory.

[agb1]

Thanks Lollorian, I will update those rules accordingly.

 

Edit:  Actually, I think this rule is improperly stated:

 

TobEx poison effect dependency=D:ToBEx(100)&lolfixer(7)|BG2EE|BG1EE

 

This means lolfixer 7 and TobEx(100) should always go together unless the game type is BG1EE or BG2EE.

 

I think it should be D:TobEx(100):lolfixer(7) ... so if you use TobEx poison effect tweak, you must also use lolfixer 7, but the reverse does not apply.

Edited by agb1, 28 December 2015 - 09:19 AM.

[Quiet]

ERROR: Failure("resource [MAGIC_MISSILE.spl] not found for 'COPY'") in apply_standard_function: This looks like something put it's dirty hands over the "spell.ids" file and did it before the mod was installed. --change-log the "spell.ids" file if you can.

 

Something like this?

ANN;BP and BPSeries AI need the following IDS entry
CMD;echo 2302 WIZARD_REMOVE_MAGIC >> override\Spell.IDS

If to remove this line, Wheels of Prophecy installs without errors.

[The Imp]

Something like this?

ANN;BP and BPSeries AI need the following IDS entry
CMD;echo 2302 WIZARD_REMOVE_MAGIC >> override\Spell.IDS

If to remove this line, Wheels of Prophecy installs without errors.

I don't understand what this represents, but the fact is, this very simple command can do:

APPEND ~spell.ids~ ~2302 WIZARD_REMOVE_MAGIC~ UNLESS ~^2302 ~

 

But the file already contains that in the vanilla BG2, so which ever mod or action by BWS fucks that up HAS TO BE REMOVED !

Like I said, it doesn't matter if the file has several:

~2302 x ~

~2302 y ~

~2302 z ~

~2302 t ~

As long as those x, y, z & t functions almost the same way.

I feel like this is fucked up by something that came from this, something that should not have been done !

Or some blind idiot just went and removed the vanilla files line 936: 2302 WIZARD_REMOVE_MAGIC

As the same file contains at line 225: 2302 WIZARD_DISPEL_MAGIC

 

And if you then wish to do something insane like replace the "2302 WIZARD_DISPEL_MAGIC" -line with something that is actually related to the dispel_magic spl (aka 326), then you do nothing to those lines, but to this line number 248: 2326 WIZARD_TRUE_DISPEL_MAGIC

DUH

Well, actually you won't, but one really needs to make sure that what ever you do, you don't fuck up the scripting with this kind of fuckuppery.

As it should never be removed or even modified, as the file can contain as many 2326 x etc lines as the idiot making the added scriptings wishes !

Edited by The Imp, 28 December 2015 - 12:47 PM.

[agb1]

ANN;BP and BPSeries AI need the following IDS entry
CMD;echo 2302 WIZARD_REMOVE_MAGIC >> override\Spell.IDS

If to remove this line, Wheels of Prophecy installs without errors.

Quiet, are you saying that if you remove that line, Wheels of Prophecy installs without errors, but with that line, it fails?

[agb1]

Still bug-hunting.  More updates:

 

* BWS:  Fixed(?) rules parsing for another special case:  dependency rules without ':' delimiter (e.g., D:modA&modB|modC)

* BWS:  Added debug message box pop-up if an unexpected situation happens:  BWS tries to enable/disable a mod/component automatically but the status doesn't actually change

 

* BWP/BGT:  Aurora Shoes & Boots component 0 moved from BG2 NPCs to BG1 Stores & Items (it's technically BG1 and BG2 both, so will move it to a BGT category in the future)

* BWP/BGT:  Aurora Shoes & Boots component 10 & 20 moved from BG2 NPCs to Portraits (install order unchanged, just category/theme)

 

* BG1EE/BG2EE/BWP/BGT;  Corrected TobEx-related dependency rules (among others, Lolfixer component 7 no longer requires TobEx 100, but TobEx 100 still requires Lolfixer 7)

[Quiet]

ANN;BP and BPSeries AI need the following IDS entry
CMD;echo 2302 WIZARD_REMOVE_MAGIC >> override\Spell.IDS

If to remove this line, Wheels of Prophecy installs without errors.

Quiet, are you saying that if you remove that line, Wheels of Prophecy installs without errors, but with that line, it fails?

Yes, I'm tried two identical Recommended-based installations and one with that line fails, but another without it - haven't any error.

[agb1]

Interesting. Maybe Spell.IDS isn't in override before that line so it is creating the file there. That would be... Bad.

[agb1]

* BWS:  scripted appends to IDS files now check if the IDS files already exist in override before appending (to avoid creating a new IDS file with only one line in it)

[zonx]

Figured I'd run a quick install (bg2ee) on latest build to see how it is going now. bg2ee reccommended completed successfully (didn't halt the install for error) but obviously there were some spell.ids issues.

Spoiler

[bpseries/source/gb-smage.baf] PARSE ERROR at line 3973 column 1-32
Near Text: )
[HaveSpell] argument [WIZARD_REMOVE_MAGIC] not found in [Spell.IDS]

[bpseries/source/gb-smage.baf] PARSE ERROR at line 3995 column 1-49
Near Text: )
[Spell] argument [WIZARD_REMOVE_MAGIC] not found in [Spell.IDS]





Mods affecting SPELL.IDS:
00000: ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ 0 1000 // Initialise mod (all other components require this): v30 BWP Fix
00001: ~BPSERIES/SETUP-BPSERIES.TP2~ 0 0 // Detectable Stats v3.1 (required for BPSeriesScript Component): v0.3121
00002: /* acted upon in an indetectable manner */~GENERALIZED_BIFFING/GENERALIZED_BIFFING.TP2~ 0 0 // Generalized Biffing: v2.2 BWP Fix
00003: /* acted upon in an indetectable manner */~GENERALIZED_BIFFING/GENERALIZED_BIFFING.TP2~ 0 0 // Generalized Biffing: v2.2 BWP Fix

Attached Files

•  WeiDU.log   25.3K   141 downloads
•  BiG World Debug.7z   85.47K   134 downloads

[Ser Elryk]

I'm still confused about whether I should download from the 'master' branch or the 'bp-test' branch if I want to make a new install. (For the purpose of playing the game, not testing, that is.)

[The Imp]

For now, I would say it's definitely the master, it was updated 10 hours ago, the bp-test 13 hour.

But that's my irrational reasoning stance.

[Ser Elryk]

So basically at any given time it would probably be best to use whichever one has been updated the most recently?

[Ser Elryk]

No because other branches contains untested code, you might face the situation when for eg: I create a Feature/TestNewInstallOrder and put my experiments there, you will download it and next day I will delete it because changes was wrong. You will endup with broken code.

 

So you're saying I should usually go with the master file, then?

Edited by Ser Elryk, 29 December 2015 - 04:50 AM.

[The Imp]

No because other branches contains untested code, you might face the situation when for eg: I create a Feature/TestNewInstallOrder and put my experiments there, you will download it and next day I will delete it because changes was wrong. You will endup with broken code.

So you're saying I should usually go with the master file, then?

Yep.

[Ser Elryk]

Thanks, compadres =)

[Tzarnal]

As a general rule for any Git repository ( or even any other version control system ) Master/Trunk is where people are doing general program stuff, branches are for new feature development, overhauls, etc.

 

Unless you want specifically the stuff on a branch for whats happening on that branch, go with main. Even if main is "outdated", branches will get merged back in, thats the point of them. Or if they don't get merged in its becuase there was some serious issues with them that could not be resolved.

Edited by Tzarnal, 29 December 2015 - 08:24 AM.

[agb1]

The bp-test branch has been merged onto the master branch.  Please use master from now on.

[agb1]

* BG1EE/BG2EE/BGT:  Consistent NPC appearance (portraits) conflict changed:  BG1NPC and BG1UB do not conflict

* BG1EE/BG2EE/BGT:  Fullplate and Packing Steel component 204 (backstabbing tweak) disabled in all pre-selections

* BG1EE/BG2EE/BGT:  Fullplate and Packing Stell components 1 and 102 enabled in Maximized pre-selection (but will be disabled automatically by BWS due to conflict rules)

* BGT:  Familiars conflict changed from warning rule to must-solve rule

* BGT:  Summoning changes conflict changed from warning rule to must-solve rule

* BGT:  Khalid (dead or alive) conflict changed from warning rule to must-solve rule

* BGT:  added Sandrah NPC component 0 dependency warning for Sandrah NPC component 12 (mod interactions)

* BGT:  linked Sandrah NPC "recommended mods for interactions" dependency rules to component 12 instead of component 0

* BGT:  added Divine Remix 1000 (sphere system) to selection and marked the component as Expert

 

* BWS:  More fixes for conflict and dependency rule processing and revised English help text on the conflicts/dependencies resolution screen (needs translation)

* BWS:  Doubled default width of the second column (component description) on conflict/dependency rule processing screen

 

* BWS:  EET Tweaks switched to use GitHub 'Latest Release' link instead of master branch; removed 'W'arning (thanks K4thos for publishing a release version on GitHub!)

 

Known issue:  if you switch from BGEE game type to BG2EE game type and select 'choose mods and components', BWS might crash -- workaround:  BG2EE selection works fine after you restart BWS

Edited by agb1, 30 December 2015 - 10:07 AM.

[zonx]

New install with most recent BWS on bg2ee with default tactical preselection.

 

Snagged on this error:

Spoiler

Installing file(s) werewyv.baf ds52329.baf

Compiling 1 script ...

Compiling 1 script ...

Processing quests and journals

ERROR: No translation provided for @314

 

ERROR: No translation provided for @314

ERROR: Not_found

Initialise mod (all other components require this) (Sword Coast Stratagems) was not installed due to errors.

ERROR Installing [Initialise mod (all other components require this)], rolling back to previous state

 

Attached Files

•  WeiDU.log   13.94K   145 downloads