Jump to content

jastey

Gibberlings
  • Posts

    13,678
  • Joined

  • Last visited

Everything posted by jastey

  1. 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. Thank you, integrated! 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.
  2. 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
  3. Oooh! You are busy! Thanks for the kind words. You know my address.
  4. 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!
  5. @Coland That is great! Did you also note the completely new component mentioned here?
  6. 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. 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.
  7. 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.
  8. 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.
  9. I'd prefer posts in the relevant mod forums tbh, so nothing gets lost. Thanks for your work!
  10. Interesting. I'll put this down on my list, thanks for the reminder.
  11. 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. 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.
  12. Thank you for your work. I put it on my list for when I do mod updates next time. No ETA.
  13. 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.
  14. Thanks for feedback and short reviews! It's always nice to read on players' thoughts about mods.
  15. Thanks for the feedback! I'm glad to hear it.
  16. @Caedwyr I'd love to joke that I'm doing this on purpose to get your corrections but unfortunately, that's my best English there.
  17. Thanks, I'll have a look at that.
  18. @argent77 thank you for the reports, that all sounds quite buggy. I will fix those when I'll have the time.
  19. Probably. Please put logs into a spoiler tag in the future.
  20. Grey clan newest official version is on GitHub from k4thos. Don't have the link currently. EDIT: ah, should have read more carefully. Not sure it's also compatible with original BG1:TotSC.
  21. You wrote: That's very general and unspecific and therefore not constructive.
×
×
  • Create New...