1.0.9
Compatibility
Required content
Changes
BetterPieChart+ 1.0.9
Major new feature — multiple views at once — plus a run of fixes and usability improvements since 1.0.3.
Two independent views on screen at once — e.g. block entities and entities side by side.
View 2 is optional and turned on from the menu via "View 2: On/Off". A "View 1 | View 2" switcher at the top of the menu; every setting (section, filter, sorting, boxes, pie/legend) applies to the currently selected view.
Each view has its own boxes, filter, and sort order. Refresh rate and overall visibility stay global. View 2 defaults to entities, view 1 to block entities. Both start in the top-left, side by side. Existing settings are migrated into view 1 automatically.
Usability:
New "Shown/Hidden" toggle right in the menu for the overall display. Previously this was only on the F6 keybind, which doesn't fire while the menu is open — so it could look like no data was coming in when everything was just hidden. Both boxes of every view can be dragged and resized in the menu, regardless of which view is active. Menu buttons are now centered instead of top-left, where they overlapped the chart boxes. Removed the "Reset layout" button — redundant now that both boxes drag freely.
Fixes:
The vanilla pie chart no longer appears on its own and can once again be closed normally with F3+1. The mod now only keeps the profiler collecting and leaves the game's display logic untouched. The view no longer jumps back to the top level on its own, and stays on the section you selected. Closing the menu keeps the view you last navigated to.
Compatibility:
Pinned to Minecraft 26.2. Other mods that also hook the profiler (e.g. Litematica/MaLiLib) may draw their own vanilla-style chart while data is being collected — dismissable with F3+1.
Imcompatible with:
-Lithium -Lunar Client
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:qlagXNJP:3CFCpOfu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qlagXNJP:3CFCpOfu"
}

