9dd5b27488
* Gradle 7.0 * Build JDK 16 * [CI-SKIP] rebase * Speed-Up build times Makes kotlin tasks run in parallel and adds back configure on demand * Updated to the final release of gradle 7.0 * Gradle Distribution SHA 256 Sum * Validate Gradle Wrapper * merged the two jobs * better name for validation * setup-java@v2 * fix? * specify arch * Setup JAVA_HOME and PATH * revert * Use the same jdk as @v1 * use setup-java@v1 too much errors * require Gradle Wrapper Validation to run build * setup-java@v2 * Regenerate cache maybe fix some issues * Auto set MC version of paperclip in GitHub Actions * Added .gitattributes Should fix issues with line endings * Update .gitattributes * Updated shadow jar plugin * fix |
||
---|---|---|
.github | ||
buildSrc | ||
gradle/wrapper | ||
images | ||
Licensing | ||
Paper@39bf5b525d | ||
patches | ||
subprojects | ||
upstream | ||
upstreamCommits | ||
upstreamConfig | ||
Yatoclip | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.template.md | ||
api | ||
build.gradle.kts | ||
gradle.properties | ||
gradlew | ||
gradlew.bat | ||
Jenkinsfile | ||
PATCHES.md | ||
README.md | ||
SECURITY.md | ||
server | ||
settings.gradle.kts |
So what is Yatopia?
Yatopia combines the code from many Paper forks and optimization mods, as well as many unique optimizations. We borrow code from the following repos:
Try it out
The latest stable builds of Yatopia are always available over at our downloads page. You can also download the latest development build here.
Documentation
You can find a full explanation of the Yatopia configuration file on the wiki. Check out the list of patches included in this project and who created them here.
Building and setting up
Run the following commands in the root directory:
./gradlew initGitSubmodules
./gradlew setupUpstream
./gradlew applyPatches
./gradlew paperclip
Using Yatopia-API
To build your plugin against the Yatopia-API, first add the CodeMC maven repository:
Maven
Add the CodeMC Repo:
<repositories>
<repository>
<id>codemc-repo</id>
<url>https://repo.codemc.io/repository/maven-public/</url>
</repository>
</repositories>
And then add the Yatopia-API dependency:
<dependencies>
<dependency>
<groupId>org.yatopiamc</groupId>
<artifactId>yatopia-api</artifactId>
<version>1.16.5-R0.1-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
</dependencies>
Gradle
Groovy DSL
Add the CodeMC Repo:
repositories {
maven {
url 'https://repo.codemc.io/repository/maven-public/'
}
}
And then add the Yatopia-API dependency:
dependencies {
compileOnly 'org.yatopiamc:yatopia-api:1.16.5-R0.1-SNAPSHOT'
}
Kotlin DSL
Add the CodeMC Repo:
repositories {
maven("https://repo.codemc.io/repository/maven-public/")
}
And then add the Yatopia-API dependency:
dependencies {
compileOnly("org.yatopiamc:yatopia-api:1.16.5-R0.1-SNAPSHOT")
}
Why aren't there many API additions?
(Modified from starlis/empirecraft)
APIs are tough to design. In projects such as Bukkit, Spigot, Sponge, Paper, etc once an API is committed, it's almost forever. You can't go breaking it without solid justification. This is the politics game.
With that in mind, much thought has to be given to the API in now and future use cases and applications to ensure it can be extended without breaking.
This is a lot of politics that we don't have time in our lives to deal with.
That being said we make light API additions when requested.
License
License information can be found here.
Security
Security information can be found here.
Statistics
Made with ♥ on Earth.