Creators
Details
Licensed CC-BY-SA-4.0
Published 8 months ago
Updated 2 weeks ago
All versions
1.5
Release
The Customization Update!last month 247
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
The customization update is finally here!
Mystcraft Beta 1.5 lets you customize your Mystcraft experience in a few key ways:
- Dye support: You can now color-code your linking books & book bags by inserting them into the crafting table with any vanilla minecraft dye.
- Book titles & notes: With the new open-book interface, you can now write notes directly into Mystcraft linking books. The top-line also serves as the book title. Changing it will re-name your linking book like an Anvil.
- Custom age imports (experimental): As requested by a few modpack creators, mystcraft now supports importing pre-existing ages with the "/mystcraft importAge <folderName>" command. Ages import from the <world>/mystcraft_import/<folderName>" directory. This feature is experimental, so please back up your save file before use.
- Replaced the ASCII-based tooltip book preview with inline media overlay.
Beta 1.5 also addresses some new & old bugs:
- Linking books can (finally) display their media preview outside of the dimension it was created in.
- Fixed a bug caused by the latest TerraBlender update that would corrupt the level.dat file.
- Restored Silk Touch mining for mob spawners, allowing spawners to be collected for use with Mystcraft editing table.
- Fixed Linking Book preview capture when crafting from the player’s 2×2 survival inventory.
- Improved Mystcraft Age dimension handling to help prevent worldgen serialization issues from returning on newly created Ages.
- Improved dyed-book title readability by applying Minecraft’s built-in text-shadow effect to lighter title colors, while leaving darker colors unshadowed.
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:PxYGeIhV:skEYSnhN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PxYGeIhV:skEYSnhN"
}

