Leaderboard

Thanks for the information. I think earlier we had decided to mostly leave it to be pretty ambiguous (as you won't encounter any real terrain on Sleheyron) as to not upset the original intent nor anything established since then. So expect a vague description that could either be barren or volcanic.

Edge of the Empire described Sleheyron as volcanic, actually: I'm not sure what is up with the galaxy map description of Korriban, though. It's usually depicted more like space Egypt in other material, and it's not even particularly volcanic in KOTOR.

I've been following this mod on and off since I was a kid lurking around Lucasforums. Although it is sad to hear you're not working on it anymore, we are all glad you're doing OK and that it has come this far. Looking forward to what the community can do with the files as a resource.

Local man discovers the Telos Military variants of Military and Sentry droids, after years of tinkering with appearances. Man is amazed the game can still toss him a curveball and surprise him with its inner workings.

Glad to hear that you are getting better Logan, that is the only thing that matters! We thank you deeply for all your hard work, dedication and contribution to the community and for your wise decision to share what you worked on with all of us! So, did anyone pick the project up to continue work on it?

The best I can tell you is that neverblender is outdated for kotor and that you should try this instead: Kotor Blender

All of my blogs now have one of those pictures that (usually) indicates the title of the blog. I’ve numbered all of my blogs since I’ve started creating them and I’ve finally reached 100 of these things. Wow. 100 blogs. Someone, please call a doctor! Instead of me rambling on yet another niche topic, I’ll now invite you to go through the previous 99 blogs and see if there’s something you may have missed from me. I’d like you to have opportunity to consider if there’s something you might add to the conversations I’ve previously started. Yes, I do realize that many of the blogs are locked. You’ll be able to tell because it has this picture as the blog’s title picture. If you encounter one of these locked blogs and you still want to acknowledge it, I believe you can still drop either a “like”, or “light side” icon, or a “thanks” icon on the blog. If you’re going to comment on M4-78 stuff, I would recommend you limit the comments on the “like/love” blog on M4-78 EP version 1.5, the “disappointed/hate” blog on M4-78 EP version 1.5, or the “M4-78: Set Decoration” blog covering all of Zbyl2 and Hassat Hunters versions of M4-78 EP. Having detailed reviews of version 1.5 – split in the pro and con blogs – will help me work on another chapter on the documentary if at some point I decide to resume working on it. Note that as of this date: version 1.5 is only available on Deadly Stream. Version 1.3 is only on the Steam Workshop, and MODDB has version 1.2. As I’m preparing to move across the country relatively soon, I’ll be holding off making any new blogs until I am settled in a new place. I haven’t even figured out where on the east coast that my wife and I are moving to so I can’t offer any estimates. And let’s be honest, time estimates aren’t one of those things that I like doing any way. (Have you ever seen my signature? LOL) If you do decide to comment on my blogs, I want to read your comments and not look at one of these . . . This . . . is less helpful to me than something like this . . . or this With the last two pictures, I know what you're trying to say and have more information to use when replying to the comment and/or making new mods. (In the above example, I corrected the mod by putting the missing file.) The likes and thanks icons don't give me any hook to work with. So my faithful reader: Keep safe, keep modding, leave some comments (on my blogs, my mods, and my videos), and I’ll see you at some point on the other side.

Thanks for the ping @Qui-Gon Glenn. You want the honest to goodness truth, the answer is just a lot of trial-and-error. Before I reached my first stable build release I had to play the games through, shifting order and switching mods out, 4-5 times before I could even complete one. That was back before I was more familiar with what I was doing, but the moral of the story, if you will, is still the same--depending on what you're trying to get to work together, it might just come down to a lot of tinkering. That said, JC is absolutely correct that incompatibilities are pretty rare. The most common type you'll have are obvious straight file overwrites, which are disproportionately texture or model changes. In those cases it's as simple as installing what you want last. More rarely you have file overwrites that involve more important files, which you can sometimes get away with overwriting if you know that the file from one mod is just minor changes (a rebalance of values in spells.2da, let's say) while another makes additions. Obviously in that case you keep the one that makes the additions, if you're dead-set on both mods, and either manually re-implement the balance changes or just eat the loss. Properly major file overwrites, like two loose appearance.2da files, can still be made to work if you've got the know-how and patience to merge the data from both files. Otherwise it's a matter of deciding which mod you prefer. TSLPatcher mods are more stable, but whether you'll encounter stability issues as a result of them is often less obvious, as they tend to do more (just by the nature of what mods benefit from using the TSLPatcher) and warnings the patcher spits out can sometimes be intentional, or benign even when unintentional. You don't always know which is which, and even if you go through everything with no errors thrown at all, you can still get a conflict at the end of the day. There's nothing you can do for that, though, except try to structure your install order logically and be smart about what mods you want to integrate. The more you add, and the more that anything you add edits, the more risk you inherently run. Determining a provisional load order is where you're going to be doing most of your legwork, and it's the step that will most directly impact the stability of your final build. This is probably the one thing I might be able to give some useful advice on. For the builds, the install order favors installing loose-file mods first, then larger TSLPatcher mods descending down to those with the most minor changes. The order of importance thus goes from the most trivial loose-file mods to the most important loose-files, then shifts to the most important TSLPatcher/.exe content down to the most trivial. In addition, mods of similar styles (texture replacers, model edits, mechanics changes, etc.) and those with similar thematic foci (Dantooine, let's say) are also grouped somewhat closely together. I've found that this is helpful in determining where you're likely to have conflicts, because by starting with the smallest mods first you'll have less stuff to go through in your override when/if you have a direct file conflict so you can easily determine what mods you're going to be forced to select between, and by grouping themes you're more likely to run into those potential conflicts back-to-back. From the TSLPatcher side of things, installing the largest mods first lets you know right away whether or not your most important mods are throwing any errors in their install phase, and also allows for mods with more specific changes (which are generally smaller) to overwrite the changes made by your larger, broad-stroke mods. Your final functional order might not be similar to that, but installing a test run in this way is the best way I've found to quickly diagnose problem areas or potential issues in what you intend to install, which will let you fine-tune what you're using and when you're installing it to get better results. Once you've cleaned up the obvious issues, though, there's nothing for it but to do a run and make sure everything works. Sometimes it won't--most times it doesn't, for me. A little over half the time I have to restart or modify a test partway through due to unforeseen issues that didn't crop up during the install phase. If you're bound and determined to use a bunch of mods, that's just how it goes.