Tags
Creators
Details
1.2.2
Compatibility
Changes
SolverMOTD 1.2.2 Changelog
Version: 1.2.2-SNAPSHOT Compatible with Minecraft Bukkit/BungeeCord/Velocity 1.8+
Updates:
- Multi-Platform Support: The plugin is no longer exclusive to Bukkit. Version 1.2.2 introduces full native support for BungeeCord and Velocity.
- Modular Codebase: The entire project structure was heavily refactored, splitting the monolithic core into platform-specific bootstrappers, proxies, and shared utilities.
- Adventure API Integration: Added support for net.kyori.adventure to manage messages, allowing compatibility with MiniMessage, Legacy strings, and BungeeCord text formats effortlessly.
- Build System Automation: Replaced raw IDE dependencies with a fully automated Gradle build script, enabling the shadowJar task to compile the plugin seamlessly out of the box.
- Decoupled Configuration API: Completely rewrote the FilesManager to drop its hard dependency on Bukkit's YamlConfiguration, introducing an IConfig abstraction with native adapters (BukkitConfig, BungeeConfig, VelocityConfig).
- Velocity Integration Fixes: Patched the startup sequence and message execution logic within SolverMOTDAPI to properly recognize and initialize the Velocity platform.
- Isolated PlaceholderAPI: Moved PlaceholderAPI logic out of the common utilities package into a Bukkit-specific class, shielding proxy platforms from NoClassDefFoundError crashes.
- State Management Fixes: Corrected a critical initialization bug where the plugin state was never being toggled to true upon successful startup.
- Data Folder Pathing: Adjusted the data folder logic across BukkitLoader, BungeeLoader, and VelocityLoader to point precisely to the plugin's dedicated folder instead of referencing the parent plugins directory.
Thanks to Zowi (NovaCraft254) for the help starting with this version.
Support: support@jeamcube.com
Wiki English: Not ready yet (Sorry) Wiki Spanish: Not ready yet (Soon)
Community: https://discord.gg/EdcYuBAdFB
Best regards, the FyrxLab team.
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:OryL7rBG:E2cVe93X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OryL7rBG:E2cVe93X"
}

