MCFurryPacks/PackFormatter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3 Commits 1 Branch 0 Tags 100 KiB
TypeScript 100%
6fddd8039f
Go to file
Donovan Daniels 6fddd8039f
Allow specifying info file
2024-05-30 14:06:16 -05:00
.eslintrc.json Initial Commit 2024-05-30 05:04:54 -05:00
.gitignore Initial Commit 2024-05-30 05:04:54 -05:00
bun.lockb Initial Commit 2024-05-30 05:04:54 -05:00
index.ts Allow specifying info file 2024-05-30 14:06:16 -05:00
package-lock.json Initial Commit 2024-05-30 05:04:54 -05:00
package.json Initial Commit 2024-05-30 05:04:54 -05:00
README.md Add info file information 2024-05-30 05:08:27 -05:00
tsconfig.json Initial Commit 2024-05-30 05:04:54 -05:00

README.md

Pack Formatter

To use this, you must have the Bun runtime installed. Simply run bun install, bun compile, and you'll find the build-packs binary in the dist folder.

Usage

build-packs

Arguments

  • -i or --indir - The input directory. Defaults to the current working directory.
  • -o or --outdir - The directory to output the compiled packs to. Defaults to dist.
  • -c or --common - The common directory containing shared files. Defailts to common.
  • -r or --revision - The revision/version. Defaults to git rev-parse --short HEAD if .git exists, else required.

Info File

An info.json file should be present in the input directory. This file should contain the following fields:

  • name - The name of the pack.
  • description - A description of the pack.
  • url - The URL to the pack's repository.
  • versions - A two dimensional array of mc version to pack format. ([[mcVersion, packFormat]])
  • exports - The exports to be made from the zip files produced for each version. A two dimensional array of mcVersion or "all". ([["all"],["1.20", "1.20.2"]])