0.9.10
Compatibility
Changes
MysticSuite 0.9.10: Smoother chat tools and a lot of small fixes
Chat channel per server
The chat HUD now tracks public, marry, and party chat separately on each server instead of once for everything. The first time you join a server the mod checks which chat you're in, and those checks no longer show in chat. The "chat set to..." replies are also hidden when the advertiser or welcome message steps out of marry or party chat to post publicly. If the HUD ever gets out of sync, /msuite chatmode check fixes it.
Staff chat removed, welcome messages are back
Staff chat tracking has been removed, since it can't be tested anymore. The welcome message keybind is back for everyone; set your message under Chat > Welcome.
Single player stays quiet
Wardrobe, Display Vaults, cosmetic collecting, and settings sync now switch off in single player and LAN worlds you host. They no longer grab chests or show Wardrobe messages there, and they come back as soon as you join a server.
Supporting the mod
/msuite donate now just explains how to support the mod. It no longer sends in-game money, and the mod no longer looks for or reports payments.
Fixes
- Commands the mod sends for you (server join setup, the advertiser, auto fly) are paced to stay under the server's limit, so you no longer get kicked for spam.
- Equipped cosmetics stay on after closing the menu, logging out, or switching servers.
- Auto fly turns flight back on if a world switches it off when you arrive, like using
/backinto the resource world. - Settings save reliably again, including HUD background opacity and auto-dropper groups.
- Fewer small stutters from jobs payouts and dragging HUDs.
- Jobs payouts of $1,000 or more are counted again.
- Emotes reconnect on their own after a dropped connection.
- The auto-dropper never drops items from an open chest.
- Inventory sort keeps items in order, and sort hotkeys no longer fire while typing in chat.
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:s4sozS2d:NpDrAbpr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s4sozS2d:NpDrAbpr"
}

