JCarter426

What exactly are you trying to do? If you want to change what the item is, like change its stats or description or appearance or whatever, you only have to edit the UTI file for it. It doesn't matter how many stores carry the item; the edits will to the UTI file affect all instances of the item, so long as you load up a save from before the item was created in the game world. If you only want to change one specific instance of the item - in other words, have Suvam sell item A and later item B - then you need to edit the store UTM file. Just as you said, make your own copy of the item with a resref and then edit the UTM to point to the new item. But this is only necessary if you want to do it.

View File JC's Jedi Tailor for K1 Summary This mod adds a Trandoshan named Garassk who will tailor robes for the player and Jedi party members. He can change the color your robes to any of four options: brown, black, red, and blue. The items retain their stats, with only the appearance of the robes changed. The tailor also runs a clothing store with infinite amounts of some generic outfits, plus a select set of armor, gloves, belts, and headgear in smaller amounts. Some of the armor he sells is new; files for the items already existed, but they were inaccessible in the regular game. I've also given Garassk an extensive dialogue tree, so you can ask him the usual questions about the planet, and he will react to certain quest states. To start, Garassk may be found in the hangar of the Jedi enclave on Dantooine. Later in the game, he moves to Anchorhead on Tatooine, down the street from the Czerka office. You will need to start a new game or load a save from before you first arrive on Dantooine for the mod to take effect. Installation Run Jedi_Tailor_K1.exe. Click "Install Mod" and select your game directory (default name SWKOTOR). Uninstallation Remove the installed files or replace from backups if necessary. Compatibility This mod patches the modules danm13 and tat_m17aa and may not be compatible with other mods that affect those areas. This mod includes an icon fix from my Mandalorian Armor mod. If you use both mods, or some other mod that fixes that icon, then you can ignore the warning about that file being skipped. This mod is compatible with my Robe Adjustment mod, allowing you to change the color of the Apprentice Robes, but you must update the Robe Adjustment mod to version 1.1 or later. This mod is compatible with my Cloaked Jedi Robes, Cloaked Hybrid Robes, and Cloaked Party Robes mods and includes a compatibility patch for the 100% Brown color option of those mods. It adjusts the tailor's dialogue to make all references to robe color consistent with the brown shades in that option (brown, black, buff, and grey). The tailor will only recognize the original game robe items plus the variants the mod adds in the four standard colors. This mod may be compatible with other mods that add new robe items, but the tailor will only be able to swap around the old kinds. The tailor will only perform for the player and standard Jedi party members (Bastila, Jolee, and Juhani). Credits KOTOR Tool – Fred Tetra TSL Patcher – stoffe, with updates by Fair Strides CSLU Toolkit – Center for Spoken Language Understanding, license courtesy Jenko Jenks DeNCS – JdNoa & Dashus DLGEditor – tk102 ERFEdit – stoffe, with updates by Fair Strides K-GFF – tk102 LipSynchEditor – JdNoa Permissions I hereby grant nobody except myself permission to upload some or all of this mod anywhere for any reason. For any reason. If you would like to include any part of this mod in anything, then please contact me for permission. Disclaimers OBSIDIAN IS THE NEW BLACK. DON'T WEAR BIOWARE AFTER LABOR DAY. Donations If you enjoy my mods and would like to show your support in a monetary manner, you may do so via PayPal with this donation link. For various legal and ethical reasons, this is entirely optional and is not a requirement to downloading or using any of my mods. I also do not create specific mods for hire. I make mods as a hobby and will most likely do so regardless of any donations or lack thereof, but modding does take up a lot of my time and every bit helps. Submitter JCarter426 Submitted 05/26/2019 Category Mods K1R Compatible No  

I believe @zbyl2 tried it a while back and reported that it didn't work.

I'm not familiar with that mod. What is the problem exactly?

Right, it can only add new lines. There's no way to combine two pre-edited TLKs at the moment except through manual editing. @Fair Strides was working on an update to TSLPatcher to resolve that, but that is pending his busy schedule.

That works, yes, but currently TSLPatcher's functionality for patching TLK files is limited. It can't edit text in existing lines - only add new ones. So any hard edits to TLK files are incompatible with each other. You have to pick one to use, and it has to be installed before anything that adds new lines. So it is still recommended to patch in new lines for small edits.

The part you want to change is in the NSS file: Location(Vector(11.85, 15.91, -1.27), 0.00) The Vector() part is the XYZ coordinates. You can get the new set of these with the whereami cheat. The last number is the bearing, in degrees. You kind of have to guess with that, as the game is inconsistent about whether 0 degrees means north or east. I'd suggest leaving it as 0.0, and then if it's facing the wrong way, try 90.0, 180.0, or -90.0 as needed. Of course you can give it any angle in between, as well. Once you have edited that, you need to compile it into an NCS file and replace the existing one. There should be a tutorial for that either on this site or in the LucasForums archives here.

For now, I'm working on higher-poly designs of the default KOTOR hilts. I have more extensive plans in the long term, though, and have a thread going for it here. That link goes to the most up to date info of my plans, I think. I put everything on hold because I thought technical difficulties would force me to change everything, but I eventually sorted that out. Just a matter of modeling the hilts now.

