jastey

Are you on BG:SoD? If yes, did you install the DLC Merger first as required for modding BG:SoD?

I also do not see any problem in your tp2. That's the only thing I could think of.

The only other option I could imagine is that you are not looking at the installed items but copied the item into the override folder by hand. That would lead to wrong texts in the name and description. I don't think that's what you are doing, though, if you just wrote a mod to install it properly.

Thanks!

1 hour ago, Guest Ront said:

You can't be more civil than that.  He has released more than 25 mods and he has to:

I'm afraid there is no "person released mods = becomes modder at G3 with mod section" automatism. Frankly put, but not necessarily meaning to imply anything for this special case: that's the reason why G3 is a community with friendly, helpful modders and good quality mods.

16 hours ago, temnix said:

The administrators here are some of the arrogant and stupid people who banned me on the other two forums.

No. Noone here has the rights to ban you on other forums.

More changes for v6.0:

new lines in necromancer.tra:

Also, changed description of component "Minor Disclosures" in the readme (changes are in bold):

On 6/4/2020 at 1:42 PM, Greenhorn said:

Heh, you are not entirely wrong here Jastey as clicking that line terminates dialogue and nets you 43 gp.

@Greenhorn I have no idea why this would be botching up in BG:TotSC. If I install it to my local copy, the additional reply option about the "Fan" will be in the greetings state as planned (the one with all the reply options). There is no reason I would know of why it would influence Garrick's "Let's go" line after he was asked to join. BG:TotSC engine is a fragile thing, though, and I didn't look at this ingame. But from the dlg, this is not supposed to happen for Garrick's original (i.e. unchanged) kickout dialogue.

For 6.0, following changes. See also post below.

In messenger2.tra there was an additional line that slipped my notice:

Quote

@256  = ~... little lights... in... the dark...~ ~... watch... them... burn...~

This will be changed into two lines for v5.1:

Quote

 

@256  = ~... little lights... in... the dark...~

@304  = ~... watch... them... burn...~

 

And the following additional lines (from T1M2HALF.baf):

Quote

@305  = ~'Rain nor snow nor gloom of night' my taut and shapely buttocks...~
@306  = ~(wheeze) Can anybody hear me?~
@307  = ~Feet don't fail me now - do I still have feet?  All kinda numb down there...~
@308  = ~I'd rather be fishing. (cough)~
@309  = ~Ow.~

@Austin thank you very much!

Kivan in BG:EE no longer has pips in spear but comes with two pips for halberds. For legacy reasons his quest gives him a spear as a reward for EE, also.

There is two obvious solutions if we want to keep the original content:

-change Kivan's pips in BG:EE and EET from halberd to spear.

-change the item to use halberd proficiency instead. (kudos to jmerry for the idea.)

I'm fine with either - or both. I would make it an optional component and would be happy if someone provides the required tp2 code / changed item.

On 10/26/2020 at 10:23 AM, Austin said:

If the mod is installed AFTER EET, then a bug occurs with Imoen: if it is excluded from the party, it will not join back (re-joining does not work).

This will be fixed in v25. Good catch!

On 11/13/2020 at 5:23 AM, Caedwyr said:

The following line from Jaheira can fire while in the Friendly Arm Inn

Alrthough I would not mind the dialogue to fire outside from nature areas, it would be weird if she'd say this before the group ever visited one. I'll add an OUTDOOR check.

On 11/13/2020 at 5:23 AM, Caedwyr said:

Also, a couple of typo/grammar corrections:

Thank you, integrated!

On 11/1/2020 at 11:09 AM, Guest Merlin said:

the 11 charisma given by the guide is not enough. It should be 13 or maybe better.

The script of Shar-Teel romance checks for CHA and STR greater than 10. The only instance where it checked for greater than 11 is in the case of a ranger/paladin PC who fell. Will be adjusted in the next version.

There will be two additional new lines in v23 in lc_noober.tra.

@Austin tagging you in the hopes that you'll correct the two last lines here and send the file to me: https://github.com/Gitjas/BG_Quests_And_Encounters/blob/master/bgqe/tra/russian/lc_noober.tra

Oooh! You are busy! Thanks for the kind words. You know my address.

Haha! That quest was only handed out to groups with lower reps, and I usually had 20 when reaching Baldur's Gate, so I never knew about it myself.

Send me the package anytime, and thank you!

@Coland That is great! Did you also note the completely new component mentioned here?

If you know the stringref number, STRING_SET should be what you need. Have a look at my Imoen4Ever mod, e.g. imoen4ever/tpa/string_set.tpa. I use STRING_SET to change references of Imoen into references about Irenicus. My first guess would be that you got the syntax wrong somehow / put it into the wrong file type maybe. If you used it in your tp2 and it didn't work, please post your code here.

3 hours ago, Roberciiik said:

Moreover, as per my understanding, it will not work with EET, because strref will be different, right?

Differences between BG:EE(SoD) and EET is easy: the stringref number of EET is 200,000 + the number of BG:EE(SoD). For BGII(:EE), stringrefs between BGII:EE and EET are the same.

Thus, if your BG:EE stringref is #15993, for EET it is #215993. I am dealing with this in Imoen4Ever, too, and do it via OUTER_SET variables.

If you want to cover the same (BG1-) stringref for BGT, too - then it gets complicated and I can't help you with how to find the right stringrefs of the BG1 part.

The reactions of BG1NPC were more of the completeness kind of sorts for authors that wanted "their" NPC to react to it (for me it was "I can't let (romanced) Ajantis *not* react to a gender change".)

bg1re focussed more of the gender change as a topic I guess and is more tongue in cheek I think. But: the topic (EDIT: topic included in BG1NPC) was extended by bg1re because it fit the mod content of bg1re.

So I guess it's more number 1.

It's not that bg1re is supposed to be an add-on to BG1NPC Project's girdle reactions (as you noticed, the tone is different due to the nature of the mod). It's more that when we wrote girdle reactions for the NPCs, we didn't want to overwrite the (few) ones from BG1NPC so some NPCs react via BG1NPC and some (others) via bg1re.

Also, BG1NPC is closed content-wise with regard to additions.

I'd prefer posts in the relevant mod forums tbh, so nothing gets lost.

Thanks for your work!

4 minutes ago, grodrigues said:

I read a post (forgot which exactly) that traced this problem to BG1NPC when installed *after* EET. If installed before, the problem went away.

Interesting. I'll put this down on my list, thanks for the reminder.

Haha, that's funny! Coland it will be, then.

This sounds great, looking foreward to receiving the files. I'm not sure when I'll do the next round of mod updates, so please have a litle patince.

11 minutes ago, Coland said:

The encoding should be fine since I made extensive in-game testing without any problem

The problem is that the old engine and BG:EE need different ones, and for the way the installer works the format needs to be the one for the old engine. The way it is provided in the mod currently is what will work on both engines.

Thank you for your work. I put it on my list for when I do mod updates next time. No ETA.

Hi @Coland, thank your for the kind words and for taking on such a huge project!

Fist you'd need to check whether your translation is still up to date. If you use a tool like WinMerge you can check for differences in the (english) tra files from the version you used for translation and the current one.

Let the files be proof read by at least one other native speaker.

I don't know how much experience with translating IE-mod tra files you have, so I'll point out the most basic requirement which is that the text lines need to be enclosed by the tildas (~~) without any spaces. I'm saying this now just in case.

The encoding needs to be ANSI (not utf-8). If you say you used the French one then that should be fine.

Then just link the package to me or send it at my username at web.de and I'll pack a new version.

Also, do not forget to specify who / by which name should be credited in the readme.