Ok, time to start using our tools. Article prerequisites: - you should be computer and Morrowind-savvy enough to be able to install and make work most of the tools. - you should be one of those couple of modders/mod users willing to learn and use my best practices. Imagine you are a player willing to install a new mod or a modder willing to make your mod as clean and error-proof as possible (I would say 'clean as an elven arse', 10 points to you if you recognize the quote without googling). I suggest you keep your modding/mod fixing work to a dedicated copy of Morrowind folder without touching the original Morrowind installation.

If the value is 1, the file FILENAME.ESP.MAP is created in the DataFiles path with the map data. Howden Wrv 204 Manualidades. If the value is 2 and one has created a directory Maps in the main Morrowind game directory, this command will create a 256x256 high color bitmap of each exterior cell in the game. This command takes a long while even. May 10, 2002 Get all the inside info, cheats, hacks, codes, walkthroughs for The Elder Scrolls III: Morrowind on GameSpot.

For in-depth explanation about having multiple Morrowind installations, read. Basically, it is just a matter of copying the entire Morrowind folder somewhere else.

After having extracted the mod package to some folder using your preferred archive tool (I like portable included in, but you can use anything you like), let's see the readme and eventually follow the instructions. Delcam Crispin Rapidshare Download. I'm using / to copy/move/compare files between folders, naturally you can use your preferred file manager, or even standard Windows file manager.

Now, let's start having a look at your mod (we will call it mymodname.esp in our examples) using. Selecting it from the mod list and looking at the right Mash panel, we can realize what are the masters of the mod. Then, I suggest you have installed and working, so we can use to find information about possible mod problems. I have it named tes3lint.pl inside the Data Files folder, and I use it from a tes3lint.bat containing this line: perl.exe tes3lint.pl -a 'mymodname.esp' >tes3lintout.txt I change the mod name each time, a little annoying, but I've not found a good way of integrate it to Mash yet. My thought about tes3lint report (tes3lintout.txt file in our example) parts: • Find out if the plugin defines autocalc'ed spell: these can cause problems (enemies killing you with too powerful spells) because they are automatically used by NPCs, so if you find these spells too powerful you may want to edit the mod in and set them as not autocalculated. • Find out if the plugin has an implicit dependency on Tribunal/Bloodmoon functions because it uses them but does not list the expansion as a Master: in this case, you may want to set the proper masters, just load the master with the mod in TESCS and save the mod; this may generate evil GMSTs, but we will clean them after. However, note that a modder may have willingly not included explicit dependency in case master resources are not needed (e.

Myself in water life mod) and stated in the readme that a Tribunal/Bloodmoon/GOTY engine is needed to run the mod, so as usual take a look at the readme to decide. • List: they will be cleaned automatically by our tools, anyway this is good to know and often an index of mod author accuracy (see also ). • Find deprecated usage of Leveled List scripting functions on standard Bethesda Lists: this is rare to find in recent mods, you could need. • Find duplicate (i.e.: 'dirty/unclean') records that are unchanged from one of the masters: this also will be cleaned by our tools. • Find all records in the plugin that override records in its Masters: usually not problem, may be by design. • Finds potentially buggy case where INFO dialogs have had their IDs changed, Shows duplicate and modified INFO dialogs: unintentional changes of this kind are a common source of dialog compatibility problems, so better fix those if you know what you are doing. • Find CELLs that trigger the FOGBUG: good to know, if you are a modder fixing your mod, better fix it in TESCS assigning to interiors a fog value of 0.01 instead of 0.