If I do, certainly. I'm working on some other hilts right now that I want to finish so I can release them as a mod, so I may take a look when those are done.

Just to be clear, are we talking about this one? I'm not making any promises yet, but I've been learning how to model lightsabers and might be up for it.

Extract entire RIM file for both of the module's files (e.g. end_m01aa.rim and end_m01aa_s.rim) to an empty folder somewhere. Open the GIT file in K-GFF. Go down to the placeable list and copy an existing struct. Paste into the placeable list. Edit the new struct's details. For the resref, use the file name of your new UTP. (You'll have to make a new UTP of course, but that's the same basic procedure.) When you're done editing, save. Create a new MOD file with ERFEdit (e.g. end_m01aa.mod). Drag all the files you extracted in step 1 (along with the edited GIT) into the ERFEdit window, then save. Install the MOD file to the modules folder. The changes will only take effect if you start a new game or load a save from before you ever visited the area in that run of the game.

Extract the UTC file and open in K-GFF. Find the equipment list and copy an existing struct. Paste into the equipment list. Check the ID of the inventory slot in nwscript.nss. Enter this as the ID of the new struct and change the resref to the file name of the item. Save and install to Override or in a .mod.

Yes. That's on the texture's alpha channel (e.g. TorKirals.tga). The RGBA color space has four channels: Red, Green, Blue, and Alpha. The first three channels determine the color. The color isn't stored as a single value (because math and computer science and stuff) but instead is split into three primary colors, with a channel for each color. Each channel is a black and white image (that's a better metaphor anyway) that just says how much of that color there is, with a range of values from 0 (black) to 255 (white) for 8-bit channels. These channels are interpolated from black and white to red, green, or blue, and then the three colors are combined to produce the final image. Like so: The alpha channel is an extra channel. Rather than adding to the color, it's used for other things, usually transparency. In this case, the alpha channel determines the intensity of the shader. In Photoshop, you can access the channels with the Channels panel: The game textures generally have alpha channels, but if there isn't one already, you can add a new one in that panel. You can click on any channel to edit it individually, and click on the RGB channel group at the top to return to RGB space.

Yes, it should be fine. There is negligible difference between all the releases up until the Aspyr update. If you run it without that, it should behave more or less as the GOG.com release, or even the one true original 4CD release.

If you want to add a placeable via the GIT file, you'll want to extract and edit m01aa.git from end_m01aa.rim. Open the file with K-GFF, duplicate one of the existing placeable structs, then edit the details. After you're done editing the file, you'll have to compile it into a .mod and install it to the modules folder. Extracting all the files in end_m01aa.rim and end_m01aa_s.rim, put in your edited GIT, and then create a end_m01aa.mod file with ERFEdit and add all the files. If you're planning to release it as a mod, though, you'll want to configure it with TSLPatcher or else it won't be compatible with other mods that edit that area. If you add the placeable with a script, you only have to edit one file and install to Override, so that's somewhat simpler provided you understand the NWNScript language. The best course of action in this case is to find and edit an existing script, either the OnEnter script for the area (k_pend_area01) or a script that fires early on in the opening cutscene (such as k_pend_rumble01).

I have no idea, but I've always seen it unchecked, so I would suggest leaving it alone. I believe this is handled through the OnEnter scripts for the water areas. None of that is configured through appearance.2da. If you want to give Bastila items when she joins the party, you can either do it by editing her UTC file (p_bastila.utc in templates.bif) or the script that adds her to the party (k_ptar_bastpart.ncs in tar_m03af_s.rim). If you want those items to appear all the time for the later encounters, you should be able to edit the UTCs there as well, but if you want her appearance to be reactive to what she had equipped when she was in the party, that's a different matter. All instances of Bastila would have to be spawned with SpawnAvailableNPC() rather than from the existing templates. And that probably could be done, though it would be quite an endeavor.

If you want, you can make a new glow color too. I've attached an editable copy of CM_Bright. Just rename both those files, recolor the TGA to your liking, then change your head texture's envmaptexture semantics to point to your new cube map. CM_Bright.tga CM_Bright.txi

It probably would be possible to set up a particle emitter on the model and give it animations... but not really practical since it would have to be repeated for every head.

Gah, wrong thread, ignore this.

Shader data for a texture is handled through plain text. The game's TPC format combines the texture and shader data into a single file, though you can also have the shader as a separate file (TXI format). The game has various shader semantics, but it sounds like the sort of thing you want is an environment map (aka cube map). These are separate textures that get projected onto the model, depending on the viewing angle, for effects such as glowing and metal. I've attached an example TXI file, though it just looks like this: envmaptexture CM_Baremetal envmaptexture means use an environment map texture, and CM_Baremetal is one such texture. It's that simple. The game has various other cube maps in addition to CM_Baremetal, such as CM_Bright (blue/green glow), CM_SpecMap (wet), and mycube (HK-47's shiny plating). It's also possible to make new ones, and I believe there are some mod resources on this site that have more. The intensity of the shader is determined by the texture's alpha channel (more black = more shader). Note that you can only have one shader per texture. You cannot, for example, have a texture with parts that are metal and parts that transparent, as there is only one alpha channel for them to use. N_Mandalorian01.txi

No problem. 🙂 You came at a good time too, just updated it yesterday.

The K2 version is here.