Custom paper fork used by Minebench.de
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Max Lee a28404e607 SPIGOT-5317: Create accessors for entity absorption hearts 1 year ago
.github/ISSUE_TEMPLATE Initial commit 2 years ago
Paper @ 75dd53c6ca Update upstream 1 year ago
patches SPIGOT-5317: Create accessors for entity absorption hearts 1 year ago
scripts Fix wrong decompile dir 2 1 year ago
.gitignore Initial commit 2 years ago
.gitmodules Initial commit 2 years ago
CONTRIBUTING.md Initial commit 2 years ago
PATCHES-LICENSE Initial commit 2 years ago
README.md Update upstream and include information in readme 1 year ago
current-paper Update upstream 1 year ago
logo.png Update readme and add logo 2 years ago
origami This is Origami, not Paper 2 years ago
pom.xml Initial commit 2 years ago

README.md

Origami

Origami Logo

Custom paper fork used by Minebench.de. The fork is based off of the framework used in Spottedleaf’s Concrete which is based off of aikar’s EMC framework.

Contact

IRC | Website

License

The PATCHES-LICENSE file describes the license for api & server patches, found in ./patches/api and ./patches/server.

Everything else is licensed under the MIT license. See https://github.com/Spottedleaf/Concrete, https://github.com/starlis/empirecraft and https://github.com/electronicboy/byof for the license of material used/modified by this project.

Plugin developers

In order to use Origami as a dependency just add the following repo and dependency to your pom:

Origami maven repository:

<repository>
    <id>origami-repo</id>
    <url>https://repo.minebench.de/</url>
</repository>

Origami-API maven dependency:

<dependency>
    <groupId>de.minebench.origami</groupId>
    <artifactId>origami-api</artifactId>
    <version>1.13.2-R0.1-SNAPSHOT</version>
    <scope>provided</scope>
 </dependency>

Building and setting up

Run the following commands in the root directory:

git submodule init
git submodule update
./origami up
./origami patch

This should initialize the repo such that you can now start modifying and creating patches. The folder Origami-API is the api repo and the Origami-Server folder is the server repo and will contain the source files you will modify.

Creating a patch

Patches are effectively just commits in either Origami-API or Origami-Server. To create one, just add a commit to either repo and run ./origami rb, and a patch will be placed in the patches folder. Modifying commits will also modify its corresponding patch file.

Building

Use the command ./origami build to build the api and server. Compiled jars will be placed under Origami-API/target and Origami-Server/target.

Updating Paper upstream

Switch into the directory of the Paper submodule and pull changes in from the repository, then run ./origami up and ./origami rb.