JCarter426

I've fixed several issues in the past weeks. One was a preexisting issue, while the others were introduced in v2.0.0. This was mostly down to me not having save files with Class-Based Properties and therefore not testing those as thoroughly as I ought to. If you installed one of the Class-Based Properties options before v2.0.4, follow these steps to fix any issues: 1. Install the latest version. You don't need to uninstall the previous version. Make sure to install the same option you installed before. If you are using another mod which edits the workbench dialogue (and is compatible with this mod) restore workbnch.dlg from the backup created. If you haven't started the game yet or haven't acquired the quest crystal yet, you should be good to go. If you have, continue with the remaining steps to fix your save file. 2. Make sure you have a save file with the crystal item in your inventory (i.e. not in a lightsaber). 3. Download the KOTOR Savegame Editor (KSE) if you don't already have it. 4. Count how many levels of each class you have to determine what your crystal's class number should be using the table below. Whichever one you have the most levels in wins. 0 Jedi Guardian/Jedi Weapon Master/Sith Marauder 1 Jedi Sentinel/Jedi Watchman/Sith Assassin 2 Jedi Consular/Jedi Master/Sith Lord 5. Use KSE to replace your crystal item. Find which item you currently have; quest crystals start with qcrystal. The items with two numbers are the crystals with standard properties. The crystals with class-baseed properties have a third number for the class. Remove the existing item, then add the correct item. For example, if you have currently have qcrystal_2_3 and have majority Jedi Sentinel/Jedi Watchman/Sith Assasssin levels, you should actually have qcrystal_2_3_1. 6. Use KSE to correct the global number 000_Quest_Crystal. This can be fund under Globals > Numerics. The number should have the same digits as the numbers in your crystal item, but in reverse. For example, if your crystal item is qcrystal_2_3_1, your global number should be 132. Don't include a leading 0. For example, if your crystal item is qcrystal_3_4_0, your global number should be 43. If you are still having trouble, you can reach out to me in the #tech_support channel of the KOTOR Discord.

It's checked in 904kreia.dlg but never set anywhere in both the original game and TSLRCM as far as I can tell—not present in any other DLG or NCS file. Easiest way to enable it would be to add a call of the script a_global_set on a dialogue somewhere, probably in her dialogue after the Atris fight. I don't know what preconditions make sense, though. It may have been related to other cut content which doesn't exist in the game files.

Girl, it took 15 years for you to get a second season.

I would recommend three separate downloads given the size. I'd probably go with 128. Icons tend to look worse when scaled up too much, but on a 1080p screen the equipment icons are about 96 pixels.

Are you loading a save from before Sherruk was spawned? If not, that is probably your issue. The game only reads from the template file when an object is created. Once an object exists in the game world, data about it is read from your save file. I would also not recommend editing NPCs with KOTOR Tool. It has a few bugs, one of which which causes all of an NPC's equipment to drop even if it was originally not dropable.

There is no script function which does anything like this to my knowledge. Whatever game mechanic change might be achievable with the KotOR Patch Manager. Some existing issues cover exposing more things to the scripting language and making hard-coded mechanics more data-driven.

The _recom value is a priority, not a level number. So if you set it to 11, there are 10 other feats the system will recommend first.

KOTOR 1 has essentially two types of level scaling: 1. Spawning more and/or different NPCs. This may be done either through a script or through an encounter object. 2. Buffing NPCs when they are spawned. This may be done either in an individual script or with the global script k_def_buff. With the first, I would expect the change in stats to feel consistent regardless of PC level. With the second, you will experience diminishing returns at higher PC levels because enemies will be getting the same flat bonus added to a higher base stat.

Broadly, you would need to: Convert the model from one of its currently supported formats to the MDL/MDX format supported by the game. This can be done in a 3D modeling program by importing the model together with one of the existing game models and making some adjustments. Change the item's item type to something else (e.g. Long Sword) by modifying the BaseItem field in the item UTI file. Here is a list of common modding tools. It isn't complete, but it's a good start. Additionally, you would need Blender, 3ds Max, or Gmax for the first part.

This mod was written to install with TSLPatcher, not HoloPatcher. I did not encounter such an error during testing and I am not seeing one now after checking again.