2a75e955a3
Upstream/An Sidestream has released updates that appears to apply and compile correctly This update has NOT been tested by YatopiaMC and as with ANY update, please do your own testing. Paper Changes: c64958508 fix: wrong return in javadocs for bookmeta (#5579) 3dbb8926e Fix PotionSplashEvent for water splash potions (#5697) b759d006e Adds per-world spawn limits (#4837) 81de619d3 Updated Upstream (CraftBukkit) (#5786) 5e3604f1b Better fix for invulnerable crystals and improve Origin API (#5761) d5fe9c817 Updated Upstream (CraftBukkit) (#5784) d20e5b195 Fix timings sometimes incorrectly marking commands (#5783) Tuinity Changes: df76b3c Updated Upstream (Paper) Airplane Changes: a13c511 Simple item block collision toggle 3cd9d1c Updated Upstream (Tuinity) Empirecraft Changes: c7ef1a7a Updated Paper |
||
---|---|---|
.github | ||
buildSrc | ||
gradle/wrapper | ||
images | ||
Licensing | ||
Paper@c649585082 | ||
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.