5286 replies to this topic

[Roxanne]

What mod is it?

That would be unfair. I have a suspicion but no evidence. Innocent until proven guilty, at least where I am from.

 

If you are so interested, look at it yourself. It is not cryptic. You could test it while you are at it.

[Blash2]

Roxanne, there is not trial here, no judges, no, lawyers, no sentences 

We're just trying to sort out a bug, this is why this thread exists, to publicly deal with problems like this one. 

 

Talking openly would allow other people to participate, maybe other modders too, whose contribution might be precious. You yourself spoke about something "cumbersome".

 

I myself have no modding skills, but for example I would try to contact that mod's author, or post the link to this thread in that mod's forum.

 

Nobody is saying that the problem lies *there*, I think this is absolutely clear.

 

Everybody would benefit from an open discussion. Think about it 

[Roxanne]

Roxanne, there is not trial here, no judges, no, lawyers, no sentences 

We're just trying to sort out a bug, this is why this thread exists, to publicly deal with problems like this one. 

 

Talking openly would allow other people to participate, maybe other modders too, whose contribution might be precious. You yourself spoke about something "cumbersome".

 

I myself have no modding skills, but for example I would try to contact that mod's author, or post the link to this thread in that mod's forum.

 

Nobody is saying that the problem lies *there*, I think this is absolutely clear.

 

Everybody would benefit from an open discussion. Think about it 

What I found turns out to be unrelated to the original problem with Grey Clan.

There is a new code block added in ar0600.bcs at the top by the Tenya mod, which should have a Continue() at the end to let a subsequent code block with OnCreation() trigger.

 

What causes the Grey Clan issue, remains unresolved. It happens in BGEE but not in EET (which uses the BG2EE platform), so the root may lie here in how the different games evaluate NumDead. But this is just guessing...

[Roxanne]

As I said at the start I have the work-around of changing this global value thanks to Artemius_I .

  SetGlobal("BW05_TGC1","GLOBAL",2)

However, to avoid people asking this question over and over again, If it can be sorted that would be good.

 

I presume that you will be informing the Tenya writer of the problem that you discovered.

As I stated above, the two things are not related, the Tenya thing is a simple improvement but not causing the Grey Clan issue. (otherwise none of the Grey Clan contents would happen, but what fails for some reason is the dead bandits count). There was a similar case with the zombies in farmland and the gibberlings fighting paladin, but none of that is the case here.

And furthermore, I cannot reproduce the error in my installs (they are all EET), it always works for me.

[jastey]

2) The AC_Quest also adds items to the Highhedg.sto for the werewolf quest in the house nearby. In my installation there are no broken items in Thalantyr's store.

