1.2
Compatibility
Changes
HandyMaths Release 1.2.1
This is a new release featuring many upgrades to the internal structure of the plugin making it faster and lighter*.
We've taken long to release this update because we've implemented one of the most advanced features ever released in a plugin, AI
*the implementation of AI increases exponentially the size of the plugin.
1. Internal Structure.
In this new update we've meticulously perfected the infrastructure of the plugin, this new update features a 10% upgrade in speed compared to the last update..
Full Customizability.
Now, with the implementation of AI, we've not only implemented it as ours, it's fully customizable, please note this is in BETA and may not work.
Let's say a person has a server with 100 players online; that server is very popular, so, instead of just showing:
-
[HandyMaths] > RESPONSE
it looks like this:
-
[NAMEOFSERVER] > RESPONSE
AI Implementation.
Now, let's adress the elephant in the room, the AI. Artifficial intelligence (AI) nowadays takes part in some of the most mechanized activities in out daily basis. So that's why we've decided to implement this.
LLM and PARAMETERS.
For the LLMs, we've chosen:
- Llama 3.1 8b
it provides excellent responses, while making them concise.
Performace.
AI, needs a lot of RAM and CPU Cores, to run, don't even get me started on the ML.
And, because Dellyrium Studios plugins are focused on lightweigh, but handy. That's the reason why we've decided to implement this on the cloud with Groq.
Minimum Specs:
- 1 CPU Core, (dedicated or shared).
- .5 or 1 GB of RAM.
PD: For setting it up you must put the Groq API key on the config.yml.
A video will be created featuring the plugin.
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:BYYdP4Pz:2GerdaNV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BYYdP4Pz:2GerdaNV"
}

