DarthParametric

There are two options if you want to apply a command to multiple NPCs with the same tag. The first is a loop iterating through every creature in the level (useful if you need to deal with multiple sets of tags), the second is to call the GetObjectByTag function multiple times, each with a different nth index to grab each creature. Check the full command: // 200: Get the nNth object with the specified tag. // - sTag // - nNth: the nth object with this tag may be requested // * Returns OBJECT_INVALID if the object cannot be found. object GetObjectByTag(string sTag, int nNth=0); Identifiers are 0 indexed, so the first creature is 0, the second 1, and so forth. So to get the 5th Tach, the command would be GetObjectByTag("c_tach", 4). Since you didn't specify an index, the compiler is pulling in the default index 0. In this case, I'd actually go with a combined variation so you can add a bit of randomness to things. Like so: void main() { object oTach; int i; location lPath1Run = Location(Vector(327.34, 206.69, 7.71), 0.0); for (i = 0; i < 5; i++) { oTach = GetObjectByTag("c_tach", i); DelayCommand(1.5 + IntToFloat(Random(3)), AssignCommand(oTach, ActionForceMoveToLocation(lPath1Run, TRUE))); } } Since pathfinding is pretty terrible, you may have to introduce additional delay between each to prevent them running into each other. You could probably just pad it by also adding in IntToFloat(i) in the delay value, which should force each subsequent value to increase while still retaining some randomness.

I have no idea if KOTOR actually supports Chinese, since it was never released in that language. I think Neverwinter Nights does though, and Odyssey is based on Aurora (NWN's engine). Start by referring to these links: https://wiki.xoreos.org/index.php?title=Xml2tlk https://wiki.xoreos.org/index.php?title=TLK_language_IDs_and_encodings In theory you'd convert a UTF-8 XML with strings in simplified Chinese to a binary K1 TLK using Xoreos with the following command: xml2tlk --cp936 --kotor dialog.xml dialog.tlk The language ID would need to be changed at the top of the XML file <tlk language="130"> based on the table from the link above. You can get Xoreos Tools here. Here's a vanilla English K1 XML if you need it: dialogK1.7z But the actual translated text is only half the job. As I mentioned above, Odyssey uses a font sheet, not a font file. It's an image with each individual letter of the alphabet in a position that is defined in the accompanying TXI file. There are about half a dozen or so font sheets in K1. They have separate ones for the different resolutions apparently, plus additional ones for the end credits and the cheat console. A font sheet itself typically has a plain white RGB (aside from icons like controller buttons). The alpha channel is a mask. Here's a vanilla English example: Since Wizard's tool doesn't support DBCS languages, you can try this older tool to generate a font sheet and TXI - https://deadlystream.com/files/file/535-kotor-font-tool-nwn-font-maker/ I'm not sure if that will work either, but it's worth a try. Unfortunately the texture sheets it creates are quite low resolution though. You'd need to duplicate the sheet TGA and TXI to match all the vanilla filenames: fnt_console fnt_credits fnt_creditsa fnt_creditsb fnt_d10x10b fnt_d16x16 fnt_d16x16a fnt_d16x16b fnt_dialog16x16 fnt_galahad14 Although I'm not sure if that last one is actually used.

Odyssey (KOTOR's engine) doesn't use regular fonts, it uses a font sheet (i.e. an image of the characters). So language is effectively "hard coded" unless you edit the font sheet. There is a tool that will help you do that - https://deadlystream.com/files/file/2375-kotor-autotranslate-tool/ - but unfortunately it doesn't support DBCS languages. But it might at least help you create a custom font sheet manually. I assume you already converted the translated text back into a binary TLK file? I'm not entirely sure if the TLK format even supports DBCS languages.

If you're talking about a cutscene playing when loading a module, then the two avenues are either the module's OnEnter script (defined in the ARE and/or IFO), or the OnEnter script of a trigger placed over the module's entry point (script defined in the UTT, placement in the GIT). The former is https://github.com/KOTORCommunityPatches/Vanilla_KOTOR_Script_Source/blob/master/TSL/TSLRCM/Modules/907MAL_Malachor_V_Trayus_Core_(cutscene)/k_907_enter.nss which looks like what you want.

Why would you make another separate patch mod? You could have submitted them to K2CP. Hell, you could have just asked to take over management of K2CP.

Added a manual reconstruction from bytecode to the repo - https://github.com/KOTORCommunityPatches/Vanilla_KOTOR_Script_Source/blob/master/TSL/TSLRCM/Modules/907MAL_Malachor_V_Trayus_Core_(cutscene)/a_904sion.nss

It can be disassembled into bytecode though. a_904sion_BYTECODE.nss

Looking at the academy DLG, the anim it uses is 10006. All those earlier ones are probably K1 references that DLGEditor is listing that don't work in TSL.

You should be able to crib what you need from vanilla scripts. In this case, the end of the scene between Kreia and Atton in the polar academy ("Sleep, murderer") should be exactly what you want. I would guess they literally just kill him rather than applying an animation.

You're far better off scripting animations rather than trying to use the dialogue animations.

Apparently so. V_FreightL01 is the actual original, which is 1024x1024.

"Extract"? You mean get the name? It's LDA_FreightL01. It also has a normal map, LDA_FreightL01b, but it's unused.

Any should work. There are a few free ones around: https://mh-nexus.de/en/hxd/ https://github.com/WerWolv/ImHex You can read this tutorial post for some general information about how to hex edit for your specific resolution. If your resolution was 1920 x 1080, for example, at the appropriate offsets I posted above you'd replace 80 02 with 80 07 and E0 01 with 38 04.

Ah. This is after the Dark Side ending? If so, that requires manually patching the exe yourself in a hex editor, since ndix UR never updated his patcher with the info. I provided some info on how to do it in the description of this mod:

Try downloading this replacement Russian font texture and putting it in your Override folder: https://github.com/KOTORCommunityPatches/K1_Community_Patch/blob/master/tslpatchdata/translation_russian/fnt_creditsb.tpc Click on the "Download Raw File" button on the top right:

Yeah.

I was thinking I should also do a version using the TOR-ported Rodian. That has regular-sized hands.