DarthParametric

Rarely are things as simple as using KTool. In many ways it's just a can opener (or rather a Swiss army knife). It can get you access to the juicy contents, but it can't make you a meal.

The script spawns the item. It isn't attached to the item itself. There's any number of ways you can fire the script, but the item is the endpoint, not the beginning.

There is no "modified" script. It's a custom script unique to the mod. There is no compatibility issue, unless someone literally steals it and copies the name.

No, you have one spawn script. It looks at the player's appearance and spawns the UTI that matches. If you are talking about compatibility, JCarter's script works in a fundamentally different way.

That's only required for JCarter's approach. The other approach only requires a simple spawn script to initially generate the item. It doesn't affect anything to do with actually creating the armour, which was ultimately what I was getting at.

No, it wouldn't. That's my point. It's just a different way of doing it.

Like I said, JCarter's script approaches the problem from a different angle. It assigns the head dynamically, while the other approach is to have separate appearances for each head and have a script assign the correct one based on the player's current appearance. The advantage that JCarter's approach has is that it will work with any custom head the player might have, whereas the other approach would require the manual addition of support for said heads by the user (in other words, unlikely to happen).

You can already do it. It doesn't remove or change the fundamental underlying limitation of the game, it's just a different approach in dealing with it.

All a disguise is is an appearance.2da row. That's it. JCarter's script is an attempt to deal with the issue of assigning heads dynamically to minimise some of the hassle, but really it's just moving the hassle to a different area. It doesn't add something that was unavailable before, and if he released it tomorrow fully working we wouldn't suddenly be inundated with new armour mods.

No it wouldn't. It's still just using disguises. If people can't even manage setting the basics of that up, they are never going to come at some convoluted script setup.

Couldn't you just spawn them out in space somewhere? Like a mile up in the air, or under the ground.

It would probably look more impressive with a disguise that didn't hide the head.

If you want to learn to swim, you have to jump in the water.

All a disguise does is point to a specific appearance.2da row. This completely replaces the appearance of the creature it is equipped on. This means it will use whatever appearance is dictated by that appearance row, including the head. So if the armour in question specified a Duros head, then when Carth equipped it he would have a Duros head. There's no easy way to dynamically assign a creature's normal head, outside of ridiculously impractical scripting such as JCarter outlined in the Republic armour thread. Either you have your disguise use a full helmeted head, or you create separate unique appearance rows for every single player and companion head, each of which requires its own matching UTI. You then have to have the player manually pick out the right UTI, or you use scripting to provide the correct one based on a script function to check the player's current appearance. The former is what I did for the TSL Jolee outfit, the latter for the hoodless/maskless Revan robes. Either way you are going to be making like 40 UTIs and appearance.2da rows. And that only accounts for vanilla appearances. That method has no provision for dealing with 3rd party custom heads.

There is no provision for adding a new armour class. That would require adding a new column to appearance.2da but those are hard coded.

I have no idea what you are trying to say, but the way armour works is that each armour class has a single model. Variants of that class just use a different texture. Weapons also have classes, but they don't share a common model. Instead, each variant uses its own unique model.

The way KOTOR works, the only way to add a new outift without replacing an entire armour class is as a disguise. Because this means it will replace the entire character, including the head, it's not overly practical to use it for anything that doesn't have a full helmet, unless you are making it for your own personal use and only care about having one head.

The Dark Side option is to force C8 to return to Elise to become her sex bot, if that's the reality you are talking about. I have no interest in making a lesbian sex box mod. If that's what you are after, you'll need to make it yourself. Yes, it would be possible, with varying degrees of effort required. However, I have no plans to port any of those myself. The latter part you describe is a disguise, the same as when you equip the Sand People outfit, Sith Trooper armour, or Space Suit/Underwater Suit.

Yeah that makes no sense. C8-42 is a stand-in for her dead husband. Definitely one droid in the game that is not open for a female replacement.

I don't have any concrete plans, just trying some stuff out. I would assume it would just be a vanilla droid replacement, but I'm open to suggestion in regards to which it might be in either or both games. There are probably some background droids wandering around levels that only have one or two ambient lines that would be easy enough to re-voice from scratch. There are some like that in Taris upper city as I recall, for example. Yes, there are three texture variants, although one of them isn't much chop. I was planning on doing the gold version as well.

Yeah but that's the only one in either game.

I debated whether or not to post this in the droid thread, but seeing as this is a direct port and not my own work I figured it more rightly belonged here. Scorpio, Imperial Agent companion from TOR, as a protocol droid: The shoulders are a bit wacky because of the width of the vanilla protocol droid rig. I had to do a lot of vert shuffling to try and match its long monkey-like arms. I widened the torso, but there's still a bit too much of a gap in some animations. But I didn't want to go too far or it would distort the proportions too much, and result in clipping problems. If it was going to be actually used in either game, it would probably need some new female VO. Would pitch-shifting the vanilla VO be sufficient?

They all have some sort of device at the back of the neck/head: I did consider adding a tank, but they already clip with a lot of hair, so adding more junk isn't likely to make things better. And there is no way to make them a skinned mesh outside of incorporating them into the head model (or going for a full body model), so trying to add stuff that extends past the head is pretty much a non-starter. Perhaps that could be an option for a specific NPC version. I was thinking about maybe trying something akin to the Cad Bane look, since there is also that style of hat available in TOR.

With this wave of new members joining in recent times, I have to wonder if perhaps turning on manual moderation of the first half a dozen or so posts for new accounts is in order. There seems to be a pattern of necroing old threads, posting in the wrong forums, etc. that could do with a firm guiding hand.

Last time I tried doing it in KOTORMax, the result in-game was pretty stuttery for even a simple, slow pan of a only a couple of meters. While your video example is nausea-inducing, its movement is smooth (all the more impressive given the breakneck speed of the translations).