Tags
Creators
Details
All versions
0.2.4-datapack
Release
0.2.4 - FreeJam Patch 44 months ago 627
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Data Pack
Changes
⚙️Technical
- The history module error now immediately triggers a log with the datapack version, so as not to ask players for it every time.
- Boost flight is now activated only by pressing [CTRL] during creative flight. Previously: [SHIFT]+[CTRL]+[W]/[A]/[S]/[D]
- Speed "1" of flight boost now means using vanilla creative flight
- All commands related to random block placement have been optimized similarly to randomreplace. (/set with random blocks will still take longer to execute than others, as there are no blocks in the region that could be skipped during the operation.)
- Added the ability to disable the multi-hotbar (Settings>Utility>Multi-Hotbar)
👁️Visual
- In the smart event console, the information and file path messages have been combined; the file path is now written on the same line, in small font.
- The loading bar at the top of the screen now actually displays the current action: placing blocks, saving Undo, saving Redo. Previously, it was always "Loading".
- Added ru_ru localization to the Welcome notification when installing the datapack
🛠️Fixes
- Deleting/updating a datapack version now clears only the tools instead of the entire inventory
- Technical garbage is now cleared if the history module returns an error. Previously, a history module error prevented the deletion of technical entities, and they remained forever unless manually removed.
- Fixed history module error caused by "Null" when trying to copy/paste a region 1 block long and wide
- Boost flight is now even smoother
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Axis WorldEditor.zip | Required resource pack | 1.13 MiB |
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:mmDrugUv:qtC3h7gB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mmDrugUv:qtC3h7gB"
}

