Fair Strides

The 8 and 64 were named according to their use. Since this game has no concept whatsoever of ammo, those slots were skipped over and probably disabled. As to the other slots, I know you don't need the info, but I'll give it anyway to explain. The slots actually do exist and the items in them are real items. There are 4 "invisible"/hidden slots that you physically cannot access in-game. Three of these are for weapons and the last for an armor slot. These are the Creature slots. Each of those slots are in my previous post. As far as how I figured it out, I literally just used the .UTC editor in KT and some old format docs from Never Winter Nights to get an idea of the slots by entering an item in one slot, saving the file, opening in K-GFF to check the number, then writing it down. I had to for KSE. Though when you think about it... They were smart. The started with 1 and literally just doubled the number for each slot's ID.

At the very very least, it sounds like you're getting caught on a door collision/walkmesh edge and the game is hiccuping, which has been known to happen at various random times in both games. Approaching the door from various angles/from the side might yield better results. Also, what were the mods you used? Though it's already been mentioned, a lot of data is saved into the save game, including the current state of every level you've entered. So the only way to reset an area completely when uninstalling mods is to use a save from before ever entering the level before.

Sorry for the delay. Sadly I don't know that this is possible to do quickly/easily. As an alternative solution, you could probably rename one of the two dialogs (I imagine the second is the less-edited version...) and then edit the OnEnter script for the module to fire the renamed dialog instead. Unless the dialog is listed in the .utc file, in which case you have to do it a bit differently.

Depends on what mods you have installed. And the removed .utc files... Did you try it with a save from before entering the Bridge level ever before?

Specifically, put the install path of the .dlg file to "modules\" without quotes and without the marks. However, TSL Patcher refuses to accept two files of the same name for editing. What I did for the lev40_carth.dlg in K1R (or at least, I really believe I followed through on it) was to: 1. Make a new main branch of dialog 2. Move all of the original file's stuff under that branch 3. Make a new main branch again (there should now only be two main branches) 4. Move/copy/re-create all of the second DLG file's stuff under this new branch 5. On the top main branch, figure out which module it is (for example, I believe the pre-Leviathan scene is ebo_m40aa) 6. Create a conditional script attached to the first main branch that has the following: int StartingConditional() { if(GetModuleFileName() == "ebo_m40aa") { return 1; } return 0; } What this does is combine both conflicting dialogs and then make the top one only trigger if you're in the right module. And this could be done for any number of conflicting DLG files. Just gets a bit cumbersome after a while.

@Kexikus: Except that going by his comment, I believe he's losing the Aurora Lights and/or lightmaps by using MDLOps to compile the area models. What he could do instead of modifying the original models and losing the data is import the basic geometry of a model, remove all of the textures and lights and stuff, and then apply the decal textures. Only thing is that this would be a new separate area model and would need adding to the .lyt and .vis and stuff.

That was probably because of the basis upon a tabletop DnD 3.5 system. A move such as this would require speed and control, so Dexterity makes sense. In fact, I think we can actually add requirements like this. There's fields for the different attributes in the .2da files.

Scripted fighting I'll have to do my homework on, but anything else cutscene-wise (like movement, sequence of actions, .etc) are good to go. I'm not saying I won't go over, I'll just need to do my own homework on it. Yes, getting their grubby hands on your beautiful stuff is doable. Compatibility is always an Achille's Heel, but I'm sure I can help you out.

And I figure I might as well fill in the gaps. 16384 = Creature Weapon L (Left?) 32768 = Creature Weapon R (Right?) 65536 = Creature Weapon B (Back? Backup?) 121072 = Creature Armor (this is often used for party member upgrades, and I believe gives the droids resistances)

The inventory slots were adapted from Neverwinter Nights beforehand. 4 = Boots, 64 = Cloak, 2048 = Arrows, 4096 = Bullets, and 8192 = Bolts. The Left and Right Ring slots were converted to the forearms, as was the Neck->Implant and Arms->Hands.

You're in luck. I blame KSE and the Toolset for having the knowledge I have in this case: Head = 1 Body = 2 Hand/Glove = 8 1st Right hand = 16 1st Left hand = 32 Left forearm = 128 Right forearm = 256 Implant = 512 Belt = 1024 You probably don't need the invisible creature item slots, but I can provide those if you want. Prime examples of their usage are the Kinrath's poison attacks and HK-47's stat boosts. 2nd Right hand = 262144 2nd Left hand = 524288 If any of the info on the Right/Left-ness of some slots is incorrect, then I definitely ask you to correct me, but this info should be accurate.

Each mesh has sections in the file format for up to 4 different textures to appear on the mesh, each with their own mapping coordinates as well. Tool-wise, we only currently support the 1 texture in MDLOps and 2 textures in KAurora. I'm not sure what you're doing to try to get the game to read it.

Okay, we've got a file from Schizo for K2 re-scaled Trandoshans and we have separate K1 and K2 versions from Darth Parametric waiting for approval. Who gets the K2 version, or should both be approved? (I don't actually know if both use the same scale factor, so I don't know if there's any differences)

