1.3.0
Compatibility
Required content
Changes
Supported Versions
- Plugin: 1.3.0 —
coreviz-1.3.0.jar - Minecraft: 26.1 – 26.3 (26.1 Apr 2026 / 26.2 / 26.3 Wilderness Bound 2026-09-15) — one jar for all
- Server: Paper 26.1+ (
[26.1.build,),api-version: '26.1') — also Purpur & forks tracking Paper API 26.1+. Not 1.21.x (Paper's version break). No Fabric/Forge. - Java: 25+ (build + runtime,
<release>25</release>) - CoreProtect: 23.1+ (API v11+) — full behavior (blocks + containers + sessions) on both 23.x and 24.0+
What's New in 1.3.0
Click-to-inspect mode (NEW)
Prefer CoreProtect's inspector? /cpv i (alias /cpv inspect) toggles inspector mode: click any block and its history opens straight in the results GUI — no typing, no menus first.
- Block breaking/placing is held back while inspecting, so clicks never edit the world by accident
- Click targeting mirrors CoreProtect (base half of tall blocks, containers/signs directly)
- Inspector state clears on quit; every GUI shows an Inspector mode: ON button to turn it off without a command
- Uses the existing
cpviz.usepermission — no new permission needed
Undo a rollback without leaving the GUI (NEW)
Rolled something back and want it back? Fully rolled-back entries now offer Restore changes (recovery compass icon) instead of Roll back:
- More-options menu: button flips to "Restore changes" with the same two-step confirm when every raw action in the entry is already rolled back
- Double right-click a dimmed (rolled-back) merged or raw row to undo the rollback and re-apply the changes, via CoreProtect's own restore engine
- Gated by the existing
cpviz.rollbackpermission — no new permission needed
Guarded rollbacks (FIXED)
Rollbacks now only touch what the GUI showed. Each call is previewed with the same filters first, everything outside the shown coordinates is snapshotted, and anything the area filter caught out there is put straight back afterwards — neighbour blocks by the same player with the same material no longer get swept up. Touched rows are attributed back to their raw entries, and the time buffer is tightened (120 s → 60 s).
Readable counts in the results GUI
- Container totals over 64 expand into several 64-stack icons sharing one parent entry (128 → 2×64) — the title keeps the true total plus Stack i-of-n lore, and pagination/clicks resolve back to the parent entry
- Block icons show a badge of up to 99 (vanilla hard cap); tooltips unchanged
- Raw breakdown stays 1:1 per logged action with matching caps
Tab-completion suggests lookup first
/cpv tab-completion now suggests lookup first, so typed CoreProtect-style flags are one keystroke closer.
Installation
- Download
coreviz-1.3.0.jarfrom Modrinth or CurseForge - Drop into
plugins/alongsideCoreProtect.jaron Paper 26.1+ with Java 25+ - Restart, join on matching client, run
/cpviz
Commands & Permissions
/cpviz [player] # menu GUI (bare /cviz re-opens last)
/cpviz u:<player> t:<time> r:<radius> a:<block|container|session> b:<item> # typed lookup
/cpviz i | /cpviz inspect # toggle click-to-inspect mode (NEW)
/cpv check u:<player> a:mining [t:<time>] # x-ray check
/cpv see # re-open last check
/cpviz clear # clear highlights
Aliases: /cpv, /coreviz, /cviz
cpviz.use(op) — use GUI & highlights & inspectorcpviz.teleport(op) — Teleport button in resultscpviz.rollback(op) — roll back / restore entriescpviz.check(op) —/cpv check&/cpv see
Typed flags: u:/user: player, t:/time: (1h, 2d12h, omit = all time), r:/radius: number or #global, a:/action: block/container/session/mining (with +/-), b:/block:/item: one Material, h: highlight.
See README for Aggregation rule (aggregation-window-seconds default 3600s = 1h bucket) and all xray-* tuning.
Notes
- No config migration needed from 1.2.x — no new keys, no new permissions.
- Paper 26.1+ and Java 25 are mandatory — older Paper / Java 21/17 will fail to load.
- Requires
repo.papermc.io+maven.playpro.comonly at build time.
Built from net.thermedwolf:coreviz:1.3.0 — Paper API [26.1.build,) — CoreProtect 24.0 (compile) / 23.1+ (runtime floor)
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:jMeqLs90:2Cxeslvb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jMeqLs90:2Cxeslvb"
}

