Oblivion
0 of 0

File information

Last updated

Original upload

Created by

MofoMojo

Uploaded by

leeus

Virus scan

Safe to use

Tags for this mod

About this mod

Oblivion ESM/ESP Script Dumper v2.8.2 By: MofoMojo GUI by: astridor/MC Galore Patch by: leeus This application takes an ESM or ESP file and extracts/dumps all of the scripts in it to a \\esmfilenameScripts directory in the location where the application is running. So, if the app is run against the

Permissions and credits
Oblivion ESM/ESP Script Dumper v2.8.2
By: MofoMojo
GUI by: astridor/MC Galore
Patch by: leeus [leandro conde@TES forums/[email protected]]

Oblivion Script Dumper GUI (v1.0.1)

Is a graphical front-end application, written by Astridor/MC GALORE, which lets you operate the dumper interacting with a visual window instead of using the command line interface. It still uses the OBScriptDumper.exe an calls it under the scenes.
Kudos and thanks to Astridor for making this great visual addon.

Oblivion Script Dumper
This application takes an ESM or ESP file and extracts/dumps all of the scripts in it to a \esmfilenameScripts directory in the location where the application is running. So, if the app is run against the oblivion.esm the scripts will be dumped to the \OblivionScripts directory.
It then creates an Index of functions and commands with hyperlinks to the script files.

Also supports DRAG N Drop. Drag an ESM or ESP onto the OBScriptDumper.exe file and it will automatically parse, create indexes, and dump the scripts in HTML format.

Usage:
OBScriptDumper.EXE <filename> [options]<br><br>Options:<br> -nohtml<br><span class="wbbtab"></span><span class="wbbtab"></span> Disables generation of .HTM formatted scripts<br> -text<br><span class="wbbtab"></span><span class="wbbtab"></span> Enables generation of .TXT scripts<br> -noindex<br><span class="wbbtab"></span><span class="wbbtab"></span> Disables generation of the index files<br> -nowiki<br><span class="wbbtab"></span><span class="wbbtab"></span> Disables linking to wiki WITHIN scripts<br> -parsecomments<br><span class="wbbtab"></span><span class="wbbtab"></span> Parses comments ";" for the occurrence of values<br> -dumpunused<br><span class="wbbtab"></span><span class="wbbtab"></span> Dumps all known functions/commands in the settings.xml<br><span class="wbbtab"></span><span class="wbbtab"></span> file to the indexes instead of just those that occur in the scripts<br><br>Requirements:<br>This application requires .Net Framework 2.0 to be installed<br><br>Notes:<br>The script dumper should be able to extract scripts from any ESP or ESM file. If you find one that doesn't work please contact me @ the elderscrolls.com forums.<br><br>The dumper now uses a settings.xml file which MUST be in the same directory as the OBScriptDumper.exe. The file can be modified to suit your own needs.<br><br>A typical entry looks like the following:<br><br> <entry location="script" class="Commands" type="general" url wiki="true">OnTriggerMob</entry><br><br>location: This tells OBScriptDumper to look specifically in scripts for the occurrence of a word. In this case, OnTriggerMob. For now, all locations must be set to "script". <br><br>url: Not used, but this will eventually be implemented to link occurrences of an entry to a different url.<br><br>class: Indicates what index the value, if found, should be added under. You can make up your own.<br><br>type: Not used, but this will eventually allow an index to group entries with the same type together.<br><br>wiki: if true, this will create a hyperlink to the wiki site, for any occurrence of the entry in a script.<br><br>I have added several sample entries to show the extensible nature of the settings.xml. One will create an Index-spells.htm which contains a list of any scripts that have the spell Vampirism50 reference. The other two are values, such as GameDay and GameHour will be found in a Index-values.htm file one with wiki links and one without.<br><br>Thanks to Grundulum of the elderscrolls.com forums for providing suggestions on fixing the false positive bug, and the idea that lead me to building the index files.<br><br>Changes:<br>Version 2.8.2<br>- Fixed problem generated by new version of .NET framework. <br><br>Version 2.8<br>- System now checks to see if a stylesheet is in the exported scripts directory. If one doesn't exist, and there is a stylesheet.css in the application directory where obscriptdumper.exe is located, the system will copy it to the exported scripts directory.<br>- Moved scripts into a subdirectory below the <module>Scripts\ directory<br>- This will likely be the last one for some time...I have moved on to another Oblivion related project and this really addresses most of what it was originally envisioned to do.<br><br>Version 2.7<br>- Added Stylesheet support. You must copy the stylesheet.css file into the proper scripts directory, manually, for this to work.<br>- Modify the stylesheet to your hearts content :)<br>- Added even more variables, functions, skills as retrieved from oblivion.exe<br><br>Version 2.6<br>- Updated settings.xml to include other known functions, global variables, stats and skills.<br>- Resolved another minor parsing bug. <br><br>Version 2.5<br>- More false negative bugs where hyperlinks weren't occurring properly. Restructured the way the HTML formatting was occurring which introduced the bug when I started checking for commented code<br><br>Version 2.4<br>- Fixed a bug where values that were after comments that occurred after a statement weren't ignored.<br><br>Version 2.3<br>- Fixed a bug introduced with the rewrite of parsing to capture comments where some values weren't being properly parsed in lines where they occurred by themselves.<br><br>Version 2.2<br>- Links to wiki within scripts automatically. Replaced -usewiki parameter with -nowiki<br>- Now it disregards finding values that are in commented lines unless the -parsecomments parameter is used. One caveat to this is that the line must begin with either a ; or spaces/tabs that lead up to the comment. Coments that begin at the end of a statement (if that's even possible in CS) will still be parsed. Thanks to Tegid on elderscrolls.com for this suggestion.<br><br>Version 2.1<br>- While on vacation, I noticed that the linkage for the Index files in the header of each index was bad. Fixed link generation.<br><br>Version 2.0<br>- Completely re-written for XML supported settings file support and extended hyperlinking.<br><br>TODO:<br>Allow default settings to be added to the settings.xml file.<br>Create a Master Index with hyperlinks to each of the Indexes.<br>I'd like to extend this to include parsing out details about gamesettings, and other scripts. This way, if someone wants to see what's changed in an ESP file, they'll be able to do so. <br><br>Known Bugs:<br>None known at this time, though messing up the formatting of the XML or leaving out something might cause problems. I have not tested.<br></module></filename>