Links
Tags
Creators
Details
Licensed Apache-2.0
Published 9 months ago
Updated last month
All versions
v1.3.0+1.21.3
Release
Screenshot Manager Enhanced v1.3.0 for MC 1.21.39 months ago 18
Compatibility
Minecraft: Java Edition
1.21.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Changelog
[1.3.0] - 2026-02-01
Added
- XMP Metadata Embedding (#50): Screenshots can now include embedded metadata (World Name, Coordinates, Biome, Timestamp, Server IP) readable by tools like Lightroom and Photoshop
- Custom Save Path (#52, #53): Define exactly where screenshots are saved — use cloud storage, external drives, or any folder you choose
- Advanced Features Section: New collapsible settings area in Mod Menu for power-user options
- Gallery Documentation (#54): New
Gallery.mdshowcasing the mod's UI and features - Automated Publishing (#56): Releases now auto-publish to Modrinth and CurseForge via
mc-publishGitHub Action - Release Runbook: New
RELEASE.mdwith step-by-step instructions and Quick Reference Card - Dynamic Version Matrix: CI/CD workflows derive Minecraft versions from
versionProperties/directory
Changed
- Metadata embedding is disabled by default (opt-in via Mod Menu)
- Custom path requires acknowledgment of warning dialog before enabling
- Release workflow uses matrix strategy for parallel multi-version builds
- Sources JAR skipped in release builds for faster builds (#57)
- Updated README with simplified release process and Gallery link
Internal
- Centralized version management — adding a new MC version only requires a new
.propertiesfile
Contributors
- @scriptmunkeeofficial
- @google-labs-jules[bot]
Optional dependencies
Any compatible version
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:xs5bRkXn:Fl8AxvUn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xs5bRkXn:Fl8AxvUn"
}

