Tags
Creators
Details
1.5.0
Compatibility
Required content
Changes
1.5.0 - 2024-04-04
-
Added chromatic (trichrome) printing process
-
Red, Green and Blue filters now have stronger effect to enable chromatic process
-
Lenses configuration is now data-driven. Custom Lenses Wiki
- LensFocalRanges config setting has been removed.
-
Changed how custom filters are configured, allowing the use of shaders from vanilla or other mods. Custom Filters Wiki
Exporting:
- Aged Photographs can be exported now (same as regular - when screen is opened). PNG will have
_agedsuffix. - Exported PNGs are now X2 the size. Configurable in client config.
- Exported PNG files will have their
Date Createdattribute set to time when they were taken. Only for exposures made on this version an up.
Commands:
- Renamed literal
exposuretoidin/exposure showcommand. - Added two optional arguments to
/exposure exportcommand:size- Defaults to "X1". (X1/X2/X3/X4)look- Defaults to "regular". (regular/aged/negative/negative_film)
idargument (in export and show commands) will show all available exposure IDs as autocomplete suggestions.pathargument (in/exposure show texturecommand) will show a list of all available textures as autocomplete suggestions.
Lightroom:
-
When in creative mode, you can now hold [Shift] to print exposure instantly and without dyes/paper
-
Experience points, granted for printing an image, are now different per process - bw/color/chromatic. Config now has three options instead of one to configure this.
-
Fixed crash when rendering a non-square texture as a Photograph.
-
[Forge] Fixed crash when clicking on exposure in mods menu. For real this time.
-
[Fabric] Fixed camera recipe not unlocking in recipe book when iron ingot is obtained.
Optional dependencies
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:xBwQsqtC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hB899VmG:xBwQsqtC"
}

