53 replies to this topic

[agb1]

This thread's purpose is to consolidate open issues on other threads for easier reference.  I will update this first post regularly to add new items and remove completed items.
 
Requests for expert review
 
1. Conflict analysis needed for Irenicus Dungeon components BP(1210):SCS(8000)
 
2. ding0 tweaks component "Revised Summoning Cap" fails to install while patching belt05.itm -- Cursed Items Revision not responsible, so is the original file bad or ding0 Tweaks has a bug?
  http://www.shsforums...ation/?p=584365
 
3. Is Miloch's Resource Fixer safe to install on EE?  Is it still necessary for BGT?  http://www.shsforums...ns/#entry472218
 
4. Verify Roxanne's patch for Tashia Remix  http://www.shsforums...od/#entry584449
 
5. Why does amtgen01.cre (from ding0's questpack) cause Item Randomiser install failure?  Wisp is investigating  http://www.shsforums...ogram/?p=584855
 
6. Issues #1, #2 and #3 reported by Niewiem have not been replicated/resolved yet  http://www.shsforums...stall/?p=585012
 
7. Anarki_Hunter reported Viconia duplicate in BGT (original still in Peldvale with no dialogue is not removed until after meeting new one south of Beregost per SCS component) http://www.shsforums...ction/?p=584556
 
8. Many issues reported by Munchkin Mooch  http://www.shsforums...eports-bg1-bg2/
 
9. tomkaz's reported problems in BG1 -- http://www.shsforums...-of-my-bgt-game

 

10. Why are Garrick Tales of a Troubadour and Tenya Thermidor (BG:EE NPC) incompatible?  http://mirandir.bald....fr/garrick-tt/

 
Requests for Fixpack
 
1. Patch BP and BPSeries AI to append missing IDS entries (EE games)  http://www.shsforums...1-bg2/?p=584321
  NOTE:  134 STATE_DISEASE_FIX needs more analysis because it conflicts with another IDS entry
 
2. Linux/OS X version of Fixpack script -- khelban12 has written one !  Needs testing  http://www.shsforums...e-2#entry584762
 
3. Update Lolfixer for EE  Reported problem:  item pictures in inventory etc. change to crate.
 
4. Implement fixes for issues on BWS workaround list:  http://www.shsforums...upbat/?p=585805
 
5. Rukrakia worldmap patching -- http://www.shsforums...hings/?p=585764
 
6. BP adds a non-existent item to AMTGEN01.cre -- http://www.shsforums...ogram/?p=585118

 

7. Patch Tower of Deception to use MAKE_BIFF for cross-platform installs -- http://www.shsforums...hread/?p=585681

 

8. Patch Divine Remix "apply kit to NPC" components -- http://gibberlings3....e=3#entry232694

 

9. Create a WeiDU-based patching script for Fixpack  http://www.shsforums...r-bwp/?p=586249

BWS To-Do List
 
Check install order for Item Revisions v4 and Spell Revisions v4 and Ascension 1.5 (EE compatible version)
 
Add Kjali Romance mod (waiting for author's next update)
 
Imp's idea:  simplify how BWS handles WeiDU version updates
 
Ser Elryk's BGEE install problem (BWS didn't run NPC_EE setup although it was selected) - http://www.shsforums...ogram/?p=584747
 
When RtF becomes available for EE, consider this for install order -- https://github.com/K...Tweaks/issues/3

 

Add additional BG2:EE mods -- https://forums.beamd...ble-mod-list/p1 and https://forums.beamd...st-additions/p1

 

Add additional IWD:EE mods -- 

 

Add offhand weapon swap mod (maybe patch so it prompts for hotkey letters instead of requiring TP2 file edit before install) -- http://sasha-altheri...dweaponswap.htm

 

Ideas for finding more bugs in mods ...

 

1. Run a grep on various mods for DO SetGlobal() END as these might not execute as intended -- http://www.shsforums...orums/?p=585856

Edited by agb1, 29 January 2016 - 11:15 AM.

[Mike1072]

4. Check if item_rev and spell_rev patches are still correct for latest IRv3 and SRv3 updates
  https://github.com/G...sions/releases/
  https://github.com/G...sions/releases/

The patches for the item_rev and spell_rev folders will be out of date, because they contained the official hotfixes. The main downloads now have these hotfixes applied.

As mentioned on GitHub, the wakizashi/ninjato patching problem has been fixed in the source code, so the separate fix mod for that is no longer needed. The _shatterfix mod can still be used with IRv3.

[agb1]

Thanks Mike. I wasn't sure if Fixpack did anything other than applying the hotfixes.

[Quiet]

4. Check if item_rev and spell_rev patches are still correct for latest IRv3 and SRv3 updates
  https://github.com/G...sions/releases/
  https://github.com/G...sions/releases/

Unfortunately, BWS can not use such links.

[agb1]

Unfortunately, BWS can not use such links.

I used lynxlynx:

http://lynxlynx.info...3/ItemRevisions

http://lynxlynx.info.../SpellRevisions

As of this morning, Ser Elryk successfully downloaded the v3 versions with BWS.

Edited by agb1, 01 January 2016 - 06:22 AM.

[Lollorian]

The patches for the item_rev and spell_rev folders will be out of date, because they contained the official hotfixes. The main downloads now have these hotfixes applied.

Thank you for confirming Removed them.

 

I noticed this thing was not applied though... do you feel it's not needed?

[Quiet]

Unfortunately, BWS can not use such links.

I used lynxlynx:

http://lynxlynx.info...3/ItemRevisions

http://lynxlynx.info.../SpellRevisions

As of this morning, Ser Elryk successfully downloaded the v3 versions with BWS.

I'm about v4 links.

[agb1]

I'm about v4 links.

OK, thanks.  I will look into this.

[Quiet]

However, links:

https://github.com/G...rchive/v4b8.zip

https://github.com/G...chive/v4b12.zip

should work fine.

[agb1]

Tested - the new links work.  Thanks Quiet!

[Mike1072]

 I noticed this thing was not applied though... do you feel it's not needed?

This is the first I've heard of it. Was it reported on the SR forums? Demi would know more about whether anything was done about it.
 

I've send question to github.com support about getting lastest pre-release API. 

The pre-releases are listed along with the other releases in the JSON output.  There's a property called "prerelease" that lynx probably already uses to filter out pre-releases in his current script.

[The Imp]

 I noticed this thing was not applied though... do you feel it's not needed?

This is the first I've heard of it. Was it reported on the SR forums? Demi would know more about whether anything was done about it.

Could you check if the item in question (ie SPWI461.itm ) in Spell Revision uses a two handed animation and thus also needs to be flagged as two handed, I think it is or at least was a Halberd from what I can presume, as it used that animation.

[agb1]

First post updated.

[The Imp]

Here's a request of 1, 2. 4. 19 hundred 3rd-ty seven, three things:

1) Reorganize these two:

