Mod Item Tool - MIT by HSD
Skyrim » Utilities
Added: 11/05/2014 - 03:17AM
Updated: 21/12/2014 - 11:54PM

97 Endorsements

1.3 Latest version

961 Unique D/Ls

1,626 Total D/Ls

13,412 Total Views

Uploaded by -=HSD=-


Last updated at 23:54, 21 Dec 2014 Uploaded at 3:17, 11 May 2014


Changing from Windows 7 to Windows 8.1 gave me the opportunity to fix a bug some users were experiencing (AppCrash with "FileNotFoundException"). I used VS 2013 to recompile things and you'll now get an additional .dll-file which is to be placed alongside the "mitconfigtool.exe" ("moditemtool.exe" doesn't need it). This should finally get rid of that 'lil bugger.

Please note that from now on all versions will be compiled for .NET Framework 4 only (Windows 7 users will have to install this seperately).


This is a fairly simple/small console-based program, which reads your load order (aka "plugins.txt") and then searches .esp's and '.esm's  for items. In the process of doing that it creates simple scripts (containing "player.additem xxxxxxxx 1") which then can be used in game.
Since Version 1.2 another tool is included making it possible to create the mandatory configuration file (which had to be done manually in previous versions), select exactly which mods will be (not) scanned for items (via an exclusion list) and what kind of items are to be registered for the scripts (Armor, Weapons, Keys, Potions etc.).

"WTF! Why would that be a good thing?" you might ask - Well, if you got 30 or more armor/clothing/weapon-mods in your load-order (like me), such tool comes in very handy, indeed.

Since I was not aware of any existing tool (or easier method [than adding the items manually in-game]) that does the job, I thought "How hard can it be?!" (cheers to JC^^) and got cracking.

Please be aware that this is a very, very "quick and dirty"-like program, it works with my installation and, in theory, should work with any other installation as well, but I can't give any kind of guarantee. Oh, and you'll need .NET Framework 4 to run it (comes pre-installed in Windows 8, Windows 7 users will have to install it seperately [if you don't have already, it's pretty common]).

