Mike1072

You could do it with a for loop. (You'd use OUTER_FOR.) The SAY command is what's adding strings to dialog.tlk, not COPY.

Check out the home page of Larian Studios, developers of the Divinity series. http://larian.com/ The .mp4 file on the page has this this information embedded in it: <dc:title> <rdf:Alt> <rdf:li xml:lang="x-default">BaldursGate_logo_III_retouched.png</rdf:li> </rdf:Alt> </dc:title> <photoshop:TextLayers> <rdf:Bag> <rdf:li photoshop:LayerName="©2019 Wizards of the Coast. All rights reserved. Baldur's Gate," photoshop:LayerText="©2019 Wizards of the Coast. All rights reserved. Baldur's Gate, Dungeons &amp; Dragons, and their respective logos are registered trademarks of Wizards of the Coast LLC. ©2019 Larian Studios. All rights reserved. Larian Studios is a registered trademark of Arrakis nv, affiliate of Larian Studios Games ltd."/> <rdf:li photoshop:LayerName="GATHER YOUR PARTY" photoshop:LayerText="GATHER YOUR PARTY"/> <rdf:li photoshop:LayerName="GATHER YOUR PARTY" photoshop:LayerText="GATHER YOUR PARTY"/> </rdf:Bag> </photoshop:TextLayers>

Wow, that's weird.

Everything on GitHub revolves around using git. Where are you getting your stats on these casual users?

Oh, it's because your window is too small.

I see it there.

I disabled Gravatar in the settings, which may be why your avatar disappeared. Gravatar will no longer being supported in future versions of the forum software, so I was getting a head start. You should be able to edit your Profile by clicking your name in the top right, then clicking Profile, then clicking Edit Profile on your profile page.

There are many different implementations of regular expressions. The different implementations each have their own syntax and support for different operations. @AL|EN 's site may be helpful to learn some of the concepts, but keep in mind that, by comparison, WeiDU's regular expressions are relatively basic. They also employ a different syntax. This is the full explanation of regular expressions from the WeiDU readme:

We can delete your account, but we'd prefer to preserve your posts. I don't believe they contain any personal data. Is this acceptable?

Quotes from the relevant posts (initial report and fix). So, the original issue was that BG1NPC was creating its version via COPY_EXISTING, but assigning a new description that matched the unmodified abilities. Therefore, the item description and abilities did not match up. cmorgan's fix was to include a version of the unmodified item in BG1NPC to ensure the description would be accurate. This is still how it is being done today: https://github.com/Gibberlings3/BG1NPC/blob/21764e059231e36240ea10513f1f6af6ee2003e4/bg1npc/bg1npc.tp2#L613-L618

Yes. Any time that variables are assigned (except within functions), those variables can be accessed anywhere. You should still have access to SOURCE_RES. If you were writing a generic patch function, you might not want to rely on it (since it can easily be overridden by an INNER_ACTION) but for something simple like this, it should be okay. That being said, this works perfectly fine as an action function.

/* fetch DV for exampe.cre */ COPY_EXISTING ~exampe.cre~ ~override~ READ_ASCII 0x280 exampe_dv PATCH_IF ((~%exampe_dv%~ STRING_EQUAL ~~) OR (~%exampe_dv%~ STRING_EQUAL_CASE ~none~)) BEGIN TEXT_SPRINT exampe_dv ~%SOURCE_RES%~ WRITE_ASCIIE DEATHVAR ~%exampe_dv%~ #32 END BUT_ONLY This also could/should be rewritten into a function. I'm on mobile right now which makes writing code painful so I'm not going to do that now.

Click the Settings button on the repo's page, then find and enable GitHub Pages by selecting the Source (screenshot here). If your GitHub account name is ABC and the repo name is XYZ, the site will be found at https://abc.github.io/xyz/.

Maybe it's related to htmlpreview? @K4thos could enable GitHub Pages for this repo. Doing so would remove the need for htmlpreview.

I mean, if a mod changed the DV of a joinable NPC, yes. But I don't see any instances of that here.

In that case, I'd scan both SPWI files (that aren't excluded by HIDESPL) and scrolls for 147 effects. You could do some checking to make sure that the spells are valid, but it sounds like nothing bad would happen if you included something that they can't actually get. Edit: I wanted to mention that I don't believe SPELL.IDS has any effect in determining which spells are shown to players at chargen - it's all dependent on the filename.

Any of those three methods might be prone to both false negatives and false positives, in an unpredictable modded game environment... I suppose I could just combine a couple of them, and make a master .2da list of learnable wizard spells... My first instinct would be to use filenames. You might want to use filenames & 147 effects. The big decider is how important it is that you catch every possible spell that a player could learn. Are you aiming for just wizard spells or wizard and sorcerer spells? What about spells added in CLAB files?

Not sure what that error is, but there is an issue with READ_2DA_ENTRIES_NOW row cols. The second parameter is the required column count. Instead of using cols (which doesn't appear to be defined), you could put a 1 there. However, the entire section of code in the previous post could be replaced with this: OUTER_SET prepared_spells_state = IDS_OF_SYMBOL (~splstate~ ~D5_SPL_PREP~)

Check out GitHub Pages. It's what we're using in our Documentation repo.

You should be starting with a blank .baf file. Having the SPWI101 block in there means you have to take extra steps to avoid adding a duplicate block later. APPEND is generally for game files. You don't really need your .baf file in the override. You can use APPEND_OUTER to append to files that are not in the override. It may even work with inlined files, which would simplify things.

For what it's worth, the previous SR spell descriptions were also generated automatically.

Yes, but then nobody would be able to paste any formatted text. It's up to you to either paste it unformatted or click the button that removes the formatting.

For clarity, we don't have any rules about that require you to be civil or avoid name calling. We encourage that, but you're free to do as you choose. Our major rule is no spam. It's rarely an issue for anyone who isn't a spambot.

I've had a discussion about this in the past.