~SETUP-WEIDU.TP2~ #0 #0 // 23800
~SETUP-BWS.TP2~ #0 #0 // 20150524 - Updated by Silent

 

2)  Make the ~SETUP-BWS.TP2~ #0 #0 ... actually an install-able mod, something to the effect of:

BACKUP ~BWS/backup~
AUTHOR ~Updated by Silent~
VERSION ~20150524~
BEGIN ~BiG World Setup~

// Adds CD_STATE_NOTVALID state
APPEND ~STATE.IDS~ ~0x80101FEF CD_STATE_NOTVALID~
UNLESS ~CD_STATE_NOTVALID~

... or what ever. It could be so very long too, if we would set all the .ids files so no other mod would need to touch them, not just the most common(aka above).

 

3) And make the above mods run with this custom command line of:

Setup-BWS.exe --no-exit-pause --autoupdate --language 0 --skip-at-view --quick-log --force-install-list 0 --logapp

 

You might ask why ?

Because the very next component will be:

~SETUP-WEIDU.TP2~ #0 #0 // xyzts

So that won't be psuedo signature of a stated message, but an actual signature of the weidu.exe's actual version.

 

*Nope, I don't have an idea what the BWS does to the weidu.exe's, but the solution I saw in one of the post earlier seemed omnius enough, considering it touches every one of the setup-*modname*.exe, and it removed all the natural protective measured build into the weidu.exe with the --noautoupdate flag to throw these.

[agb1]

I suggest putting IDS entries in Fixpack instead - it is more portable than BWS and is also used by BWP so we would avoid unnecessary duplication.

I'm not clear why setup-weidu should precede setup-bws. The only purpose of setup-bws I can see is to put the BWS version string into the weidu.log, and the same is true for setup-weidu. What problem are you trying to fix here? Is your idea to use WeiDU's auto-update feature instead of what BWS currently does (replacing every setup-exe with a downloaded copy of WeiDU.exe)? Except for situations where a user wants to use a newer version of WeiDU than what BWS is configured to download, which is clearly an expert user case, I don't see a problem with how it currently works?

[The Imp]

... which is clearly an expert user case, I don't see a problem with how it currently works?

Well, this is not the case, if you look at the thread I linked, or ALIEN's request for a permanent beta weidu.exe link. There's a reason behind all of that.

[agb1]

ALIEN's request is anticipating a future where EET is approved for general use before WeiDU 238.01 becomes a stable release.  At the moment EET is the only mod that depends on 238.01 and EET is disabled in BWS unless you modify its include files manually (outside the program).

[The Imp]

ALIEN's request is anticipating a future where EET is approved for general use before WeiDU 238.01 becomes a stable release.  At the moment EET is the only mod that depends on 238.01 and EET is disabled in BWS unless you modify its include files manually (outside the program).

And thus the BWS could use the stable beta v23801 from the link, why ask for a .exe while you already have the .zip file ? I tried to get the answer, but never got one.

[agb1]

I'll let ALIEN speak to this if he wants. I have not looked into changing the WeiDU version used by BWS so I don't know the details yet.

Meanwhile, I'm still not clear what you were trying to accomplish with your suggestion above?

[The Imp]

Running the --autoupdate flag ones at the start of the install would make it easier to control the version of weidu.exe ... just like it did before all this automating of stuff.