A Note regarding error messages (in game) when using the scripts
This issue still exists and I can't really find a solution for that other
than to properly manage your load order. I've (sometimes) had this issue
while using BOSS or LOOT (I didn't manually manage the load order while
BOSS or LOOT were at it until I got suspicious, because they seemed to
make just a huge mess of it [regardless which of both I used - I didn't
use both at the same time]). What happens there is: The mod IDs are
calculated normally/correctly for the "esm-section" (the scripts do work
for the .esm-files in that case), but before skyrim loads the
.esp-files it does increment the ID counter by one. This of course means
that the majority of the generated scripts is essentially useless,
because the actual mod's ID are always greater by one (thus resulting in
these error messages).
Not using BOSS or LOOT and rearranging the mods with NMM in a careful manner (plugin dependencies) resulted in a
far less chaotic load order and surprise, surprise: Problem gone.
I don't really understand this, because generating a useable load order is
exactly what BOSS or LOOT are made for ... probably a mistake on my
side using BOSS/LOOT incorrectly (other than that: no clue).
I know now why this particular weirdness happens and I probably have to apologise for having blamed BOSS and LOOT: This issue happens due to problems with plugin-dependencies. I had one particular mod still enabled while plugins it depended on were disabled (funny enough that "my" skyrim didn't crash due to this, because normally it takes even the slightest opportunity to CTD ["Oh, you wanna load a save? Sry, gonna crash there!"]).
To sum it all up: My own stupidity is to blame. - If you get this issue, check your plugin-dependencies.


1. Download
2. (Optional) Verify the hash-checksum
3. Extract and/or copy the "moditemtool.exe" and "mitconfigtool.exe" into a folder of your choice.

Usage of "mitconfigtool.exe"
Creates/modifies the configuration files for "moditemtool.exe".

1. Run "mitconfigtool.exe". If it doesn't find an existing configuration, it guides you through the configuration process (selecting the skyrim folder is pretty much it). Keep in mind that sometimes when other windows are on the screen simultaneously, this tool tends to "hide" behind these windows when it displays the next dialog (just go to the taskbar and reselect it in that case) - Most likely this is fixable, but I just didn't want to spend much time on that particular issue (it isn't exactly a 'biggie').

After the configuration is done (or an existing configuration is present) the tool loads the skyrim's plugin list and displays it in the checkbox list. There you can choose which plugins are to be excluded when scanning for items (if there's no existing exclusion list, all .esm-files will be checked for exclusion automatically - this, of course, can then be changed).
Above that checkbox list you will find a section for selecting which item types should be included when scanning and another section to change the configuration paths (should you ever need to). (The whole thing should be pretty self-explanatory)

A Screenshot of the main dialog can be seen in the images-section ("Screenshot 1").

2. When you have selected the desired options/settings, click "Save" or "S'n'C" (which means "Save and Close"). If you click "Close" while there are still changes pending to be saved to the configuration files, you will be asked if you want to save before closing the application (standard program behaviour).

 - When plugins are removed from skyrim's plugin list that currently are in the exclusion list, these will be displayed with '(***)' prior to their filenames (at the next start of the config-tool). Furthermore these will be put at the end of the exclusion list and, if not deselected, still be saved in the exclusion list as well. This way, they don't get removed (unless you specifically deselect them before saving) from the exclusion list if a plugin is removed from plugins.txt. See "Screenshot 2".

Usage of "moditemtool.exe"
Creates the actual scripts for in game use.

1. Just run it (it will process the plugin-files and create the scripts according to the configuration made with "mitconfigtool.exe").


1. If the load order is changed you'll need to run "moditemtool.exe" again (if necessary "mitconfigtool.exe" as well to modify the exclusion list). If this happens a lot, I suggest creating a .bat-file which executes it prior to staring skyrim/skse.
2. Alongside the seperate (relatively small) scripts for each plugin, "moditemtool.exe" furthermore creates one big script containing all scanned items. Beware: Can crash your game of it contains a 'uber' massive amount of items to be added (yes, I've seen that before) and can mess up mod-quests (because it will add quest items to your inventory as well). You can execute it with "bat getAllModItems".

Things I wanted to mention

1. The sourcecode will be available for downloading as well, but be warned: I wouldn't consider it "nice" or "good programming style" or "efficient" (and you'll find that some variable names are in German). Things get even worse regarding the config-tool: Apart from the itemType bool-Array description, I've made no comments whatsoever ("get things done" and not "get bogged down with explaining and documenting [basically all the stuff you don't want to do^^]"). It isn't a great deal of code and many things are probably done much easier/faster/shorter using methods or expressions I've never about, but I think it's relatively easy to understand (and after having looked at it you'll likely think "man, this idiot's code is utter trash").
2. I will try to sort of "maintain" this "thingie" for a bit, but most of the time I'm preoccupied with studying, being at work, making music or playing (skyrim, swtor etc.), so I can't guarantee for "quick solutions" should the program crash, get the mod-IDs wrong or fail in any other thinkable way (it shouldn't make your computer explode, though^^). If anybody out there would want to update/rerelease it or incorporate the concept into another utility (BOSS springs to mind)- no biggie, just do it (no permission needed).
3. Hashes will be provided in the download-descriptions.


.NET Framework 4.0 (pre-installed since Windows 8)
Skyrim ... obviously

- Platform upgrade to VS 2013 from VS 2010
- Recompile with VS 2013 (.NET Framework 4 only from now on)
- No changes to the sourcecode itself

- Added support for more (hopefully missed none) item types (like keys, potions and so on)
- Added support for a list to exclude plugins from scanning (rather than to hardcode this into the program code like I've done in previous versions)
- The newly added configuration utility now makes the usage of MIT easier and allows managing the exclusion list

- The original mechanism to delete all old scripts before scanning for new items didn't work, because of a stupid mistake I made (not a biggie, thus I didn't upload a new version). Now it works as intended (it deletes all files containing "gami_" and the "getAllModItems.txt" file in the skyrim folder [excluding subfolders])
- Enabled the program to scan for weapons (WEAP-records)
- Prior to Version v1.1 empty ARMO-records were added to the scripts (resulting in these empty "added"-notices in skyrim) - this should now be fixed
- Added an optional line in the .settings-file to enable the user to configure which item types should be scanned for
- Original Release