1.3.1
Compatibility
Changes
CoreViz 1.3.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.3.1 | coreviz-1.3.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 both 23.x and 24.0+. On 24.0+ (API v12+) containers use the typed containerLookup(); on 23.x (API v11) they use a direct query of CoreProtect's own container table — same results either way. |
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.3.1
🕐 Inspect looks back 30 days (FIXED)
cviz inspect used to search only the last 24 hours (or whatever range you'd last picked), so activity from a few days ago came up as "No activity found" — while CoreProtect's own /co inspect, which defaults to 30 days, found it fine. Inspect clicks now default to 30 days, matching /co inspect.
- New optional config key:
inspect-default-lookback-hours: 720— tune it if you want a different inspect window. - A range picked in the time range menu still overrides it for the rest of that login.
📋 Results show the searched time range (NEW)
The loading screen and results GUI now tell you which window was searched — e.g. "Range: last 30d 0h" (or "all time" for typed lookups without a time flag). "No activity found" now says what range was searched instead of just suggesting a longer one, and /cpv see reports the window its x-ray check actually used.
No config migration needed from 1.3.0 — the new key is optional and defaults to 30 days. No new permissions.
Dependencies
- Hard: CoreProtect 23.1+ on the server.
- None else — no database, no extra libs.
Installation
- Download
coreviz-1.3.1.jar(mvn clean package→target/coreviz-1.3.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
/cpviz i | /cpviz inspect # toggle click-to-inspect mode
/cpv check u:<player> a:mining [t:<time>] # x-ray mining check (overworld + nether)
/cpv see # re-open last x-ray check
/cpviz clear # clear your persistent block highlights
Aliases: /cpv, /coreviz, /cviz
cpviz.use(default:op) — use the GUI / command + highlights + inspectorcpviz.teleport(default:op) — "Teleport to location" button in resultscpviz.rollback(default:op) — roll back / restore entries via button or double right-clickcpviz.check(default:op) — use/cpv checkand/cpv see
Typed flags: u:/user:, t:/time: (1h, 2d12h, ... omit = all time), r:/radius: (number or #global), a:/action: (block, container, session, mining for check), b:/block:/item: (one Material), h: (highlight).
See README.md → "Typed lookups" and "Aggregation rule" for full syntax and the aggregation-window-seconds tuning (config.yml). X-Ray thresholds tunable via xray-* keys.
Compatibility notes
- Backwards compatible with Paper 26.1 and 26.2 —
api-version: '26.1'is the minimum, Paper loads it on any newer 26.x server. - Not compatible with Paper 1.21.x and older — that's Paper's intentional major-version break at 26.1 (new
26.x.build.*version scheme). - Java 25 is mandatory on all 26.x. Starting with Java 21 or 17 will fail before the plugin even loads.
Built from net.thermedwolf:coreviz:1.3.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:dYjP474X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jMeqLs90:dYjP474X"
}

