Add the tasks, this is useful

This commit is contained in:
Telesphoreo 2022-04-22 02:07:24 -05:00
parent cd9edca0e9
commit 67d8415fb3

View File

@ -1,14 +1,9 @@
# ForkTest - A Paper fork, using paperweight # Scissors
This is an example project, showcasing how to setup a fork of Paper (or any other fork using paperweight), using paperweight. Scissors is a fork of Paper that aims to fix exploits possible in Creative Mode. Many of these exploits are ones that
Paper's own team has either refused to fix or would have.
The files of most interest are
- build.gradle.kts
- settings.gradle.kts
- gradle.properties
## Tasks ## Tasks
``` ```
Paperweight tasks Paperweight tasks
----------------- -----------------
@ -29,12 +24,3 @@ runDev - Spin up a non-relocated Mojang-mapped test server
runReobf - Spin up a test server from the reobfJar output jar runReobf - Spin up a test server from the reobfJar output jar
runShadow - Spin up a test server from the shadowJar archiveFile runShadow - Spin up a test server from the shadowJar archiveFile
``` ```
## Branches
Each branch of this project represents an example:
- [`main` is the standard example](https://github.com/PaperMC/paperweight-examples/tree/main)
- [`submodules` shows how paperweight can be applied on a fork using the more traditional git submodule system](https://github.com/PaperMC/paperweight-examples/tree/submodules)
- [`mojangapi` shows how a fork could patch arbitrary non-git directories (such as `Paper-MojangAPI`)](https://github.com/PaperMC/paperweight-examples/tree/mojangapi)
- [`submodules-mojang` shows the same as `mojangapi`, but on the git submodules setup from `submodules`](https://github.com/PaperMC/paperweight-examples/tree/submodules-mojangapi)