th3w1zard1

That messagebox should be impossible. There are pre-validators that run before an installation even starts to prevent issues such as that. Given that instruction #2 is attempting to move <<modDirectory>>/tslrcm_*/* straight into the game folder, my best guess is you have a folder named 'tslrcm_something' that's empty in your mod directory. If your log files say 'newSourcePath' or something in the exception that would confirm. So the solution would be to cleanup any folders in your `mod directory` and ensure you have permission. Try running the built-in permission fixer tool. Alternatively, try running modsync as root, or as admin on windows (or vice versa if the error occurred with escalated privileges). If that doesn't work you're looking at several bypass solutions: The easiest would be to first install with the EXE, then run the install exactly as you did, and press the X in the upper right when the error pops up. Doing so should abort the install while still in the installation loop, which IIRC should then consider tslrcm an installed component. If by some chance you don't get the same error again (which again should be impossible: the installer is made to reproduce the same results every time), there are no functional game changes or stipulations caused by unzipping over prior tslrcm installs, since the EXE installer is just a glorified unzipper itself. The other slightly more involved workaround would be modify the instructions. 1. Click TSLRCM on the lefthand side of the app. 2. Click 'raw edit' tab. 3. Delete everything that is below the following: [[thisMod]] Guid = "d2bf7bbb-4757-4418-96bf-a9772a36a262" Name = "The Sith Lords Restored Content Mod 2022" Author = "zbyl2, DarthStoney, Hassat Hunter & VarsityPuppet" Category = "Essential" Description = "The whole reason why you would mod KOTOR 2, the legendary mod that includes bugfixes, restored content, and altered scenes to return the game to what it was meant to be. This mod isn't just essential--it's mandatory." Directions = "Executable. Recall that M4-78 is incompatible with this build; do not use it alongside TSLRCM! Remember also that the Workshop version of this or any other mod is NOT to be used!" IsSelected = true Language = ["All"] ModLink = ["https://deadlystream.com/files/file/578-tsl-restored-content-mod/", "https://drive.google.com/drive/folders/156EqzmEESrxksm1f0cPl2tMUf-AOUt8Y?usp=sharing"] [[thisMod.Instructions]] Action = "Extract" Overwrite = true Source = ["<<modDirectory>>/tslrcm_*.zip"] instruction #2 is the move action. So it, and everything under it will be deleted, leaving you with a singular 'extract'. Why is it this convoluted/necessary and why is it not easy to skip a mod? The whole point of the app is to guarantee that any user using the same options as another user are guaranteed to aggregate the exact same installation. ModSync uses identifiers to determine what's installed, to determine what all can and can't be installed, and it also affects the install order. If you were to deselect tslrcm, all the mods that rely on it would no longer be triggered. If you pin some error logs here I can hopefully fix the bug for you and the next unfortunate soul. I am unable to reproduce the issue on my machine so it very well could be platform-specific.

It's failing to pre-validate that the file in the archive being installed indeed exists in the archive. My guess is the archive you downloaded is corrupted/incorrect. Try running again with 'verbose' mode enabled, see if the logs have any more useful information. this is now fixed I was given permission to reupload as a .zip. You need to use the ZIP version of TSLRCM, The EXE version is NOT compatible. You can find a link in the app itself, click on 'tslrcm' at the left side and the link is at the top of the Summary tab.

Oops, you're 100% correct. I had the wrong scoundrel mod in there compared to neocities. Has been fixed on the main page.

Posting in case someone comes along with the same question... The reason they break cutscenes has been solved. It was not the game's fault, rather the tools modders have been using to pack .MOD's in the past. Creating the `702KOR.mod` with Holocron Toolset for instance makes the whole thing completely playable without issue. Presumably the same with 401DXN.

Creating tools is my specialty. Let me know if you're finding some task in this project incredibly tedious, that a specialized tool could address. Would love to help out.

Thanks, was about 99% sure that was the case after checking `changes.ini` but wanted to triple check. Cheers! Thank you for making this!

If using your K2 force powers in K1, do I install this before or after, or does it not matter? Couldn't find any information on the readme's about it.

EDIT: All of this is fixed. I won't have time to update the instructions and do tests but you can download the previous version it's looking for, just press this button on the DS page. v1.3.1 is what you want. Looks like @Ashton Scorpius updated their mod to use my latest update of HoloPatcher. From what I can tell no content changes were made. As for the dm_qrts yeah it looks like I accidentally used the archive from the full build. Both should be the same thing, since you aren't interacting with the archive outside of KOTORModSync there shouldn't be any spoilers but otherwise just try not to read the main DS page when downloading it. Sorry I couldn't provide a direct fix at the moment but I hope this at least gets your install going if you did want those two mods.