All versions
1.0.4
Release
PlayerManager 1.0.4last month 36
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Changes
PlayerManager 1.0.4 – Messenger Update
New Features
- Added a private-message messenger directly inside PlayerManager.
- Incoming
/msgmessages are organized into individual conversations. - Added player search and suggestions when starting a conversation.
- Replies automatically use the server’s supported private-message command.
- Added a dedicated Messenger hotkey, defaulting to
U. - Added visible, draggable scrollbars for the conversation list and individual chats.
- Conversations can now be permanently deleted.
- New private-message notifications with an optional notification sound.
- Added a setting to display private messages in both the Minecraft chat and PlayerManager, or only inside PlayerManager.
- Open conversations now automatically scroll to the newest incoming message.
- Messages received while a conversation is open are automatically marked as read.
Fixes
- Fixed incoming replies occasionally not appearing.
- Fixed sent messages appearing twice in conversations.
- Fixed private messages only being detected once.
- Fixed messenger elements overlapping at different GUI scales.
- Improved conversation-list scrolling and responsive layout behavior.
- Prevented private-message processing from causing duplicate mention sounds.
- Improved compatibility with different server commands such as
/msg,/tell,/w,/message, and/whisper.
Compatibility
- This build supports Minecraft 26.3 with Fabric.
- Minecraft 26.2 requires a separate compatible build.
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:bIXUqZ0D:O6XP2uUO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bIXUqZ0D:O6XP2uUO"
}

