DarthParametric

If using KTool then go to Tools -> Options -> Other and tick the box to have it check the Override folder for 2DAs. It will show your custom added row in the drop-down list then (may need to be closed and restarted). If using KGFF, look in the PropertiesList and find the property struct with the PropertyName value of 59 (Disguise property's row ID in itemprops.2da). The Subtype value is the appearance.2da row ID (would be 351 in your pictured example).

You're looking at the unpatched UTI by the looks. If you install the mod, or just look at changes.ini you'll see that it adds a custom appearance row with N_CassusFettB01 as the racetex and patches the UTI to point to that. But yes, your summary at the end there is correct.

The basic approach for a full body appearance like this is to set the UTI up as a disguise. It's the same way the space suit, underwater suit, Sith armour, and Sand People clothing works. In the UTI you add the disguise property, which points to an appearance.2da row ID to use as the appearance. In this particular case, the existing Mando rows are set up to use set "racetex" texture overrides (N_Mandalorian01/02/03), so you'll need to create a new row that duplicates one of the existing ones but points to your own custom racetex variant. Since you've already got a mod that does exactly what you want, the best starting point is to poke under its hood and see how it works.

You don't need to got to the trouble of using TSLPatcher for testing purposes. Create a MOD of the vanilla module (.rim/_s.RIM plus _dlg.erf for TSL) with ERFEdit, copy it into the modules folder, then add your edited UTC/s to the MOD. Remember that once you enter a module for the first time its content is stored in your save file. So typically you'll want a save before entering a module for the first time. That's less relevant if you are spawning creatures via script.

Using Holocron Toolset's GIT editor is the easiest way. Select the game from the drop-down on the main page, switch to the Modules tab, select the appropriate module from the drop-down list, expand Module Data and double click on the GIT to open the GIT Editor. That will give you a top-down view of the module's layout with all the starting objects. But be aware that many encounters are scripted, so certain creatures may not exist on the map by default. It's important to note that you should pretty much never dump edited UTCs (or any other template) in the Override folder, especially for TSL. The only exception is for global templates. This is because TSL is notorious for reusing UTC ResRefs across modules, although even K1 does this to some extent.

Download and install 7-Zip - https://www.7-zip.org

Well there's your problem. I don't think that exists. The MOTF double saber uses variation 7 not 8.

Hex editing is no longer required. That was only back in the ye olde pre-v1.0 MDLOps days. These days you can decompile the model to ASCII with either MDLEdit or MDLOps, edit the ASCII in a text editor, then recompile. Or with KotorBlender you can just load the binary MDL directly into Blender, edit it in there, and export a new binary model.

I still need to fiddle with the lip sync for the Dantooine Ruins scene, but since that's horribly laborious, I decided to look at some of the other scenes. Here's a first crack at recreating the Star Map visions - albeit without the black spiderwebs/fog effect. It's not exactly 1:1, but close enough. With the animated camera setup done, it should be pretty simple to transfer it to the other three maps to capture their movies, and get the footage for the cross-fade during the revelation scene. Edit: Tweaked the setup a bit after working on the Kashyyyk map. Edit 2: Added the Manaan and Tatooine map sequences. One thing I don't understand is why they are so inconsistent. Some barely show the map opening before they end, others show the later section of the anim where you can actually see the galaxy map. I think it would probably be worth offering alternate versions that follow the Tatooine map's timing. Edit 3: Maybe the timing differences are because they used those same clips to create the Revelations sequence. I personally took a different approach in order to properly sync their animations and get a seamless transition between each shot.

Depends entirely on the quality. As long as it doesn't turn out to be some Kaevee-level monstrosity, or worse, it's worth a try.

I notice you don't appear to be using the neutral creatures fix to GN_RespondToShout in k_inc_generic, which is not ideal. It can lead to sequence breaks under some circumstances, and screwy behaviour in general. See the edit in K1CP's repository here.

It's entirely possible, as long as you are willing to create custom stunt animations to facilitate it. But you don't necessarily have to make the whole thing from scratch. You can cheat a bit, as I did in that example, by taking an existing idle animation and then just editing the appropriate bits (like the right arm/hand in that case). In your case you could cheat a lot with existing anims. Have a shot from behind the player as they crouch down to pick up the datapad (have a look at Carth crouched down next to Saul on the Leviathan bridge for an example of how to do this). Then do a close-up shot of the player holding the pad where you basically only see the pad and the sides of the hands. That could probably be completely static, just a locked pose, which is pretty simple.

Good catch. There are probably similar cases, but it's difficult to find a way to catch all those types of things without doing it manually.

This is normal. Adjusting the map requires an exe hack. Last I head ndix UR had finally figured out the exact offsets, but he hasn't updated his WS menus mod as yet.

Anyone is able to beta test at any time they want, simply by cloning the repository locally. Although it should be noted that TSLPatcher is no longer supported and HoloPatcher is now the required installer. If you want to try out the current build and test for bugs then you need to be quick. I will be starting my second 1.10.0 beta test playthrough this weekend, looking to have the final release ready by Xmas. Edit: As of this evening, I have wrapped up the last of the planned updates before I begin beta 2 this weekend. So if anyone wants to do a playtest, now is the time to jump in. But you'll need to be quick with your feedback, since I want to get the final release out by next weekend. Current changelog for v1.10.0:

Interestingly both MDLEdit and MDLOps crash when trying to load or compile the exported ASCIIs. Someone proficient with Blender will have to do it in KBlender. Perhaps @WildKarrde could take a crack at it.

Now do it in Aurebesh. By the way, I wouldn't say that level of detail doesn't have a place, as long as you are willing to go the extra mile to facilitate it. In other words, create a cutscene where you actually get a chance to show it off. I am doing a vaguely similar sort of thing with comm messages (which hopefully I'll get around to finishing next year some time).

You could source new head models from TOR, although the textures are a bit too cartoony to use as-is. At least the earlier stuff anyway. They have been trending towards a more realistic style in more recent updates, at least for unique NPCs (not that I have actively played for a while).

The starting conditional sets whether the branch is available or not. But k_con_fperslow is actually easier, since it checks for the PC having either FORCE_POWER_AFFECT_MIND or FORCE_POWER_DOMINATE, whereas k_con_fpershigh requires FORCE_POWER_DOMINATE. In other words, the two scripts should really have been labelled "easy" rather than "low" and "hard" rather than "high". Unlike with skill-based Persuade, there's no DC check with Force persuade. You can either do it or you can't. The outcome is entirely dependent on the DLG itself. In this case, it's one of those "illusion of choice" type situations. There's no branch for success because you were always being railroaded into a fight. The only option to do what you want would be to replace that branch with all new custom VO that leads to a new exit node.