NOTE: If you've previously installed the mod, remove it before extracting a new version. To do this, uninstall all previously installed components and delete the mod folder and executables.
Make sure the game is not running while installing the mod.
When installing or uninstalling, do not close the DOS window by clicking on the X button! Instead, press the Enter key when instructed to do so.
If you use SoD from GOG or Steam, you need to prepare your game with DLC Merger before installing any mods:
argent77's DLC Merger
For Enhanced Edition it is important that you istall the mod to the language version you are playing the game in. Otherwise, the dialogues of the mod will not show but give error messages.
The EE games are actively supported games. Please note that every patch update will wipe your current mod setup! If in the middle of a modded game you might want to delay the patch update as even after reinstalling the mods, you might not be able to continue with your old savegames.
Extract the contents of the mod archive to your game's main directory (BG:EE/SOD/BG2/BGT/BGII:EE/EET which contains the CHITIN.KEY file). On successful extraction, there should be an c#husam folder and a setup-c#husam.exe file in your game folder. To install, simply double-click setup-c#husam.exe and follow the instructions on screen.
Run setup-c#husam.exe in your game folder to reinstall, uninstall or otherwise change components.
Extract the mod archive, then copy the contents of the folder into your game folder (BG:EE/SOD/BG2/BGT/BGII:EE/EET which contains the CHITIN.KEY file). If properly extracted, you should have a "c#husam" folder, setup-c#husam, and setup-c#husam.command in your game folder. To install, simply double-click setup-c#husam.command and follow the instructions on screen.
Run setup-c#husam.command in your game folder to reinstall, uninstall or otherwise change components.
Extract the contents of the mod to the folder of the game you wish to modify. Download the latest version of WeiDU for Linux from https://github.com/WeiDUorg/weidu/releases and copy WeiDU and WeInstall to /usr/bin. Following that, open a terminal and cd to your BG2 installation directory, run 'tolower' and answer Y to both queries. You can avoid running the second option (linux.ini) if you've already ran it once in the same directory. If you're unsure, running tolower and choosing both options is the safe bet.
Run WeInstall c#husam in your game folder to install the mod. Then run wine BGMain.exe and start playing.
Husam NPC was implemented with WeiDU with highest priority to compatibility with other mods.
The mod is compatible with Imoen 4 Ever.
As an NPC mod, this mod should be installed after quest mods and before tweak mods. There is crossmod content included in the mod which should show if the install order suggestions are being followed.
To see most crossmod content, install the mod in the following order (other mods listed in alphabetical order!):
(at least the Crossmod component:) AFTER: Ajantis BG1 Expansion, Sir Ajantis for BGII, Alternatives, Brage's Redemption, Brandock the Mage, EET, Expanded Thief Stronghold, Imoen4Ever, The Boareskyr Bridge Scene, Transitions.
(main component:) BEFORE: Grey the Dog, EET_End.
Please note: For Husam to react to game events in SoD accordingly, the main component (Tracking System, 2nd component) of "Road to Discovery" needs to be included in your install (independent of install order).
Husam is a Shadow Thief from Amn, who was sent in BG1 to make sure the accusations against his guild regarding the murders where proven to be wrong. In the original game, he reveals himself to the PC near the end of BG1 and guides the PC to the real culprits.
The mod contains 3 components:
Component 1 is the main component that will insert Husam as an NPC into SoD and BGII. All other components are dependent on this one but optional.
As a second, optional component, the mod's portrait and soundset can be assigned to the original game Husam, as well. This will not change his very first line if met while he is still pretending to be drunk.
The 3rd component installs the crossmod with other mods and should be installed late.
The 4th component gives a choice of an alternate portrait by Acifer, which was the default portrait for the first releases. See below to have a look at the portraits.
Please note: For Husam to react to game events in SoD accordingly, the main component (Tracking System, 2nd component) of "Road to Discovery" needs to be included in your install (independent of install order).
In SoD, Husam will be standing in the BG East area (where Sorcerous Sundries is located), in the north at the bench. He will not approach the PC by himself.
Note that Husam will only appear if the PC worked with him in BG1 (or a new SoD game).
In BGII, he will be in Mae'Var's hideout.
Husam comes with friendship talks, own quest, and banters with some NPCs, and player initiated dialogues. In SoD, the latter offers the possibility to ask Husam about information with regard to Caelar's crusade. His "information services" are such that he will not spoil any details by himself, but only if the PC asks him directly. In SoD, Husam joins the PC to get firsthand information about the coalition - and the PC himself, about which he communicates completely open. In BGII, Husam will have lost his loyal rogues to Mae'Var and Irenicus. He will join the PC for revenge.
When first met in SoD, he will be a first level unkitted thief, but receives correspondingly experience points according to the PC's level.
If following as a "7th party member", Husam will gain XP automatically every time when rejoining the group if his XP are lower than the PC's.
Husam's alignment is Lawful Evil. He will not leave the group due to reputation.
His stats are the following:
- STR: 17
- DEX: 18
- CON: 16
- INT: 15
- WIS: 14
- CHA: 10
Husam's soundset are some of his original lines from BGII. I will replace this with a custom or more suited soundset eventually.
Husam's portraits were generously created and provided by Acifer. There are two portraits to chose from in an optional component, of which the default one is included in the main component:
Default portrait ----- Alternate 1
Husam wants to join the PC in SoD to get firsthand information about the coalition's doings. The PC himself has also aroused the interest of the Shadow Thieves - completely without obligation, of course. After joining, Husam cannot be kicked out of party - not even to wait for a short moment. Instead, he can be told to "stay close", which will free his party slot and make him follow as "7th party member". (Glitches and things to note with regard to this see below).
In SoD, Husam has his spies and informants, inside the coalition forces as well as the crusade. He can also be asked to get more information by the PC via player initiated dialogues. The information will be such that no crucial game knowledge will be just spoiled. They will either be available later, and the PC will have to explicitely tell Husam to reveal them.
In BGII, Husam needs to be freed from captivity. He will have lost his loyal rogues and his standing with the Shadow Thieves and will join the PC's group to get revenge if asked to. In BGII, he can be kicked out normally.
If you need the party slot for someone else, Husam can be kicked out of the party and told to "stay close", then he will follow as a "familiar" or, as I call it "7th party member". If in 7th party member mode he needs to join the group from time to time to level up. In 7th party member mode Husam can be selected and given commands, as well as told to use quick slot items. All his dialogues, banters, and interjections will trigger as normal.
To rejoin the group, talk to him and tell him you need "access to (his) inventory", and he will rejoin as a full party member. If you time this accordingly, the moment he is in group before any other kicked out NPC reaches the PC for his post-kickout dialogue is sufficient to let Husam level up and rearrange his spells and items, without having to finally kick out any other party NPC to achieve this. (Unless those just leave without a follow-up dialogue, of course.)
He cannot die while following as a 7th party member, but will remain at 1 HP. If Husam's HP fall to 1 HP during a fight, he will pass out. Healing him then will not change this. He will change to "neutral blue" so enemies stop attacking him. Once the fight is over, he will regain consciousness, be healed fully, and rejoin the party as a "familiar" as before. The full healing might be seen as a cheat, but it's one way to fix the engine behavior (not to call it bug) with Husam dying upon rejoining if his HP are too low.
The 1 HP drop out can be prevented if Husam is healed in time during a fight. If told to he will give a warning before his HP drop too low, but this seems to be buggy in BGT.
NOTE TO PLAYERS:
Unfortunately, the "7th party member mode" in the game requires special handling to accommodate all restrictions:
(The hints are a mix of the existing engine restrictions and the workarounds I used).
-The NPC has no "Clear Fog of War" around him in the 7th GM. So he can "disappear" in the "black" area of the map. Unfortunately, this can lead to Husam no longer be included in the "gather all party" button although he is still green circled and will return properly with the group as soon as he is seen by a full party member again. This is especially annoying if he loses sight of full party members because the AI wanted him to walk to whatever destination on a different path, and he needs to be searched for by walking the map until he can be seen again. This seems to be especially a problem if several "7th party members" follow, and with the old game engine.
-Items in the NPC's inventory are *not* recognized as items owned by the group. This is an engine problem. It follows that quest items that are needed in the game should not be in the NPC's inventory if they are to be recognized by the quest giver. Examples: Elvenhair's book, Ankheg shell for Taerom, etc.
-Quest items tagged as "critical" will be moved to the PC's inventory when moving to the 7th PMM. This may cause items from the PC's inventory to end up on the floor. This is an engine problem. As a result, you should always check after switching the NPC to the 7th PMM to see if items have landed on the floor!
-When new items are given to one of my NPCs in 7th PMM in a quest specifically for this NPC, they always appear in the inventory of the group or PC, even if the NPC is supposed to receive them. This is an engine problem. Even if I scripted it so that the items would end up in the NPC's inventory after the encounter, they would still be handled via the PC's inventory. And thus, items from the inventory may have ended up on the floor.
-For my NPCs, I have tried to have their own quest items (even if they are original in-game items, as long as they are necessary for my NPC's quest) recognized in the NPC's inventory as well. This works with the following restrictions:
-- All items in question are handled through the PC's inventory before they are either given to or received from a quest giver. This means that other items may have ended up on the floor.
-- If the item was in a bottomless bag (this includes all kind of bags, gem bags, bags for bottles etcpp.), then the item will not be removed in a dialogue with the quest giver. It is still in the bottomless bag afterwards and can cause problems if the scripting of the quest does not consider this (and assumes that the item should be gone).
-- 2. Problem with items in bottomless bags: If the item was in a bottomless bag, then the game crashes for unknown reasons if the NPC is to be taken afterwards into the group as a full member. This "crash bug" can be worked around by saving the game and reloading it.
This mod is unofficial Fan Content permitted under the Fan Content Policy. Not approved/endorsed by Wizards. Portions of the materials used are property of Wizards of the Coast. ©Wizards of the Coast LLC.
This mod is also not developed, supported, or endorsed by BioWare, Black Isle Studios, Interplay Entertainment Corp., Overhaul Games or Beamdog. All other trademarks and copyrights are property of their respective owners.
