Tags
Creators
Details
1.6.0
Compatibility
Required content
Changes
1.6.0 - 2024-05-11
-
Middle mouse button can now be used to open Camera controls.
- Allows opening controls without dismounting from a horse. Or jumping off a plane mid-flight. (Without rebinding sneak)
- This is independent of the main hotkey, and will work alongside it. Can be disabled in config.
-
Right-clicking on the Camera in inventory will open Camera configuration screen.
- Right-click with item install/swap an attachment.
-
Added KubeJS integration - Wiki
-
Added three java events (same as in KubeJS) for addon developers.
-
Added Jade integration to Lightroom: it now shows printing progress arrow.
-
Added config option to disable attacking while looking through Viewfinder.
-
Added config option to delay capture (useful when GUI elements are not hidden fully, which happens with some shaders)
-
Stacking two Photographs (by right-clicking in GUI) will keep the resulted item in slot instead of picking it up.
-
Camera tooltip now shows exposed/available frames of the inserted Film Roll.
-
Developed rolls now show frame size (if custom) in tooltip, same as undeveloped rolls.
-
Adjusted 'No Film' icon position with different GUI scales.
-
Adjusted Viewfinder 'catching-up' movement for different GUI scales.
-
Photograph paper texture is now randomly rotated to have more variation.
-
Slightly modified Aged Photograph texture to have less rounded corners.
-
GUI titles now have a separate lang entries instead of using corresponding block/item entries.
-
Fixed custom Lenses not syncing to the player when they join a server.
-
[Fabric] Fixed Sequenced Film Developing (with Create) recipes not showing in EMI
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| exposure-1.20.1-1.6.0-sources.jar | Unknown | 678.56 KiB |
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:hB899VmG:AlbUxt2P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hB899VmG:AlbUxt2P"
}

