Leaderboard
Popular Content
Showing content with the highest reputation since 10/07/2026 in File Comments
-
2 points
-
2 points
-
Sounds good :) I am not sure what souser means. If it is the source files for the galaxy map, then that is just there for people who want to make other mods that use those same files compatible. Anything that is for needed to play the mod should already be where it needs to be in the folders. If you are talking about something else, then please let me know.1 point
-
That sounds great! I would love for more people to be able to play it! You have my permission to do that. As for your second point, my personal philosophy with designing these quests is that they're "all side quests." Some of the side quests are connected and over the course of development there somewhat did emerge a "main quest" of sorts (though if you're already translating it, you probably also noticed my internal quest names do occasionally indicate main and side quests, but those were more for my reference more than anything else, lol). I can think about it, though. Denoting side quests with the "Bonus Mission" label in the log does make sense.1 point
-
Hola, si te interesa, puedo traducirlo por ti y luego puedes subirlo. Ya lo estoy traduciendo para poder jugarlo yo mismo. Pero si te interesa, puedo compartirlo contigo para que otros hispanohablantes puedan jugarlo. PD: En el archivo Global.jrl, sugerimos que especifiques qué misiones son secundarias y cuáles son principales, como en el juego base y el mod M4.78. Pero es sólo una sugerencia. En fin, saludos y gracias de antemano.1 point
-
I think the discussion is mixing several different issues and treating an installation order as a proven compatibility solution when it isn't. Regarding Doodmane444's June 23 report: the tested order was K1CP → Sleheron → BOSSR, and some placeables disappeared in BOSSR modules. However, the suggested alternative still placed BOSSR last. It mainly changed the order between Sleheyron and K1CP, so it doesn't establish that this arrangement actually solves the underlying BOSSR placeable issue. As JCarter426 pointed out, if BOSSR is exhausting the available placeable rows in placeables.2da, changing the installation order cannot magically increase that limit. There is also the reverse side of the problem. OnJuly 2–3, Doodmane reported that BOSSR could replace leftover, unused Czerka sign placeables in Sleheyron's sle_m30aa.mod with its own stasis NPC. He traced this to obsolete placeable entries left in that module after the signs had been built into the model instead. This is a concrete example of BOSSR affecting Sleheyron, rather than the other way around. It is also a specific module/resource conflict, not proof that one universal installation order fixes everything. So I think we should distinguish between: 1) conflicts caused by overlapping or reused placeable references; 2) the actual placeable row limit; 3) installer overwrites and changes to shared resources. These are not necessarily the same problem, and they cannot all be solved by simply moving one mod to the end of the installation order. For players who want to enjoy both expansions without potentially ruining an existing modded installation, I would suggest keeping separate game folders: 1) Keep the existing installation for BOSSR and its associated setup. 2)Make a copy for a Sleheyron-focused playthrough, installing Sleheyron and its relevant compatibility patches there. 3) Start from a save made before the Dantooine Jedi Council mission, or use the save provided with Sleheyron, which starts at the intended point in the story. This doesn't magically make the two mods compatible within one installation, but it provides a practical way to preserve both playthroughs without repeatedly rebuilding the same game or risking the original setup. The current Sleheyron 3.5 instructions do provide a specific combined installation order and compatibility patches. However, I would still like to see reports from people who have actually completed substantial portions of BOTH expansions in the same installation. Ideally, such reports should specify the exact mod versions, installation order, and which parts of both campaigns were actually played. Loading a save or reaching a particular planet is not the same as demonstrating that the entire setup is compatible. I think that would be much more useful than continuing to assume that one installation order automatically protects one mod from the other.1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
This is an incredible find! I've found hours of content to keep myself occupied this entire day, and I've only done Korriban and Tatooine! I am quite content with a large amount of side quests that don't serve a unified plot line. At least, beyond the commonality that they relate to the aftermath of the Jedi Civil War. KOTOR II, as I've read it described, is essentially a "road trip from hell to absolutely nowhere, all the while pondering the void". To quote the cliche, "it's the journey, not the destination". This game is actually perfect to use for myriad narrative vignettes that are seemingly unrelated. I look forward to playing more, and seeing what you may add! Keelah se'lai1 point
-
1 point
-
The only mod that I installed that modifies pcdead2.dlg was the Extended Enclave mod. I am using 1.8.6 RCM. I have two pcdead2.dlgs here. The "original" is the the backup made from this mod's TSLPatcher. The second, the "old" is the one that this mod's patcher made. The third is the modified one I made to fix this issue.original pcdead2.dlgold pcdead2.dlgpcdead2.dlg Edit: I just tried installing it again a separate install. TSLRCM 1.8.6. + M4-78 1.5 Then Extended Enclave 2.52 (standalone then M4-78 as per installation instructions). Then this mod. Reproduces this problem.1 point
-
The latest version includes some files which were left out of the installation instructions for the Korriban add-on. If you already have the mod installed, you can apply the same fix by copying the following files manually from the tslpatchdata folder to your game's override folder: g_a_clothes38.uti ia_cloths_038.tga N_SithComF38.tga N_SithComM38.tga1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
Thanks for the report! Turns out I missed some conditional scripts, but I’ve now re-added them to the archive. I’ve uploaded an updated version, and the changes are retroactive, even if you’ve already trained your companions. Just pulled an update based on your reports. The issue has been fixed, please download the new version.1 point
-
1 point
-
1 point
-
Hey there! Thanks for trying the patch out! I will take a look and see if I can reproduce the issue on my end, keep an eye out for a fix. EDIT: Have reproduced the issue and have a fix! The same issue also killed HK-47's eyes as well as a couple other issues. I should have a new release up shortly. Released!1 point
-
1 point
-
1 point
-
Not the mod author, but I can tell you it's because you already completed Tatooine on that save. Basically, you can't modify a module after you've already visited it in a save (with very few exceptions). But that being said: you can just use the cheat code "warp m19aa" to teleport to the start of the Tatooine temple, just past the entrance within the Krayt cave. Have fun!1 point
-
Here is how I *actually* fixed this mod. Tools needed: Kotor Tool: and: Why Kotor Tool: You need it to actually add a new property First install the mod as normal. Why this mod breaks: If you open up the "jedirevan_robes.uti" file and look at it's properties you will see an "ERROR" in the 'Disguise' property. That is why this keeps crashing. First thing we need to do is actually *remove* that property. You cannot do this in Kotor Tool to my knowledge. Download and install K-GFF and run the .exe, navigate to your override file, find "jedirevan_robes.uti" open it. Look for the property that has a value or something to do with 500 something in it, i forget the actual number, but that's the disguise property, and that 500 something number is why it's breaking afaik. Use K-GFF to remove that entire property. Save it. Relaunch Kotor Tool and verify that the property is gone. Now go to OPTIONS of kotor tool go to 'other' and check the box "Find .2da files in override" This is what will let the GFF editor in kotor tool actually see the custom disguise added in the appearance.2da that the TSL patcher installs when you first install the mod. Go back to "Open GFF" in kotor tool. select "jedirevan_robes.uti" navigate to properties. Select 'disguise' in the bottom, the box under, click, and scroll ALL the way down (You should see a list of your appearances in your appearance.2da file) find ZM_Star_Forge_Robe. Click on it. Your new "jedirevan_robes.uti" should look like: If you have a character with the armor already on it. Then use KSE to remove it from that save. Reload the game, save over the save no longer having the armor, re-add it to you via KSE, load that save again and check to see if it still breaks.1 point
-
1 point
-
That's what I had in mind. I was just going to wait to see if there were more files that I might need to correct. What do people think; should I make a hotfix/patch after a week or two? Or after a certain number of files? Of course, I hope that there won't be any other erroneous files that I messed up on. With the Kreia model I had tested and took screenshots, but forgot to copy the correct mdl files from the test Override folder into the final mod folder.1 point
-
I'll have to check my old files. I may have already done something with a collar fix once upon a time. Maybe I can do something again but in 4x. I'm not sure; I haven't tried them with the High Quality blasters installed. I suppose that my model is just as compatible or not-compatible as the vanilla model. I only re-arranged the uvw map and scaled up the main texture. I didn't do anything with the blaster texture that the model calls for. I do know that the vanilla blaster only works with the 01 droid, and none of the 02-05 versions, due to the appearance.2da being capable of calling for only one texture at a time (they end up using the C_DrdWar02-05 texture for both the droid and the blaster). I do like the solution that they came up with for the Kotor 1 Community Patch (in theory since I haven't tried it in-game) where they removed the blaster from the C_DrdWar.mdl and make it so that it uses an equipable blaster. I assume that my 4x textures can be used with that model. My uvw fixes don't have any drastic fixes, they're almost imperceptible in-game unless you're really looking hard.1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
Done with the highest quality, I admire the fighting scenes, a few minutes ago, my Revan fought spider kinrat and I just looked at it and admired! The Jedi Enclave now looks as befits him to look with the Jedi in his robes! I thank you for your great work. I believe that you will have at least a huge success with the work on the robes of knights and Jedi masters from kotor TSL1 point
-
1 point
-
1 point
-
1 point
-
0 points
-
Hey! I’m glad you like the mod. Yes, I plan to make a HoloPatcher version once I’m done with the stuff I’m working on right now, since it’s long overdue. As for the double-bladed red lightsaber, I removed it because I couldn’t give it to Traya without conflicting with several other files of the same name, which soft-locked the game. I pulled it after I got a report that someone near the end of the game couldn’t progress past the Telos Academy. Back then, I didn’t fully understand how Override files interact with same-named files in each module. That would’ve been avoided if I’d used HoloPatcher from the start, but skill issue. Since then I’ve learned how to handle it properly, and I’ll re-include the red lightsaber as an optional install.0 points
-
0 points
-
0 points
-
Apparently, I left this thing sitting at 1.2 for ten years while the old WIP thread still says that 2.0 was supposed to be the real finished version. Fair enough. I should probably finish what I started. Thank you to everyone who downloaded, played and remembered Ultima Duel Room after all this time. This project was much larger than the K1 Duel Room even back then, with 340+ opponents already in the public build and a ridiculous amount of unfinished work planned beyond it. I am not promising that I will blindly implement every idea my younger self wrote down in 2016. Some of those ideas deserve to stay in 2016. But I am coming back to the project, cleaning it up properly, finishing what still makes sense, and giving TSL - Ultima Duel Room a real final release soon. You kept it alive for ten years. I can at least close it properly. I am much more active on Nexus these days, so if you want to follow the rebuild and my current projects, you can find me here: NarzelithOfficial's Profile - Nexus Mods0 points
-
0 points
-
0 points