JCarter426

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.

In the mod's tslpatchdata folder, open changes.ini and configure it to automatically detect the path. LookupGameFolder=1 And make sure the right game is set. LookupGameNumber=1 for KOTOR 1, or LookupGameNumber=2 for KOTOR 2. I would guess that TSLPatcher detects the path from the registry, so if necessary you could also edit those with Regedit. 32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\BioWare\SW\KOTOR HKEY_LOCAL_MACHINE\SOFTWARE\LucasArts\KotOR2 64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BioWare\SW\KOTOR HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\LucasArts\KotOR2 Double-click the Path key and then change the path to what you want.

Is that Android? I don't know what the situation is on mods for that. The rest of the model is there, so unless you left out a file, I don't think it's anything you did wrong. Might be Android doesn't like the texture format, or the trickery I used to get the black to render in front of the white. I don't know how that would turn it yellow, though.

Sounds like the skin modifier got messed up at some point. If it were 3ds Max I'd try a skin wrap using the original model, but I'm not sure if Gmax has that option.

Select the Odyssey Base, then in the KOTORMax MDL Loading panel, select Import Anims Only and browse for a model that has animations. S_Male02 has most of them; I've attached an ASCII for it. s_male02-mdledit.mdl.ascii

Hmm, that is odd. They're definitely linked and exporting, but obviously something is wrong. What about loading animations onto the model in Gmax? It's possible the meshes are there, but the skin data is messed up and sending them off into an unseen part of the area.

Hmm, if you import the ASCII you exported back into Gmax, are the torso meshes there at all? If not, that means they either still weren't linked properly or failed to export for some other reason.

It might, or at least it did in the past.

Did you use the Fast Linker in KOTORMax/KOTORBlender, or just your modeling program's link tool?

Hmm, interesting idea. I'm not sure if those would be appropriate for the ones Zhar gives you though, so early in the game. Unless maybe you could upgrade them later. I have thought about adding more robe drops before; as I recall you can't ever get master variants of the red or blue robes. I don't have any specific plans yet, but I'll think about it.

View File JC's Robe Adjustment for K1 Summary This mod adjusts the way the player acquires Jedi robes during their training on Dantooine. There are two parts, which can be installed individually or together: Apprentice Robes: The player will be equipped with Apprentice Robes as soon as they begin their training (in the montage). The Apprentice Robes look like brown Jedi Robes, but have the stats of Basic Clothing, so this is merely an aesthetic change. These robes have no prerequisites and can be worn by all humanoids in the party, regardless of Jedi class. Early Jedi Robes: Master Zhar will reward the player with Jedi Robes once they have chosen their Jedi class and constructed their lightsaber (i.e. as soon as they have the prerequisite to equip robes). Originally, he only granted them after all the trials were completed. The early access will allow you to wear robes in combat during the final trial. Installation Run Robe_Adjustment_K1.exe. Select which version to install. a) Apprentice Robes b) Early Jedi Robes c) Both a) and b). 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 overrides the scripts k_pdan_jedi17, k_pdan_zhar03, and k_pdan_zhar06. It may not be compatible with other mods that alter the Jedi training portion of the game. Credits KOTOR Tool – Fred Tetra TSLPatcher – stoffe DeNCS – JdNoa & Dashus K-GFF – tk102 NWNSSCOMP – Torlack, stoffe, & tk102 And thanks to ebmar and DarthParametric for planning and reconnaissance. 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 THE PATH YOU HAVE CHOSEN TO WALK IS DIFFICULT. INTENSIVE TRAINING WILL PREPARE YOU PHYSICALLY FOR THE DEMANDS OF MODDING. MEDITATION WILL TEACH YOU TO CHANNEL THE POWER OF LUCASARTS. TO TRULY UNDERSTAND THE WAYS OF KOTOR, YOU MUST OPEN YOUR MIND TO KNOWLEDGE. SEEK WISDOM IN THE TEACHINGS OF THE GREAT MODDERS OF OUR COMMUNITY. A MODDER IS NEVER ALONE - OTHERS IN THE COMMUNITY WILL ALWAYS STAND BY YOU. YOU AND BIOWARE SHARE A SPECIAL BOND. DO NOT BE AFRAID TO TURN TO THEM WHEN YOU NEED HELP IN YOUR MODDING. THE WAY OF KOTOR IS DIFFICULT. IT REQUIRES GREAT DISCIPLINE. YET EVEN THOUGH YOU ARE A MERE END USER, YOUR POTENTIAL IS UNLIMITED - AND YOUR PROGRESS AMAZING. IN ALL MY YEARS I HAVE NEVER SEEN ONE WHO HAS READ THE README SO QUICKLY. YOU HAVE DONE IN WEEKS WHAT MANY CANNOT DO IN YEARS. I AM HONORED TO WELCOME YOU FULLY INTO THE KOTOR COMMUNITY. 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/04/2019 Category Mods K1R Compatible No