-
Notifications
You must be signed in to change notification settings - Fork 0
Addon Guide
Follow the instructions on the Origins wiki or use this project's build.gradle as an example if necessary.
Provi's Origins uses JitPack to provide its dependency, just like Origins does. If you want to build against this project or use any of its features in your own addon mods you can use the JitPack page to retrieve the dependency.
Follow the guidance on the Origins wiki on how to get started with making a datapack.
If you want to use anything from Provi's Origins in your Origins datapack, simply remember that this project uses a different namespace, proviorigins. As opposed to Origins itself using the namespace of origins for powers and actions.
The data folder of this project is a datapack itself, and can work as an example if necessary. This is similarly true for (presumably) all other Origin addon mods.
If you already have a working workspace set up for an Origins addon, you can add Provi's Origins to your workspace by adding to your dependencies block (same place you put the Origins dependency):
modimplementation "com.github.provismet:provi-origins:${project.provi_origins_version}"To adjust the version without having to mess with your build.gradle, add the following line anywhere in your gradle.properties file:
provi_origins_version = <version number>
Where "<version number>" is replaced with whatever the current working build is, e.g. 1.3.0
At the time of writing, Origins (1.20+) itself fails to build on JitPack, this is due to ReachEntityAttributes not yet being updated to 1.20. Therefore to build off of this mod in your own workspace you'll need to clone this mod, Origins, and ReachEntityAttributes to your own computer and add them to your local Maven (there are pinned instructions for this in the Origins discord).
Modrinth Maven may also work (I always upload my source jars to Modrinth), but that is untested.
If the dependency fails, it's usually because JitPack timed out when generating it - it should work fine if you just try again.
If the JitPack page says that the dependency failed to generate entirely (despite the GitHub build on this project succeeding) then the reason is usually due to Origins itself failing to build on JitPack. This happens occassionally as Origins has many dependencies and they do break sometimes.