All Activity

This sounds like an issue with Sleheyron's installer. The installer should be configured to store new appearance rows as 2DAMEMORY tokens so they can be reused for NPC appearances, rather than hard-coding specific appearance rows for NPCs. Brotherhood of Shadow is not compatible with K1CP, and changing the installation order will not resolve the placeables issue. Brotherhood of Shadow uses up almost all remaining placeable rows, making it incompatible with other mods which add placeables. The only way to resolve this is to patch the executable to increase the limit. On top of that, Brotherhood of Shadow just has a large scope and nobody maintaining it anymore so it is incompatible with a lot of mods in general.

When I go to the Sheriff that then redirects me to the cantina to progress the story and get the new party member, once I click on the dialogue to go to the party selection screen, it crashes (CTD) and I never get to the point to select the party. Saw that you read comments on file page more often than file support page.

First of all, BOSSR is and has always been incompatible with K1CP. Btw @SAO1138 I just read the description and you'll want to delete BOSSR from your recommendations or at least warn users about this. This particular mod has been designed to work with the vanilla game and that's it. Although I didnt try myself so no idea if it only brings small issues or game breaking bugs but I've seen testimonies of people who couldn't even complete the game with both installed. And that's not even talking about Sleheyron which brings a lot of new placeables. Even with K1R it breaks some placeables. BOSSR should be a mod played once, and if it were me I'd just advise to play from the savegame the author gave. And Sleheyron would've been the same if I didnt insist to Sao that we should make it compatibility friendly with an installer such as Holopatcher. Second, Sleheyron first brings many issues such as the ones you described but also others, like some of K1CP improvements not being taken into account, or even overriden by Sleheyron. Third, a compatibility patch is NOT needed if we do things right. And as Ndrew said very clearly, people are stupid so might as well do things smartly and in the simplest way possible for end users. Hm that's not what Sao told me. It's mostly because we didnt yet fix an issue with the Patcher regarding the 2DAMemories for the placeables.

When we did tests for 3.1 and 3.2, it was discovered that installing the community patch first causes issues with some npc appearance changes. I believe it was causing one of the Twilek's in Bogga's cantina to disappear entirely. The other factor is BOSSR. If you install the community patch first, then Sleheyron, then BOSSR, it also causes a few placeables to disappear in certain areas of BOSSR's modules. Because of this, the best order/option right now for compatibility we found was Sleheyron first, K1CP, RC-K1CP, K1CP compatibility patch, then BOSSR. This ensures there are no missing placeables or changed appearances (Besides now hearing about the gizka/orange twilek issue). There's likely a way to fix the red Twilek from disappearing, so that K1CP can be installed first before Sleheyron. I just wasn't able to figure it out, but that is the reason for why it's currently recommened/wrote for Sleheyron to be installed first. Apologies for the misunderstanding.

No idea why this wasn't kept in the base game

Haha I'm not mad dw, we know each other pretty well now. You dont need to play the intermediary. Yeah you're right in that it's a big mod, so compatibility was a 2d objective, etc etc. Hm I'm pretty sure it's just from that new update, and that's fortunate coz let's be honest way more people would've had that issue lol. Yeah, yeah, I know... I'm just too stubborn and optimistic so I assume people are smart. Ik, nor was my explanation. Just asked him what he did so he could fix his own situation himself, but ig you already did that. HAHA I hope not coz dang