(Quoting this because I can't find the original report.)

As far as I can see all Ascalon's Questpack adds to stores are Guril berries that use an existing BAM. No items are added to Thalantyr's store.

[jastey]

About Askalon's Questpack, here is what K4thos wrote about the same exact error with another mod:

 

"There were some changes between beta and release candidate release. That error means that the mod uses outdated "eet_cpmvars.tpa" file (EET 1.0 RC and later doesn't use FluidStates.tpa at all).

Copy this file "EET/other/cpmvars/eet_cpmvars.tpa" and overwrite the same file located in "bgeespawn/lib/" directory with it. This will fix the problem.

 

I will send updated version to AstrobryGuy. Thanks for report."

 

So probably the error, and thus the solution, is the same. Remove from BWS until solved?

This will be fixed in the next version, thank you for the report.

[Blash2]

Definitely too many "pack" in the same post.

[Ser Elryk]

Since the new BWP 17 is out, its Textpack and its Fixpack force the user to start the BiG World Install.bat if it is found in the same directory.

Since the BWS uses the Smoothpack, it unpacks the Installpack.

So to stop the Textpack from complaining, you'd have to rename the BiG World Install.bat to something else.

 

I tried to do an install yesterday and this issue stopped me. Hopefully it'll be fixed/adjusted soon.

[Roxanne]

Since the new BWP 17 is out, its Textpack and its Fixpack force the user to start the BiG World Install.bat if it is found in the same directory.

Since the BWS uses the Smoothpack, it unpacks the Installpack.

So to stop the Textpack from complaining, you'd have to rename the BiG World Install.bat to something else.

This fix has been implemented as interim solution a few days ago.

 

A better solution is pending decision which is connected with the larger question whether BWS should still support classic BG and BGT installs now that BWP 17 is out. Without any maintenance for the BGT branch of the BWS, it is not functional anyhow and it would be much better to remove the option from the BWS GUI altogether to avoid confusion (This is a simple switch in one menu that can be undone within minutes should the BWS maintenance problem be resolved at a later stage.)

[Roxanne]

Definitely too many "pack" in the same post.

The only reason this still is used by BWS are some modders who insist that the user is forced to see their mod's readme after install by having code like

notepad mymod\mymodmustReadme.txt

which forces a window with the readme to open and thus requires the user to close it and resume BWS.

 

Otherwise only BGT installs done with BWS would require the new BWP version...but that is a long story...

 

The main problem in BWS (aside from old software used), is that it carries the history of a decade with it. But whenever you attempt a clean-up and throw some old garbage out, the zealots start throwing stones at you because some lost soul in the multiverse might one far day decide he needs it. This way there is no progress but just slow decay.

Edited by Roxanne, 03 October 2017 - 02:11 AM.

[aiqa]

I am not getting the BGT menu options at the "Select game-type / installation-method:
Does anyone have any ideas how to fix that?

[Roxanne]

I am not getting the BGT menu options at the "Select game-type / installation-method:
Does anyone have any ideas how to fix that?

To install BGT, you now need to use BWPv17 which you find here http://www.shsforums...ld-installpack/

 

The reasons why BWS currently cannot support BGT installs are discussed here:

http://www.shsforums...c/59470-bwpv17/

[aiqa]

So I assume this was an intended change? Yesterday it still worked.

 

And I read that thread, but a reason for removing the classic BGT from BWS is most certainly not discussed there.

The only thing that happened there is some childish back and forth between people that prefer the classic version or the enhanced version.

 

This is quite an annoyance. I've spend almost a week figuring out which mods I want and which I don't want.

So now I have a "BWS-Selection.ini" file all set up to my preference, and now I have to start all over again with BWP to figure out how I can get everything working there.

 

Also, when features are deprecated, it's common sense to give some warning ahead of time.

Edited by aiqa, 04 October 2017 - 07:13 AM.

[Roxanne]

So I assume this was an intended change? Yesterday it still worked.

 

And I read that thread, but a reason for removing the classic BGT from BWS is most certainly not discussed there.

The only thing that happened there is some childish back and forth between people that prefer the classic version or the enhanced version.

The BWS requires a large update in the BGT configuration after the changes. Nobody is there to do such updates. The BGT section of BWS is not maintained for over half a year now. Any attempt to use it will result in failed installations and a lot of waste of time.

 

In case someone is found to bring BWS up-to-date, the BGT part can be re-activated. Currently it is better to suspend it instead of suggesting to users an impression that the functionality really exists.

 

The situation regarding BWS and BGT support has been reported in this thread here repeatedly. Any call for help has been left unanswered, With the latetst update of the crucial files for a BGT install, the BWS does no longer work for the *classic game*.

 

The EE/EET part works again after a quick and dirty fix was installed, since those games are still maintained by a different group of helpers. All of that is missing for BGT.

 

Sorry, but please do not blame the messenger.

Edited by Roxanne, 04 October 2017 - 07:19 AM.

[aiqa]

It doesn't work before 1 file is detected, which is hugely easy to work around. The rest of the installation process worked fine just yesterday.

 

Not sure if english is your first language Roxanne.

But you use "do not blame the messenger"  when you have nothing to do with the actual subject and only supply information.

When I look at the BWS https://bitbucket.or...p/bigworldsetup I am seeing that these commits are done by you.

So again, that is not how you should handle a software project with actual endusers.

Edited by aiqa, 04 October 2017 - 07:33 AM.

[Roxanne]

It doesn't work before 1 file is detected, which is hugely easy to work around. The rest of the installation process worked fine just yesterday.

 

Not sure if english is your first language Roxanne.

But you use "do not blame the messenger"  when you have nothing to do with the actual subject and only supply information.

When I look at the BWS https://bitbucket.or...p/bigworldsetup I am seeing that these commits are done by you.

So again, that is not how you should handle a software project with actual endusers.

Are you saying that you did a successful and playable BGT install within the last two weeks with BWS?

Edited by Roxanne, 04 October 2017 - 07:35 AM.

[aiqa]

Yes it worked fine.

 

The only reason I even wanted to use it again, is 1 mod that didn't turn out the way I wanted (bgspawn is adding to many spawns for my tastes, but that is just the desgin of the mod).

 

And BWP is just not a good alternative. It might work well for installations, maybe even better (?), but it's not even close in how free (and easy) you are in configuring the game to your liking. There is nothing else that can really replace WPS in that regard.

 

A better option would have been to just add a "unmaintained" disclaimer to the BGT classic part.

Edited by aiqa, 04 October 2017 - 07:55 AM.

[Roxanne]

Yes it worked fine.

I did a very large install with all the big mods that have recently changed and it worked with lot of manual intervention. Since components were added or have changed, the resulting game appears playable but you find a lot of issues when you move further into the game or take a closer look at scripts and files.

 

The BWS promises the player bug-free and enjoyable installs with a minimum of conflicts or need for manual intervention. We cannot assure this for BGT at all anymore. You get something, but what it is, nobody knows.

 

But of course, there is a way to still offer BWS for BGT to the user, with a big *use with caution* sign on it. It is a game of chance, depending on your mod selection (BWS does not offer all mods and all choices for some mods anymore due to missing updates. Subcomponents occasionally appear with wrong descriptions. A lot of fixes and patches are failing due to changed versions.)