MO Skyrim Tool Launcher 0.0.0.6

The program can set the working folder for the called application.

This can be handy, if the program uses it's working folder when browsing for files.

This does NOT override the default behaviour for programs that call the "Open File Dialogue" with standard settings as then Windows will use the user documents folder as starting folder.

The following folders can be assigned as working directory:

- the source folder of the source file,

- the folder the called program is installed in,

- Skyrims Data folder,

- the emulated path,

- Auto Mode.

if the assigned working directory is not available/could not be found, the program will use Auto Mode.

if anything else than the numbers 1 to 4 are entered, the entered value will be threated as path.

The AutoMode will choose in the following order, based on what's available:

emulated path, folder of the source file, Skyrims Data folder, the install folder of the called program.

Side note:

Some program need their install folder to be the working directory, as else they'll not be able to find their files.

This can be done by configuring the program accordingly, so the use of this folder is forced for specific programs.

See the next section for details.

if the source file can not be found, the program will try to keep as many valid data as possible, whereby this data is split as followed:

- file w/o extension,

- full path (i may include checking each folder in the full path, but no promisses),

- drive.

This way the browse dialogue will start with the available valid data, instead of the default directory.

Meaning: You start browsing from the available folder and/or drive, which should save you some time.

Convert to 8.3 convention for path and file names.

This is available for the source path & file, the path and executable for available programs and MOs path and executable.

As for the source path and file, this bypasses a bug in MO and is only applied to the file name itself, if it contains a space, so the original (long) file name is preserved.

As for the other options to convert to 8.3, this can be used for programs that have problems with long path and/or file names or with to many sub directories and to shorten the commandline.

This program uses an iNi file for configuring programs, while 2 Skyrim programs are hardcoded and by this don't need to be added to the iNi.

Those programs are:

- Creation Kit

- Archive.EXE

The listet Papyrus Compiler Wrapper is still a W.i.P. and will no longer be displayed in later version, if the APPS PapCompWrapper is not installed. So this entry can be ignored as it's of no use in combination with the vanilla Papyrus compiler.

An iNi file, including a comment section with explanations at it's beginning, is part of the download.

if the iNi file got lost or screwed up, here the template for V0.0.0.6 of this program:

