OpenSource/PaperMC
OpenSource/PaperMC
1
0
Fork 0
mirror of https://github.com/PaperMC/Paper.git synced 2024-12-26 14:30:17 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update minecraft dir references

Browse source
This commit is contained in:
Nassim Jahnke 2024-12-22 11:45:15 +01:00
parent 90d50aafc5
commit 8ad15d64f0
No known key found for this signature in database
GPG key ID: EF6771C01F6EF02F
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
CONTRIBUTING.md
View file

@ -66,16 +66,16 @@ Assuming you have already forked the repository:
2. Type `./gradlew applyPatches` in a terminal to apply the changes from upstream. 2. Type `./gradlew applyPatches` in a terminal to apply the changes from upstream.
On Windows, replace the `./` with `.\` at the beginning for all `gradlew` commands; On Windows, replace the `./` with `.\` at the beginning for all `gradlew` commands;
3. cd into `paper-server` for server changes, and `paper-api` for API changes. 3. cd into `paper-server` for server changes, and `paper-api` for API changes.
**Only changes made in `paper-server/src/vanilla` have to deal with the patch system.** **Only changes made in `paper-server/src/minecraft` have to deal with the patch system.**
`paper-server/src/vanilla` is not a git repositories in the traditional sense. Its `paper-server/src/minecraft` is not a git repositories in the traditional sense. Its
initial commits are the decompiled and deobfuscated Vanilla source files. The per-file initial commits are the decompiled and deobfuscated Minecraft source files. The per-file
patches are applied on top of these files as a single, large commit, which is then followed patches are applied on top of these files as a single, large commit, which is then followed
by the individual feature-patch commits. by the individual feature-patch commits.
### Modifying (per-file) Vanilla patches ### Modifying (per-file) Minecraft patches
This is generally what you need to do when editing Vanilla files. Updating our This is generally what you need to do when editing Minecraft files. Updating our
per-file patches is as easy as making your changes and then running per-file patches is as easy as making your changes and then running
# TODO # TODO
in the root directory. If nothing went wrong, you can rebuild patches with in the root directory. If nothing went wrong, you can rebuild patches with

2
build.gradle.kts
View file

@ -145,7 +145,7 @@ tasks.register("checkWork") {
val input = providers.fileContents(layout.projectDirectory.file("$CACHE_PATH/last-updating-folder")).asText.map { it.trim() } val input = providers.fileContents(layout.projectDirectory.file("$CACHE_PATH/last-updating-folder")).asText.map { it.trim() }
val patchFolder = layout.projectDirectory.dir("paper-server/patches/sources").dir(input) val patchFolder = layout.projectDirectory.dir("paper-server/patches/sources").dir(input)
val sourceFolder = layout.projectDirectory.dir("paper-server/src/vanilla/java").dir(input) val sourceFolder = layout.projectDirectory.dir("paper-server/src/minecraft/java").dir(input)
val targetFolder = providers.gradleProperty("cleanPaperRepo").map { val targetFolder = providers.gradleProperty("cleanPaperRepo").map {
expandUserHome(it).resolve(input.get()) expandUserHome(it).resolve(input.get())
} }