DarthParametric

You shouldn't need to specify the unequip. It will happen automatically when equipping a new item.

Does he actually have the items? I assume you aren't editing the UTC if you have to script the change. How are you spawning the items?

The AI is set up to wait a round before equipping weapons to prevent it breaking. If you want someone unarmed to equip a weapon then you need to do that before turning them hostile and initiating combat. Try something like this: #include "k_inc_generic" void GoHostile() { ChangeToStandardFaction(OBJECT_SELF, STANDARD_FACTION_HOSTILE_1); DelayCommand(1.0, GN_DetermineCombatRound()); } void main() { object oDarkJedi02 = GetObjectByTag("tat17_darkjedi02", 0); object oDarkJedi03 = GetObjectByTag("tat17_darkjedi03", 0); ActionEquipItem(GetItemPossessedBy(OBJECT_SELF, "ITEM_TAG_HERE"), INVENTORY_SLOT_RIGHTWEAPON, FALSE); AssignCommand(oDarkJedi02, ActionEquipItem(GetItemPossessedBy(oDarkJedi02, "ITEM_TAG_HERE"), INVENTORY_SLOT_RIGHTWEAPON, FALSE)); AssignCommand(oDarkJedi03, ActionEquipItem(GetItemPossessedBy(oDarkJedi03, "ITEM_TAG_HERE"), INVENTORY_SLOT_RIGHTWEAPON, FALSE)); ActionDoCommand(GoHostile()); AssignCommand(oDarkJedi02, ActionDoCommand(GoHostile())); AssignCommand(oDarkJedi03, ActionDoCommand(GoHostile())); }

This particular instance is caused by one of the module include constants. Read more here. Per that thread, you can bypass it by hex editing. #include "k_inc_generic" void main() { object oDarkJedi02 = GetObjectByTag("tat17_darkjedi02", 0); object oDarkJedi03 = GetObjectByTag("tat17_darkjedi03", 0); ChangeToStandardFaction(oDarkJedi02, STANDARD_FACTION_HOSTILE_1); ChangeToStandardFaction(oDarkJedi03, STANDARD_FACTION_HOSTILE_1); ChangeToStandardFaction(OBJECT_SELF, STANDARD_FACTION_HOSTILE_1); AssignCommand(oDarkJedi02, DelayCommand(1.0, GN_DetermineCombatRound())); AssignCommand(oDarkJedi03, DelayCommand(1.0, GN_DetermineCombatRound())); DelayCommand(1.0, GN_DetermineCombatRound()); }

Ah. That would presumably be where they have both a Sound (for generic alien/droid-speak) and a VO_ResRef rather than one or the other.

Where have you seen 3 used?

No. Most of the vanilla textures in the PC version already have it as part of their TXI data. The engine should just ignore anything that isn't valid.

It doesn't do anything. It's not an engine semantic, it was used by Bioware's texture compiler when creating TPCs and TXBs. It would downres the source texture into a 256x256 TXB, whereas the TPC would remain the original 512x512 or whatever it was.

There shouldn't be any issues as long as you don't just duplicate it but edit it appropriately. For example: //Check for banter 12 if (!GetGlobalBoolean("G_Banter12") && IsNPCPartyMember(NPC_T3_M4) && IsNPCPartyMember(INSERT_NPC_ID_HERE) && GetDistanceBetween(GetPartyMemberByIndex(0), GetPartyMemberByIndex(1)) <= 5.0 && GetDistanceBetween(GetPartyMemberByIndex(0), GetPartyMemberByIndex(2)) <= 5.0 && GetDistanceBetween(GetPartyMemberByIndex(1), GetPartyMemberByIndex(2)) <= 5.0) { AssignCommand(GetPartyMemberByIndex(0),ClearAllActions()); AssignCommand(GetPartyMemberByIndex(1),ClearAllActions()); AssignCommand(GetPartyMemberByIndex(2),ClearAllActions()); UT_SetTalkedToBooleanFlag(OBJECT_SELF); ActionStartConversation(GetFirstPC(),"Banter"); } Insert it below case 11. You'll see there's a gap above the last three closing braces: ActionStartConversation(GetFirstPC(),"Banter"); } // INSERT NEW ENTRY HERE } } } Just make sure the boolean name matches whatever you choose for your added ones. For the DLG, you'll need a new starting conditional. The vanilla ones also have a second script to set the global to true, but you can just roll that directly into the starting conditional, like so: int StartingConditional() { if (!GetGlobalBoolean("G_Banter12") && IsNPCPartyMember(NPC_T3_M4) && IsNPCPartyMember(INSERT_NPC_ID_HERE)) { SetGlobalBoolean("G_Banter12", TRUE); return TRUE; } else { return FALSE; } }

