
kyoyu
ArchivedShare .litematic with other players on the server. Litematica and Forgematica support. Inspired by Syncmatica.
Tags
Creators
Details
v1.1.4-mc1.21.1
Compatibility
Changes
What's Changed
- Separate 1.19.4 and 1.19.2
- Fixed compatibility in 1.19-1.19.2.
- Fixed only sending JSON in Forge.
Known Issues
We will debug properly...
- The schematic name is not displayed in Explorer. (1.14.2~1.15.2) (Fabric / Forge)
- Unable to connect to the server. (1.20.2~1.20.4) (Fabric / Forge)
- Crashes for unknown reason. (1.20.6) (Forge)
- Crashes at launch. (1.14.2) (Forge)
- Nothing happens. (1.20.6~1.21.4) (Forge / NeoForge)
Full Changelog: https://github.com/Vulpeus-Server/kyoyu/compare/1.1.3...1.1.4
Build Information
- File name:
Kyoyu-v1.1.4-mc1.21.1-forge.jar - SHA-256:
5d2f8f83dff03230f321f83d46f3a67f25dfda3ca74419909d5a05f659c7a775 - Built from: https://github.com/Vulpeus-Server/kyoyu/actions/runs/13196720983
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:VozTPxB4:YCyTd6Sc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VozTPxB4:YCyTd6Sc"
}
