Links
Tags
Creators
Details
Licensed CC-BY-NC-4.0
Published 3 years ago
Updated 2 years ago
All versions
2.0-beta-3
Beta
2.0-beta-3 for 1.19.43 years ago 38
Compatibility
Minecraft: Java Edition
1.19.4
Platform
Forge
Supported environments
Client and server
Changes
--- 2.0 beta 3 ---
New Blocks:
• Position Code Block
• Transfer Neutral Code Block
• Redstone To Direction Code Block
• Direction To Redstone Code Block (not working properly at the moment)
Changes:
• The following Blocks can rotate on all sides now:
○ Property Transfer Number Code Block
○ Opposite Number Code Block
○ NBT To Property Number Code Block
○ Property To NBT Number Code Block
○ Degrees To Radians Number Code Block
○ Radians To Degrees Number Code Block
○ Property Transfer Logic Code Block
○ NBT To Property Logic Code Block
○ Property To NBT Logic Code Block
○ Opposite Logic Code Block
○ Uppercase Text Code Block
○ Lowercase Text Code Block
○ Property Text Code Block
○ NBT To Property Text Code Block
○ Property To NBT Text Code Block
○ Opposite Transfer Direction Code Block
○ Rotate Clockwise Transfer Direction Code Block
○ Rotate Counterclockwise Transfer Direction Code Block
○ Item To Text Code Block
○ Name Of Items Code Block
○ Lenght Of Text Code Block
• Texture changes for All Left & Right Transfer Code Blocks
• Some Reordering in the Code Blocks Creative Tab
• You Can Now use the following text for the Text To Direction Code Block: D, U, N, S, W, E
Bugfixes:
• Direction Code Item is in the correct creative tab.
Internal Changes:
• New Block Models For:
○ Every Transfer Code block & Chain Switching Block (transfer block)
○ Left & Right Transfer Code Block (transfer left block, transfer right block)
• Removed Unnecesary Textures
• Neutral Code Block Update Tick Procedure Variable Naming Changes (due to confusion)
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:lQI4JCnA:25YP18tc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lQI4JCnA:25YP18tc"
}

