forked from mirror/Folia
.github/workflows | ||
build-data | ||
gradle/wrapper | ||
patches/server | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
build.gradle.kts | ||
gradle.properties | ||
gradlew | ||
gradlew.bat | ||
README.md | ||
regiontodo.txt | ||
settings.gradle.kts |
ForkTest - A Paper fork, using paperweight
This is an example project, showcasing how to setup a fork of Paper (or any other fork using paperweight), using paperweight.
The files of most interest are
- build.gradle.kts
- settings.gradle.kts
- gradle.properties
Tasks
Paperweight tasks
-----------------
applyApiPatches
applyPatches
applyServerPatches
cleanCache - Delete the project setup cache and task outputs.
createMojmapBundlerJar - Build a runnable bundler jar
createMojmapPaperclipJar - Build a runnable paperclip jar
createReobfBundlerJar - Build a runnable bundler jar
createReobfPaperclipJar - Build a runnable paperclip jar
generateDevelopmentBundle
rebuildApiPatches
rebuildPatches
rebuildServerPatches
reobfJar - Re-obfuscate the built jar to obf mappings
runDev - Spin up a non-relocated Mojang-mapped test server
runReobf - Spin up a test server from the reobfJar output jar
runShadow - Spin up a test server from the shadowJar archiveFile
Branches
Each branch of this project represents an example:
main
is the standard examplesubmodules
shows how paperweight can be applied on a fork using the more traditional git submodule systemmojangapi
shows how a fork could patch arbitrary non-git directories (such asPaper-MojangAPI
)submodules-mojang
shows the same asmojangapi
, but on the git submodules setup fromsubmodules