;[...]    : The section is the name of the program, that'll be displayed in the list.;Path	 : Must contain only the full path to the programs executable.;EXE	  : Must contain only the executable name of the program, including extension.;FileType : The files types (files extensions) the program supports.;WorkDir  : The working directory for the program. Can have the following values:;		   1 = if an file is given, the directorie of this file will be the WorkDir.;		   2 = The folder of the program will be the WorkDir.;		   3 = Uses Skyrims data folder as WorkDir.;		   4 = The emulated path will be the WorkDir, if applicable. if set to this, but MO is not used, AutoMode will take place.;		   if you leave this empty, the programm will try to determine itself, but programs that need their dir as WorkDir may not work.;		   The order for AutoMode is: EmuPath, SourcePath, SkyimData, ProgPath.;		   if filled with anything else, then the listed number, the value will be interpreted fixed as path.;PathEmu  : Bool value (0 or 1) that disables (0) or enables (1) the usage of the Path Emulation.;		   in case of MO, MOSKTL will try to emulate the vanilla path, that will be available thru MO for the given file.;		   The path will have to have a valid vanilla path structure, Like Meshes\*, Textures\* aso inside it.;		   So everything after a vanilla folder will be appended to <SkyrimPath>\Data\, like <SkyrimPath>\Data\Meshes\*.;Use83Path:    Converts the programs path and executable into the 8.3 convention.;		   This might bypass additional errors in MOs parameter handling and can be used;		   for programs that don't work correctly with long paths and filenames or to many sub directories and;		   it's usefull (in tandem with Use83Src & USe83MO) to shorten the commandline.;The order the programs are listed here, is the order, the programs will be displayed in the list.;The only exception are programs that are registered for a filetype and this type of file is given.;As then those programs will be listed first, but in case of multiple still in the order they appear here.;Entries in the [MOTL] block are settings to control this program.;Use83Src  : Converts the source path and maybe the file name into the 8.3 convention.;		    Meant to bypass an error in MO, where MO removes quotes from paths that contain spaces, so those files could not be loaded.;		    The name of the source file will only be converted, if it has a space in it's name. This should help preserve long file names.;		    Boolean value: 0 = off, 1 = on;Use83Progs: Same as Use83Src, but converts the path and executable name of MO and launched programs.;		    Meant to avoid possible other errors and to shorten the command line.;Minimize  : Enables the minimize checkbox by default, so this program minimizes after laucnhing a tool, instead of closing itself.;		    if minimizing is your prefered method, you don't have to click the checkbox everytime as long as this option enabled.;		    Boolean value: 0 = off, 1 = on[MOTL]Use83Src=0Use83Progs=0Minimize=0[NiFSkope]Path=H:\Patches\The Elder Scrolls V - Skyrim\Mod Organizer\Tools\NiFSkopeEXE=NiFSkope.EXEFileType=NiFWorkDir=4PathEmu=1[TES5Edit]Path=H:\Patches\The Elder Scrolls V - Skyrim\Mod Organizer\Tools\TES5EditEXE=TES5Edit.EXEFileType=ESP, ESMWorkDir=2PathEmu=1[TESVTranslator]Path=h:\Patches\The Elder Scrolls V - Skyrim\Mod Organizer\Tools\TESV TranslatorEXE=TESVTranslator.EXEFileType=ESP, ESM, STRiNGS, iLSTRiNGS, DLSTRiNGSWorkDir=4PathEmu=1[SaveTool]Path=h:\Patches\The Elder Scrolls V - Skyrim\Mod Organizer\Tools\SaveToolEXE=SaveTool.EXEFileType=ESS, SKSEWorkDir=1PathEmu=0[BSAopt]Path=h:\Patches\The Elder Scrolls IV - Oblivion\BSAopt V2.0.0EXE=BSAopt x64.EXEFileType=BSAWorkDir=1PathEmu=0[Test]Path=C:\Test 1, 2, 3\EXE=Test_1.EXEFileType=WorkDir=PathEmu=

Programs that are configured in this programs iNi will be displayed in the in the list of available programs in the same order, they are listet in the iNi.

So if you want to change the order in the list of available programs, just move the iNi blocks accordingly.

The only exception are programs that are registered for a specific file type and that match the file type of the source file.

Those will always be displayed on top (with a ">" as prefix), but still in the same order, they have in the iNi.

The open file dialogue will use the last opened path as source folder or fallback to MOs mod folder, Skyrims Data folder or this programs install folder - in this order.

The LOG window is usually of no big use, unless you notice something is missing, like a registered program.

Programs that can not be found, will be displayed in the log window and not added to the list of available programs, because ... uhm ... they're not available.

The "Source file" text box is locked and can not be altered. This may change later.

- add support for multiple files [canceled - will not be included]

- add Drag & Drop support

- make the source file text box editable

- check if the source path is an installed MO mod and check if this mod is enabled in MO and offer activating it if needed, as else EmuPath will not work

- create context menu entries for this program and all programs managed by it, incl. MO versions

- when opening a file that's not registered with this program, try to get the associated program and offer to add it to the iNi, followed by registering itself for this filetype

- if only a file was handed over, add current dir as path (for all command prompt lovers)

- add wildcard support for file types so HexEditors and such are always offered

- minimize to tray

- other stuff, like fixes and suggestions

Simply unpack into MOs install folder.

Unpack into MOs install folder, overwrite and you're good to go.

if you already have a custom ini from before V0.0.0.6, those are the changes for manual adding:

- comment section

- MOTL settings, right below the comments

A spoiler inside the configuration spoiler shows the iNi, so you can copy & paste the new entries.