Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated 4 months ago
All versions
1.5.1
Release
LamMailBox 1.5.1last year 48
Compatibility
Minecraft: Java Edition
1.21β1.21.9
1.20.x
Platforms
Folia
Paper
Purpur
Changes
Updates β¨
- Added pagination to mailbox and sent mail GUIs, keeping each viewer's page state and exposing configurable previous/next buttons plus a page indicator.
- Introduced custom model data support across GUI decorations, command items, and mailings so resource-pack overrides display consistently in previews and persisted mail.
- Expanded composer and review screens with back buttons and editor shortcuts, making it easier to jump between the mailbox, sent list, and item editors while drafting mail.
Fixes π οΈ
- Apply configuration-driven item meta without overwriting existing lore or custom model data, preserving detailed previews for stored mail, decorations, and command bundles.
- Restored legacy command items by falling back to the generic action key when specialized metadata is missing, keeping older configurations clickable.
Changes π
- Raised the default configuration schema to 1.6 and added pagination/back-button/custom-model entries throughout
config.yml, alongside matching guidance inmailings.yml. - SQLite storage now migrates
mail_command_itemsto add acustom_model_datacolumn and persists the optional value parallel to YAML command item definitions.
Notes π
- Use the command item editor's new custom model button to set a numeric model id or type
CLEARto reset, and update page button slots/materials to fit your layout before deployment. %current%and%total%placeholders populate the pagination indicator text; translate the new config messages/titles if you localize player-facing strings.- If you upgraded from v1.5 or earlier, edit
gui.main.items.mail-display.slotsto free the bottom row (slots 37β44) so the next-page button has room; otherwise pagination controls stay hidden. - Back up your data before upgrading so the automatic column migration and config updater can run safely, then
/lmbreloadto refresh GUI layouts after adjusting defaults.
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:SCwoZLMd:httEWRQi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SCwoZLMd:httEWRQi"
}

