Fair Strides

void main() { if ((GetIsPC(GetEnteringObject()) == 1)) { location lJump = Location(Vector(244.0, 55.1, 8.99), 0.0); int iIndex = 0; object oTarget = GetPartyMemberByIndex(iIndex); while(GetIsObjectValid(oTarget) == 1) { AssignCommand(oTarget, ActionJumpToLocation(lJump)); iIndex++; oTarget = GetPartyMemberByindex(iIndex); } AssignCommand(GetFirstPC(), ActionStartConversation(GetObjectByTag("DarthMalak"), "scene_06", 0, 0, 1, "", "", "", "", "", "")); PlayRoomAnimation("StuntRoom40d", 1); } }

Loading up the level's files, I believe the issue is the fact that the module's spawn-in point is right in the middle of the room. If you want to move them back behind the door, you have two options: 1. Open the "module.ifo" file in K-GFF and set the "Mod_Entry_X", "Mod_Entry_Y", and "Mod_Entry_Z" fields to 244.0, 55.1, and 8.99. 2. Modify the script to move the PCs to those coordinates using "AssignCommand(, ActionJumpToLocation(Location(Vector(244.0, 55.1, 8.99), 0.0)));"

@DarthParametric: What module is that one again? I can load it up and check it out (the module with the Leviathan).

@Pepoluan: As it turns out, I'm rebuilding the TSLPatcher in a different language (from Delphi Pascal to Perl) due to some annoying issues with it. Most of your list I've already been implementing. I can probably allow a "modinstall.ini" in the same folder as the .exe, with a sub-folder called "moss". The "modlist.ini" would then have a list of installs to run back-to-back, with paths to the .ini files to run and the name of the Info file. The paths would be relative to the mods folder.

@Kreia: You're evil for showing the food and not sharing! @Deadman: Nice! Given the mixed opinions I've been trying to avoid hearing, I was expecting a crying face...

As far as I am aware, the only thing that would happen is that the wrist launcher's texture wouldn't change. I can retrieve my old files and test, though.

Oh, I really dig the shine and effect work you've done on it. I kept it to a separate texture all by itself, but I should be able to re-rig your texture like that. Though, I might need a copy of the UV template for just the wrist launcher to make mine match up.

Ah yes... You see, I still have the files for all of this, DP. However, I got hung up waiting for someone to reply to a PM conversation about working on Mira's head model for me. I could release it without the head changes I wanted to do, I guess.

Nothing new on the NPC Overhaul as far as I am aware. As for the other two mods you've linked, those should work just fine.

Drop this into your Override folder, assuming you don't already have the file in there. baseitems.7z If you do already have one, then you'll need to open it with KotOR Tool. Find the row that you want to edit and then go to the "weaponwield" column. 1 = one-handed melee. 2 = two-handed melee, one attack. 3 = two-handed melee, two attacks. 4 = one-handed ranged. 5 = two-handed ranged, one attack. 6 = two-handed ranged, one attack.* *: Going by the above pattern, I would assume that 6 was originally meant to be two attacks as well like the melee counterpart, but that obviously never got programmed that way. Setting the repeating and heavy repeating blaster lines to have "weaponwield" of 3 will not turn them into melee weapons, at least as far as the feats to use and being used at range. I didn't exactly check the math on the to-hit and damage bonuses...

http://deadlystream.com/forum/files/file/1176-train-the-handmaiden-beta/

@SH: This is partially my fault. I'd received a PM a few days ago from ArrenKae and neglected to respond to it... @ArrenKae: I saw your PM in my email on my phone. Something unknown to most of the community is that I broke the screen on my laptop, which is the only thing I can mod on. However, I managed to dig up a VGA cable to connect it to my TV as an external monitor. That being said, I read your PM and have been too busy to respond. This is the last week before Finals for this term at the community college and I may very well fail Math. I have some homework that is due today and then need to study for my Math final tomorrow. IF I still have time left to go over everything with your current issue, I'll respond either here or in a PM.

The issue is you're trying to use nwnnsscomp.exe directly. And you can't use just what I wrote above. That's just a sample of what you'd need in "a_makejedi.nss"; you'll want to use that as a base and open it. What you want to do: 0. If you don't already have it, grab the "nwscript.nss" from the "scripts.bif" of both games and put the file in the games' respective Override folder. 1. Open KotOR Tool's Text Editor. (either use the button below the menu or the menu itself) 2. Open the .nss file you want to edit or copy-paste in. 3. Edit the code however you want, then when you go to save it, make sure it has ".nss" at the end. 4. Go to the menu in the Text Editor, the option on the far right, and hit "Compile" after you set whether the script is for KotOR 1 or KotOR 2.

You can use KotOR Tool to both write/edit the .nss files and compile to .ncs files. I've not used Blue's tool and the Toolset Beta is really not ready for that. I've been working on the Toolset when I can, though college eats into that a lot...

To help clarify DarthParametric's statement:

@Mellowtron: I have been absolutely buried and haven't done crap for modding in a while, but here's what you need:

Then I'll look at the source code for TSLPatcher tonight and see what it does before it installs the files.

Try moving the installer to your main D:\ directory and running it there. If that still doesn't work, I can try to look at what TSLPatcher should be doing before it runs the install.

Within the mechanics of the game, we can't do this. The game locks the stuff in unless you want to purposefully lose levels in KSE.

You will want to edit the "a_makejedi.nss" file (which can be found in the "scripts.bif" file or I believe in the 003EBO.mod with TSLRCM; both can be accessed using KotOR Tool). This file is the one that actually assigns the classes to the NPCs, so it's already split up into running code for each one. From there, you should be able to use Qui-Gon Glenn's advice.

If you have KotOR Tool, you can open the "damagehitvisual.2da" file. The value you will want to edit is the one in the "rangedeffect" column for the "Blaster" row at the bottom. To properly edit this, you'll want to open the "visualeffects.2da" file as well and look through it for something similar to what you want. Then you'd take the value in the "(Row label)" column and put that into the "damagehitvisual.2da" as described above. After that, you'd click in some other spot of the "damagehitvisual.2da" file and then save it to your Override folder.

I feel it is important enough to mention that the chat shutting down was more of an IPBoard issue, not a Deadlystream issue, as far as I could tell from the details.

A persistent issue I had, though I believe it was due to lack of updates or the graphics card. It proved harmless, as the in-game dialog is still there.

I managed to do this on a few of the menus, but the issue that had me stop was that no matter which way I adjusted the values, the game would apply an offset to the clickable locations for triggering buttons. At one point, I had to be a quarter-inch or better diagonally-upper-left of where the button was to be able to click on it... I imagine this could be due to aspect ratio, but I don't know for sure.