Bartimaeus

@WanderingScholar "SAY" is what is responsible for giving items/spells/creatures new names/descriptions, so if you comment out a spell like so... COPY ~spell_rev\spwi3##\spwi308.spl~ ~override~ // Lightning Bolt SAY NAME1 @515 SAY UNIDENTIFIED_DESC @516 COPY ~spell_rev\spwi3##\scrl1k.itm~ ~override~ SAY NAME2 @515 SAY IDENTIFIED_DESC @516 -> /*COPY ~spell_rev\spwi3##\spwi308.spl~ ~override~ // Lightning Bolt SAY NAME1 @515 SAY UNIDENTIFIED_DESC @516 COPY ~spell_rev\spwi3##\scrl1k.itm~ ~override~ SAY NAME2 @515 SAY IDENTIFIED_DESC @516*/ It prevents the spell and associated scroll resources from being overwritten with SR's main changes, which will additionally prevent any name/description changes as well. In practice, there are certain spells that will cause SR to crash and burn if you prevent them from being installed though, so beware that; generally, most should be okay, Lightning included (...I, too, sometimes miss the old bouncy lightning).

Being aware of and thankful for your circumstances is always a good frame of mind to occupy. Thinking of how different and how much harder your life would likely be if you were born at most any other different place/time in the world and throughout history should naturally induce such a feeling...as well as at least a little empathy for the others that were not blessed with your fortune, who from birth have always been on the outside looking in for one reason or another. Though that's also no reason to ignore that we can also strive for better, that we must strive to at least prevent the kind of encroachment that will inevitably makes things worse.

