This is why procrastinators always win! If I simply think about doing something long enough, someone else will do it!
In all seriousness, great to hear, I hope to eventually try and put together a guide, maybe even a complete modpack (assuming I can get permission from TSLRCM authors) with these kinds of bugs/polish issues ironed out, so if you get it working, I may ask to use it (of course, with credit).
Or maybe someone else will beat me to the punch entirely! Either way, great work!
I haven't slept at all and it's 6 am here but I do believe I have solved the issues I mentioned. I compared the dialog.tlk for the PC and Switch versions of KOTOR 2, output the difference (favoring the switch), which left me with all the instances of altered button prompts made specifically for the switch, as well as some other interface text elements. Then I made a script to look at that output and the TSLRCM dialog.tlk, updating any strings with the same id to the switch iterations, and inserting any strings with entirely new ids as well. A preliminary test shows promise, but after I complete a full playthrough I will post everything and credit both dMATOovoxq and jacqylfrost.
For now I need sleep.
I appreciate you taking the time to respond. I've gotten it to work and even made my own script based off of the one posted.
Currently trying to figure out why this breaks some tooltips/button prompts, I suspect it's because TSLRCM does not edit dialog.tk but outright replaces it, and now a bunch of popup windows ingame reference PC controls instead. If/when I figure that out, I will share it here.
As stated above, I am very busy, at the moment I am settling into a new job, and I just got back from a convention. I've given @dMATOovoxq/Dr Snuggly my blessing to split this off into their own modding framework with their improvements, but they previously indicated they have no plans to get this working on Windows. I will look into this myself at some point, but to be frank, I'm exhausted, and this is my first weekend off in nearly 3 weeks, and I'm taking a breather.
Never say never, but don't expect it soon. I may look over my notes and see if there's something I missed when I wrote the readme later today, but I did get TSLRCM and another mod working just fine with this, so I suspect I may have worded something poorly or just forgotten a detail. The script shouldn't be strictly necessary for TSLRCM, I'm just not sure what issue people are running into. Some have gotten it working just fine.
Actually, got it working! Screenshots attached — one with the first sign that TSLRCM is working in the character creation menu (the "Mobility" feat is added), and one with the first in-game sign that it's working (the first dead body has a Vibrocutter instead of a Vibrosword). However, I had to take a modified approach to this, details below.
Background: I'm sure you've noticed already, but there's no real pattern to which files live in the romfs's override folder vs. the Localized override folder. So, I dumped it all from the Switch and mapped out where each override file is supposed to be (along with other folders split between romfs and Localized, like romfs/StreamSounds/).
Resolution: I've attached a modified version of your original framework. I've flattened the directory structure to get rid of the Localized folder, so all mods are installed into romfs/ (instead of installing to romfs/Localized/English/ and moving things around afterwards). Once the mods are all installed, run the finalize.sh script to restructure everything into what the game expects on the Switch, then copy the Title ID folder (i.e. 0100B2C016252000) to the SD card under /atmosphere/contents/.
NOTE: the script I wrote will only work on macOS or Linux (or on Windows with WSL2 or Cygwin, if you're feeling adventurous). It can be easily adapted to Windows batch or PowerShell, but I don't currently have the inclination or motivation to do so.
Feel free to incorporate this into this framework, if you wouldn't mind adding an attribution (to DrSnuggly, I’m in the process of changing my username here lol), if you feel it's appropriate.
UPDATE: WIth jacqylfrost's blessing, I've spun my work into it's own framework that can be found here (along with a GitHub project to create issues and the like). Now with the TSLRCM main screen working!
Damn, you have a good memory. I ended up installing TSLRCM on my PC — after waking up on Peragus and bashing the first door with the Plasma Torch, searching the closest body will give a Vibrocutter (TSLRCM) instead of a Vibrosword (base game). There also should be a feat called Mobility available in the initial character creation menu, but not sure if that counts as "UI" stuff that this framework wouldn't support.
That being said, it looks like your instructions didn't work for me on Switch. I ran through them a couple times just to make sure I didn't miss something dumb, but it's certainly possible I still did. I saw a few others were having difficulties as well — any ideas? Regardless, appreciate the work you put into this.