1.2.1
Compatibility
Changes
CoreViz 1.2.1 — Paper 26.1+ (26.1.x / 26.2.x / 26.3 Wilderness Bound)
GUI front-end for CoreProtect. Aggregates repeated container/block actions into clean net totals — e.g. +13 and +14 Iron Ingot from the same player/chest/hour become one +27 Iron Ingot line. Everything is an inventory GUI, no /co lookup spam.
Supported versions
| Component | Version | Notes |
|---|---|---|
| Plugin | 1.2.1 | coreviz-1.2.1.jar |
| Minecraft (Java Edition) | 26.1 – 26.3 | 26.1 (Apr 2026), 26.2, and 26.3 Wilderness Bound (2026-09-15) — same jar for all |
| Server | Paper 26.1+ ([26.1.build,)) |
api-version: '26.1' — loads on 26.1.x, 26.2.x, 26.3.x and newer. Will not load on 1.21.x and older. Works on forks that track Paper API 26.1+ (Purpur, etc.). No Fabric/Forge. |
| Java | 25+ (build + runtime) | Minecraft 26.1+ requires Java 25. Compiled with <release>25</release>. |
| CoreProtect | 23.1+ (API v11+) | Full behavior (blocks + containers + sessions) on 24.0+ (API v12+). On 23.x (API v11) blocks, sessions, and x-ray checks work; container history is skipped with a warning — CoreProtect only exposed container lookups from API v12 onward. |
One jar for the whole 26.x line.
plugin.ymldeclaresapi-version: '26.1'andpom.xmlcompiles against[26.1.build,)(forward-compatible).
What's new in 1.2.1
Patch release — CoreProtect backward compatibility. No config changes, no new permissions.
🔌 CoreProtect 23.x support (FIXED)
Previously the plugin refused to load its CoreProtect hook on servers running CoreProtect 23.x:
[CoreViz] CoreProtect API version 11 is too old. This plugin requires API version 12+ (CoreProtect 24.0+). Please update CoreProtect.
That no longer happens. The hook now accepts API v11+:
- Blocks, sessions, and
/cpv checkx-ray analysis work on CoreProtect 23.1+ — these use the long-standingperformLookup()/sessionLookup()API paths, which are unchanged across versions. - Container history still needs CoreProtect 24.0+ (API v12) — CoreProtect's own API layer cannot return container rows through the legacy lookup path, and the typed
containerLookup()only exists from v12. On 23.x servers container results are skipped: one console warning on hook + a one-line in-game note (container history needs CoreProtect 24.0+ — showing blocks/sessions only) instead of silently missing rows. - The v12-only calls are isolated so 23.x servers never touch the missing
LookupOptions/ContainerResultclasses — noNoClassDefFoundError, verified against the built jar.
To get container history on every server, update CoreProtect to 24.0+ there. Nothing to configure on the CoreViz side either way.
Dependencies
- Hard: CoreProtect 23.1+ on the server (24.0+ for container history).
- None else — no database, no extra libs.
Installation
- Download
coreviz-1.2.1.jar(mvn clean package→target/coreviz-1.2.1.jarif building from source) - Put it in
plugins/alongsideCoreProtect.jaron a Paper 26.1+ server running Java 25+ - Restart, join on a matching 26.1+ client, run
/cpviz
Commands & Permissions
/cpviz [player] # menu-driven GUI (bare /cviz re-opens last results)
/cpviz u:<player> t:<time> r:<radius> a:<block|container|session> b:<item> # typed lookup
/cpv check u:<player> a:mining [t:<time>] # x-ray check (overworld + nether)
/cpv see # re-open last x-ray check
/cpviz clear # clear highlights
Aliases: /cpv, /coreviz, /cviz
cpviz.use(default:op) — GUI / highlightscpviz.teleport(default:op) — Teleport buttoncpviz.check(default:op) —/cpv check//cpv see
Typed flags: u:/user:, t:/time: (1h, 2d12h, ... omit = all time), r:/radius: (#global or number), a:/action: (block, container, session, mining), b:/block:/item: (one Material), h: (highlight).
Compatibility notes
- Not compatible with Paper 1.21.x and older — that's Paper's major version break at 26.1 (
26.x.build.*scheme). - Java 25 is mandatory on all 26.x.
Built from net.thermedwolf:coreviz:1.2.1 — Paper API [26.1.build,) (api-version: '26.1') — 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:WmIPlpsi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jMeqLs90:WmIPlpsi"
}

