Tags
Creators
Details
1.4-beta.1
Compatibility
Changes
π Change Log β Version 1.4
Major Changes & New Features
-
Added connection to CoreProtect. Now, if you had CoreProtect logs on your server, Placing/Breaking blocks will be transferred to BrushLogger. Transferring changes to containers and signs will be added later.
-
Added a 3-second brushing delay to match vanilla archaeology mechanics. You now need to hold right-click and maintain the brushing animation to reveal a block's history.
-
New Container History GUI: * Replaced text-heavy chat logs for containers with a clean, interactive 54-slot GUI.
-
Logs are now represented by the actual items moved, with detailed tooltips (Action, Player, Count, and Time).
-
Added a gradient title for the GUI, fully customizable via configuration.
-
Introduced a Glowing Outline effect that triggers once the investigation is complete, highlighting the specific block you are inspecting.
-
Vanilla Animation Sync: Optimized the hand-swing and item-use logic to ensure the vanilla brush animation plays smoothly without being interrupted by block interactions.
-
Configuration & Customization Output Mode Toggle: Added container_output_mode to messages.yml, allowing you to switch between the new GUI or the classic CHAT output for container logs.
- Enhanced MiniMessage Support: * The History Brush now supports full RGB/Gradient names (e.g., gradient:#FFD700:#FFA500).
- GUI item descriptions and titles now correctly render all MiniMessage tags.
Bug Fixes & Technical Improvements
-
Fixed Animation Stutter: Resolved an issue where the brushing animation would reset or glitch when interacting with chests or other "interactable" blocks.
-
Action Cancellation: The plugin now intelligently checks if a player is still holding the brush and staying online during the 3-second delay to prevent "ghost" menus from opening.
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:LduAqaxj:hGrN8WzK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LduAqaxj:hGrN8WzK"
}

