
Player Finder
๐งญ Player Finder is a lightweight client-side Fabric mod that helps you quickly locate the nearest player in multiplayer. It displays the player's name, distance, direction, and nearby player count through a fully customizable HUD. With an intuitive se
1.2.2
Compatibility
Required content
Changes
๐งญ Player Finder 1.2.2 โ Stable Release
๐ ๏ธ Bug Fixes & Compatibility
This release focuses on bug fixes, improved stability, and compatibility with Minecraft 26.1โ26.3. No new features have been added.
๐ Bug Fixes
- Fixed invisible menu titles and HUD Position Editor instructions.
- Fixed the keybind category name to display as Player Finder in Minecraft's Controls menu.
- HUD Position Editor improvements:
- Pressing
Escapecancels editing and restores the last saved position. - Reset Defaults resets only the HUD position, preserving the selected text color.
- The preview now matches the actual HUD for more accurate positioning.
- Pressing
- Improved handling of damaged or unreadable
config/player-finder.jsonfiles. Default settings are used for the current session without immediately overwriting the original file. - Prevented potential crashes when displaying Enabled/Disabled toggle messages on Minecraft versions where that functionality is unavailable.
- Added error logging for menu-opening failures to make troubleshooting easier.
๐ง Minecraft Compatibility
The same JAR is intended to support:
- Minecraft 26.1
- Minecraft 26.1.1
- Minecraft 26.1.2
- Minecraft 26.2
- Minecraft 26.3
Requirements:
- Fabric Loader 0.19.3 or newer
- Fabric API
- Java 25
๐พ Configuration
Your existing settings, including HUD position and text color, are preserved.
๐ฆ Release Notes
This is a maintenance release focused on reliability and compatibility. All existing Player Finder features remain unchanged.
Optional dependencies
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:BbXUrdiY:rU1tf8rD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BbXUrdiY:rU1tf8rD"
}
