Links
Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated last month
All versions
0.3.4+fabric-1.20.1
Release
createphotomovement-fabric-1.20.1-0.3.4last month 107
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Fixed
- Solar Sails and the Solar Windmill Bearing dropped nothing on 1.20.1: breaking a Solar Sail (any colour) or a Solar Windmill Bearing on Fabric 1.20.1 or NeoForge/Forge 1.20.1 destroyed the block without dropping its item, and Silk Touch made no difference. The 17 loot tables involved had only ever been written for 1.21.1. A block with no loot table drops nothing at all, and Silk Touch is a branch inside a loot table -- with no table there was nothing for it to trigger. NeoForge 1.21.1 was never affected. Reported on CurseForge.
- Mineable tags never applied on 1.20.1: both 1.20.1 targets shipped their
mineable/axeandmineable/pickaxetags underdata/minecraft/tags/block/, which is the folder name 1.20.5 introduced. 1.20.1 readstags/blocks/, so it never saw the files and the solar generators got no tool speed bonus. Drops were not affected by this -- no block in the mod requires a specific tool to drop.
Internal
- Shared source set: the block entities, renderers and server config that were copy-pasted across all three targets now live once under
common/and are compiled into each target against its own Minecraft version. - Tests: headless unit and resource tests (
gradlew :common:test) and 36 in-game tests on NeoForge 1.21.1 (gradlew :neoforge:1211:runGameTestServer). Two of the resource tests exist because of the two bugs above: one asserts that every block has a loot table, the other that each target's data folders use the naming of its Minecraft version. - CI: builds and tests all three targets on every push.
- Build script:
tools/build_mod.ps1invoked agradlew.batinside each target folder. No such file exists -- there is one wrapper, at the repository root -- so the script aborted on the first target. It now runs:neoforge:1201:buildand friends from the root, which is also the only way the sharedcommon/sources resolve. The headless tests run first;-SkipTestsopts out. - Version bump script:
tools/bump_version.ps1wrotegradle.propertieswith a UTF-8 BOM in front of the first line.
Supported Platforms
- NeoForge 1.21.1
- NeoForge 1.20.1
- Fabric 1.20.1
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:xOQW4NMc:wHYXwgoC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xOQW4NMc:wHYXwgoC"
}

