Leaderboard
Popular Content
Showing content with the highest reputation on 09/05/2020 in all areas
-
2 pointsHello! Does anyone know if there is a mod that does give unique names to the dozens of datapads found in the game that use the generic "datapad" name? I find rather annoying that the player is forced to read the content to understand which one is which since there are often several generically named ones in the inventory at the same time. I might do the job myself if no one has done it already. Cheers!
-
2 pointsWhat's Taking So Long? CPUs and NCS Bytecode NWScript and NCS Control Structures Difficulties and Errors All of this was taken into account when I said I think I can get this done by the end of September. Just thought people might be interested in the gory details. Also, as I work on this I'm encountering what appears to be poorly coded scripts. For example: That last one is doesn't look right. May need to create a second WIP: the Script-Fixing Project. Sigh...
-
1 pointNah, it's not side effects I'm worried about, it's stuff like checking if an object is valid, and only doing something if so. Safe navigation. I don't remember any specific code I wrote where that might be a problem, but I can definitely imagine the possibility. I probably would've used && and it would be safe though. @DarthParametric and I observed in some tests that the compiler we have is definitely not the most up-to-date one, and it seems like it was the case with the one BioWare used as well because the game scripts are full of unused garbage included from header files that the same update to the NWN compiler was supposed to scrub out.
-
1 pointI had to play from the start as I had no prior saves before going down, but after removing p_jolee001.utc the cutscene went back to normal and I could progress further. On the plus side I made my own companion tweaks which I will upload once I've finished the game.
-
1 pointI would say fix it where possible. I can't imagine a situation where someone would purposefully write a condition with side effects as a secondary condition with the intent that short-circuit evaluation would be ignored, or more importantly, any situation where that would be needed. It's far more likely that there are scripts that are taking performance hit from the lack of short-circuit evaluation, and could potentially be causing bugs. The random loot in KOTOR 2 overflows the stack if you spawn too many items at once, for example. There could be more intensive operations, like in the AI, that could potentially be causing problems. Maybe that would even account for bugs such as creatures randomly not attacking in the middle of combat. I'm certainly worried I might've written code under the assumption that short-circuit evaluation would be obeyed. I suppose if that's true, I could invert the logic to use && in the meantime, since that does seem to short-circuit properly. I'm almost afraid to ask, but does NWScript have a goto statement? I haven't seen any example of it in code, or any reference to it, so I assume not. Oh, I hadn't seen this one before, but I've seen problems like it. It's understandable considering that not all the developers were computer scientists, and even designers like David Gaider and Chris Avellone did incidental scripting to take some of the burden off the programmers, but the downside to that is not everybody necessarily knew what they were doing. Plus the one you quoted looks like it might've been a copy/paste error, considering that it's only the last branch that's wrong. Stupid mistakes can happen to anyone.
-
1 pointJust wanted to thank you for a very interesting and detailed examination of NWScript and how its flaws could actually hurt people creating new code without knowledge that sometimes it could turn into something wrong (the "OR" condition - it would be great if your decompiler could fix this). Thanks for all the hard work you're putting into this.
-
1 point
-
1 pointAfter a long fight against the Korriban wastes module I finally finished the last BoSSR skybox: That leaves two mod skyboxes to do. I think those shouldn't take long but then again I thought the same of the skybox above... I'll keep you updated. In the meantime I also changed my mind and added some traffic to all Coruscant skyboxes: I'll do the same for Nar Shaddaa and probably Taris as well to better sell the cityscape of those planets.
-
1 point
-
1 pointSo....HEYYYY! I'm back...sort of. So I recently broke down and bought TSL on STEAM with TSLRCM 1.8.5 and have been trying to play through that without breaking it... No luck. I keep crashing at 231TEL.mod right after Atton's dialog in the shuttle and the little movie clips of the shuttle getting shot down. First instinct was to blame it on Bao-Dur. But I dont think that's it. Has there been any issues reported with this .mod file or Bao-Dur crashing the game when he shows up? Starting to drive me batty as I DO happen to be working on an update of TSSM, trying to get that mod working with Steam's version. Been a learning process for sure... Also, the big question...should I just be installing my saber mods into TSLRCM's workshop directory straight away?!? When I go to start working on SLM's compatibility with TSLRCM that might be helpful info. Anyway..I might be back for awhile to try to get my old saber mods running for Steam.
-
1 pointI know that another mod exists called "Save Mission" by jc2, which ultimately has all the same functions as my mod. I created this mod from scratch, using "Save Mission" as inspiration, so it has all different dialogue for the player and NPCs. The outcome is the same, but the events unfold differently. I feel that these differences, as well as the absence of a few bugs that are present in Save Mission v1.5a, mean that these mods both have merit. You may enjoy jc2's "Save Mission" much more than this mod, so I'd suggest trying both out and keeping the one you like better (you can't install them both at the same time). EDIT: Make sure you have v1.2 of the mod, as it improves the dialogue choices and fixes a bug that usually prevents you from killing Mission. Even though this mod is about keeping her alive, it's still good to have the option to kill her as normal.
-
0 points
Version 1.2
2,672 downloads
==================== Spare Mission and Zaalbar v 1.2 ==================== Created by DarknessSquall (aka Scarrab) 8/31/20 SPOILER WARNING FOR DARK SIDE PLAYTHROUGHS! . . . . . . ==================== Description ==================== This mod adds options for Dark Side ending players to keep Mission (and by extension, Zaalbar) as a party member, or to non-lethally remove Mission from the party while keeping Zaalbar. The default options that end in violence remain in the game. ==================== Long Description ==================== One of the most common complaints I've noticed about the Dark Side ending is that there's no way to avoid killing Mission. And the only way to keep Zaalbar alive is temporary as well, since he turns on you as soon as he realizes what happened. Some people refuse to go dark side for that reason - myself included! The way the game forces you to kill her really doesn't feel good, especially since Zaalbar has sworn his loyalty to you; killing Mission will obviously jeopardize that. Mission says she doesn't believe you'll kill her, and the only way to handle that is to...kill her? The violence felt unnecessary, and possibly out of character, depending on how you play the game. That's where this mod comes in. For dark side players at the end of the game, two new options have been added, bringing a grand total of three options for dealing with Mission & Zaalbar: 1) Retain them both as party members 2) Remove Mission as a selectable party member without killing her, but retain Zaalbar 3) The vanilla options to kill Mission & Zaalbar, which still function exactly as they do in the base game My goal was to write the dialogue and script the events in the most lore-friendly, in-character, way possible, so that the mod felt seamlessly integrated into the game. If I have succeeded, first-time players won't even notice that a mod is running. Mission seemed very opposed to the idea of swearing loyalty you, but she also wasn't going to run away or attack you willingly. I believe that in this situation, where's she's stuck between a rock and a hard place, there are ways to avoid the situation ending in violence. Also, if anyone is worried about messing up their alignment - you will not gain light side points for choosing any of the options in this mod. Nothing about the situation really feels like a "light side" act, to me, after all. ==================== Installation ==================== Manual install: Open the folder called "Manual Install", then place unk41_mission.dlg, nm10ackand01052_.lip, nm20aagrif05041_.lip, and nm40aamiss08014_.lip in your Override folder, which is located in your Knights of the Old Republic installation directory. Automatic install: Open the folder called "Automatic Install", then run TSLPatcher.exe and follow the on-screen instructions. ==================== Technical Description ==================== This mod consists of only a single .DLG file edit, but it gets the job done. Three of Mission's voice lines from other parts of the game are reused, so the corrosponding .LIP files are also needed, otherwise her mouth won't move for those lines. ==================== Compatibility ==================== This mod is not compatible with jc2's "Save Mission" mod or Tanesh's "Recruit Mekel" mod As long as you aren't using a mod that modifies unk41_mission.dlg, there shouldn't be any problems. If you're not sure, check for the presence of unk41_mission.dlg in your Override folder before installing this mod. ==================== Known Issues ==================== If Mission and Zaalbar have already been killed, you can't go back in time and bring them back. Load an earlier save to when they were still alive. If you choose to keep Mission as a party member, you can still talk to her like normal, and she'll give the same usual responses and act like nothing happened. Chalk it up to her mind being overly optimistic as a coping method, and/or her still being in denial about you having turned to the dark side. If you left Zaalbar on Kashyyyk and never allowed him to rejoin your party, I believe your only option will be to kill Mission. I haven't personally tested this. ==================== Uninstallation ==================== Automated uninstall: Not supported! Manual uninstall: Navigate to the Override folder in your KotOR installation directory and delete unk41_mission.dlg, nm10ackand01052_.lip, nm20aagrif05041_.lip, and nm40aamiss08014_.lip. ==================== Version History ==================== v1.2 - 9/3/20 Added checks for Zaalbar's presence, and a fixed a serious bug where you couldn't kill Mission v1.1 - 9/2/20 Improved the player's dialogue options v1.0 - 8/31/20 Initial release ==================== Permissions ==================== This mod should only be available for download on NexusMods.com and DeadlyStream.com. You may only upload this mod to another website for the purpose of preservation if it is no longer available for download on BOTH of those websites, and if you credit me as the original author. You may not include this mod in any mod compilation without my permission. You may edit this mod for your own personal use, but you may not upload a modified version of it to the internet. ==================== Thanks & Credits ==================== jc2 - Created the "Save Mission" mod, inspiring me to create v1.0 of my mod. Then, we had a good conversation about more ideas, inspiring me to release the v1.1 update Michele - Messaged me about the "Recruit Mekel" compatibility issue, which led me to discover a few serious bugs, leading to the release of the v1.2 update DarthParametric, JCarter426 - Gave me detailed and extremely helpful answers when I asked for information on the Deadly Stream forum Death a Barbar - and all the other dark side players who requested a mod like this Fred Tetra - created the KOTOR Tool TK102 - created the DLGeditor stoffe - created TSLPatcher All Star Wars fans - except for fans that believe KOTOR is non-canon now (just kidding...mostly...)