Tags
Creators
Details
2.2.5+1.21.11-spigot
Compatibility
Changes
MC-Sync 2.2.5
| Version | 2.2.5 |
| Loader | spigot |
| Minecraft | 1.21.11 - 26.1.1 |
| Build fingerprint | c2cf04a0a67b7e88d169c0c94edd8b15699e8c8b06ffd62537e27c1c4d2bde17 |
Servers with update.mode: notify (the default) announce this build in their log and in
/mcsync status. Nothing is installed automatically: replace the jar by hand, it takes effect on
the next restart.
The update check never points you to a different Minecraft version: this build only ever offers itself to servers on the versions listed above.
Commands run by a flow on this server go through commands.mode like commands from Discord. On
the default whitelist only the whitelist commands run; anything else is refused with
command.status forbidden and a tip in the run log -- add it to commands.allow and set
commands.mode: allow.
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:noKcRQOR:DkzYnZfH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:noKcRQOR:DkzYnZfH"
}