Dutifully noted, though I admittedly have very little patience for people who take undue pride in their (arbitrarily decided at birth) nationality and the related issues that come with it. But then again, probably just a hair less than half of the population of my own country would have very choice words for me indeed for my thoughts and feelings regarding said country. Hey, maybe I'm just a big ol' jerk with a little too long of a memory. So not counting today... 2017 December (weidu itself): 2018 January (BG2 Fixpack): 2018 February (Tweaks Anthology): 2018 August (IR): 2018 August (Tweaks Anthology): 2018 September (Tweaks Anthology): 2018 September (TBL): 2018 September (BG2 Fixpack): 2018 September (Tweaks Anthology) 2018 September (SCS 2018 October (TBL): 2019 January (TBL): 2019 Feburary (SCS 2019 April (TBL): 2019 June (SR): 2019 July (SR): 2020 Feburary (SRR): 2020 Feburary (SR again after I said "haha, no, never" in the SRR thread): 2020 April (IM10_Simd0): And the list keeps on going, but I don't want to read any more than that. Hey, uh...hey, maybe...maybe stop doing that. Yeah, you'd think it'd be a learning tool even for young native speakers. The multitude of sounds that letters can make in English is not at all conducive to getting a grasp over the language, and never mind loan words. You could phase out using them as you get older. Heteronyms can also be a problem where diacritics would be helpful. Read vs. read, as an example: one of them is pronounced with a short E, one with a long E...there are certain sentences where you can't accurately distinguish between heteronyms and the sentence is ambiguous as a result. Eh.

Sharp remarks? Just trying to have a friendly conversation about language and its proper use, .

I apologize that my language has borrowed one of the words from yours and transliterated a widely accepted variant without the pointless* diacritics, but that's the way she goes. *Note: pointless in English. I'm sure they serve their use elsewhere, but as English is entirely without them, it doesn't really make a whole lot of sense to use them. Given how inconsistently letters are used in English, it might prove helpful for those learning the language if it did have them, though...that might be a very useful learning tool if you're coming from a different language where they're the norm.

lmao If one is experiencing symptoms of deja vu...

lmao, think this poor guy had a couple of too many ales...or perhaps something else Although pretty different from the BG1/2 art styles (stylistically speaking, they remind me more of NWN1 than anything else - generally more natural looking lighting and colors than NWN1 would offer, though, which helps them fit in more with BG), they are quite neat.

I did not see this thread until just now, whoops. I don't believe it's possible that you could have seen that particular error regarding strrefs.tpa if you tried to install IR from your link, because the linked V3 does not contain any mention of "strrefs.tpa" in the entire mod: that's a V4 thing. Now I do believe you when you say that you got that particular error when you tried to install IR v3 + IRR, as you would receive that error (along with a great deal many others even if that error were fixed), because IRR is based off of and requires IR v4, and there are substantial differences between the two. As for why IR V3 failed to install in the first place...well, it would depend on what exact error you got there, but I just don't think it could've been the same strrefs.tpa error, as I literally did a complete search of every single file within the V3 package for that, and there was not a single mention of it...in contrast to V4, where it's one of the first lines of main_component.tpa, which is practically the first thing that runs when you try to install the main component of IR.

Mildly pointless note: that particular tweak comes from and is in base IR.

Not as far as I know, no; if anything, I think 4.19rc1 should be slightly more compatible with IRR versus b18 due to some slight compatibility additions for 4.19rc1.

Alright, best of luck. Not sure what to try with the bad file for the time being.

Well...that's very strange. The component is essentially "this list of AoE projectiles should bypass Mirror Image, so scan all .itm and .spl files to see if they use one of the projectiles from this list, and if so, set said .itms and .spls to bypass AoE; also, here are some special cases that we will manually set as well". If it only happened once, I'm inclined to believe it was just a bizarre fluke...probably. Did any other mods touch this file? I installed it straight from the link you provided (and confirmed that G#TFVAMP.cre was in my override) and then installed SRR immediately after, no issue. If some other mod touched this .cre, it may be that I need to install that as well to figure out what went wrong.

Thanks! So the Mirror Image Fix error suggests that it doesn't install because the Main Component wasn't already installed, so I think we can safely ignore that for the time being. Although that component really should still be installable even if the user chooses not to install the main component, so I'll have to fix that regardless; if I had to guess, that issue will occur in the non-Revised version of the component as well, because that chunk of code concerning sppr951d.itm has not changed between the official version and my version. The simplest fix would be to simply gate it behind a "make sure the file actually exists in the first place" check, which I'll implement. (e): Now implemented in the latest repository version, fixing that particular issue. The main component error is a little more...mercurial to me. Creature "G#TFVAMP.CRE" failed to patch correctly, but why is it being patched in the first place? Presumably some global creature patch (a patch that scans all .cre files and potentially makes changes to them depending on if certain criteria at met) at some point in the mod is failing on that particular creature, but I don't know which global patch, I don't know who/what the creature is (except that they're probably some kind of vampire based on the .cre filename), I don't know which mod the .cre comes from, and I don't know why it's failing. If you would be so kind as to do a changelog for that particular .cre filename to see where it comes from, it would be of great help for me to track down the issue; sadly, a Google search for it did not turn up even a single result. Possibly your spell_rev.debug and a copy of the .cre would help as well, though I suspect I'll have to use your changelog of the .cre and create an install that matches your install log in order to figure it out.

"Currently SRR doesn't apply to SR per latest update"? What exactly is spitting that out, and on what criteria? But yeah, I don't really know what the installation process of a mod looks like on non-Windows environments, I guess. From what I can tell looking at the .tar.gz files for both b18 and b19, the structure for both is identical, so I don't see why anything would have changed: https://dl.dropboxusercontent.com/s/3054q6gp3imvm6y/explorer_jbEyQgaTv7.mp4 In the past, I've created combined archives for people in the event of non-Windows OSes not being able to combine them correctly, so if you ever need that, just hit me up.

No, I've always disliked Find Familiar - for those reasons, and also because I prefer to control less characters (to this point, I usually only use a maximum of 5 party members), not more, and Find Familiar is obviously a bit of an antithesis to that in basically adding another semi-party member without much purpose. The thief-like familiars don't get ever good enough thieving abilities to make a thief unnecessary, and the caster-like familiars get a couple of utility abilities, but both are so vulnerable outside of like right at the beginning of BG1 that the hassle is not really worth the trouble. So you get your bonus HP and have the thing sit in your inventory 99% of the time...at least, if you're sane. I know there's at least one mod out there that revamps Familiars (though I haven't played around with it myself since I just...fundamentally don't like the idea of familiars), but I don't know about just killing the constitution/HP stuff.

Did it fail to install, or are you using some other measure to determine how cleanly it copies over? v4.19rc1 hasn't changed the process any here on Windows: https://dl.dropboxusercontent.com/s/qp17a23i25tgqd4/explorer_Ef3xgztbRJ.mp4

Find Familiar spell description: I personally think this mechanic (but also the mechanic of the caster gaining HP while the familiar is alive) is incredibly dumb, but Find Familiar is a difficult beast to tame between the different games, so I'm not inclined to touch it or its mechanics.

Welcome. So I installed the three mods that you listed as affecting this item. ~ITEM_REV/ITEM_REV.TP2~ #0 #0 // Item Revisions by Demivrgvs: V4 (Revised V1.3.860) ~CDTWEAKS/SETUP-CDTWEAKS.TP2~ #0 #1140 // Gems and Potions Require Identification -> Gems and potions: v15 ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ #0 #5900 // Initialise AI components (required for all tactical and AI components): 34.3 However, still no protection from normal weapons. You're welcome to place the resulting file in your override to fix the issue, though: https://dl.dropboxusercontent.com/s/j3yk099saccp8vi/ring97.itm As for why it happened in the first place...it's difficult to say.

This proves that IRR did not add it. The backed up RING97.itm in weidu_external\cdtweaks\backup\1140 is the file that weidu will restore if that component is uninstalled. Since this is the version of the file immediately after IRR changed it but before anything else has, that means that since the property is not there, IRR did not add it. It would have to be there if IRR was at fault, since all of IRR's changes to it have occurred by this point, but neither of CD Tweaks' or SCS's have. This is the precise purpose of using changelog and following when/how a file was changed by specific components by being able to look at the backups. So now the next question is if the backed up version of the file in the Stratagems component 5900 backup folder has it; if it does, that means the CD Tweaks component added the property. If it doesn't, that instead 99% suggests that the version of SCS you're using did it. While I am pleased to see that IRR didn't do it, I'm still going to be quite mystified if it turns out that the CD Tweaks component did, since that would seem to be quite out of scope for that component; if SCS did, that...would make more sense, except for the fact that I've literally installed SCS 34.3 after IRR in my current install, and it did not happen. Strange either way, really.

It's not intended, but also, RING97 doesn't give protection from normal weapons. Clearly it does in your game, but in mine with both IRR and SCS, it does not. It seems pretty unlikely the CDTweaks component would give it, so I'm a little stumped. If you could look at RING97.itm in the backup folder for CDTweaks component 1140 and see if it's still the case that it has the protection from normal weapons property, that would be helpful.

Seems likely it's just an issue of "this string reference is intended for BG2/EE, and it's something else entirely in BG1/EE".

Yeah, I was just thinking I really need to remember how to find this post in the future when somebody asks again, . Yes, I play with SCS, and have made some changes (such as the range of spells and some of the optional settings.ini switches) around it.

Nice job! Long-time coming, . Install order: For SRR, I recommend before Anthology Tweaks but after most other content mods, generally. But I admittedly play with a pretty pared down install without anything that majorly adds or changes the spell systems, so there may be notable exceptions I am unaware of. Probably only people who use them could tell you, though.

I've done SRR/IRR my way and without oversight, largely without comprehensive documentation (partly because I initially intended for them to be only for me, partly because the effort started long before it was hosted on GitHub, partly because fixes both minor/major and creative design choices all got jumbled up and intermixed and this makes documenting all changes very difficult and certainly impossible to decouple); this is highly problematic because SR and IR are simply not my mods. No ifs, ands, or buts about it. As subtledoctor is helpful to remind anyone who asks something like what you just did, the official versions of SR and IR still work, so you should only use SRR or IRR if the changes I've made appeal to you. And because of the problematic nature of its development, neither SRR or IRR will ever become the official versions: such a decision would have to be both community driven and with at least Mike's approval, and while Mike (admin on these forums and one of the two original developers for IR) has mentioned being open to the possibility, it seems unlikely at this stage that a kind of community consensus could ever be reached even if we wanted to determine a definitive answer about it. Which is precisely my great frustration with working on the official version with my two other custodians (subtledoctor and grodigrues): I can unilaterally implement changes to SRR/IRR immediately as soon as I have time and inclination, whether it's a fix or a new direction for a spell or item, and if somebody doesn't like it, they will come in here and post, and we'll have a discussion about it and I can revert or change it if necessary, which I have very frequently done when those types of issues have arisen. Likewise, if someone wants to see some kind of new change that I didn't think of yet, they can also come in here and suggest it and see how I and others feel about it, and possibly get it implemented quickly. With SR, even simple bug-fixing requires consensus between we three custodians (sometimes understandably so, because what seems to be an obvious "fix" to one of us the other two have, at times, vocally disagreed with and nixed), while creative decisions (i.e. changes that don't fall under bug-fixing) require "input from the community", and that has been...well, very difficult to get, so most changes are effectively off the table - see the initial post's spoilers at the bottom to see what kind of changes would be largely off-limits to bring to the official mod. Those changes are mostly non-negotiable for myself personally: I implemented them because I wanted them or other people wanted them, so obviously I am not willing to arbitrarily give them up for the sake of "well, we weren't able to reach a consensus about them". The community going against them I would accede to, but more what happens is that there isn't enough input of any kind at all, thus effectively placing the official versions in stasis for the most part. With the janky way SRR and IRR are installed, it necessarily requires that users know what they're installing, which I think requires a higher degree of awareness and involvement than if someone's just casually installing normal SR/IR while expecting them to be exactly what they're always been. After all, you have to, at a minimum, be at least lurking on these forums and visit the IR/SR sections and see the threads and read about them. I appreciate and value that level of initiative and involvement from the people who use or have used SRR and IRR. Conversely, if you are the mind that the official versions of these mods should not be changed except for bug-fixing (and people certainly do still use the official versions), then having all of my changes dumped and integrated into the official version would be a bit of a disaster for them, wouldn't it? So I am content with how things currently are. tl;dr: If you want SR/IR exactly as they've always been, it's probably not a good idea to use SRR/iRR: use the official versions instead.

https://dl.dropboxusercontent.com/s/xv31e0koue6nuc6/WeiDU.log This is the latest I've made.