Jump to content

Bartimaeus

Modders
  • Posts

    2,494
  • Joined

  • Last visited

2 Followers

About Bartimaeus

Recent Profile Visitors

6,900 profile views

Bartimaeus's Achievements

  1. The "Add 9 new arcane spells" component causes installation to error out on SPWI466.spl, but I'm not sure what the exact issue is: I've read the readme for ToF and that component adds some new arcane spells, but none to the 4th level, so I'm not sure why it could even conceivably be an issue for that particular component. Deleting SPWI466.spl allows installation to proceed...and restoring it after installation is complete prevents Polymorph Self from being broken, and it doesn't need to overwrite anything. I installed every other component of ToF and did not run into any installation issues (besides a few harmless-looking warnings anyways). Let's see if I can drill down the issue by deleting chunks from the relevant .tpa until it passes... Okay, it's "create_boneguard" that is causing the installation failure. Preventing the "create_boneguard" LAF from running allows installation to pass. What's in create_boneguard? DEFINE_ACTION_FUNCTION create_boneguard BEGIN // sanity check ACTION_IF VARIABLE_IS_SET "WIZARD_MONSTER_SUMMONING_7" BEGIN LAF make_label STR_VAR label="dw#createboneguard" END // tell SCS it's installed // clone the wrap spell (note we're assuming the spell has a subspell to handle Timestop issues) WIZARD_CREATE_BONEGUARD,WIZARD_CREATE_BONEGUARD_SCROLL=spl.copy["%WIZARD_MONSTER_SUMMONING_7%"=>WIZARD_CREATE_BONEGUARD|icon_base_name=boneguard_ icon_location=icon force_extended:i=0] [ m_name:=@50 m_description:=@51 m.spl_enforce_school{necromancy} ] ACTION_IF FILE_EXISTS_IN_GAME "%WIZARD_MONSTER_SUMMONING_7%A.spl" BEGIN COPY_EXISTING "%WIZARD_CREATE_BONEGUARD%.spl" override LPF ALTER_EFFECT INT_VAR match_opcode=146 STR_VAR resource="%WIZARD_CREATE_BONEGUARD%A" END OUTER_SPRINT resref_payload "%WIZARD_MONSTER_SUMMONING_7%A" OUTER_SPRINT resref_payload_new "%WIZARD_CREATE_BONEGUARD%A" COPY_EXISTING "%resref_payload%.spl" "override/%resref_payload_new%.spl" END ELSE BEGIN OUTER_SPRINT resref_payload_new "%WIZARD_CREATE_BONEGUARD%" END spl.edit[%resref_payload_new%] [ m.ab_fx.alter{s_opcode=177 s_parameter2=2 s_probability1=50 s_dicenumber=0 s_dicesize=0 s_resource:=dw#spbgd|match="s_opcode=331"} m.ab_fx.clone{s_probability2=51 s_probability1=100|match="s_opcode=177" number:i=2} ] eff.make[dw#spbgd] [ m_duration=2400 m_timing=1 m_resource:=ms7bgrd m_resource2:=spraised m_target=1 m_opcode=67 ] log_this[%WIZARD_WAIL_OF_THE_BANSHEE_SCROLL% %WIZARD_CREATE_BONEGUARD_SCROLL%|file=arcane_spell_maps.2da] // tweak monster file cre.copy[ms7bgrd|source_locbase="iwdspells/copyover/wizard_monster_summoning_7"] [ m_both_names:=@52 IF {!is_iwd} {{ m.cre_swap_scripts{gnsummm=>bdsum00} }} m_xp_value=0 m_allegiance:=controlled m_str=21 m_dex=16 m.fx.delete{s_opcode=233} ] END END Letting it to run but taking out just this small chunk... // clone the wrap spell (note we're assuming the spell has a subspell to handle Timestop issues) WIZARD_CREATE_BONEGUARD,WIZARD_CREATE_BONEGUARD_SCROLL=spl.copy["%WIZARD_MONSTER_SUMMONING_7%"=>WIZARD_CREATE_BONEGUARD|icon_base_name=boneguard_ icon_location=icon force_extended:i=0] [ m_name:=@50 m_description:=@51 m.spl_enforce_school{necromancy} ] ...allows installation to proceed. I'm really not seeing why this bit would be in any way problematic. (e): WIZARD_MONSTER_SUMMONING_7 was disabled from being installed in base SR (for a few reasons - they summoned basilisks which were either too powerful or completely useless, and there was a need to appropriate its scroll for Gate IIRC), but it is installed for SRR (which creates and places scrolls for it while also changing it to Greater Wolfweres...which are still probably problematic but a lot better than basilisks). Similarly disabling Monster Summoning IX from being installed on SRR's side also 'fixes' the issue (because now this entire chunk doesn't run), but now how do I fix the issue between SRR and ToF without completely disabling MS9? And why the error about SPWI466.spl of all things? And disabling MS9 from being installed but then installing ToF's IWD arcane spells makes the same SPWI466.spl installation failure start appearing again, presumably because that component adds Monster Summoning IX (or VII - whatever, the 9th level version) which then allows this Create Boneguard LAF to run. I really don't get the SPWI466.spl connection and how/why ToF is trying to do anything with it from here (presumably there is some function buried deeper that I can't seem to find). If only weidu would tell you why a file is being loaded... Stumbling around in the dark sucks. (e): I just thought of a much better idea: instead of using the "SPWI" namespace for any new polymorphs (which was a silly decision in the first place!), I'm just going to rename them to "DVWI" instead. Survey says...that it successfully fixes the issue. Righty-ho, that's a hell of a lot simpler than attempting the divination and ritual blood sacrifices necessary to figure out what the heck goes on in ToF/SCS, . The latest repository/master version of SRR should have the issue solved, @neuroghast.
  2. That comes from the SR master, right? Unlike the SRR master, the SR master is not really built for being downloaded and installed by users (note that there's no weidu setup included to even install it and you'd have to get your own), but it will have all the very latest changes to SR if any have been made compared to the latest "release" package. If you're installing SRR over it, I'd just use one of the latest releases instead. GitHub projects are managed differently from one to the next - sometimes the master is the best option to use (as I would say is the case for my projects), sometimes you should really stick to the official releases.
  3. Yes. When you "install"/extract the distributed .exe to your game directory, it'll create a "setup-spell_rev.exe" and "spell_rev" folder in your game directory. The idea with SRR is to overwrite that .exe and folder with SRR's own (keeping whatever files SRR hasn't modified but overwriting the ones that it has modified), which yes, should theoretically also allow you to use an automated installer to install the same components as you would for an SR install. The version of SR used as the base does not matter, as all relevant files are overwritten anyways (assuming that it's beta 18 or later).
  4. Yes. ToBEx fixes those problems on an engine level (i.e. it should catch every source), whereas SR just applies a global patch to petrification that should catch all vanilla-game but not necessarily all mod-added sources of petrification added after SR is installed (and it doesn't try to fix the disintegration and freezing issues - well, it changes the Disintegration spell to not actually use the disintegration effect, but any other source of disintegration that does use the disintegration effect would still destroy all items without the ToBEx fix). There's not really too much reason to not use those ToBEx fixes...not unless you want items to be destroyed, anyways. No idea about the "compatibility issue", but I've used the latest version of ToBEx as well as ToBExAl and can't say I've ever noticed any glaring issue. I wonder if maybe there's an issue of those ToBEx components force-dropping creatures' inventories in a misapplied/inappropriate situation or something, but I'm really not sure, it'd be better to ask the mod author Insomniator...but I think they haven't logged back in since SHS went down for a number of months.
  5. I don't know about IWDification, but SRR should be fully compatible with 1pp (no matter whatever components you use - assuming you install 1pp before SRR, as suggested in SRR's readme). The impact of 1pp on SR/R is not nearly as great as that on IR/R, but SRR should take advantage of 1pp's visual changes/additions.
  6. Circumventing the start of BG2 taking away all of your items is going to present many more duplicates (e.g. The Helm of Balduran), if that's what you mean. Don't think that's really something IR can control.
  7. The player can find but cannot have two copies of the item: as mentioned in MikeX's post above, one HAMM04.itm is in BG1 (Ulgoth's Beard), and one HAMM04.itm is in BG2 (de'Arnise Keep...in the golem room, I think). With the very few amount of enemies set as "Giant Humanoid" in BG1, I'm afraid that's not really the case. The complete list: HACK, OOPAH, PLYOGRE, OGRECO, ARGHAI, OOPAH2, OGRE, GOLEMF, GOLEMF2, OGRE02, GORF. And it's only obtainable in Ulgoth's Beard...after you've cleared Durlag's Tower. I've checked all of these, and it pretty much leaves just Gorf as a potentially valid target to use its unique ability upon - contrast that with BG2, which has over 200 different creatures set to "Giant Humanoid". There's another factor I'm not super fond of: Dwarven Thrower already pretty much has this item's property, with its +5 damage to ogres and giants, which means two hammers with close to the same unique property... I suppose one will never intersect the other, since Dwarven Thrower is in BG2 and the Knee-Capper will be in BG1, but it's still less than ideal. Hammer of Corrosion, on the other hand, still potentially has value even that late into the game, as its properties are decently attractive in BG1 even only at +1 enchantment. But additional critical hit chance, I think that'd be just about alright to add given the item's description, and the vs. giant humanoids property can just be flavor more or less. Additional critical hit chance is a little overused for BG2, but I think it's just Backbiter, Long Bow of Marksmanship, and Heavy Crossbow of Accuracy that have it in BG1, so... Though in IR's property system, I don't think it'd be called "Massive". Actually, the Martial Staff is the only crushing weapon that has additional critical hit chance in IR/R, and that property is called "Impactful", which I always thought lacked a certain...well, it's not "Keen". Never could think of anything I liked better though, so it's tough to criticize.
  8. @MikeX @Salk 1. I don't think its original stats make a compelling case for a restoration given its weakness and location. At the point where you obtain it, it is effectively just a War Hammer +1 as you have already fought almost all the giant humanoids that you'd face in the game, with maybe just a couple of exceptions (e.g. Gorf in the Undercity). 2. It would require writing a new description for The Hammer of Corrosion, which has stolen and mangled The Knee-Capper's. I'm not against the idea (I've done similar such things for other items which had straight replacements by IR), but given the two issues here, I think it would need to be properly workshopped to make it worthwhile.
  9. They're not SR/R spells, no, but there are other spells in IWD that are also not touched by SR/R either, and more what I question is whether SRR can safely overwrite those summoning spells without issue. Polymorph Other was added to druid spellbooks by SR, but I believe SR actually has it as a 5th level spell, whereas I moved it down to 4th level for SRR because I felt it didn't adequately compete at 5th level. Though given the dearth of offensive spells at 5th level for druids, maybe it would've just been better to just fiddle with the numbers instead. From what I could tell, yes. I installed only that NPC mod, and Holvir came with two different versions of Protection from Evil.
  10. I installed the NPC mod you linked: are you seeing it on that mod's Holvir NPC? Because I installed that mod without SR at all and that's what his innate abilities look like to start with, whereas the Undead Hunter that the game starts you with and a self-made paladin that I created both looked right when SRR is installed. Druids are supposed to have Polymorph Other at 4th level, yeah. The double Resist Element, not so much. The question with the summoning spells is whether or not SR's Animal Summoning spells should overwrite them or if they should just co-exist to make sure there aren't any issues.
  11. Thanks for the report: Bhaalspawn ability resources will no longer be installed on IWDEE games. These didn't look to be resources occupied by anything on a vanilla IWDEE install anyways, but if the game is inexplicably adding them to your characters when they do exist, then I might as well just make sure they're not installed. SPCL212 is supposed to be Protection from Evil in IWD, not Detect Evil. It will no longer be installed for IWDEE games. A note here about SRR's innate abilities: these are not always given full descriptions, as descriptions were not ever visible for innate abilities pre-EEs. In the case of base class abilities, I should probably make an effort at some point to include them. I've looked for other similar erroneous overwrites, and I have identified a few BG1 NPC abilities that are problematic (e.g. Safana's Charm Person ability will overwrite IWDEE's Eye of the Sword). Like the previous Bhaalspawn abilities, these all have now been disabled from being installed wholesale for IWDEE games. I don't see any other problematic innate/class abilities, but I could be wrong. Couldn't confirm the "Mage Armor causes Stoneskin visual" bug, I'm afraid: the normal graphic seemed to play just fine for me. I'm not familiar with the NPC mod, but with the way that the spellbook-fixing component is coded, I don't really see any reason that the component shouldn't work for IWDEE. Although just because I don't currently see why it wouldn't, doesn't mean I'm right. I tested its installation on a vanilla IWDEE game and it essentially did nothing, but that's because on a vanilla IWDEE game, there aren't any party members for it to edit. I've opened it up to IWDEE games in the very latest repository version for the time being - if you ever test it and it's horribly broken, be sure to let me know, but I think it should be perfectly fine. Again, thank you for the testing and detailed feedback!
  12. I think the last time I played Werewolf Island, I slew the Loup Garou or whatever it was called, went back to the town, and talked to Kaishas, which turned the whole town hostile. I still had that lady's baby, who turned into a werewolf before I could hand him over to her, but I was able to talk to Farthing and give her the doll...right before she transformed into a werewolf and I had to kill her. The whole island is probably some of the shabbiest content in the entire BG series, and it's setup very badly in terms of mechanics, writing, and outcomes. I guess I at least got an adopted son and doll out of it.
  13. According to GitHub, I replaced SW1H54.itm (The Equalizer) with a new version that was...exactly the same size, which it should not have been if I had uploaded the correct version with those opcodes removed. ... So I previously mentioned that my normal program for managing and updating my repositories wasn't working anymore due to licensing changes with that program, but I'm happy to report that I found a workaround a while back that will hopefully prevent something silly like this from happening again, though obviously I didn't notice this specific issue with The Equalizer here. Thanks for staying vigilant, and presumably you know how to remove those 319s yourself.
  14. Depends on how familiar you are with making changes to mods, I suppose. Here is the relevant section for Vitriolic Sphere from SR's spell_rev\components\main_component.tpa: Here it is for SRR: Here is how you would want it to look: You'd want to include all relevant and modified files here from SRR are in the right place within your SR installation folder (i.e. SRR modifies spwi427.spl, dvvtrsph.pro, and dvvtrsph.spl, so make sure you retrieve those from the SRR package and overwrite their SR counterparts). Next, you'd want the description of the spell from SRR to replace the normal SR description in spell_rev\languages\arcane.tra: Doing all that, I think it'd be good to go to install SR's main component and get SRR's Vitriolic Sphere. No guarantees, though. I suppose you should also change the description to say "20" feet instead of "10" feet, as that would be the doubled notation for SR (SRR's Vitriolic Sphere explosion is the same size as a Skull Trap, whereas SR's is half that size).
  15. The low hum sound effect? That's tied to the pink cylinder graphic. Removing the pink cylinder effect (opcode 156) from the spell would work...or replacing whatever is the sound file with a blank .wav would as well.
×
×
  • Create New...