JCarter426

You're right, they should use punchthrough. I likely typed additive out of habit, or copied an older file without checking. I had been planning to change all those from TGA/TXI to TPC format anyway, so I'll do an updated version soon.

Aww. ❤️ But, hmm. As far as the icon goes I just forgot that. It's a separate texture file, which you can similarly figure out by checking the defaulticon column in baseitems.2da. The texture will be i + the defaulticon string + _0 + the texture variation, for example ia_class4_001 for the first light armor. These textures are in swpc_tex_gui.erf instead of the other ones. For the model, I'm not sure what you mean. You can't replace the model for just one item with a simple file swap. If you want to do that, you'd have to make a new line in baseitems.2da and then change the base item type in the .uti file, and even then you are still limited to one of the ten player models (A through J). So you could change the Republic mod armor from D to A-C or E-J, but you couldn't for example make it look like the Republic soldier armor without changing all other D models, because there are a limited number of available slots in appearance.2da. The only practical way to get around this is via a disguise item, like the Sith uniform, Sand People clothing, and Mandalorian assault armor. If you did want to replace all the D models, assuming you have your replacement models PFBC and PMBD already done, you'd have to install the .mdl and .mdx files for those, and replace every texture variation for every item on that model, of which there are 8 in K1. And that certainly can be done, but it isn't practical if you only want to change one item.

In K2, probably yes. In K1, probably no. I suggest using NWNSSComp instead. I've attached some batch scripts that'll compile all scripts in the NWNSSComp folder provided the games are installed or if you copy the corresponding nwnscript.nss file to it too. compile_K1.bat compile_K2.bat

It's a model. If you check visualeffects.2da, you should be able to get the model name (which is usually v_something) and edit the model from there. Visual effects are typically particle emitters, so you don't need much in the way of modeling skills to change something like the color.

I don't believe so. The closest thing would be to provide different options via the namespaces.ini functionality. This would give the user a dropdown menu so they can choose 1, 2, or however many extra feats, but you'd still have to set up each option individually.

Figure out the file name of the item. Cheat code lists like this can help with that. Open the item (.uti file) in KOTOR Tool. Most of them can be found in BIFs > templates.bif > Blueprint, Item. Determine the texture variation, which the .uti file will tell you. Determine the model letter. The .uti file will give you the base item type, which refers to a line in baseitems.2da. The bodyvar column (very far to the right) will give you the letter. Determine the texture prefix. Check the character's line in appearance.2da and look for the texture column that corresponds to the model letter (e.g. texc). Male and female textures are usually different, so you'll probably have to get both. For player items, they're usually PFB-something & PMB-something. Add the texture variation number at the end of the prefix and you have the full texture file name (e.g. PFBC01 & PMBC01).

First of all, you don't need to and probably shouldn't change the race. In most cases, you also don't need to change the model. You were getting crashes because you entered a model that didn't exist. What you want to do is change your appearance line so it looks like this: modela texa P_BastilaBA XYZ_Bast And then take a copy of P_BastilaBA01, edit it however you want, and rename it to XYZ_Bast01. Substitute XYZ for whatever prefix you want, anything that guarantees it's a unique file name, not used by the game or other mods (e.g. I would go with something like JC_Bast or if I had to do several different ones, JC_BastA, JC_BastB, etc). Appearance.2da has essentially two options. If the texture cell is empty (****) then the model will only render any textures that are on the model. When a string is input (e.g. P_BastilaBA) it is used as a prefix for the texture. This gets added to the two-digit texture variation on the item (default 01) giving the final texture name (e.g. P_BastilaBA01).

That should be easy enough. You can do it in visualeffects.2da by looking for the entry with the model name (v_burnmark) and blanking it out with ****. Or if you prefer, swap the model out with an invisible one, like renaming a copy of plc_invis to v_burnmark.

This is a visual effect model, v_burnmark. But I think the issue there happens because it's clipping with the sand dune, and probably nothing can be done about it indeed, unfortunately. It's just down to where the visual effect occurs and the shape of the area.

I've never used the mod and don't know what it does, so I really couldn't say.

Nothing. The code is already there. Removing the comment characters transforms the in between block of text from a comment back into actual code.

// single line comment /* multiple lines with comments */ So you'll want to remove /* and */ to enable the code between them.

The semi-regular report on my extraneous activities continues. I spent the better part of March breaking and then fixing my computer, but there's some new stuff too. Here’s what’s been going on since last time: Updates Odyssey++ - Recent updates to Notepad++ radically altered the file structure, so I’ve updated Odyssey++ to keep up with that. New Mods Feat Fixes for K2 - Fixes some feat stuff for K2. Several feats weren’t available to certain classes for reasons unknown, and Finesse: Lightsabers didn’t do anything Finesse: Melee Weapons wasn’t already doing so it had to die. Security Spikes for K1 - Security spikes never did anything on the PC version of K1. I’ve replicated their intended function as best as I could, so when you use the item you get a temporary bonus to your Security skill. Or, if you prefer, you can choose the other option that removes them from the game altogether. Mandalorian Armor for K1 - Makes the wearable Mandalorian armor more consistent with other Mandalorian armor in the game so they follow the usual blue/red/gold rank system. Also fixes a few other oddities with Mandalorian-related items. Backstroke of the Old Republic - Edits all text in the game to provide a... different experience. Something Completely Different A while back, @A Future Pilot recruited @DarthParametric and myself to help with the next update to the K1 and K2 Community Patches. We’ve mostly been working on the K1 one first. AFP had a list of issues he’d been collecting since the last release, almost a year ago now, and we’ve checked off just about everything on that list. Between those and the other issues we found while fixing those, plus some more that were reported in the interim, I think we’ve easily doubled the amount content in the Community Patch. You can follow our endeavors on GitHub.