Tags
Creators
Details
4.0.1
Compatibility
Changes
MailboxGUI 4.0.1
MailboxGUI 4.0.1 is a small bug-fix update focused on the floating new-mail paper icon notification system.
This update is recommended for all servers running MailboxGUI 4.0.0, especially servers using the floating new-mail notification feature.
Bug Fixes
- Fixed floating new-mail paper icons not updating after an admin removes mail from a player inbox.
- Fixed floating paper icons remaining above a mailbox after the mailbox is unregistered.
- Added cleanup behavior for broken leftover paper icons from 4.0.0.
- Fixed notification state so the paper icon is removed when no unseen mail remains.
- Preserved the paper icon when more unseen mail still exists in the player inbox.
- Updated the floating paper icon so it is only visible to the mailbox owner.
New-Mail Paper Icon Behavior
- When a player receives mail, the icon appears above their registered mailbox.
- When the player checks their inbox, the icon clears normally.
- When an admin removes unread mail, the icon updates correctly.
- When a mailbox is unregistered, the icon above that physical mailbox is removed.
- If 4.0.0 left behind broken floating paper icons, 4.0.1 will clean them up as chunks load or during notification refresh.
- Other players no longer see someone else’s floating paper notification.
Upgrade Notes
If you are updating from 4.0.0, this should be a straightforward drop-in update.
Recommended steps:
- Stop the server.
- Back up your
plugins/MailboxGUI/folder. - Replace the old jar with the 4.0.1 jar.
- Start the server.
- Confirm old floating paper icons are cleaned up.
- Confirm new mail notifications appear only for the mailbox owner.
Compatibility
- Supports Spigot/Paper 1.18.2 through 1.21.11.
- Supports 26.1.x, 26.1.1, and 26.1.2.
- Dynmap marker support is still not currently supported on 26.1.x / 26.1.1 / 26.1.2 until Dynmap provides compatible builds.
- MailboxGUI itself continues to work normally without Dynmap on those versions.
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:34j7WS4b:G58yD5vg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:34j7WS4b:G58yD5vg"
}

