[EDIT: These two posts have been moved to their own thread
here, and all future edits will be done on that thread instead.]
MODDING BASICS (by a fellow amateur), PART 1
PrefatorilyWhen I first decided- after a veritable decade away from BG1 & 2 (with brief interruptions by BG1 reinstalls through the intervening yrs)- to go online over 3 months ago to see if there was anything better than DSotSC out there in the way of BG mods, this was the first thread I found. It didn't help me much for what I needed simply to get started, so I floundered a bit, wondering if it was even worth it. But after starting a
post that began the process for me, over the course of these last 3+ months I was helped into the modding process by numerous regular posters here, including especially igneous.sponge, Son of Imoen, Humanoid_Taifun, Grond0, suttree, Irrbloss, and DMWW. Their contributions (and patience) were, have been, and continue to be invaluable to my attainment of any sort of mastery over the modding process... and I'm still learning... so I owe them my gratitude. I also feel grateful to the modders out there who did all that work (ugh) so the rest of us could play, and I feel like I want to give back- at least to the BG "community" at large- somehow. I can't mod-build or code (at present), and I never have been particularly game-savvy with any game, but I can at least articulate what I've gone through. Besides, why go through all this learning process just for myself?
It was as I glanced at this thread again recently that I thought, "Wouldn't it have been nice if there were a post right there in the beginning that supplied me with all (or most of) the info I needed to point me in the right direction and avoid a number of the 'learning curveballs' involved in the process?" Not that people couldn't benefit from the same brain-exercise that I've been experiencing during that process, but it just would have been nice if I hadn't had to also endure the same brain-wracking... or in any case require so much coaching. So that's mostly what I'm going to attempt with this post: to lay out a sort of beginner's guide to BG modding.
So this is really directed to first-time mod-users, those interested but not knowing how, those already in the process but who could use some direction... you know: not an advanced guide or a challenge to modders who know their code from their cantrips... Anyone else should feel free to correct me or make suggestions obviously, particularly if I end up laying caltrops or simply miss something that seems essential... I'll edit as I can to clean up whatever messes my mistakes might cause...
At the OutsetFirst of all, you need to start out with the basics
correctly- a must if any mod use is going to be reliable. You'll need full versions of the game- either BG1, BG2, or both- and then you'll need to patch them. A "full" version means installing every game element to your hard drive so that you don't require a single swapping of discs (and so the mod installation will be able to find the material and modify it). In BG1 a full install is accomplished by manually clicking everything clickable with the "custom install" option, while in BG2 it's only a matter of choosing the "full install" option. It is recommended that you also install the official expansions: Tales of the Sword Coast (TotSC) for BG1 and Throne of Bhaal (ToB) for BG2. Although they aren't necessary for all mods, there is some significant content you miss by leaving them out of the equation, particularly Durlag's Tower and the game's ultimate conclusion in ToB, and some mods do require one or the other expansion or both.
You'll also need to patch your games to the most current version because that is the version for which all BG modders have made their mods. You can get the latest official patches for BG (BG1 only) as patch #
1.1.4315 or BG: Tales of the Sword Coast (both BG1 and the TotSC expansion) as patch #
1.3.5521 for BG2: Shadows of Amn (SoA only) as patch #
23037 or BG2: Throne of Bhaal (ToB) (if both SoA and ToB) as patch #
26498. Keep in mind that there are different patches for different countries (at least for BG1 & TotSC), and Fileplanet seems to have a list of links for other version beneath the one to which I've linked. None of those links are "recommended," by the way, (I can't remember where I got mine,) but they are carrying the proper patch version. You can always find the one you need by a simple Google search (which is how I just found them). Note that if you install BG1 and TotSC you only need the TotSC patch, but if you also install BG2 and ToB, you should go in that order: BG1, TotSC, TotSC patch, BG2, ToB, ToB patch.
You should also make a habit of installing your games
outside the Program Folder. This is primarily for Windows Vista (and possibly also Windows 7) users, but it may just be a good habit for any Windows user. Vista in particular tends to apply operating system standards to anything within the Program folder, sometimes preventing you from saving or altering things and other heavy-handed intrusiveness. If you instead create a folder called, say, Games in your C-drive folder- i.e.,
next to, not
inside the Program folder- you can avoid a lot of Vista difficulties. Another Vista (and probably Windows 7) loveliness is that whenever you start your game, you're better off not simply double-clicking the desktop icon or single-clicking it from the Start Menu or what-have-you. Instead right-click the game icon and scroll down to "Run as administrator" to bypass yet another wave of Windows OS intrusiveness. I've found that this also works for other games on Vista. Trying to run the game normally can end up failing in such a way as to make you believe the game is broken, but in fact it's only Vista imposing itself.
The other thing you should do is change your "baldur.ini" file to add a couple lines, but remember that the entries are case sensitive and must be typed
exactly as they appear below. After the [Program Options] line, create two new lines each for these two:
DebugMode=1
(this enables a number of options if you need to "cheat" to get around issues; for instance, a plot item might not show up due to a mod bug, but using the CLUAConsole you can bring in the missing item and thus not lose your game; in-game you can access the CLUAConsole by simultaneously clicking the "Cntrl" button and space bar, and then use various commands as described, for instance, at
this site)
and:
LoggingOn=1
(this creates a log that will track any errors that arise during gameplay, especially useful for troubleshooting if there is a crash)
Another step is necessary before modding in order to protect yourself from having to reinstall the game from discs over and over, thereby having to repeat all the above steps over and over again as well. Instead you should create a "clone" folder of both the fully patched & prepped BG1 folder contents and the fully patched & prepped BG2 contents. What I've done is create another folder in the Games folder which I call BG Mods, and in there I have another folder called Clones that holds all the separate cloned folders- namely "BG1 Clone," "BG2 Clone," and others.
In order to clone properly simply create the clone folder, naming and placing it as you wish, highlight everything in the primary game directory folder, copy all the contents, then open the clone folder and paste everything there. Then wait until it's finished pasting. It can take up to a half hour (depending on computer speed), but it will be far easier and quicker to reinstall using this copy-paste method than starting over from discs and patches and baldur.ini edits over and over. When it comes time to reinstall your game- whether because you want a new install, you suspect your game has become corrupted somehow, or any other reason- you only need to go into your game folder, select everything, and delete it. You should then have an entirely empty game folder. Then go back to the clone folder, copy everything, return to the game folder, and paste it all back in there again. All the files will recognize the game folder only anyway. Voila... Again it can take time, but it's less hassle, and it's unquestionably faster than starting everything laboriously from discs to edits again.
That's pretty much all the pre-modding basics you need to cover.
It is worth preparing yourself for multiple installs. Although it is possible to use a mod's own uninstall option, it is always less risky to go the longer but more sure route of a complete reinstall (deleting everything and starting over) because mods often overwrite each other, and if you remove only one mod, it may also remove all the changes it made to yet another mod- or it may simply not uninstall its code and components particularly well- and then your modded game becomes corrupted and prone to crashes and bugs from the uninstall alone, not due to actual bugs in the remaining mods themselves. I've found from experience (and others can attest to this) that doing a complete reinstall when any changes need to be made is simply always the better route to go. As Grond0 put it:
Although I've found it reasonably easy to get a good stable set-up (in both EasyTutu and BGT) I've had very little success in revising this, i.e. when I try and make a change to an existing mod, as you describe above, it has usually caused significant problems. Now my feeling is that I won't make changes or, if I really need to, it will probably be quicker to reinstall from scratch.
Note that there is an easier method to restore your primary game to pre-modded status, but because I've found in every single instance that it fails to work properly, I'm not going to link to or recommend it. It does promise a much faster reinstall though...
To Mod or Not to ModYou really needn't- and perhaps even shouldn't- mod BG at all if you've never played the game. In fact, mods are best appreciated if you've had some thorough experience with the "vanilla" (unmodded) game itself, knowing both its strengths and its limitations firsthand before deciding on how you want to change the gameplay. Also by Grond0:
Although as you can see there is a huge range of mod choices out there you shouldn't feel compelled to use them immediately... The 'vanilla' game is great in its own right and it's probably not possible to really appreciate what the effect of mods will be on your personal gaming likes and dislikes until you have some experience of it.
So if you haven't even played BG before, you really should
not do modding... at least in my opinion. There are plenty of tweaks to the game out there- many, many, many of them. But if you have no clue what the game even entails from in its timing, encounters, pace, game system, etc., why consider how you wish to tweak it? After you've play it through once, if you enjoyed your first experience, go on to BG2, and in the process learn the game mechanics, form opinions about them, get to know the NPC system, adjust to the humor and the type of intriguing and/ or offbeat experiences the game presents, gain some mastery of battle tactics, have patience with the inevitably less-realistic graphics play environment, and most of all keep an open mind about what's been so likable and memorable about this game-that-launched-an-era for so long.
Even if all you do is play through the first few chapters and explore a bit to get a sense of how the game plays and the type of world into which you're delving, you'll be far better off in deciding how you'd like to see the game modded. BG was worth playing exactly as it was a decade ago, and those who mod generally do so because they still want to play it a decade later, albeit with various changes and extras to correct perceived game mechanics issues and to add extra content.
The Initial Modding ChoicesI'll also add a quote from Humanoid_Taifun that should further preface any modding choices. In response to a first-time mod-user's request for a list of mods...
So sayeth the wise Humanoid_Taifun...
Maybe I should have said this earlier, but the reason I haven't suggested any more mods yet is that I believe that 3 mods is plenty for a first-time mod user. The more mods you add, the more likely you will encounter incompabilities, leading you back to the belief that mods are bad.
This is a good lesson I didn't internalize myself. You'll have a lot more fun if you just find a few you really like the sound of and feel strongly about seeing in your game, figure out all the how's and what's and where's of installing them (I'll be detailing installation assistance of sorts later), successfully install them all, and then see and enjoy the results in actual gameplay. Then as you play through a modded BG you'll start to get more ideas about more modifications you might want to see, you'll read up on more available, and maybe you'll drop some of the ones you used for seemingly better versions or simply because they didn't work for you, and maybe you'll keep some which become standard mods you'll always use and add more. Also from Humanoid_Taifun:
Once you start modding, from time to time you will find mods you won't want to play without anymore. Over time, these will accumulate.
But most importantly you should keep the mod accumulation modest enough to be able to turn around fairly quickly and adeptly back to the game itself- i.e., rather than becoming bogged down in issues you've encountered due to having modded too much at once. What I missed out on during the first 2 months of modding was actual gameplay. Having started with nearly no modding experience, I ended up researching and experimenting so much and then reinstalling so many times to get a workable install that I've only played only one single- and quite buggy- full game during that entire period. (And there were still issues...) I tend to be unreasonably tenacious about things, however, so I have the capacity to run my head into a wall for nearly 2 months straight and keep at it. I doubt most first-time modders are quite so... erm... thick-headed... Instead most would have become daunted early on and surrendered to the idea that modding doesn't work. It does work: I can (finally) attest to it (and plenty of others can as well). And no one need be as compulsive as I've been.
It is also much easier to troubleshoot any issues which arise from modding that you do encounter if you've only introduced a few new mods than if you have 10 or 20 (or 80) new mods all at once with no clue which mod or mods are contributing to or causing the issues. They can range from nuisances to CTD's (crashes-to-desktop), so know going into the process that this can and does happen. But limiting your own modding ventures can reduce the instances and severity of them and also reduce the time required to fix and/ or recover from them. Note that many mod developers are well-aware of the issues that can result from their mods, so they will often release them with many built-in provisions to avoid them. Also most mods have a forum where the creators can take feedback and learn better about the issues their mods cause or suffer, and then release updated versions that, once again, have built-in fixes. But the process continues to develop, and modders- despite being relatively well-connected- are in no way part of a professional, official team that collaborates on all projects as did the original BG development team (more or less), so there will continue to be issues to work around. Best to play it safe and just enjoy things little by little.
The initial launch of the modding process for me was to find out about what mods are actually out there to choose from. I had no idea what mods were available or even what aspects of the game had been modded or even were moddable. The modder community has been fairly busy in the decade since BG's first release, and there is a lot that's been attempted, much of which has become a sort of standard fare through testing and mod-user preferences. Mod-makers are typically fans of BG (not official company men of Bioware on a payroll) and thus the entire enterprise is "amateur" in that way, but there is also an awful lot of talent and skill that these mod-makers employ to one degree or another in order to produce working mods, a talent and skill that I and probably a lot of BG players do not share. Thus also what you find is that the quality and extensiveness of mods has generally developed over the course of years after the initial release of BG, as has the sophistication of the modding community, but the process has not exactly been systematized, and new modders simply pave new roads where other modders have stopped, advancing wherever the greatest interest happens to be at that stage. What I'm driving at is that the process is necessarily going to be a bit less formal and not exactly uniformly orchestrated: there is no official "BG Mod User Guide" out there.
Ode to the day that a version of BG comes out that has all pertinent mods in one, single, large, easy-to-read, well-organized installer engine with full descriptions replete with links to current mod info by each mod name on a comprehensive list and a simple box-click for mod components to choose from... of course with all the mods working together compatibly and all being installed without any further issues for the player to be concerned with... but that day is... well, don't hold your breath...
WeiDUSpeaking of centralizing the modding community, there has been one development that has made many mods more compatible right at the start of their creation. The WeiDU tool has become a standard of sorts for contemporary mods because it is a single tool to build a number of different mod effects (or something like that). In any case once a mod is built with it, it is more likely to work with other mods that were also built with it- much more likely than mods that weren't. I'm not a mod-builder, so I can't explain how, but I have seen the modder tutorials associated with the WeiDU tool, and I can see how it systematizes the building process. All you need to know to mod, however, is that mods that were built with it are generally going to be more stable and less prone to inter-mod conflicts when installed with other WeiDU mods.
The other thing you need to know is that when you install mods it creates a log in your game folder. That log can be very useful for two things, but I'll only mention one for now: assisting in troubleshooting errors. If you get into trouble with your install, you may be asked for your WeiDU log by anyone trying to help you. If you've installed something wrong or in the wrong order, or installed a problematic component or a conflicting mod, this might be apparent to anyone seeing the log, and ultimately will be to yourself. We'll return to WeiDU later in another context.
If you're going to mod, you should get a WeiDU.exe in your game directory. A common mistake in this regard is to think you need to
install the WeiDU.exe somehow, when in fact all you need to do is extract it. This means you download it, extract it from the .rar (or .zip) file it comes in, and place it in the game directory. And that's it. It will take matters from there by itself, creating a log as soon as the first mod is installed. WeiDU can be obtained
here, scrolling down to the line stating "Download the 'Weimer' Dialogue Utilities" after the link.
Tutu v BGTBefore leaping into a survey of the willynilly of mods (which we'll do at some point, I promise!), it should be known that there are two main larger-scale BG-world changer mods-
EasyTutu and
BGT- in relation to which most of the rest of the mods are add-ons. There are other macro BG-world changers, but, 1., I have no experience with them (and thus can't help anyone with that); 2., they tend to be somewhat older (pre-WeiDU and buggy) and thus often unsupported (i.e., the original creator isn't around to field questions and update their mods with fixes); and, 3., as far as I know, they are not nearly as widely used as EasyTutu and BGT. You're welcome to try others instead, but the key with these two in particular is that they generally maintain the
content of the BG-world- i.e., the quests, storyline, NPCs, etc.- all as they would be in a vanilla game. The other macro BG-world changers tend to remake the BG-world in a much more drastic version, some even removing the main campaign and quests entirely, I believe. Dark Side of the Sword Coast, for instance, remakes an ogre-dominated area to be full of elves instead... for no apparent reason. Those I haven't concerned myself with. BG is a great gameworld in itself, and there is considerable variety that you can add to the BG experience using only mods with Tutu and BGT- or with neither- but you'll ultimately make your own decisions.
Both EasyTutu and BGT maintain BG's main game experience intact, but what they both
add is to apply the the game engine of BG2 to the BG1 gameworld. This means that all the advances that were made in the BG1 game engine by the official BG development team to produce BG2 become implemented retroactively to BG1. There are a number of advantages- such as a more complex proficiency system, access to class kits, reasonably increased missile stacking, access to BG2 creatures, etc.- but the most important consideration is that most of the mods of, say, the last maybe 5 or 6 years have been designed to work with one or both of these two BG1 gameworld changers. It is still very much an option to simply add mods to the vanilla BG1 gameworld without installing either one, but increasingly modders are designing their mods for one or both of those platforms, many not even testing for compatibility with vanilla BG1, mostly because the improvements that came with BG2's game engine are so obvious to those who've played it. (They were not to me, however, since I only played it once a decade ago, as opposed to the 20-30 times I played BG1 back then.) It is generally assumed that if you're modding, you're also using one of the two, but it is
not in any way required, and there will be plenty of mod-users who will affirm that they mod without either on a regular basis. Still I'd rather introduce the new mod-user to them because of their popularity and the advantages mentioned above.
EasyTutu came first- or rather BGTutu came first (meaning "BG-to-[BG]2") but that got displaced by the present standard, EasyTutu (or just as correct simply Tutu). It's been around since very soon after BG2 came out, I believe. Installing it only entails creating a new BG2-improved BG1 in its own folder. When you play through to the end of the game, you then must import your character to a BG2 game as you would normally with a vanilla game. On the other hand, BGT (Baldur's Gate Trilogy- i.e., BG1/TotSC + SoA + ToB) is a more recent development but old enough that most of the major mod issues that arose with it have been corrected. Instead of simply modding BG1, it creates a new, comprehensive BG game that spans from the initial BG1 character creation to the climactic ending of the saga in BG2's ToB, using a cutscene movie to link the two otherwise entirely separate games. Instead of having to import your character, the character porting is done automatically, and it even ports over the exact same statistics of NPCs you may have encountered during the BG1 portion- with the same attribute points, class, level, HP, etc.- though this only applies to Imoen, Jaheira, Minsc, Viconia, and Edwin. The mod BGT Tweaks has an option to port over other native BG1 NPCs, but only those five arrive with dialogue designed by the original BG2 developers. A mage character with a familiar can also keep their same familiar, though it has to be found in the initial BG2 dungeon.
There are advantages and disadvantages to both engines. With Tutu you need only concern yourself with mods that affect the BG1 portion of the game, and it has been around a lot longer for the bugs to be worked out of it. That said, there are two chronic Tutu issues. One is the "greenifying" of water: all water appears a solid light green. You'll need to install the
Degreenifier near the beginning of your Tutu install to make it work, but I've found that it doesn't fix all water, such as the puddles outside Durlag's Tower or water baths in temples. There is also an issue called the Beregost Bug that
still intermittently plagues Tutu players who enter the early town of Beregost and then leave. There is a fix, however, either at
this site or as a component in the mod Sword Coast Strategems I (SCS I) (discussed later), but I would recommend using the SCS one if you're going to install SCS anyway. The mod
Tutufix should also be installed early on to address things that Tutu doesn't.
BGT has already incorporated the Beregost Bug Fix into it, but the mod
BG2 Fixpack needs to be installed prior to the installation of BGT in order to correct things BGT doesn't address and ensure proper functioning of a lot of mods that were developed with it installed. It's also a good idea to install
BGTTweaks afterward, just as with Tutufix. BGT's interweaving of both games can create many potential issues with inter-mod conflicts, not only due to the greater number of mods and components that become involved, but also because mods must accomplish more to be compatible with both simultaneously. It is not at all impossible to do so, and most mods span both without issue, but the potential for conflict is there. Once you feel you can manage a proper mod install that can span both mods, you would find that you can use BGT just as easily. Another issue with BGT that I've found is the increased walking speed which makes your character move faster than creatures that would ordinarily be faster than you, unbalancing the game in your favor, but some prefer that, so it is really just a personal choice and a weighing of that against BGT's advantages.
Another issue arises regarding whether mods are compatible with Tutu or BGT. As Irrbloss once wrote, it's "hit or miss" when it comes to inter-mod compatibility issues between individual mods and either engine:
There is nothing about Tutu or BGT that makes one or the other more or less suitable as a platform for other mods. (If anything, the advantage is with Tutu here, since that really can be used as a platform, while BGT requires you to install some mods before BGT and other mods after BGT.)
Whether mod X works better on Tutu or on BGT is simply a matter of luck and, more importantly, how thorough the modder was in testing his mod.
Sometimes modders create their mods exclusively for only one of the two, sometimes for vanilla and only one, sometimes for both without vanilla, sometimes only testing their mod on some combination of the three, and sometimes simply investing more attention in one format than others.
It is not an entirely arbitrary situation, however. Tutu has been around quite a while, so many of the more long-standing mods will be compatible with it. However, it is no longer being developed- and hasn't been for years- while BGT is, and there is a trend toward BGT because of the conveniences of modding for a single game and the appeal of the BGT bridged-world format. BGT has been incorporated into a larger modding venture called
Big World Project that is being designed at present to make modding much easier. However, the BWP is far from being issue-free as yet, and new modders would probably be better served by simply learning to work with individual mods themselves first, sticking with Tutu and BGT installs before trying that more complicated and recent option. And again my limited experience makes it safer to advocate only what I know.
New mod-users will have to make up their own minds in choosing between Tutu and BGT, but at during the early stages I would recommend starting with EasyTutu like I did. Because it involves changes only to BG1, you'll not need to figure out what to do about BG2 mods yet, nor consider the plethora of extra BG2 mod components that get introduced when using BGT (due to the addition of BG2 content in BGT). If and when you're already fairly acquainted with both BG1 and BG2- but especially BG1- and feel ready for extra modding, then try BGT, or you can always just make a modded BG2 install (which obviously doesn't need Tutu or BGT since BG2 already has the BG2 engine).
Although both Tutu and BGT require the BG2 or ToB play disc (if you used discs to install the games), the two installs work somewhat differently. Both require that you have the full and
unmodded BG1 and BG2 installs on your hard drive, but they install to different game directories. While EasyTutu will create its own game folder (which you should also locate outside the Programs folder) using both BG1 and BG2 game folders as a model, BGT will create itself as a graft into your BG2 game folder. Since Tutu requires an unmodded BG2 game folder, you'll need to create an EasyTutu game first- or at least keep your BG2 clone safe and be prepared to swap the BGT contents out in order to enable a Tutu creation. I would recommend also making a clone of your otherwise pre-modded EasyTutu game folder to go next to the other BG1 and BG2 clones. When you want to do a reinstall, you'll instead just delete all contents of your EasyTutu game folder to paste-replace with the EasyTutu clone contents, just as with BGT you would delete the contents of your BG2 folder to replace with the BG2 clone contents. And again- it's just the fastest, most stable way I know to do a reinstall.
If you are going to install either of them, then this too must be kept in mind: Tutu is (generally) installed before any other mods while BGT is installed after a few mods that lay a framework for it. So keep in mind that BGT may be a macro-mod, but for compatibility reasons that I wouldn't delve into even if I had the expertise to do so, you need to install it in the proper order just like any other mod. This notion will be returned to later in the "Mod Install Order" section.
Mod Readmes & ForumsAlso before installing anything you should research each and every mod you're using. This need not be daunting, especially if you're modding in order to add fun things to your BG gameplay. Some mods are very simple with few components to consider (many are single-component mods) while others have upwards of 40 or so different components to choose from. Given how involved this can be, it is yet another reason to use fewer mods in the beginning. Every mod obviously has a webpage where the download is available, but nearly all mods also have a page devoted to a readme that explains the content of the mod, gives tips about installation, and details the various components in the mod.
Not all mod readmes are the same. Some are exceptionally helpful and detailed while others are skimpy on information, outdated, and/ or are outright erroneous. This doesn't mean the mods with the latter type of readme don't work, but just that a good readme is something to be appreciated... The best readmes- such as for the mod
Sword Coast Strategems I &
II- lay out a comprehensive, proofread, up-to-date, and articulate survey of their modification including a list of every component with a complete description of each one.
By the way contrary to rumors, this cruel slander by Grond0 is completely erroneous:
I couldn't believe you (I eat 50 mod readme's for breakfast...) could have missed that reference.
I have never eaten more than 10 or 12 readmes before midday, so I just wanted to resolve this outrageous exaggeration...
But seriously, the more mods you use, the more readme consultation you'll need to do and the more interrelated details you'll need to factor into your modding decisions. It's not so complicated as I make it sound (or I wouldn't have been able to do it myself) but for sure it pays to read the readmes and keep a wary eye for details.
Many mods also have a link to an active forum administrated by the mod-builder- or by a team of those involved with developing that mod and possibly other mods- where mod-users can post their criticisms of, suggestions for, and praise about the mod. You can learn at such forums what kind of issues others have had or are still having with the mod, whether and how well such issues have been addressed, whether there is a hotfix needed to play the mod without bugs, or what plans there are for future revisions of the mod.
Although you may find answers at the Bioware BG forums- particularly the "Game Technical Support" section- to specific questions you may have about a given mod, you will most likely get more detailed, immediate, and effective answers at the forum site of the mod itself. Keep in mind that it is not always the mod you're having trouble with that is the mod causing the issues. Some mods may work very well to install their own content, but in the process may corrupt or overwrite something that another mod already installed... or a host of other possibilities... So just keep an open mind if and when posting there rather than presuming the mod-builder has done something screwy- or presuming that the mod-builder hasn't... I for one am just impressed at what many mod-builders have been able to do and am glad to see that development does continue.
Mod Install OrderOne of the key issues to look for when perusing mod readmes is compatibility between mods. Mods do different things, involve a variety of different content, and may- especially when modding similar content, such as, say, rules governing rest options- negate each other's components or in any case cause conflicts. However, if you install them in the proper order you can prevent or minimize the issues involved. Many mod readmes will state explicitly where to place their mod in relation to other content-related mods, and almost every time that recommendation will also be shared by the readmes of the mods mentioned. Some mods may spell out exactly how to place their mod or particular components of their mod in relation to specified other mods, but most mods aren't so vigorously and extensively tested by the modder. In fact, one mod may recommend an install order relative to another mod that is an opposite recommendation to what is recommended in the readme of that other mod regarding the original mod. (I know of only one such mod: Ashes of Embers, to be addressed later.) In any case, it is always prudent to simply read carefully the readmes of every mod you're using and to even take notes if need be. By listing the mods in a word document you can easily arrange them so that, when you're ready for the install, you can simply go down the list one at a time.
This list shows a large number of mods known to be compatible (or not compatible) with BGT. There doesn't appear to be any such list for Tutu, but I've come across a few mods that are only for Tutu, such as the NPC mods
Finch and Indira which are mods that add new NPCs to the Tutu-altered BG1 gameworld replete with their own dialogue, quests, and interactions with native BG NPCs.
Fortunately you needn't experiment with mod install order blindly. It is true that there is no readme that simply gives you a list of every other mod in the order best to install them. However, the EasyTutu and BGT mods each have a fan base that has determined a fairly comprehensive mod install order list to assist you. They are not complete (though very nearly), and they are not
necessarily in the order recommended by the individual mod readmes themselves (though they usually are). It can be the case that a single component of one mod is better to install earlier while the rest are better near the end, and this "fine tuning" isn't addressed within these mod install order lists. Nevertheless they are a
generally useful guideline to follow when determining the order of install for the mods you've chosen, and the mod readmes generally note specific details while forums too will provide the necessary information.
Below are the semi-official mod install order lists that have been worked out by EasyTutu and BGT users. I list them only for reference at this point. There is more that you should know before delving into the mods themselves...
1. A fairly well-established EasyTutu mod order list is
here...
2. A huge BGT mod list which more or less lists everything in install order is
here... (Note that it is not necessarily a strictly BGT list, but rather a list compiled by the Big World Project which, as mentioned above, prefers to use BGT. However, I've used it as a mod order list for 80 mods with relative success.)
3. And a list which was designed for the mod Rogue Rebalancing is
here... (I present this one only because it is by far the most comprehensive install guide presented for a single mod that I've come across. It demonstrates that the mod builder has taken a lot of time and effort to extensively test the mod with other mods to determine compatibility issues beforehand. If only all mod-builders were so thorough...)
Installation Preparations and Process: Mod Install TypesThe installation of a mod is usually a bit more technical than installing an application, but still very simple. When you download a mod from its web origin, you're not downloading a little mini-application- nor even the mod itself. Instead what you're downloading is an extractor bundle. What you're looking to obtain from that extractor bundle are the key mod elements, not a single "playable" item. The primary mod files to look for aren't hard to identify: they're generally the same for every mod. They should consist of:
'[mod name]"
(folder)"setup-[mod name].exe"
"[mod name in all-caps].tp2"
"[mod name].DEBUG"
(may or may not be there)First you'll need to get those unextracted mod files into your game folder. So what you download is the extractor, not the mod items themselves, and what you'll need in your game folder must come
from those mod extractors. Thus the first part of the "installation" is primarily just extracting files to the game folder. The second part is to initiate the actual mod element selection and insertion process which I'll discuss later.
The extractor generally comes in one of two forms: a .zip/ .rar file or an installer .exe. You don't get a choice: it's up to the mod designer to package their mod one way or another. The former type usually opens (with winzip or winrar) to present you with exactly the items you need, and I find these to be the most pleasant extractor type because you can now simply extract the necessary items directly to your game folder, and you're done. You'll know if it's one of those types of extractors because, when you open the .zip/ .rar file, you'll find inside precisely the file types mentioned above.
Those are the mod files you'll be looking for to simply drag-and-drop or copy-paste from the extractor to your game folder. Do that and you're done with the first part of the installation: the extraction. To begin the mod element insertion phase, you then just double-click the "[mod name].tp2" to open a command prompt that leads you through which elements of the mod you're going to install.
But not all extractors are so simple. Sometimes the .zip/ .rar will open up to give you an installer .exe- so after extracting the .exe installer type to your game folder from the .zip/ .rar extractor, the former extractor becomes the latter. Most are one or the other.
The .exe installer type ostensibly offers you an easy path of installation, doing both the extraction and element insertion all for you, but I find this to be the more complicated version for reasons I'll explain in a moment. Once double-clicked in the game folder, it first extracts the necessary mod files to a designated directory, and then auto-initiates the "[mod name].tp2" file- whether you're ready to start selecting mod items for insertion into the game or not...
One important thing to remember with .exe installers is that when it prompts you for a directory into which to install the elements, the default folder that the installer application presents is not necessarily (and most often isn't) the folder you want to install to. In other words, don't just click "OK." Check the directory it has listed. This is one thing that makes the .exe type of extractor more of a bother despite seeming to do everything for you: you now must navigate through all the acknowledgments and browse for correct folder selection every time. Some installer .exe's make the folder in which the .exe is currently sitting become the default install folder, so if the installer .exe is sitting in the game folder, that can be at least a little more convenient, but most will prompt you to install in some nonexistent folder in the Programs folder or elsewhere. So be wary when dealing with .exe extractors to pay attention to the destination directory.
Another issue with all extractors is the clutter they cause. Once their job is done and you've extracted everything, there's no need to keep that the .zip/.rar or .exe installer file around in the game folder. Thus they end up making it harder to sort through your game folder to find something. Thus I create a folder for every downloaded extractor, named accordingly with the version listed in the title, and then put all those mod extractor folders in their own folder called "Mod Extractors..." Not sure if this makes me an organization freak, but it certainly simplifies things...
Installation Preparations and Process: Streamlining with Copy/PasteI will also here mention a step that is not necessary, but once again, if you plan on doing multiple installs, this step will make the reinstall(s) that much easier, and if you start off doing this, it will make future mod adds a cinch. I've done many reinstalls by now, and- weary of the time it can take to go through each extraction one-by-one- I've sought the most streamlined, simplified, and swift way to manage it.
Similar to the advantages of creating and working with a "clone" folder, you can also utilize a "Mod Collection" folder that contains all the mod files you'd otherwise be laboriously extracting into the game folder with every new install. First you get all the necessary mod files into the "Mod Collection" folder. When you've copy-pasted all the contents of your "clone" game folder back into the emptied main game folder, you can simply then copy-paste all the contents of your "Mod Collection" folder into the main game folder as well. Having already extracted every needed mod file once into the "Mod Collection" folder, you can now bypass the extraction process altogether and simply copy-paste from then on.
Creating the "Mod Collection" folder becomes slightly more complicated because of those .exe installer type extractors. In the case of the .zip/.rar extractors you can just drag-drop or copy-paste directly to the "Mod Collection" folder, and you've got all you need. With the .exe installer types, first you have to set the destination directory for the "Mod Collection" folder and let it start attempting to install the mod there. Of course, there is no game in the "Mod Collection" folder, so it won't be able to complete the mod item selection process that it attempts to auto-initiate. That's fine because the .exe installers always start by extracting the necessary mod files first, so it will have already done all it needed by the time it gets to that part. As it enters that stage, it will open up a command prompt as if to start offering the mod item selections, but instead it will "ERROR" out due to a failure to find the game's "dialog.tlk" file. Simply enter the key to abort the command prompt and check the "Mod Collection" folder to see that the needed files were indeed extracted there regardless.
Creating the "Mod Collection" folder
is an extra step, but it saves time in the long run by simplifying subsequent reinstalls. Any new mods need only be extracted once into that main "Mod Collection" folder. A further time-saver that utilizes those mod files will be discussed later.
Of course, you could use the "clone" folder as the dumping ground for the mod files, first extracting to the "Mod Collection" folder to get the proper files and then copy-pasting those "Mod Collection" files to the "clone" folder. Thus when you copy-paste from the "clone" folder to the game folder, you'll be transferring both the game files and mod files from the "clone" folder all at once, saving one copy-paste step. But I prefer to micromanage at least that much, keeping segregated the mod files from game files until the final reassembly. If you accidentally start a mod's installer and "corrupt" your cloned game, you'll have to delete everything, segregating out the mod files anyway, and redo the game files. That's a bit more bother than I want to risk, so I just keep them separate. If you keep them separate and want to remove mod files from the group of them you have, you also run no risk of deleting main game files with them, and you can always distinguish mod files from game files that way. And it keeps the "clone" folder more of a perfect "clone."
You might also want to create two separate "Mod Collection" folders- one for EasyTutu, one for BGT- because the mod assortment will be different between them given that some mods work for one and not the other, or some mods have separate versions for each, but that will add more space to your hard drive. Note that the WeiDU.exe should be put into the "Mod Collection" folder with all the mods to be part of the copy-paste group transferred to the game folder.
Installation Preparations and Process: Hotfixes and PatchesOnce you've extracted everything you need to your game folder or "Mod Collection" folder, this would be the moment to apply hotfixes and patches to the mods that require it. These are the "fixes" that were offered by the mod creator due to issues with the mod that warranted immediate redress but aren't part of the official mod files. The "fixes" will usually be included in the next version release of the mod, but mod creators tend to release the official versions only after significant content has been added or changed rather than simply to address one issue, so the fix/ patch is usually a temporary remedy until that next version. Keep in mind that not all mods require such fixes. Out of 80 mods I've been experimenting with only a few required such "fixes."
You'll know if the mod you use requires a hotfix or patch by checking out the forum page of the mod where you're downloading it. It may also be listed on the download page. In order to be sure you're not missing a needed hotfix or patch, it's recommended to periodically check back at the official forum for each mod to ensure you've got the latest version and/ or hotfix and stay current with new developments. This isn't so much a chore, given that new versions of the mod mean potentially interesting new content and options. New versions may also have more or better features and/ or fix bugs in earlier versions or even address inter-mod compatibility issues. Plus it's better to get the hotfix or patch applied
before starting a game with the buggy version, especially since you may not know that it was that particular mod that's causing the bug, and in any case, it's better not to have to reach a "fatal" bug after hours of gameplay and have to "fix" it then and start over.
As an added plus, applying the hotfixes/patches to the mod files directly after extracting the mod files into the "Mod Collection" folder makes certain that the mod files being repeatedly copy-pasted with each reinstall are always up-to-date and free of issues. And this way once again you'll only need to apply them once.
The way most hotfixes work is by a simple drag-drop. After downloading the hotfix, you look in your mod files for the file that is identical to the one that has been hotfixed. It may be the "[mod name]" folder itself or a file inside that folder. You then simply take the downloaded hotfixed file or folder and drag-drop it wherever the original version is. You'll be prompted as to whether you wish to overwrite the existing files, and you should click "OK." That's it- hotfixed. A patch may come as an .exe which you simply run. It does all the patching by itself.
Installation Preparations and Process: Mod Item SelectionOnce you've extracted the necessary mod files and have "hotfixed" them, then copy-pasted them into your game folder (after copy-pasting the clone material), you then begin the mod element selection process with the double-click of the "[mod name].tp2" mentioned previously for each and every mod (or use the .bat process I describe later). You are presented with the command prompt where you'll be asked to make selections.
The first selection is universally language. English is a standard, but others do appear, depending on the mod. Then it follows with which mod elements you wish to have implemented in the game. You simply follow the questions to complete it, and it makes the necessary game alterations or additions with each selection you make at the command prompt until the selections are complete and it prompts for a finish. There are plenty of mods that have only one element, so there is only thing to choose- often simply to install it or not. Others have a large number of elements and you have to choose between different options for how that game element will (or won't) be changed.
Another consideration to take into account is that you can install only portions of a mod if that's an option. Even the mods that have a plethora of different components to choose from do not require you to approve any. You could even select only one of 50 that you like, though it is true that some mods have a main component that must be installed to enable any of the other components. One rule to apply when selecting components is to limit the installation of modding of a particular type- such as say, spell modding or item modding- to a single mod- i.e., rather than using several mods to change spells or avatar appearance. This can limit the possibility of one mod corrupting the same content being modified by another mod and causing bugs. The proper mod install order can often ensure such overwrites are done properly, but you're safer to simply stick to one mod for one particular element change. Also- as was mentioned before- you may need to install one component of a mod, then install components of other mods, and then return to the first mod for more components. The mod Item Revisions, for example, involves this, but that mod's readme explains this better than I will here.
(Continued in next post)
Modifié par Bhryaen, 19 janvier 2012 - 10:10 .
).
.
Retour en haut