Jofferson (not to be mistaken with “Geoffers”) is a tool designed to help you with manifests, aliases, overrides and mixintos.
The main interface. Red means that there’s something wrong with this mod, resource or reference.
The resource inspection window. It shows what points to this resource and what this resource (likely) points to.
- Scans all folders for valid manifests
- Creates a list of all references inside a manifest. This currently includes aliases, overrides and mixintos.
- If a reference points to a json file, said json file is (kinda “stupid”) parsed for other references too.
- Able to list all references to and from a resource.
- Filter functions to quickly search for stuff.
- Able to deal with directories and smod files. Even mixed!
- Context menus to copy (absolute) paths, open files or open folders directly.
- Error reporting window that lists all errors that were encountered while attempting to parse this mod.
What it’s useful for
- Get an insight into a mod’s aliases, overwrites and mixintos
- Validate that all your
file()s are properly formatted
- Find missing resources
- It’s also a kinda nice wallpaper.
The usual .NET Framework 4.5. This time WPF is also a requirement, but that has been part of Windows since Vista - so you most likely already have it.
This is mainly a debugging/validation tool. Since I’ve seen that it might not be obvious how
file() or mixintos/overrides work, there’s lots of errors that could arise.
What do you think should Jofferson offer as functionality? Should it go beyond the normal entity/jsons and parse the UI/components/functions too (only in the manifest - i.e. not recursive like it does the .jsons)?