All versions
v26.11.4-mc26.1
Release
FireCoreMod v26.11.4 for Minecraft 26.131 minutes ago 3
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
FireCore 26.11.4 adds the pieces Showcase needs to show real blocks and windows, and makes the scene screen easier to use with long scene lists.
Showcase scenes
- Block entities in scenes. Block entities draw in their scene, and their data from the structure file is loaded.
modifyBlockEntityandmodifyBlockEntitieschange a scene's own copy of a block entity, the same way after a seek back. - Scenes can show a mod's own window, with the cursor clicking its buttons, dragging its sliders, typing into its fields and picking from its dropdowns. Nothing a window sends reaches the server while a scene drives it.
- Named chapters:
addChapter(name, english)gives a chapter a name, shown in the timeline and in the scene bar. - A scene bar down the left edge lists every scene of an item, with its chapters, so you can skip to one. Long names show in full in a tooltip. The bar bounces when the screen opens and peeks out every 15 seconds while it is folded.
- Tags can group their items under headings, with
section(...). Each heading starts a new row on the tag's page. - The demo scenes use a checkerboard floor.
- Identify mode names the part under the pointer on a block made of several parts, such as an AE2 cable with a part on it.
- Dragging the view, and the wheel, show a short hint that fades after the first use.
Fixes
- The Showcase screen no longer takes clicks through to JEI's lists when a window is open.
- A text field inside a window that is scaled down clips correctly on 1.21.1.
Compatibility
- Scenes and tags built against 26.11.3 keep working.
addKeyframeandattachKeyFramestill work, and are deprecated in favour ofaddChapterandattachChapter. - Versions: 1.21.1, 26.1, 26.2 and 26.3.
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:r90ajF68:uQt0Pscp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:r90ajF68:uQt0Pscp"
}

