Skip to content
This repository has been archived by the owner on Mar 3, 2024. It is now read-only.

Releases: parzivail/RainbowForge

DumpTool v1.3.1

10 Aug 23:50
c173b0d
Compare
Choose a tag to compare
  • Fix a large unmanaged memory leak caused by zstd

DumpTool v1.3.0

10 Aug 21:57
f2c103e
Compare
Choose a tag to compare
  • Greatly improves organization and folder structure when dumping meshprops
  • Includes support for a bunch of new container formats to improve find and similar commands' ability to find assets

DumpTool v1.2.2

04 Aug 16:18
4a58e73
Compare
Choose a tag to compare

Fixes an issue with loading some meshes via the RainbowForge library.

DumpTool v1.2.1

04 Aug 03:09
6dbe188
Compare
Choose a tag to compare

Fixes another crash relating to findallmeshprops.

AssetCatalog v1.0.1

04 Aug 16:17
4a58e73
Compare
Choose a tag to compare

Fixes an issue with loading some meshes via the RainbowForge library.

AssetCatalog v1.0.0

04 Aug 14:24
8a62d33
Compare
Choose a tag to compare

AssetCatalog lets you open a forge file, browse through assets (just mesh assets right now), categorize them, and label them for later use.

AssetCatalog

DumpTool v1.2.0

04 Aug 02:21
1691a08
Compare
Choose a tag to compare

Fixes a couple of crashes when it encounters assets it can't unpack. Same usage as the previous release.

DumpTool v1.1.0

03 Aug 00:48
cebccbf
Compare
Choose a tag to compare

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.

DumpTool v1.0.1

02 Aug 18:39
5207898
Compare
Choose a tag to compare

I am a fool, the commands are now actually registered with the command line parser. Yeehaw.

Basic Usage

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.

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.

DumpTool v1.0.0

02 Aug 18:34
fb281d9
Compare
Choose a tag to compare

DumpTool v1.0.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.

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.