Morrowind Plugin Manager 1.2

Beschreibung: =============================================================================Morrowind Plugin Manager 1.2by DW (, 2004=============================================================================Table of Contents:-----------------1.1 Version History1.2 Package Contents1.3 Development Environment1.4 Development Notes1.5 Installation1.6 Uninstallation1.7 What It Is1.8 What It Does1.9 Usage1.10 Not-So-FAQs1.11 Disclaimer1.12 Distribution and Copyright1.13 Thanks1.14 Contact1.1 Version History:-------------------MPM 1.2, September 2004- timestamp defect fixed- support for nonstandard archive structure- minor GUI defects fixedMPM 1.1, August 2004- RAR archive support addedMPM 1.0, May 2004- Original release1.2 Package Contents ( (v1.2, 9/19/2004 13:39, 1,708,032 bytes)unrar.dll (7/14/2004 21:11, 158,208 bytes)readme.mpm.txt1.3 Development Environment:---------------------------MS Visual C++ 6.0Qt 2.2 ( ( ( SP1, Win98 SE1.4 Development Notes:---------------------The zlib source was compiled for use as a static library, but not modified.The unrar.dll is used by and packaged with MPM 1.2 in an unmodified state.1.5 Installation:----------------Extract the Morrowind Plugin Manager archive to a folder of your choice (forinstance, your Morrowind folder). If you are upgrading from a previousversion of MPM, simply overwrite the old files. MPM 1.2 is fully backwardcompatible - you do not need to modify an existing plugin database.1.6 Uninstallation:------------------No changes to your registry or system folders are made by this application.Simply delete the files that came in the install package, and any filescreated by its use (mpm.cfg, mpm.pdb, mpm.log). Be sure to uninstall anyplugins before removing the application though, or you will be left withall installed plugin files on your drive.1.7 What It Is:--------------Morrowind Plugin Manager was developed for two main reasons. First, it wassimply for me to get experience using C++ with the Standard Template Library,and GUI development using Qt. The second reason is that another mod utilityfor Morrowind (I assume you know which) doesn't work as I'd expect, or wish.It skips installation of files which it determines are not necessary (basedon a scan of the ESP and ESM files) for the plugin to operate (meaning, forexample, the plugin author's documentation is not installed). And the scan isnot reliable, as stated in the code (it doesn't detect certain dependancies),so sometimes it fails to install and uninstall files which do in fact belongto a given plugin. With MPM, I skip that complexity and instead install allfiles in a plugin archive.1.8 What It Does:----------------Morrowind Plugin Manager installs all files found in an archive to yourchosen Morrowind installation path, and associates them with the pluginentry in the plugin management display. File collisions are handled byallowing you to overwrite, skip, or rename the file (the plugin archive nameis automatically appended to the file, allowing you to try the file latermanually if you choose) with a click of a button. Plugin and file sizes aredisplayed in the interface. Uninstalling a plugin removes all filesassociated with the plugin except files shared with any other plugin, andremoves empty directories that are no longer needed.A configuration file, 'mpm.cfg' is saved in the MPM folder. This filecontains your chosen Morrowind install path as well as the original filelisting at the time of Configuration. Do not delete this file unlessinstructed to do so by the application. The application will prevent youfrom reconfiguring if you have any plugins installed, however, if youintentionally delete it to avoid this safety check and then change theMorrowind path, you are asking for trouble. That is essentially separatingthe plugin database from the indexed files.A plugin database file, 'mpm.pdb' is saved to the MPM folder. Do not deletethis file unless instructed to do so by the application. It is written inplain text and is in the format, '[archive name]:[file name]'. You can editit by hand but be sure to follow the format. Failing to do so could lead toa damaged or inaccurate database. Make a backup copy first.If 'Options -> Write Log To File' is selected in the menu, output shown inthe log window will be written out to a log file, 'mpm.log'. The settingfor this option is intentionally not saved, as log files can grow veryquickly. Simply set the option when you run Morrowind Plugin Manager if youwish to log the session. You are safe to delete the log file at any timewhen it is not in use.1.9 Usage:---------MPM will prompt you to configure your Morrowind path on the first launch.Depending on the number of files currently in your 'data files' folder andthe speed of your machine, this initial configuration process might take afew seconds, so be patient. If you wish to reconfigure it later, choose'Options->Configuration' from the menu (no plugins may be installed when youconfigure). To install a plugin, click 'Install', and browse to a validplugin ZIP or RAR archive. If an unpacked file already exists, you will beasked what action you want to take (skip, overwrite, or rename). If thedisplayed filename is truncated due to length, hovering the mouse pointerover it will show the full filename in a tooltip style popup. It shouldbe obvious, but I will say it anyway - use caution whenever using the "YesTo All" overwrite option. Be very sure what you're about to overwrite, oryou could be overwriting default Morrowind files without knowing it. It isalways best to step through an install, manually verifying overwritesfile-by-file. To uninstall a plugin, choose the plugin from the list andclick 'Uninstall.' No shared files will be deleted. Registered file typesin the 'Files Used' list can be opened with your operating system's defaultapplications by double clicking the file or pressing return. You can choose'Options->Write log to file' to log all activity to a file (mpm.log).Before patching Morrowind, it is highly recommended that you uninstall allplugins installed by MPM. After you patch, be sure to reconfigure MPM. Thiswill rebuild the base configuration for MPM, and will prevent the overwritingof plugin files by new files added or changed by the patch, and vice-versa.An advanced mode exists for MPM, for the sake of cleaning your 'data files'folder in the event that an installation problem occurred which you cannotundo, or you damaged or deleted your plugin database file, etc. It isrecommended that it be used only when necessary. To access the cleanupfunctionality, run mpm with the '-advanced' switch. A new menu item,'Clean Up', will appear in the File menu. If you wish to remove all plugins,and clean your folder of unplugged files, or otherwise return MPM and the'data files' folder to the state it was in when you last configured MPM, youcan use this advanced function. It will delete all files in the 'data files'folder which are not listed in the MPM configuration file (mpm.cfg). If thisis not completely clear to you, do NOT use this functionality. To repeat,ALL files other than those listed in mpm.cfg will be irrevocably deleted.This includes all files not installed by MPM - for instance, a plugin file ofyour own you might be working on would be deleted. Additionally, your plugindatabase file (mpm.pdb) will be deleted. You've been warned and re-warned.Use caution if you insist on using this advanced feature!Note that the Clean Up process can be intensive and take several minutesdepending on the speed of your computer and if you have many pluginsinstalled. If MPM appears to have locked up during a Clean Up, chancesare it has not - just be patient.One final caution: If you are manually copying plugin files to your 'datafiles' folder frequently, be aware that these files will not be configuredas either the MPM base configuration or an MPM installed plugin. These filescould be at risk for overwrite or deletion, if you install or uninstall aplugin that shares the file name(s). One of the principal design intentionsfor this utility was to keep the 'data files' folder clean of junk files,and keep all plugin files associated with their plugins. If you choose tomanually pollute the folder, MPM cannot be held responsible. The best way toavoid this is to always use MPM to install plugins from zip archives (orconfigure the PDB entry by hand if you are comfortable doing so). Besides,you DO keep your own plugin creations separately backed up in zip archiveform, don't you?1.10 Not-So-FAQs:----------------Q: What is different with version 1.2 of MPM?A: Timestamps were not being written properly for extracted files inversions of MPM prior to 1.2. I'm a bit surprised that 5 months and nearly4000 downloads (as of 9/04) beyond original release, neither I nor otherMPM users had noticed or commented on this defect. Regardless, I believeit is now fixed. Additionally, some support has been added for nonstandardarchive structure. MPM should now be able to install plugin archives it didnot previously support, namely those built up from folders other than the"data files" folder or deeper. The 'File Exists' dialog has been changed tono longer resize based on filename length. Long filenames are now truncatedin the display, with the full filename shown in a tooltip by hovering themouse over the displayed name. Finally, a few minor GUI annoyances havebeen corrected.Q: What is different with version 1.1 of MPM?A: Support for RAR archives has been added.Q: I am upgrading to MPM version 1.2 from a previous version. Do I need touninstall and reinstall my plugins?A: No, the database for MPM has not changed for the upgrade to version 1.2.It is fully backward compatible.Q: Okay, but what about this timestamp thing? Is it important?A: Yes, timestamps can be important for Morrowind plugins. If you havebeen using an old version of MPM and have not had any problems with pluginordering, then you might as well leave them as they are. If you have hadproblems, or want the timestamps for your plugins to be correct against theoriginal release archives, then you should uninstall/reinstall the plugins.Q: What plugins can be installed using MPM?A: MPM installs plugins from ZIP or RAR archives with directory structurepreserved. As of version 1.2, as long as an archive contains properdirectory structure, MPM should be able to install it correctly. Forexample, MPM 1.2 will understand any of these following archive formats:Example 1: readme.txt/textures/flamesword.tga/sounds/swordout.wavExample 2: /data files/readme.txt/data files/textures/flamesword.tga/data files/sounds/swordout.wavExample 3: /games/morrowind/data files/readme.txt/games/morrowind/data files/textures/flamesword.tga/games/morrowind/data files/sounds/swordout.wavSupport for archives built up from folders other than the "data files"folder or deeper was added because, although it is silly to pack an archivein such a manner, quite a few plugins do exactly that.If a plugin archive does not contain proper folder structure or naming, orhas no folder structure at all where it should exist, it is not the faultof MPM. That is the plugin author's choice of blunder.Q: What about plugins that come packaged as a self-installing archive?A: If you want or need to use MPM with a self-installing plugin (for instance,GIANTS), you could simply install the plugin to a temporary folder and thencompress the files into a ZIP or RAR archive that MPM can use.Q: I see that MPM lists installed plugins by the original archive filename.Do I need to keep the archive file? Does MPM use it after installation?A: No. The original archive filename is used to remind you of the exactpackage from which the plugin was installed, the version which was installed,an alternate name you may have chosen for the plugin, etc. After a pluginhas been installed, you can safely delete the archive file if you wish.Q: Can MPM only use ZIP files? What about RARs?A: As of version 1.1, RAR support has been added. An archive file can benamed anything - a file extension (or lack thereof) is unimportant - but itmust be a ZIP or RAR compressed file.Q: I accidentally deleted my plugin database (PDB) file. Am I screwed orwhat?A: Pretty much, yes, but you can try to minimize leftover junk on your drive.The best thing to do would be to try to remember each plugin you hadinstalled, and then reinstall them right over the old files. That way, MPMwill build an entirely new database from the plugins, and it will be as ifyou'd never lost the database at all. In the worst case scenario, where youcannot remember what plugins you had installed, you have the files leftoveron your drive. So basically, it's as if you had not used MPM at all. You'lllose some hard drive space to those files, but it won't harm your machine oryour Morrowind installation. In this case, you could opt to use the advancedcleanup functionality (see '1.9 Usage'). Or you could delete leftover filesmanually.Q: Files renamed with MPM's automatic renaming are not associated with theplugin. Why?A: When a file is renamed with MPM, the plugin name is appended onto thefilename. For example, "readme.txt" becomes "readme.txt.myplugin". Thesefiles can be manually examined by you, deleted by you, or used to replacethe original by you. Trying to keep track of that in the plugin database isunrealistic. Therefore, when you choose to have a file renamed during aninstall instead of skipping it or overwriting the original file, you assumecontrol over it. You could for instance decide after trying a renamed file,that you prefer the original version, and thus you only have to restore theoriginal and delete the unassociated renamed file. Doing so will not affectyour plugin database, so everything is kept in order.Q: Is there any danger in installing a plugin by unzipping it myself? Whatif I use another plugin installer?A: Yes, this could be dangerous. Read section '1.9 Usage' - it's important.Q: Does MPM do anything to change my system settings or the like?A: No. MPM does not register or install any system files. It does notchange your registry. It does not watch you sleep at night.1.11 Disclaimer:---------------I assume no responsibility for anything that happens to you, your PC or data,or your love life due to the use or misuse of MPM. It shouldn't affect themin any way, except perhaps for improving your love life.1.12 Distribution and Copyright:-------------------------------MPM is copyright(c) me, DW. It may be distributed as is without modificationto this package or the contents, for use with the game Morrowind. It maynot be packaged and or sold by any money grubbing magazines and schlockwaredistributers without my prior written consent. If you have a questionregarding distribution, contact me ( Assume no rightswith regard to this package. If you have obtained this package throughdistribution such as on a CD or with a game magazine, you and I both haveprobably been ripped off. Please take a moment to inform me am in no way affiliated with Bethesda Softworks. Morrowind and allassociated properties are their copyrights.1.13 Thanks:-----------Special thanks to DB and TN for (almost tireless) assistance and suggestions.Thanks to Dongle for the Oblivion v1.1 Daedric font.1.14 Contact:------------This application has been virus scanned, tested, and used; however, nosoftware can claim to be perfect. If you find an operational defect, let meknow. To otherwise comment, praise, moan, etc., send email


Mit der Nutzung dieser Website erklären Sie sich damit einverstanden, dass wir Cookies verwenden. Weitere Informationen hierzu finden Sie in unserer Datenschutzerklärung.