Tags
Creators
Details
5.0.1
Compatibility
Changes
MailboxGUI 5.0.1 - Backend Access & Offline Admin Sends
MailboxGUI 5.0.1 adds optional command-based mailbox access and improves admin mail targeting for offline players.
Added
- Added
/mailbox openand/mb open.- Opens the main MailboxGUI menu directly from command.
- Disabled by default.
- Useful for backend servers, Velocity networks, or servers without physical mailbox/Post Office access.
- Controlled by:
mailbox:
command-open:
enabled: false
- Added the new permission:
mailboxgui.player.open
- Added the new admin recipient tag:
offlineplayers
offlineplayersis supported by:
/mba sl
/mba sp
/mba scod
/mba sm
Example:
/mba sl offlineplayers 'Welcome to the server' --from ExampleServer --delay 10
Improved
- Admin mail commands can now target all known offline players without sending to currently online players.
- Offline player targeting supports MailboxGUI network-aware player tracking where available.
- Player help and tab completion now only show
/mb openwhen command mailbox access is enabled and the player has permission.
Language Files
- Updated language files to
file-version: 12. - Added translated messages for command mailbox access and related help menu entries.
DiscBridge Compatibility
No DiscBridge update is required for this release.
MailboxGUI-DiscBridge 1.0.0 works with MailboxGUI 5.0.1.
The new /mb open command does not affect DiscBridge, and the new offlineplayers recipient tag uses existing MailboxGUI delivery events that DiscBridge already supports.
Updating
You can update manually by replacing the MailboxGUI jar and restarting your server.
You can also use the built-in update command:
/mba update
/mba update confirm
Then restart the server to complete the update.
Velocity / Network Setups
If you run MailboxGUI on multiple backend servers, run the update command on each backend server that has MailboxGUI installed:
/mba update
/mba update confirm
Then restart each backend server.
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:6Pm7qqGZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:34j7WS4b:6Pm7qqGZ"
}

