Tags
Creators
Details
1.0.0-neoforge-alpha.13
Compatibility
Required content
Changes
πͺ MysticEssentials v1.0.0-alpha.13
Release: Alpha 12 β Alpha 13
Target: NeoForge + Fabric (1.21.x)
β οΈ Important Update Notice for Server Owners
- You MUST delete the following files before starting Alpha 13:
config/mysticessentials/config.jsonconfig/mysticessentials/messages/es_us.json- These files will be regenerated automatically on startup with the new keys and structure.
β¨ Added
π Vault System (GUI-Driven)
- Added a complete Vault System with a 6-row (54-slot) selector GUI.
- Vault selector now supports pagination (45 vaults per page).
- Added Vault Settings GUI (right-click a vault):
- Rename vault (GUI-only, no commands)
- Set vault icon (uses main-hand item, permission-gated)
- Reset a single vault (permission-gated)
- Reset ALL vaults (admin-only)
- Vault names now support color formatting (
&legacy colors, hex support via permissions/config). - Vault data is stored per-player in JSON:
- Path:
config/mysticessentials/vaults/<uuid>.json - Items are serialized safely using SNBT.
- Vault metadata (custom name + icon) is persisted correctly.
- Path:
π Localization & Messages
- Vault UI text migrated to MessagesUtil, allowing server owners to customize:
- Button names
- Lore text
- Menu titles
- Added Spanish translation (
es_es.json) for Vault-related UI. - Improved locale fallback handling and message resolution order.
π¬ Chat Enhancements
- Added groundwork for clickable http/https links in chat via mixin-based handling.
- Improved Gson handling for message files (HTML escaping disabled where needed).
π Changed
- Vault selector icons now display:
- Colored vault name (
<name> - #<index>) - Slot usage (
used/available)
- Colored vault name (
- Default vault naming now respects configurable color codes.
- Vault icon permissions are enforced strictly (
messentials.vault.item.<id|*>). - Configuration structure expanded to support new vault settings.
π Fixed
- Fixed vault item data not saving correctly, which caused:
Tried to load invalid item: 'No key id in MapLike[{}]' - ItemStacks now serialize and deserialize correctly using SNBT.
- Prevented invalid empty ItemStack entries from corrupting vault files.
- Resolved multiple edge cases with vault loading, saving, and UI refreshes.
βοΈ Notes for Server Owners
- Vault limits are permission-based:
messentials.vault.amount.<number>messentials.vault.row.<1-6>- Locked vaults are visually shown using the configured locked item & name.
- All vault modifications (rename, icon, reset) are GUI-only by design.
Full Changelog: https://github.com/L8-Alphine/MysticEssentials/compare/1.0.0-alpha.12...1.0.0-alpha.13
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| MysticEssentials-neoforge-1.0.0-alpha.13-sources.jar | Source jar | 11.57 KiB |
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:JEA9OHq8:T2iDXf27"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JEA9OHq8:T2iDXf27"
}

