Tags
Creators
Details
All versions
1.1.0
Release
CoreProtectVisualizer 1.1.03 months ago 42
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Spigot
Changes
Added
- Action-based coloring — Green glow for placed blocks, red for broken, cyan for interactions, yellow for unknown. Colors configurable via
visualization.action-colors. - Shulker display engine — Alternative rendering mode using invisible shulkers with glow outlines. Selectable via
visualization.engine(block_displayorshulker). - CoreProtect API integration — Plugin now hooks CoreProtect's API as a fallback to determine block types and actions when text parsing is insufficient.
- Message buffering — Per-player buffer keeps recent CoreProtect messages to correctly associate actions/materials with following coordinate lines.
- Configurable coordinate patterns — All regex patterns are now in
config.yml; the plugin has no hardcoded patterns. Added the clickable(xNNN/yNNN/zNNN/world)format. - Hex color support — Block colors and action colors accept
#RRGGBBhex values in addition to named colors. - Configurable fallback material —
visualization.default-block-materialcontrols what block type is shown when the original material can't be determined. - Fully configurable messages — All plugin messages moved to
config.ymlwith&legacy +&#rrggbbhex color support.{count},{key},{value}placeholders supported.
Changed
- Render engine — Replaced GlowingEntities (shulker-based) dependency with native Paper
BlockDisplayentities. Zero external runtime dependencies for rendering. - Block color system — Migrated from
ChatColortoorg.bukkit.Colorfor full RGB support. - API version — Bumped from 1.19 to 1.21.
- Message detection — Replaced fragile heuristic (
message.contains("CoreProtect")) with pure regex-based coordinate extraction and proper JSON chat component parsing. - Material parsing — Now handles lowercase material names (e.g.
grass_block) from CoreProtect lookup messages.
Removed
- GlowingEntities dependency — No longer bundled; rendering uses native Paper APIs only.
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:ItVUm2zW:mLiB0tAu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ItVUm2zW:mLiB0tAu"
}
