Leaderboard
Popular Content
Showing content with the highest reputation on 03/08/2022 in all areas
-
2 points
Version 1.0.0
727 downloads
The Khoonda turrets are on the fritz again. And who can blame them? A cursory inspection reveals that salvagers have clearly stolen their internal components, as they appear to be missing half their geometry! Let's switch these turrets to the correct model. For an existing game, use a save file made before visiting the Khoonda Plains for the first time (this mod won't affect save files made any later). This mod requires TSLRCM in order to install properly. Installation: Download the 7z file and extract to somewhere convenient for you to access on your computer. You can run the recommended automatic installer in the "Installer" subfolder, or open the "Manual Installation" subfolder and follow the instructions in the included read-me to install it yourself. The installer is an .exe file, which may be run natively on Windows, or with free programs like Wine on macOS and Linux. Uninstallation: Run the automatic uninstaller in the "Uninstaller" subfolder, or open the "Manual Installation" subfolder and follow the instructions in the included read-me to uninstall it yourself. Modifications (Automatic Installation): -khoonda_turre001.utc appearance type changed from 182 to 640 -khoonda_turre002utc appearance type changed from 182 to 640 -khoonda_turret.utc appearance type changed from 182 to 640 Included Files (Manual Installation): -601dan.mod Compatibility: Users should expect full compatibility with any other mods, so long as they do not attempt to overwrite the data listed above. This mod requires TSLRCM. Another good mod to check out if you have not already is "Khoonda flag fix" by FF97, which will restore the missing texture for the Khoonda flag above the building. Acknowledgments: Thanks to Fred Tetra for making file extraction easy with KotORTool, and to Stoffe and Fair Strides for easy .mod extraction with ERFEdit, and of course for TSLPatcher. This modification is not supported by Obsidian Entertainment, Lucasarts, Disney or any licensers/sponsors thereof. Use of this modification is at your own risk and neither the aforementioned companies nor the author may be held responsible for any damages caused to your computer via this modification's usage. -
1 pointhello! i recently just finished kotor 1 and i really enjoyed the apart from deck 2, i get the vibe it blocks a lot of build if it doesn't its the most punishing aspect of the game. its weird that being outnumbered was harder than Malak and it made the suspense leading to the battle feel pretty bad. i have got kotor tool and i have opened two files that i believe are linked to dec 2. the two files are: sta_m4ab_s.rim, this one contains the turrets on two, the other file is sta_m45_s.rim, it contains all of the enemy's you cam have spawned in a section.i have looked at them and they all come under hostile faction. im also a little confused on what file contains the spawning rate. does it come under triggers or dynamic are info? any help would be appreciated. i'm not a modder but i'm passionate about the game, and i don't believe this section would go down to well especially if younger kids wanted to get into it. any help would be greatly appreciated
-
1 pointSure, that's just a combination of what I suggested above. I think 9 total is a bit low though. I haven't checked what the actual trigger arrangement is yet, but an alternative approach would be to nix the heartbeat altogether and switch to the triggers each spawning a single group.
-
1 pointThe mooks spawned on Deck 2 and Deck 3 both use the same setup (with only minor differences in the UTCs spawned). The module heartbeat that spawns them has a check against a global number (K_STA_HORDE), which stops spawning once it hits 9 and a global boolean (K_STA_SPAWNER) which is an on/off switch. There is a trigger OnEnter that resets the global back to 0, but that has a local boolean check so that it should only fire once. However, on Deck 2 there are three reset triggers and on Deck 3 there are five reset triggers. On top of that, there's a start trigger that also sets the global back to 0 and sets K_STA_SPAWNER true to start the spawning. On Deck 3 there is only one of these triggers (which you'd expect), but on Deck 2 there are five of these, effectively acting as reset triggers. I'd guess these work in conjunction with cutscenes, but I haven't checked that. By my count, that should mean a maximum of 40 mooks on Deck 3 but 56 on Deck 2. You'd need to add a counter script to verify it though, since it's entirely possible that other resets happen during cutscenes. In terms of stopping them, the easiest solution is probably to add a new global number that increments with each spawn and then have it terminate the spawning script once it reaches whatever arbitrary cap you decide on. Alternatively, a less intrusive option would be to simply lower the K_STA_HORDE check value, so the spawner terminates sooner each timer it resets. Edit: So I just did a quick run through with some kill blasters and with a counter added to the scripts. I ran around until they stopped spawning. I got a total of 28 mooks on Deck 2 and 47 on Deck 3. I think I may have hit some reset triggers early on Deck 2, which reduced the count there, but Deck 3 gave me more than I expected, so I gather there must have been additional resets somewhere. Maybe via door OnOpen scripts or something.
-
1 pointI'm wondering how Lehon will work for Kotor 2. I assume that the Star Forge is still a mystery to those who weren't either present at it's battle or top Sith/Republic officials. If you make Revan light sided, then Lehon could be a place of mystery, with secrets of the Star Forge lost. If Revan is dark sided, then the Star Forge is still there, just not used and is dormant. It'll be kind of hard to hide that fact, unless it's your intention to make the Exile aware of the Star Forge.
-
0 pointsThere was a solution posted here to the Steam Community a couple years ago that worked for some Linux users.