jastey

@subtledoctor Feel free to make an add-on of kinds. I would also be willing to include something like this as an optional component into I4E if you'd provide it.

Thanks for the interesting discussion! I can only repeat myself that I don't see a problem. BGII with I4E is the same situation like BG1: you know you should go / could go to some place eventually - in BG1, it's first the FAI to meet Gorion's friends, then the Nashkel mines, etcpp but there is no real reason to, no pressure (other than NPCs complaining and the game not progressing). BGII with I4E is the exact same situation. The PC knows there is this place where they could go eventually, but there is no rush if they want to go exploring first. As I said, I don't see a "motivation problem" with I4E installed. And: This.

Completely understandable! Yes, ANSI is correct for German tra files.

Ah, I see. Using Sakphul should be alright. But it's what I wrote above, better change the whole sentence to one of my alternatives. As it is, it's a direct translation from the English original but it doesn't really make sense in German. Or just leave it as it is now since the whole mod should be proof read if possible. I'm in the middle of Fading Promises that has similar issues.

The green lines look very good. Some things: @294: Sakphul legen ihre Hände nicht an Drow. I'm unhappy with this sentence. "Hände an jemanden legen" is not correct German. Better change this to "Sakphul lassen ihre Hände besser von Drow." or "Sakphul fassen keine Drow an." Minsk is written with a "k", this needs to be corrected at some instances (e.g. second instance at @241). And more things: du, dir, dich, dein with a small letter if it's a casual "you" and not a formal form of address. This would need to be corrected in the whole document. "weiß" with "ß", not "ss" (e.g. @168) @35 = ~Wow! Ich liebe es, in der grossen Freiheit draussen zu sein! Versteh mich nicht falsch, ich mag die Stadt und alles, aber hier fühle ich mich frei. So richtig frei.~ -> großen, draußen I guess there is more of these things, unfortunately I don't have time to poof read it currently.

I got the last proof readings back, thanks to @Brokenkatana . I need to integrate them and run a quick test concerning compatibility with Transitions mod. I'm on it but no ETA.

Hm, Aran mentions something. But if the group is already with Aran, they already decided to pay and go with the Shadow Thieves to Brynnlaw. I appreciate the suggestion, but I don't think I can make it work as a main motivation to set sail.

Thank you very much, @Austin and yota13!

There is a working alpha but some quests are not finished yet, so nothing for betatesting yet. No ETA. Thank you for your interest!

As much as I agree that this would be in character for Imoen imho, you have one error in your train of thoughts: with I4E installed, neither Imoen nor the PC know any details about Spellhold, the Asylum, and the way the people are treated there before they get there.

Thanks @Endarire for drawing my attention to this.

@Austin In case you haven't yet, please also include a (detailed if possible) changelog.

@Austin Did you take the version 1.7 from SHS into account for your changes?

LT23 is a wakup dialogue and will only happen if EDIT: in the rest dialogue before (LT22): -the PC encouraged Dynaheir to persue the idea of echanting items with magic although it's forbidden to Hathrans. -AND does not succeed in distracting her from the temptation to do it. This means either that the PC just goes to sleep or his constitution is lower 13. Talking her out of it, not talking to her at all, or constitution higher than 12 plus agreeing to help Dynaheir distract herself from the idea will skip LT23.

You need to install NPC mods before EET_End. exe. Deinstall EET_End, install Aran, reinstall EET_End.

I don't think so. This is BG1NPC.

@LukeSolas do you mean the BG1 or the BGII variant? They are quite different in design.

The unidentified / check whether it's identified is a neat trick, if it works. But @Lauriel you also want to make sure the player is aware of what the note says, so I'd leave the "NPC reads it aloud" in as a failsafe.

Have fun!

I have no experience with the automatic converter. This is what I wrote in a hidden forum before with regard to making old BGII (NPC) mods EET compatible. For BG1 mods it depends whether it already covers the "Crossing the Great Divide" (back in the day between BGT and Tutu, but the principle is the same between BG:EE and EET) or not. Addition to that: PIDs need to include "IsGabber(Player1)" into the trigger, then EET automatically adds triggers to the SoA part so it doesn't block the ToB dialogues.

@Bertle Not in the readme, but in the folder "docs" is a file "romance_notes.txt" which states:

Very well said. +1

@Jazira Thank you!

The mod updates to v6 with compatibility to Transitions v0.4 beta.

If the mods are hosted by an active site, the admins / moderators would be the ones responsible for updates. In general, technical updates, compatibility updates and bugfixes will be accepted. You could ask before hand to make sure the mod is not being worked on, and afterwards offer your update in the official mod's forum. If the mod is not connected to an active modding site, you could still make an update and offer it at one of the bigger modding sites, preferably as close to where the mod was hosted/discussed/already updated before. This was also done for very old mods, the updates were offered at SHS "Mod Resurrection" section or also at BeamDog's. Important is that you explicitely state that it's an update, keep the author's name and credits, and list the changes inside the mod package - and are ready to take it down if requested. A no-go is uploading at an own modding site with an own attached forum and proclaiming that's ok because "mod was abandoned". Also, we are talking about technical and compatibility changes and bugfixes. Closing holes as I did for NTotSC is borderline - I only did it because many people already put effort in this revised version and adding a functioning journal system and closing dialogue holes seemed like a "fix" to me. Adding new content or changing / removing content because you don't like it is going too far.