Links
Tags
Creators
Details
0.5.1+MC1.21.1
Compatibility
Changes
0.5.1 (English)
INT Type
This version officially introduces the INT (Integer) type and logically optimizes existing nodes, switching all ports that should logically be integers from FLOAT to INT.
Affected Nodes
The specific ports of the following nodes have been updated to INT type:
- Variables:
int: Basic node providingINTtype constants.
- Flow Control:
for_loop: Loop start value, end value, and current index.wait_tick: Number of game ticks to wait.
- List Operations:
get_list_item: Index port.list_remove: Index port.list_set_item: Index port.list_length: Length output port.
- String Operations:
string_length: Length output port.string_substring: Start index and end index.
- Math Logic:
random_int: Minimum/maximum inputs and result output.to_int: New node for explicitly converting float or other types toINT.
- Actions:
set_entity_on_fire: Duration in seconds.add_potion_effect: Duration and effect level.
Blueprint Editor Help
This version adds a Help Button (?) to the top toolbar of the Blueprint Editor, which opens a brand-new interactive help interface:
- Shortcut Guide: Detailed listing of all core shortcuts supported by the editor (e.g.,
Ctrl+C/Vfor copy/paste,Ctrl+Z/Yfor undo/redo,Ctrl+Pfor quick search, etc.)
Client Nodes
Introduced the concept of Client Nodes, including the following:
- Interface & Toasts:
client_show_toast: Shows a brief text toast on the client.
- System Tools:
client_open_url: Opens the specified URL on the client.
Other Changes
Changed the following:
- Changed the root directory of the context menu from
node_category.mgmctonode_category.
Fixes
Fixed an issue where the content of InputModalScreen.java was difficult to read.
Thanks
- @load-ing_ on BiliBili
- @Mo_Yang-Mo_Yin on BiliBili
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:gCQA12mz:FzNHlfgj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gCQA12mz:FzNHlfgj"
}