When I say this this is not directed at JasonRyder. As a modder who has spent a decade at this, I have dealt with many players who are genuinely brain dead when it comes to them installing mods. Following dodgy mod builds made in 2014, not using the TSLPatcher installers, using K1R and K1CP together, to even installing the Lonna Vash in the Korriban Tomb mod with M4-78EP. And those are just the genuinely stupid/ignorant people, in this case the mod page and the readme possess conflicting information - install Sleheyron first VS install K1CP first. Now, for Kotor I you treat K1CP as you treat TSLRCM in Kotor II - K1CP is the "base" mod upon which all other mods come afterwards. But for someone who doesn't make mods or is familiar with this game's file structure, the K1CP being installed first might not seem obvious. And when the mod team leader, SAO, has written "install Sleheyron first" on the mod page why would these users ever think to think otherwise? It's safe to assume that most users who play Kotor mods have never made a mod for any other game, they would look up to the mod author as a "wise sage" who knows what he's doing. If SAO says install Sleheyron first, why wouldn't users trust his word when it's on the mod page, the first page that they read? If SAO added "delete System32" on the mod page's installation process, people would probably follow that instruction and not think twice about it. Again, most people are dumb - unlike you. That, and you literally became a modder yourself, proving that you are far more committed to learning about this game and how Kotor mods work then 90% of users. People will be dumb, and we modders just got to deal with that. And in this case, the inconsistent install order on the mod page and in the readme is the cause of this confusion and not user stupidity. If this problem has been present since the mod has been released back in 2025, then the fact that the mod page's incorrect install order has only just now been reported in June 2026 probably proves that most users probably HAVE followed the readme's installation and not the mod page's installation. Yeah, and they chose the mod page over the readme. SAO wrote the mod page, and users will assume he wrote the readme too (even if you wrote his readme, users will assume SAO wrote it). With most mods, the readme included in the mod is identical to the text found on the mod page so reading the mod page is almost always the same as reading the readme file. If Sleheyron Story Mode's readme file is different from the text on the mod page, that is a massive problem as most users aren't going to read both - they'll pick one or the other. And since users are faced with the mod page before downloading the mod, and reading the readme is optional, users will most likely read the mod page over the readme. As a modder myself, I more often then not leave my info.rtf files blank because I assume that if people have activated the HoloPatcher then players aren't going to stop to read whatever is written on the info.rtf file. The moment they click on the HoloPatcher.exe is after they have already committed to installing the mod. Now I'm sure he had a genuine technical reason as to why he did that, and he just didn't realize that my mod relies on K1CP being installed first or else the Giant Gizka spawns throughout the game as a bug. To be fair, SAO is just some guy who came in out of nowhere in 2025 and dropped the biggest mod to ever release in years, outside of Edge of Darkness and ROR, with up to 30 modules and a recruitable character. He probably self taught himself how to mod the game, maybe even for years too, so I can understand why he focused 100% on Sleheyron and that he is only just now, after the mod has been released, sort of been forced to consider compatibility with vaguely named mods (K1 Community Patch VS Restored Content for the K1 Community Patch etc) because the player base expects to be able to have an uber dubber bug fix + restored content + Sleheyron playthrough. To be fair on SAO, installing Sleheyron first might've worked had it not have been for my use of K1CP's orange Twi'leks so I can entirely forgive him for missing it. And the fact that he's corrected the install instructions means that he's listened to our report, I don't see their being any further reason to continue being mad over this considering he just fixed the problem.

I don't want to sound rude or anything but people need to be a bit more autonomous when modding. When I started installing mods, not even making them, I spent hours downloading manually and thinking about the install order, organising everything for my custom installations. And I'm not even talking about mods like BOSSR for which we literally need to create a folder to make it work. So yeah, people read the mod page ? Sure but if we have something called a ReadMe, READ IT ! To answer your question about how I wrote it, it was indeed in the info.rtf file (WHICH PEOPLE ARE SUPPOSED TO READ AS WELL, OR WE WOULDNT WRITE ANYTHING ON IT) as well as the ReadMe itself, but Sao changed it apparently for some reason. Regarding how I communicated with Sao himself, we talked about it several times on Discord. We've been planning the install order to be K1CP, RC-K1CP, Sleheyron. Of course installing Sleheyron first is stupid and I never would've advised that, DUH. Ik what I'm doing. That being said, ig installing Sleheyron before RC-K1CP would be fine but for the sake of simplicity I prefer the other way around. Edit : actually, I think you're right, RC-K1CP last is better because from what Sao told me, we didn't do the 2DAMemories for the placeables in the ini file. Although I was almost sure we did. Does RC-K1CP add any placeables in the 2DA ? If not, then I'm pretty sure the install order between these 2 doesn't matter. It's just that Sao forgot that K1CP wasn't included in RC-K1CP, somehow.

