Fair Strides

Not possible at all.

I've always looked at the trick options like that as reasonable. You are trying to persuade them, but not everyone's going to be able to be persuaded to do something. For example, would you expect to ever be able to successfully persuade HK-47 to hug and love someone, or would you ever expect to be able to persuade a hardened criminal to go surrender to the TSF and confess their crimes? Some people just won't do something, and it's realistic that they reflected that with these automatic no options. And Zbyl, if you continue reading, you'll see that the guy gets absolutely fired up because this was supposedly the first persuade option you run into in the game and that it's shown to the player but never actually doable. He doesn't think a game should string you along, and he considers that facet of RPGs (what, no sense of humor with a game) to be something negative to the genre...

I'm thinking I'll have to re-structure the original mod installation (I've tried to avoid doing that), since I've noticed that the file in the override might have conflicts with other occurrences, so I'll need to make sure all .utc edits are in their own little modules.

Ideally, you'd have listed all your mods originally, as has been mentioned several times by reference of the READ-ME SECOND thread.

Frequently Asked Questions What is the KotOR Toolset? The KotOR Toolset is the culmination of 8 months of work (started March 1st, 2015 and released the Public Beta December 25, 2015, with breaks in between) that started out as 15 minutes of planning. I hope that this toolset will one day replace KotOR Tool as the modding standard. What are the system requirements? That you have at least 500MB of RAM (I've seen it use up to 340MB myself) and at least one KotOR game installed on your computer. Beyond that, it's a pretty simple package: no 3D rendering, no texture-editing, and any necessary libraries are shipped with the tool. What makes it different from KotOR Tool? To be quite blunt about it, it's for newbs. Unlike KotOR Tool, the Toolset is centered around level-editing using a top-down display of the game's collision maps as the surface of the levels. The Toolset also has editors for almost every one of the games' formats (no models, textures, texture info, or path files), some of which were neglected or never done with KotOR Tool. Something else that's different is that the Toolset tries to teach you by explaining what most of the editable things in a file are, and giving examples of how it's used in-game. What inspired you to make this? Inspiration? I'd call it a prolonged bout of insanity! I was four days into a month-long break from modding and was going crazy, so over the span of 15 minutes, I thought of how I could render the collision maps and then use a bounding box to find the overall boundaries of the collision maps to get a good viewer for the levels. After that, everything just snowballed. With thanks from Malkior, I also was able to obtain a PDF manual on how to use the Neverwinter Nights 2 toolset, and drew inspiration from its layout and structure. What if my question isn't on here? Then I would ask that you PM me your question and I will do my best to add it here promptly.

What bugs have been reported and how to report new ones! To report a bug, you MUST use the following format!: 1. What game(s) do you have installed, and what versions are they? 2. Where are they installed? 3. What does the log.txt file located in the same folder as the Toolset say (if possible, delete the file and re-create the bug)? 4. Is the bug repeatable? 5. What game mode was the Toolset in when the bug occurred? 6. What can you tell me about the bug? 7. Can you please upload your Toolset.ini file and log.txt file? Below I will try to record and link any bugs that have been reported, as well as organize them by severity and status.

I've had reports on both sides of the fence about the success of the installation, and there's literally only a few lines that were edited in the changes.ini. The parts that the installer keeps failing on aren't changed. What people can do: 1. Remove Read-only on the whole mod folder and subfolders and files. 2. Set the installer to Compatibilty Mode for Windows XP SP 2. 3. Run the installer as an admin.

Well, there was that time aboard her ship involving her, him, another man, and a blaster. As i recall, Obi-wan's words were, "If you had asked me... I would have left the Jedi Order."

If you find VAs (even if they cost some money), please be sure to let me know, as I would have a great interest in their services as well. "_"

scrysblu001.utp scrysgrn001.utp scrysppl001.utp scrysred001.utp scrysred002.utp scrysylw001.utp All found in danm14ae_s.rim.

Which modding tool didn't work?

Well, I'll need to know what you've done to the script before I can help. Please post the full script, surrounding it with

The DeNCS is just for decompiling the scripts. You'd need to copy what's in the window and then paste it into KotOR Tool's text editor or there's a Scripting tool in the modding tools section. .nss files are Script source files, but .ncs files are the Script compiled files used by the game.

Yes, it is possible. Below is a decompiled "k_pdan_saber16" script: Something to keep in mind: intGLOB_148 = 1 (Guardian) intGLOB_149 = 2 (Sentinel) intGLOB_150 = 3 (Consular) stringGLOB_4 = "g_w_lghtsbr01" Blue stringGLOB_5 = "g_w_lghtsbr03" Yellow stringGLOB_6 = "g_w_lghtsbr04" Green

If you get that error, right-click on the left window with all the numbers and spaces and select "View Source" or "View Code" or whatever it is. So... You want to know how to change the lightsaber you build?

1. You get to pick which crystal Dorak gives you, but if you're wanting something other than Blue, Yellow, or Green, then you'd need to either edit one of the scripts or add another option to the dialog with a new script. Blue crystal response uses k_pdan_saber12, Yellow crystal response uses k_pdan_saber14, Green crystal response uses k_pdan_saber13. These scripts can be found in the dan13_s.rim in KotOR Tool. 2. You would need to edit the k_pdan_cryst01, k_pdan_cryst13, k_pdan_cryst14, k_pdan_cryst15, k_pdan_cryst16, and k_pdan_cryst17 scripts in the danm14ae_s.rim in KotOR Tool. 3. That would depend on the level, but you could look for a .uti file or something in the level, or try looking at the level's On-Enter script... You will need DeNCS to decompile the scripts. DeNCS should be on starwarsknights.com.

I would assume yes it would work now. I just need to get one or two more things working with VP before I could think about releasing it.

The offsets could very well be there, but I could try compensating for that in 3DSMax. As far as Headfixer, it works by hex-editing specific spots in the binary model, spots whose position doesn't change between models. I'd need to ask VP what the new values are, but there is also the issue of finding out where the hex-edited info lines up in the ascii model/MDLOps' compiling process. Short answer: Headfix is still needed, since right now trying to find where its binary data is in the ascii/compilation is not an easy thing.

On her body model, the hip/waist is the most noticeable part. Running Mira's head through MDLOps once to decompile and once again with no edits yields this: Before (Compiled with MDLOps 0.5 and then ran through VP's Headfixer) After (Compiled with the new MDLOps and then ran through VP's Headfixer) As you can see from Mira's upper lip, things still aren't quite perfect. VP and I want to add another extra leg or two to the calculations that will hopefully fix that issue.

Before: After:

KSE is a .exe, so it should be running as a program... Notepad and the like shouldn't be opening it. It's downloaded as a compressed file, so you'll need 7zip or something similar to unpack it.

You would download all of those, every last one of them. Then google "7-zip" and download the right one for your OS (32-bit = x86, 64-bit = x64). Then right-click the bos_sr_1.0.part01.rar and "7-zip" should be in the right-click menu with an arrow beside it. Mouse over it and then in the foldout, select "Extract Files" and finish it off with clicking "OK". Then you'll need to also extract the bossr_patch_1.1.7z. When everything is done extracting, you should have two folders: "bos_sr_1.0" and "bossr_patch_1.1". Go into the first folder and click on the .exe to start installing the mod. When that is done, go back one folder and then go into the patch's folder and do the same thing.