A simple package manager for KubeJS.
- Python 3.8 (or higher)
- Pip
- Git
- Curl (probably pre-installed)
curl -s https://raw.githubusercontent.com/Modern-Modpacks/kjspkg/main/install.sh | sh
Download this bat file and run it
or use WSL
Installing packages:
kjspkg install [package] [package]
kjspkg install kjspkg:[package]
kjspkg install carbon:[package] # CarbonJS compatibility (https://github.com/carbon-kjs)
kjspkg install github:[author]/[package] # External packages
Removing packages:
kjspkg remove [package] [package]
Updating packages:
kjspkg update [package] [package]
More info in the help page:
kjspkg help
-
Create a repository containing your scripts and assets
-
Add a file to your repo named
.kjspkg
and format it like this:{ "author": "<your_name>", "description": "<description>", "versions": [<Version key numbers (see the numbers in parentheses in the table below). Can contain multiple numbers>], "modloaders": [<Modloaders ("fabric"/"forge", "fabric" will for quilt as well)>. Can contain multiple modloaders], "dependencies": [<Package names that your package depends on, blank if none. To depend on mods add "mod:" before the mod id>], "incompatibilities": [<Package names that your package is incompatible with, blank if none. Incompatible mods are also supported (use the same syntax)>] }
-
Fork this repo
-
Clone it
-
Add your package to
pkgs.json
file. Format it like this:"your_package_id": "your_github_name/your_repo_name",
- You can specify the branch by adding
@branch_name
at the end of the string, otherwise it will automatically use themain
branch
- You can specify the branch by adding
-
Create a pull request
-
Wait for it to be accepted
Forge | Fabric/Quilt | |
---|---|---|
1.19 (9) | ||
1.18 (8) | ||
1.16 (6) | ||
1.12 (2) | ||
1.7 (🧌) |
Tested means that the version is confirmed to be working;
Not tested means that the version should work, but hasn't been tested. Feel free to test it yourself and let us know so we'll update the readme.
Full support means that we focus on that version;
Partial support means that the version is supported, but not as much as the fully supported ones;
No support means that the version works, but any issues that you have with it won't be fixed.
Borked means it doesn't work lmao.