Tags
Creators
Details
All versions
0.6.0+1.20.1
Beta
v0.6.0+1.20.1 [Forge]last year 67
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
0.6.0+1.20.1 - 2025-09-29
Added
- Added a new resource-pack-based data-driven system for addon devs to customize how their iotas are rendered in the Splicing Table. (Docs)
- Added Hexical interop to make the telepathy and notebook keys work in the Splicing/Mindsplice Table GUI.
- Added support for "rainbow brackets" (also known as bracket pair colorization) to the Splicing Table. Introspection and Retrospection are now tinted rainbow colors based on their depth. The list of colors is configurable in HexDebug's client settings, and there's also an option to disable the feature entirely.
- Added a config option to disable showing pattern names in embedded lists.
Changed
- ⚠️ Rearranged the client config. In particular, the
invertSplicingTableScrollDirectionoption has been moved tosplicingTable.invertScrollDirection, so you'll have to set this option again after updating if you've changed it from the default. - Updated zh_cn translations, by ChuijkYahus in #43
- The Mindsplice Table casting button tooltip now includes the block's name (eg. from renaming it in an anvil).
- Item Type and Item Stack iotas from MoreIotas now render as the item they represent in the Splicing Table.
Fixed
- Fixed a bug where the Splicing Table's contents would be dropped on the ground when upgrading it to a Mindsplice Table (#47).
Optional dependencies
Any compatible version
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:A2pscGC5:RxcelIlw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:A2pscGC5:RxcelIlw"
}

