pepoluan

OMG, you're right!! I had been looking at my Wisdom while wearing the $name Crystal. Thanks! Gosh, I feel stupid

If I remove the crystal from the lightsaber, the "[Wisdom] Attune crystal" line is missing... what gives?

That's awesome! I'm not a Perl programmer, though, so if you release the source code, I might not be able to assist much (not well versed in Perl ) Just some thoughts, hopefully can inspire you: My plan was to make the installer config optional, so if the installer config is not found in the same directory as the TSLPatcher.exe file, it will revert to the 'normal' behavior For the "modlist", I originally plan on simply creating a filter prior to the loop; the "modlist" would specify exactly the name of the sub-mod to install (the name comes from the "namespaces.ini" file?) The filter syntax I envisioned is 'glob-based' (instead of regex-based) with one prefix character indicating install or not, processed in order, e.g.: +* = install all sub-mods -*NAR = remove all sub-mods that end with the letters "NAR" (case-insensitive) +101NAR = install sub-mod with the exact name "101NAR" These three lines will result in installation of all sub-mods, except mods ending with "NAR", but will install "101NAR" I want to patch it also to unconditionally append to the installation log, recording the time of installation and which sub-mod got installedIf it installs multiple sub-mods in one go, it will first record the time of start and the list of mods after being filtered (see above), then for each submod installation record the time of installation and which sub-mod got installed Anyways, glad to hear that the TSLPatcher is not abandoned, yay! Feel free to hit me up if you need my help; I'll try to assist the best I can.

Where can I get the source code to TSLPatcher? I'm in the midst of installing a bunch of mods, and it's... mind-deadening tedium to keep selecting the Kotor2 folder under steam... So, I want to patch the tool to be able to read a "config file" telling where the Kotor2 folder is. And, if I have the time to do it, probably modify the tool enough to be able to tell it which mods to install (all, or a subset), so it can iterate over the list of mods to install rather than having the user running the TSLPatcher tool TENS of times (Example: The "TSL NPC Overhaul" mod which contains 60+ mods inside of it -- mind-numbingly tedious ). I might even expand the tool to be a full-fledged "Patch Manager" ... but that's more the long-term personal wish of mine

Okay, so my KotOR2 is Steam Edition, and I've "subscribed" to TSLCRM (that is, install the TSLCRM from Workshop). I plan on installing "Slender Bodies for Females" (+ its compatibility patch). Can I install this on top of "Slender"?

Okay, I think this is due to a conflicting mod, but just checking: In my game, before I met Ziagrom, Mika gladly offered me his goods. But after meeting with Ziagrom, Mika instead stopped selling his goods. Not that I need the goods, though, but this ... inversion, is kind of upsetting. Anyone can confirm the same bug, and what mods you're using? For the record, this is a list of the mods I have, in installation order:

BioWare's GFF files are simply... uhh... perplexing. I had... quite an interesting time trying to grasp my head around the ideas. So this post is kind-of a self-note for me. So, we have "Structs". Inside a Struct, there's a property "FieldCount" A Struct can have one "Field", in which case the "DataOrDataOffset" property contains an index to the "Fields Array", pointing directly to the lone field definition of that Struct. So far so good. But what's interesting is if a Struct has more than one Fields. In this case, the DataOrDataOffset property points to -- here's the key -- somewhere within the "Field Indices" section of the file. Then you get N elements from the Field Indices starting from the location that DataOrDataOffset pointed to (where N is = FieldCount above). In other words, the "Field Indices" list is an "unlabeled" set of Fields. It's a looooong list formed from the list of Fields used by Structs. Illustration: Let's say Struct 1 uses fields 1, 4, 5. Struct 2 uses fields 1, 2, 5, 6. Struct 3 uses fields 3, 4, 5, 6, 7. The content of "Field Indices" will be: 1, 4, 5, 1, 2, 5, 6, 3, 4, 5, 6, 7 Struct_1.FieldCount == 3 Struct_1.DataOrDataOffset == 0 (numbering begins from 0) Struct_2.FieldCount == 4 Struct_2.DataOrDataOffset == 3 Struct_3.FieldCount == 5 Struct_3.DataOrDataOffset == 7 WHew. Now, that's not difficult, isn't it? Now that I can (kinda) grasp the "major structure" and ERD of the GFF file, I should be able to parse dem files... And with this understanding, I also realize that I have to totally rewrite the logic of the current parser, to make things efficient and to enable a file validity checker. Huh. I need some rest.

Just an update on my project to create new modder tool: The .2da file parser works! Yaaay! This is the commit where the file parser works. Tonight (22:51 at my place as I typed this blog entry) I'm going to work on the .dlg parser. Especially because for unknown reasons KotOR Tools refuse to parse any .dlg files I have.