Tags
Creators
Details
0.3.3
Compatibility
Changes
AnhyLingo Version 0.3.3 Release Notes
We are excited to announce the release of AnhyLingo version 0.3.3, which marks a significant advancement in the plugin's development. Key highlights of this version include:
-
Code Refactoring and AnhyLibAPI Integration: A substantial portion of AnhyLingo's code has been refactored and transformed into a separate library, AnhyLibAPI. This change means that servers wishing to use AnhyLingo must also install AnhyLibAPI. This separation not only streamlines AnhyLingo's codebase but also enhances its functionality and reliability.
-
Optimization and Bug Fixes: Along with the refactoring, the remaining code in AnhyLingo has undergone significant optimization. We have addressed numerous logical and technical errors, resulting in a more robust and efficient plugin.
-
Dedicated AnhyLingo API: An important addition in this version is the introduction of AnhyLingo's own API. This dedicated API provides other developers with the opportunity to use AnhyLingo as a library, allowing for greater flexibility and integration in their plugin development projects.
We believe these updates will greatly enhance the user experience and offer developers more tools and functionalities to explore and utilize in their Minecraft servers. As always, we are committed to improving AnhyLingo and eagerly await feedback from our user community.
Important to Know:
AnhyLibAPI must be loaded on the server as a plugin. It's crucial to understand that AnhyLibAPI, in its role as a plugin, does not monitor any events, have timers, or interact with the world or players, ensuring no additional load on the server's operation and performance. The primary purpose of AnhyLibAPI is to provide its API to other plugins, serving as a robust foundation for extending their functionality. This design ensures that AnhyLibAPI enhances plugin capabilities without compromising server efficiency.
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:uKvEKgDV:tsGqCleF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uKvEKgDV:tsGqCleF"
}