Are you agreeing with me that the install order was K1CP, Sleheyron, then RC-K1CP? Or are you saying that it was meant to be Sleheyron, followed by K1CP, followed by RC-K1CP. Do know that it was I who informed SAO that installing K1CP after Sleheyron broke RC-K1CP and, therefore, the K1CP, Sleheyron, and RC-K1CP order of install was required. Also, not going to lie, if you're referring to the info.rtf file which the HoloPatcher projects before the install I'm fairly certain most users, modders included, ignore that. Most people read the main mod page and/or the mod's readme for the install instructions, and I can confirm that the main mod page did, in-fact, say Sleheyron, followed by K1CP, and followed by RC-K1CP for the installer. Did you tell SAO personally, via DMs, the correct install order or did you rely solely on SAO reading the HoloPatcher info.rtf? JasonRyder probably followed this mod page's instructions which, before this most recent update, said Sleheyron, K1CP, and RC-K1CP.

I've been using this for a few hours now, main issue I have is the text on the computer consoles you can hack and droids you can repair doesn't show up. If there is a way to just revert the font for computer consoles and droids I'd still love to use this for the dialogue font increase. I also had two other issues but I consider them minor. The chat bubble that pops up from random npc that don't have dialogue cutscenes doesn't show text most of the time and as other users mentioned you can't see the amount on some things, like currency when you loot. I'm using the 50% increase on 1440p resolution, I've installed all mods from the kotor community portal build guide. This is the only extra mod I've added outside the build guide.

@SAO1138 Isn't purple the color of Vapaad users? Or those who toe the line between light and dark? I get wanting Vima to stand out a bit more but I don't think you should do so for the sake of it

@SAO1138 I LITERALLY WROTE THE INSTALL ORDER BLACK ON WHITE EVERYWHERE IN HOLOPATCHER WHEN I SENT IT TO YOU ! Grrrrrrrr @JasonRyder Did you follow HoloPatcher's instructions and the ReadMe ? They are usually the most accurate and up to date documents you need to follow when installing mods. If Sao didn't change it, the precise install order should've been explicitly written before you clicked Install.

A massiv improvement of the Telos storyline in particular but it is sadly pretty noticeble that there wasn't much else left of the original storyline that can be worked with beyond that. Once you get to Nar Shaddaa, the GenoHaradanpretty much stops being relevant, then pops up right after G0T0's yacht blows up, you have a small boss fight and then their role in the story is already over. You never even get to know who exactly hired them to hunt down the remaining Jedi (or at the very least the Exile) and that is a bit of a bummer. Needless to say, what little there was to be restored has me intrigued for the planned "Enhancement Project".

I think this mod could use another patch or two, because it seems to me that the team behind it made the mistake of not only including content that Obsidian was unable to put into the game in time but also restored things that were deliberately cut by Obsidian. Cut because they were an early idea that got quickly abandoned, a bad idea or part of a plot-point that simply no longer fit into their final vision for Kotor 2's story. Things such as Kaevee, Sion telling the Exile on Peragus that he's there to warn them despite being there to kill them, Saedhe's original head which clearly doesn't fit his VA, the struggling Duros merchant Dendis Dobo suddenly selling Jedi Robes, Lightsaber Crystals and Melee -as well as ranged weapons just like his criminal brother, Kreia and Atris revealing in their conversation that Kreia manipulated Atris into exiling the Exile or the player now being able to control Brianna AND being given the option to have her stun rather than kill her sisters (doesn't work with Kreia still calling Brianna a slayer of her own kin on Malachor V if the stun option was actually taken). Likewise, there are a few other things that the mod should've restored but didn't for some reason, requiring separate mods to do so instead. The most frustrating example here being the original head model for Brianna's Sisters, as Brianna is constantly stated to look different from her sisters due to her having a different mother despite her and her sisters all using the same head model. Or for less gear grinding but still disappointing examples: Dustil's appearance on Korriban and the Vao Armband.

Since this mod is incompatible with any other mod that modifies T3's dialogue, it appears to be incompatible with Sleheyron Story Mode.