Links
Tags
Creators
Details
Licensed Apache-2.0
Published 7 months ago
Updated 3 months ago
All versions
v2.0.0+1.21.11
Release
Screenshot Manager Enhanced v2.0.0 for MC 1.21.113 months ago 367
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Changelog
All notable changes to Screenshot Manager Enhanced will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[2.0.0] - 2026-05-18
Added
- Minecraft 26.1.2 Support: Fully functional client compilation and packaging under the modern Minecraft
26.1.2build classpath using Java 25. - Java 25 Compilation Tooling: Upgraded version configurations and matrix resolution workflows to seamlessly support newer target environments.
Changed
- Mojang Mappings Migration: Transitioned the primary compilation mapping baseline from old Yarn mappings to standard official Mojang mappings for all active releases (
1.21.11and26.1.2), ensuring high compatibility with vanilla APIs. - Reactive UI Modernization: Rewrote visual hover effects in the screenshot gallery UI using owo-lib's reactive mouse-event framework (
mouseEnter/mouseLeavesubscriptions), completely abstracting target-specific rendering contexts from screen definitions. - Client Code Consolidation: Unified complex GUI controllers (
GalleryScreen,SingleImageScreen,ScreenshotMetadataCollector) back into a single shared source set in thecommonsubproject, deleting over 800 lines of duplicate client-side classes. - Consistent Directory Semantics: Renamed the historical
java-moderndirectory tojava-21to match properties definitions and reflect its targeted Minecraft 1.21 baseline.
Removed
- Legacy Client Classes: Deleted the now-unused
java-8,java-17, and legacyfabricclient source sets (20+ files) - Obsolete Build Configurations: Removed
java8.gradle.ktsand related legacy build logic - Build Matrix Redundancy: Simplified the CI/CD matrix to use a single
versions.properties-driven configuration
Contributors
- @scriptmunkeeofficial
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:QSPIfWXj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xs5bRkXn:QSPIfWXj"
}

