AbyssMoth Package Hub

AbyssMoth Package Hub is an editor window for installing, removing, and updating a curated list of AbyssMoth and RimuruDev packages from one place.

It is useful when you have many small utility packages and do not want to remember every repository URL by hand.

Installation

Install the package through Unity Package Manager with Add package from git URL... and the repository URL of this package.

You can also add it as a local package while testing.

Usage

Open AbyssMoth/Package Hub.

The window loads a bundled catalog from PackageCatalog.json and shows package status for the current project.

Available actions:

• Install a single package
• Remove a single package
• Update a single package
• Select multiple packages and run one batch install, remove, or update
• Update all installed catalog packages
• Open the repository page for git-based entries
• Open the catalog builder to edit entries without writing JSON manually

Catalog Override

The window supports an override catalog file path.

If an override path is set, the tool tries to read that JSON file first. If it fails, it falls back to the bundled catalog and shows a warning.

Catalog JSON format:

{
  "packages": [
    {
      "displayName": "Package Name",
      "packageName": "com.example.package-name",
      "installIdentifier": "https://github.com/user/repo.git",
      "repositoryUrl": "https://github.com/user/repo",
      "group": "AbyssMoth",
      "sourceKind": "Git",
      "description": "Short description."
    }
  ]
}

For registry packages, use sourceKind: "Registry" and set installIdentifier to a normal UPM identifier such as com.unity.nuget.newtonsoft-json@3.2.2.

Catalog Builder

Open AbyssMoth/Package Hub Catalog Builder to edit the catalog in a form-based window.

The builder supports:

• Add blank entries
• Add draft entries from a GitHub URL
• Auto fill metadata from a GitHub repository package.json
• Edit existing entries in the current catalog
• Save to the bundled catalog or a separate override file
• Validation for duplicate entries and self references

Notes

Git package updates use the configured .git URL from the catalog.

Registry package updates use the configured package identifier and version from the catalog.