Links
Tags
Creators
Details
Licensed AGPL-3.0-or-later
Published 4 years ago
Updated yesterday
All versions
v2.0.0
Release
2.0.0yesterday 2
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
- Screencapper now runs on OneConfig and needs it installed. All of its settings are in the OneConfig menu.
- Added a Screenshots page to the OneConfig sidebar, where you browse, search, sort, view, copy, upload, open and delete your screenshots, one at a time or in bulk.
- The screenshot preview is now a HUD. Move, resize and style it in the OneConfig HUD editor. With chat open, hover it to copy, upload or delete, or click it to view the screenshot.
- The chat message for a new screenshot is now a card showing its time, resolution and size, with its actions on a second line. Picking an uploader, confirming a delete and uploading all happen on that line instead of sending new messages.
- You can set up several uploaders, pick a default and upload to any of them. Imgur is built in, any host that takes an image over HTTP works, and ShareX
.sxcufiles can be imported. - Every link a screenshot is uploaded to is remembered across restarts, and you can upload it again at any time.
- Upload, copy and delete results now show as notifications.
- Added
/screencapperand/screenshots. - Settings from older versions, including your custom upload host, move over on first launch.
- Supports Minecraft 1.21 to 1.21.1, 1.21.4, 1.21.5, 1.21.8, 1.21.10, 1.21.11 and 26.1 to 26.3 on Fabric, and 1.8.9 on Ornithe. Minecraft 1.18.2 to 1.20.6 are no longer supported.
- Screencapper is now licensed under AGPL-3.0-or-later.
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:yzNFLSqx:SYVcdMWX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yzNFLSqx:SYVcdMWX"
}

