Tags
Creators
Details
All versions
0.5.11-2
Release
SchemFlow 0.5.11-2last year 13
Uploaded by
Compatibility
Minecraft: Java Edition
1.21โ1.21.8
Platforms
Paper
Purpur
Changes
0.5.11 (and hotfixes 0.5.11-1 / 0.5.11-2)
Added
- Group lifecycle commands:
group delete <name> [--confirm](preview schematic count before destructive action)group rename <old> <new>- Safer create with duplicate name detection
- Trash & restore workflow:
delete [group:]namenow soft-deletes to S3.trashrestore <name> [-group <dest>]to bring items back (optionally to a different group)trashlists trashed schematicstrash clear --confirmpermanently purges (guarded by confirmation)
- Undo / Redo support for SchemFlow delete operations (
/SchemFlow undo/redo) with fallback to WorldEdit history for pastes - Group-prefixed tab completion (
group:name) and inclusion of group-prefixed names in cache - Confirmation previews for destructive operations (group delete, trash clear) showing item counts
- Ephemeral paste cache directory (
plugins/SchemFlow/work/cache/) auto-purged on enable/reload/disable
Improved
- Listing (
/SchemFlow list) now groups schematics by group with total counts - Clearer feedback & error messages across command suite
- Consistent MiniMessage styling for all command outputs
- Cache refresh logic aggregates both plain and group-prefixed forms for faster tab completion
Fixed
- Duplicate group creation now returns a friendly warning instead of silently reusing
- Ensured biomes flag handling defaults to included unless disabled
- Hotfix 0.5.11-2: removed dependency on a missing method for ephemeral cache path in some environments (build compatibility)
Internal
- Safer async wrapping for storage operations
- Reduced transient file retention (auto-clean ephemeral paste artifacts)
- Updated documentation (README + wiki) to match new command set & workflows
Notes
- Only
/SchemFlow fetchwrites persistent schematic files;pasteuses ephemeral cache - Use
--confirmfor irreversible operations (group delete,trash clear) - WorldEdit OR FAWE required (not both)
Upgrade Guidance No config changes required. Existing schematics remain valid. You may safely update the jar and use new group management + trash features immediately.
Optional dependencies
Any compatible version
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:RWuhoVqf:ecl7l3ke"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RWuhoVqf:ecl7l3ke"
}

