Graphene is pre-production software. Bugs, performance issues, and crashes can and will occur. In using this software, you assume all responsibility for any damage that occurs. If you encounter an issue, please check here to see if we're already tracking it, and if not, file a report yourself. We'll get on it as soon as we can.
Graphene adds patches to Purpur from...
- Sugarcane
- Yatopia
- Origami
- Parchment
- Mirai
- Patina
- JettPack
- Akarin
- Pufferfish
- Sakura
- Crunchy (repo taken down)
- Utopia
- Slice
- KTP
- Nyper (repo taken down)
- Nabulus
- P4per (patches edited and squashed)
- Leaf (repo taken down, patches edited and squashed)
Downloads can be obtained from the Github Actions page.
All patches are licensed under the MIT license, unless otherwise noted in the patch headers.
First, clone paperweight and run ./gradlew publishToMavenLocal in its root directory.
Then, clone this repo and run ./gradlew applyPatches in its root directory.
Patches are effectively just commits in either Graphene-API or Graphene-Server.
To create one, just add a commit to either repo and run ./gradlew rebuildPatches, and a
patch will be placed in the patches folder. Modifying commits will also modify its
corresponding patch file.
Use the command ./gradlew build to build the API and server. Compiled JARs
will be placed under Graphene-API/build/libs and Graphene-Server/build/libs.
To get a paperclip jar, run ./gradlew paperclip.
To install the graphene-api and graphene dependencies to your local Maven repo, run ./gradlew publishToMavenLocal