DumpTool v1.1.0
All of these commands which output files or directories put them in the current working directory. Therefore, it is not advised to run commands which generate a lot of output (i.e. dumpall
, etc) in the folder where the program resides.
Any of these command usages can be accessed through the help interface:
Usage: DumpTool.exe help
Commands
list
List all of the UIDs and their types in the given container.
Usage: DumpTool.exe list <forge file>
find
Find the forge file(s) in the given directory that contain an asset with the given UID
Usage: DumpTool.exe find <directory of forge files> <uid>
inspect
Get some basic details on a given UID from the perspective of the containing forge file
Usage: DumpTool.exe inspect <forge file> <uid>
dump
Dump a non-archive asset
Usage: DumpTool.exe dump <forge file> <uid>
dumpall
Dumps all non-archive assets
Usage: DumpTool.exe dumpall <forge file>
This command is slow.
dumpmeshprops
Dump all of the MeshProperties containers a flat archive, using the search index to recursively dump all of the models and textures referenced by each container
Usage: DumpTool.exe dumpallmeshprops <index file> <forge file> <uid>
See the index
command for help on creating search indexes.
dumpallmeshprops
Dumps all flat archives which contain MeshProperties containers
Usage: DumpTool.exe dumpmeshprops <index file> <forge file>
See the index
command for help on creating search indexes.
This command is slow.
findallmeshprops
Searches all of the MeshProperties containers in the given forge for ones that contain the given UID
Usage: DumpTool.exe dumpmeshprops <forge file> <uid>
This command is slow.
findallmeshpropsglobal
Searches all of the MeshProperties containers in all of the forges in the given folder for ones that contain the given UID
Usage: DumpTool.exe dumpmeshprops <forge directory> <uid>
This command is slow.
index
Create a search index of all of the forge files in a given directory. Required for some commands.
Usage: DumpTool.exe index <directory of forge files> <output index filename>
The output index filename doesn't matter as long as you use the same one in commands that require it, although the .db
extension is preferred. The produced databases are standard LiteDB databases and can be browsed or accessed using any standard LiteDB tools.