MailboxGUI 4.1.1

MailboxGUI 4.1.1 is a polish update focused on storage conversion completeness, item template storage, command/help clarity, and language updates.

Highlights

• Added provider-backed item template storage.
• Added item template support to /mba convert.
• Improved storage conversion validation.
• Improved MySQL table validation for all 4.1.x data.
• Cleaned up admin help menu command labels.
• Improved /mba sp and /mba scod help descriptions.
• Updated command suggestions to prefer t:<id>:<amount> template aliases.
• Updated language files to file-version 7.

Storage Conversion Polish

Item templates are now stored through the active MailboxGUI storage backend:

• YAML: plugins/MailboxGUI/data/itemtemplates.yml
• SQLite: mailboxgui_itemtemplates
• MySQL: mailboxgui_itemtemplates

The /mba convert command now includes:

• Player data
• Post Office data
• Delayed mail data
• Item template data

Conversion backups now also include itemtemplates.yml.

MySQL Validation Improvements

MySQL validation now checks and creates all required MailboxGUI tables before switching storage:

mailboxgui_playerdata
mailboxgui_postoffice
mailboxgui_delayedmail
mailboxgui_itemtemplates

This helps prevent incomplete storage conversion when using MySQL.

Command & Help Menu Polish

The admin help menu now shows the shorter item-template aliases:

/mba itsave <id>
/mba itlist [page]
/mba itdelete <id>
/mba itgive <id> [player]

Package command help was also improved to better explain material items, XP, and item templates.

Examples:

/mba sp <recipients> [from] <item|t:id|xp...>
/mba scod <recipients> [from] <price> [r:player] <item|t:id|xp...>

Tab suggestions now prefer the shorter template format:

t:<id>:<amount>

instead of:

template:<id>:<amount>

Language Updates

Language files were updated to file-version 7.

Only the changed 4.1.1 help/menu keys were updated, and translated comments were preserved.

Upgrade Notes

Existing MailboxGUI 4.1.0 data remains compatible.

If a server used item templates in 4.1.0 with SQLite or MySQL, existing standalone data/itemtemplates.yml data will be imported into the active storage backend when possible.

No mailbox reset is required.