Links
Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated 2 months ago
All versions
0.3.2+neoforge-1.20.1
Release
createphotomovement-neoforge-1.20.1-0.3.26 months ago 44
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Fixed
- Solar Windmill Bearing: Fixed #11 — multiple visual issues with the bearing block:
- Bearing top and back-shaft were invisible while Flywheel was active (Flywheel default). Registered Create's
BearingVisualas the Flywheel visualization forSOLAR_WINDMILL_BEARING, mirroring Create's ownWindmillBearingBlockEntitysetup. - Bearing top showed a static "ghost" while the contraption rotated. Removed the static
Topcuboid fromsolar_windmill_bearing.json— that Y 12-16 slot is reserved for the dynamic partial model. - Bearing top and shaft rendered nearly black even with open sky overhead. Added
.noOcclusion()and overrodepropagatesSkylightDown/getLightBlockonSolarWindmillBearingBlockso sky light reaches the bearing's position.
- Bearing top and back-shaft were invisible while Flywheel was active (Flywheel default). Registered Create's
Removed
- Forge 1.20.1: Removed the empty
forge/build target. NeoForge 1.20.1 is a near-drop-in fork of Forge 1.20.1, so users on Forge can use the NeoForge 1.20.1 jar.
Internal
- Publish script: Fixed
tools/publish_mod.ps1so Modrinth uploads use the same per-loader naming as CurseForge (createphotomovement-{loader}-{mc}-{version}). The previous script sent the sameversion_number(0.3.2) for all three jars, which Modrinth rejects as a duplicate after the first upload — this is why only 2 of 3 jars made it onto Modrinth for v0.3.1.
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:rc6BvPDU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xOQW4NMc:rc6BvPDU"
}

