Tags
Creators
Details
5.26.9.21
Compatibility
Changes
New features asked by the community, and a few bug fixes. Thanks to dinobossyt, yuiso., drfrostx, themirinto and darklionqc for their ideas and reports.
New
- Item preview in the editors: in
/ei editor(and the other editors), the icon of each item now shows its name, lore, enchantments and attributes. You can check your items without opening them one by one. It can be turned off witheditorIconPreview: falsein the SCore config. - Custom fishing loot: the new command
CHANGE_INTO_ITEMturns what a player catches with a fishing rod into any item or ExecutableItem, with the normal fishing animation. A full guide is on the wiki ("Custom fishing loot"). - Gradient names and anvils: an ExecutableItem that is enchanted or repaired in an anvil keeps its colored / gradient name. If the player types a new name, the item is renamed like in vanilla. Option
keepNameInAnvilin the ExecutableItems config, enabled by default.
Fixes
- ExecutableCrafting: the vanilla Crafter block ignored the amounts of your custom recipes (a recipe asking for 32 items could be crafted with 1). It now respects amounts and conditions. It can be turned off with
enableCrafterBlockSupport: false. - SCore: a server with SCore, Multiverse-Core and Iris installed together could refuse to start (
Circular plugin loading detected). Fixed. - SCore: world conditions no longer show an error for a Multiverse world that is loaded after the plugins.
- SCore: no more error in the console when the server stops, on servers that use Geyser.
- ExecutableItems: several default items were repaired (
Prem_Grass_Cutter,Prem_Firework, the Morph tools...). Your existing files are not modified: delete a default item file to get the repaired version.
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:ZfcV7L06:HDuJ4399"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZfcV7L06:HDuJ4399"
}

