Links
Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 4 days ago
All versions
1.7.0
Release
TropiHunterBoard 1.7.04 days ago 101
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Changes
HunterBoard 1.7.0
New
- PvP local replays: battles between players are saved as files playable in the Pokémon Showdown viewer, with a clickable link in chat at the end. Off by default;
/hbreplayshows the status, toggles sound and opens the folder. - Radar bar at the top of the screen, showing Tropimon's radar markers, with its own settings (length, size, height, always visible, hide in menus, hide Tropimon's bar).
- Full capture card: ability, IV quality and all six IVs on a single page (optional).
- Automatic rank detection from the server (manual choice still available).
- Hunts saved per Minecraft account: several accounts on one instance no longer share a board.
- Weekly reset: last week's board is cleared automatically on Wednesday at 9 pm (Paris time), with an optional countdown on the HUD.
Options
- Redesigned options screen: tabs, one option per row, aligned controls.
- Hover any option for 2 seconds to read what it does.
- Accent colour swatches, a "Default sizes" button and a button to open the replays folder.
- "Reset all" now asks for confirmation.
Fixes
- HUD size settings had no effect once a HUD had been resized in the position editor.
- The HUD footer count and bounty did not update after an automatically validated catch.
- Misaligned elements in the options screen, notably the colour settings.
- Toggling the HUD now shows a message, so a hidden HUD is no longer mistaken for a broken one.
- The PvP panels do less work every frame.
- The donate button now credits Coquelicots.
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:gbxjFDbh:oUoONOWm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gbxjFDbh:oUoONOWm"
}