Do you know why or how your computer isn't able to install the CSLU Toolkit? Besides that, the only way to do it is manually, with phonetics (which is all about the shape of the mouth when making sounds, I believe).

This is in the OnEnter, k_003ebo_enter.ncs. This won't decompile, but there should be a .nss of it from TSLRCM in the 003ebo.mod.

Well I don't know what exactly you mean by the "start the escape from Peragus scene", but in order: 1. This is attond.dlg in 003EBO. 2. This is 003atton.dlg in 003EBO. 3. I'm going to assume you mean whatever starts the sequence after Peragus gets blown up? If so, this script could be found in 003atton.dlg. If you mean something else, then please let me know so I can do some more digging.

SWFP_DAMAGE_VFX = VFX_PRO_DRAIN; effect eVFX = EffectVisualEffect(SWFP_DAMAGE_VFX); The eVFX is the effect applied to the targets, the impact effect. It references SWFP_DAMAGE_VFX as a shortcut, so changing that top line is what you want to do. The VFX_PRO_DRAIN is another shortcut from nwscript.nss that references visualeffects.2da again. This will be replaced just like you did with the beam effect. In the visualeffects.2da, look through the "VFX_IMP_" entries ("IMP" is short for "IMPACT"). You can sort the .2da by a column by click the label at the very top of the .2da file's column.

Hi guys! It's been long enough that I've had time to go over some things and get some feedback on my previous blog post about a scripting event. I've checked my schedule and gone over some software with Xuul and I believe I have a plan now. The Scripting stream will be done twice. This is to accommodate both those in the United States with one schedule and the rest of the people (who mostly reside in the European timezones). Otherwise the timezones just don't match up (my 10AM is someone else's 6AM of the next day, to take it to the extreme). USA Zones Stream: Thursday, December 15th, at 5PM PST (UTC-8); this is 9PM over in New York. European + Extras Stream: Saturday, December 17th, at 9AM PST (UTC-8); this is anywhere from 4 to 8PM in or around Europe. This gives me several weeks to prepare material and test my equipment (I'll be PMing at least two people to help me with test streams) out to help make sure this goes off smoothly. For those that just aren't able to attend at all for whatever reason, I plan on recording at least one of the streams, editing it, and uploading it to Youtube with bookmarks for content. This would understandably be a delayed thing that might not happen until around New Year's if everything went well, so I will ask for your patience ahead of time. Once again, suggestions for any particular areas to focus on or material to go over (even examples of things to do or scenarios to work through) are welcome and appreciated.

Should you be interested in any more scripting or want to learn more, I'll be doing a streaming event where I go over scripting, trying to teach others about it and how to do it. It'll be in about three weeks or so, once on Thursday (around 5PM PST, which is UTC-8) and once on Saturday (around 9AM PST, which is UTC-8). http://deadlystream.com/forum/blog/64/entry-169-a-proposal-for-scripting

EffectBeam(VFX_BEAM_DRAIN_LIFE, OBJECT_SELF, BODY_NODE_HAND); If you open nwscript.nss and search for "VFX_BEAM_DRAIN_LIFE", you will find that it will be listed something like this: int VFX_BEAM_DRAIN_LIFE = ; The number there is the same number as the row number in the visualeffects.2da file (the column furthest to the left when you're editing a .2da file is the row number). The "VFX_BEAM_DRAIN_LIFE" is merely a substitute for the number. This is to make it more understandable for people reading the script. In this case, you'd replace the "VFX_BEAM_DRAIN_LIFE" with either 2069 (the row number from visualeffects.2da that indicates Plasma Spray) or "VFX_BEAM_PLASMA_SPRAY" without the quotes. Be aware that the only reason you can use "VFX_BEAM_PLASMA_SPRAY" instead of the number is because the original values from visualeffects.2da are listed in nwscript.nss. Any that are added from a mod can't do this.

I wasn't sure if that would be the case or not. The first part of the EffectBeam and EffectVisualEffect functions is the number. The text that is there is something from nwscript.nss that references the row in visualeffects.2da. You'd replace that with the row number itself.

You would need to open k_inc_force.nss, locate each of the powers you want to edit, and swap the numbers in the EffectVisualEffect and/or EffectBeam functions with a different number from visualeffects.2da. After that, you'd save the k_inc_force.nss in your Override folder and compile k_sp1_generic.nss, which is what actually fires the force powers in-game. I don't know if the Plasma Thrower's visual effect is part of visualeffect.2da or not, but there is VFX_BEAM_PLASMA_SPRAY, which is row 2069, so you might try that value.

Ah. That is done in the area models themselves. The plane meshes have the decal textures assigned to them just as if they were a wall, floor, or any other object. The decals are UV-mapped to the meshes and the alpha channel makes anything but the decal on the texture transparent, allowing it to show clearly. I don't know off the top of my head if the area models have the plane be a completely separate mesh from the surface it's supposed to show against or not, but each mesh can have up to 4 textures assigned to it. We don't officially know if the 3rd or 4th slots work, but the 1st slot is usually the texture in question and the 2nd is usually the lightmap or similar. It could be that the decal texture (assuming it's assigned directly to the surface itself) could either be in the 2nd or 3rd slot, I'd imagine.