Leaving aside the fact that I thought the entire point was to add new banter, not replace the existing ones, how do you expect me to know what's wrong when you haven't even said what you have done and provided the scripts, DLG, etc.?

MDLEdit decompiles a binary model into memory when loaded, so there's no need to generate physical ASCIIs unless you intend to load them in Max/GMax. I don't believe MDLOps supports the Xbox format, no. Perhaps @seedhartha could be convinced to add Xbox support to KBlender (which now imports/exports binaries directly) if you ask nicely. I'm not familiar with the differences between the PC and Xbox formats, so I couldn't really say what in particular could be causing issues. The only time I have seen something similar is with ye olde MDLOps mangling meshes, so my guess would be that MDLEdit is doing something incorrectly for those models for some reason.

There's no reason it shouldn't run under Win 10. It requires Java though, which is less than ideal. You could always spin up a Win 7 VM and run it under that if you want to contain the taint. Edit: Added the Upari amulet fix to K1CP - https://github.com/KOTORCommunityPatches/K1_Community_Patch/blob/master/Source/k_pkas_hurtgive.nss

You really should just grab DeNCS. void main() { object oPC = GetPCSpeaker(); object oCrystal = GetItemPossessedBy(OBJECT_SELF, "kas25_wookcrysta"); ActionGiveItem(oCrystal, oPC); } The problem is the UTC doesn't actually have the item in its inventory. They used ActionGiveItem because that makes the NPC walk to the PC and do an animation, but it needs to either be switched to a CreateItemOnObject directly spawning it into the PC's inventory, or it needs to first be spawned into the Wookiee's inventory and then given to the PC, or the Wookiee's UTC needs to be edited to add it. If you find a problem that either Community Patch doesn't address, you can just raise an issue for it on the repo. I've added this one (and I also see an issue with the heal scripts).

Since you can't actually add new companions, just replace the vanilla ones, I assume he's using either Jolee, Juhani, Zaalbar, or HK's slot? As such he will potentially incorrectly trigger certain vanilla banters because the script only checks the character slot is active in the party, not what the tag of the actual NPC is. You'll probably need to add a tag check to prevent the appropriate vanilla banters accidentally firing, if there are any. And, likewise, also add a tag check to only trigger your new ones correctly. I haven't looked at the DLG or the associated scripts (I gather that's what the starting conditional script in the first post is), but I assume it is setting the appropriate global to true once a given scene has started, so you'll need to replicate that behaviour as well for your added DLG nodes.

Creating new globals is as simple as adding them to the end of the 2DA. It will require starting a new game for them to work though. Adding extra custom conditions to trigger your banters will require editing the k_bant_trig script. I'm not sure how many total triggers are in the game, so keep in mind that adding additional banters means potentially reducing the likelihood of seeing vanilla banters, since each trigger will only fire once (unless you change the TALKED_TO local boolean checking/setting in k_bant_trig).

As the script says, it's a global boolean. Or technically 11 booleans. The globals are defined in globalcat.2da. The banters are fired by triggers in various modules. They should all use the same global trigger template, k_bant_trig.utt which uses the global script k_bant_trig as its OnEnter. Since 11 cases already exist for vanilla banters, you'd need to add new globals and new conditions for your added banters.

The ones in the archive are just the vanilla scripts so you don't need any special permission. You can credit me for supplying them if you want, but all I did was decompile them and tidy them up a bit so it's really Bioware's work not mine. For compatibility purposes we encourage people to look at K1CP's source, available here, which people are free to use as a basis for their own mods as long as credit is provided. You are likely running it from inside Program Files. Don't put/install anything there and your life will be much easier. Windows is particularly bitchy about permissions there.

Module scripts only exist as binaries. They need to be decompiled. Currently the only option is DeNCS - https://web.archive.org/web/20160405105949/http://starwarsknights.com/mtools/DeNCS.zip Attached are the vanilla module scripts that I have already previously decompiled and cleaned up while working on K1CP. unk_m44ac_Lehon_Temple_Summit_Selected_Source.zip

You say that like I'm supposed to know what it is, but I gather from your subsequent comment that the game is running under a 360 emulator. Assuming everything else is working correctly, it's mostly likely a MDLEdit issue with the conversion. Make sure you are using the most recent beta version, not the outdated one from the official release thread.