Tags
Creators
Details
1.26.9.20
Compatibility
Changes
Minecraft 26.3 is supported! This update also fixes a few bugs. Thanks to vinrey123 and psystorm for their reports and for testing the fixes before release.
All plugins
- Added support for Minecraft 26.3. Please update SCore and your plugins together before moving your server to 26.3: older versions do not load items correctly on 26.3.
- The plugins are now ready for the next Minecraft versions too: a brand new version will no longer break item loading while you wait for an update.
ExecutableBlocks
- Fixed a duplication bug on Minecraft 26.x: breaking an ExecutableBlock that is a container (hopper, barrel, chest...) dropped its content twice.
- If DecentHolograms is installed but does not work on your Minecraft version, block titles now use the built-in display instead of showing errors in the console.
ExecutableItems
- Tool rules: using crops like
POTATO,CARROTor theALL_CROPSgroup no longer breaks the item. Before,/ei giveand/ei editorshowed an error for these items. - Two messages of the English language file were broken and are now repaired automatically.
SCore
- When a condition has a mistake in your config, the console now clearly tells you that this condition is ignored and which item and activator are concerned, so you can fix it quickly.
Good to know for 26.3
- MyFurniture works on 26.3, but its packet-based extras are paused until PacketEvents releases its 26.3 version.
- DecentHolograms does not support 26.3 yet. Block titles keep working with the built-in display.
Nothing changes in your configs. If something looks wrong after updating, open a post in the bug channel.
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:5bB2tTKm:tZe29hsu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5bB2tTKm:tZe29hsu"
}

