JCarter426

The implication of the dark side ending is that the Republic is destroyed. Obviously there had to be some semblance of a status quo for a sequel to happen and for the Republic to exist in the films. Revan's disappearance allows for that while also at least giving some recognition of players' choice in the first game. Even if Malak had access to the Trayus Academy, it was not his center of power. The Star Forge was. On the other hand, and I know you take issue with this, the Sith of KOTOR 2 did not have the Star Forge. In the wake of their civil war, their center of power moved. I don't understand what this means. The Sith in KOTOR 2 would not exist without Revan. Of course the Trayus Academy was connected to him or her. The Sith governor you meet was still being trained. Presumably, there, but that is beside the point. There were multiple training facilities. Korriban was not unique. Again, the idea that Revan had multiple masters was established in the first game. Zhar says that Revan had a master other than himself, and we are never told who this is. KOTOR 2, as a sequel, introduces us to a character that must have existed, but that we had never met before. You are given every opportunity to disagree with Kreia in dialogue, and the very nature of the game, with you as the player and Kreia as the final boss, forces you to oppose her ideologically. Kreia herself admits to her hypocrisy and that she has to be stopped: Nobody is forcing you to believe her point of view is correct. Chris Avellone has said that he wrote Kreia to raise questions that he had about Star Wars, but I think you are putting words into his mouth as much as he put into Kreia's. I'm not familiar with other Expanded Universe material relating to the Mandalorians from that time, so I can't comment, but this is a minor reference that players familiar with the films would understand and is irrelevant to the story of the game. I don't know how you inferred so much from a few sentences that say little more than "a battle happened." The Battle of Malachor V is a minor plot point that is barely mentioned in the original and elaborated upon in the sequel.

Yeah, it's the fade out effect that causes this problem with certain hardware. I think I've had this problem on destroying NPCs that have bump maps. It's probably a memory leak or some similar issue.

It is explained that after Revan disappeared, nobody was powerful enough to control the Star Forge: The existence of one academy does not preclude the existence of other academies for other purposes. The Sith have multiple training facilities in the first game: Korriban, Lehon, Manaan, Taris. There is no reason they couldn't have had another on Malachor, assuming it was even active after Malak took over. Chronicles of the Old Republic implies that it was abandoned at some point and reestablished by Kreia after the events of the first game: Although that source is riddled with continuity errors. I don't know where you got this from. The only character in the first game who explicitly mentions having trained Revan is Zhar: And that implies that Zhar was not Revan's primary master, just as in the second game, it is said that Revan had many masters: You disagree with the villain of the story's point of view. And this is a problem how? I thought this was an explicit reference to Jango Fett's death in Attack of the Clones. The only mentions of Malachor in the first game are: This seems consistent with the second game's depiction of the events to me, in as much as it can be consistent with so little existing information.

Yes, I've received some reports of problems on Android. I think this is specific to the device's hardware, and I don't know of any way to fix it at this time.

It looks like whatever changes that mod makes to Bastila's dialogue is incompatible. However, the two mods do essentially the same thing, at least as far as Bastila is concerned. If you want to use the rest of that mod, it should work if you delete the Bastila files before installing mine.

This is normal. You shouldn't move/remove them before running TSLPatcher. TSLPatcher will patch the existing files and this is usually fine. This, however, is not normal and means the mod didn't install correctly. Are you using any other mods that affect k_hbas_dialog.dlg? And if so, could you attach your backup copy of it?

Yeah, I know. And with a managed language, they have the luxury of being more willy-nilly than if it were C++ or C. Still, I don't think they would be doing it all over the place if it were so universally unacceptable. It's safe as long as you don't read before assigning at some point, and modern IDEs and compilers go out of their way to prevent you from doing that by accident. Again, if you have a compiler you can trust. I know the Visual Studio C++ compiler has some silly bugs, and Clang lets you do things it really shouldn't do because that code won't compile with anything else, to say nothing of NWNNSSComp. I know in most use cases it's minimal, but it can make a difference if you're processing huge amounts of data in a database, which C# and .NET are often used for. The reason C# allows uninitialized local variables, unlike, say, Java, is specifically for the performance gain. It mattered to somebody somewhere at some point. I mean if you give a variable in an inner scope the same identifier as one in the outer scope. The variable in the outer scope is hidden. Which you can also file under don't do that, but people make mistakes. Well yes, ideally you shouldn't have too much nested code in the first place. Another reason why I don't mind NWNNSSComp replacing nested else/if with else if.

I've seen numerous examples in the documentation for C# and Java, including the very page on variable initialization in C#. The C++ textbooks I've read (Starting Out with C++, Professional C++, C++ Notes for Professionals) obviously warned about the dangers of using uninitialized variables, but still used the extensively when it was safe. I was taught that a) it is theoretically more efficient in languages that don't require variables to be initialized (e.g. C++ and C#) as minimal as that efficiency gain may be, and b) it's more readable—if you don't know what the value will be, don't say that's the value, as that's potentially misleading. This, on the other hand, I was taught was bad practice because it increases the chance of hiding variables by accident and creating conflicts. So I was told that it's better to avoid this except for temp variables in a for loop or for a swap. This was just within a function, though—obviously global variables have their own problems. I was also told that, in terms of memory, it's better to allocate it at the start of a function and have it crash there if it's going to crash rather than in the middle of execution. But I question whether that's a realistic problem anymore. Well... yes. I believe you. 😧

This is still common practice, at least as far as I've been taught. Yeah, there are security issues if you then try to read one, but modern compilers either won't let you do that or will initialize it with a default value, if the language itself doesn't. With that in mind, I don't see the issue. I agree. I'm not concerned about syntactically identical source code. The way the source code is written is... not always the best way, to put it lightly. The issues you've mentioned before don't seem like they should cause problems to me. Like with the nested else/if vs a simple else if, that'll only be functionally different if you declare something local to the else branch's scope. And, obviously, don't do that. And I doubt the compiler would've optimized for it that way if it would produce functionally different code. It usually knows better than we do. I think that depends on whether you ask Oracle or Google...

This isn't possible. Weapon sounds are determined by the base item type, and it isn't possible to add new lightsaber types. At most you could have different sounds for standard/short/double.

Yeah, there is not much benefit if I still have to type out a list. I can write a program that wouldn't require that. That part is no big deal. What I'm unsure about is whether certain files would have to be edited internally. That's more involved.