
Nexa AI Chat
The Mod/Plugin Introduces Nexa Ai Agent into the Minecraft. Your sidekick in minecraft! Accessible from the chat. You can talk to it anytime, even ask it to do actions. it has all context of you and environment so when it talks, you better listen.
Tags
Creators
Details
2.2.0
Compatibility
Required content
Changes
Nexa 2.2 - Changelog
Nexa 2.2 brings full Bring-Your-Own-Key (BYOK) support, persistent conversation memory across sessions, and instant action previews! You can now easily plug in your favorite AI providers, chat seamlessly without losing past context, and enjoy a cleaner, faster in-game experience. All Nexa users are requested to immediately update to version 2.2 or above. All previous versions will be deprecated soon and would not work.
- Connect directly to Google Gemini, Groq, Ollama, or any OpenAI-compatible AI provider using the new ingame settings menu tab or
/nexa-config byokcommands. - Fine-tune how deeply your AI model reasons before responding, with custom thinking modes tailored for Gemini, Groq, and Ollama.
- Nexa now remembers your conversation history even after disconnecting or restarting the server, automatically managing long chats so it never forgets context.
- Confirmations for actions (such as teleporting, building, or giving items) now appear instantly with helpful details like travel distances, world border checks, and exact effect durations.
- Optimized UI rendering prevents menu micro-stutters, and streamlined network communication makes AI replies faster and more reliable.
- Any existing custom key configurations are automatically imported into the new system the first time you boot up 2.2.
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:eFhkNO4w:rUrUKqSg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eFhkNO4w:rUrUKqSg"
}
