Links
Tags
Creators
Details
1.1.8
Compatibility
Changes
Version 1.1.8
Overview
This major release introduces comprehensive web search capabilities with multi-engine support (Bocha and Brave), enhanced configuration management, and improved user experience with new commands and language switching. The update focuses on bringing real-time information retrieval to AI conversations while maintaining flexibility for international users. This version supports Minecraft 1.20.x through 1.21.x.
New Features
-
Web Search Integration:
- Added support for two search engines: Bocha (Chinese-focused) and Brave (International)
- Automatic web search when messages contain trigger keywords (configurable)
- Manual search command
/ollamachat search query <text>for on-demand searches - Search results are formatted and fed to AI for informed responses
- Configurable result count (1-50), site filtering, and time range restrictions
-
Multi-Engine Support:
- Bocha Search Engine: Chinese-focused search with site inclusion/exclusion, time range, and freshness filters
- Brave Search Engine: International search with country, language, and safe search settings
- Easy switching between engines via
/ollamachat search engine <name>
-
New Search Management Commands:
/ollamachat search toggle- Enable/disable web search/ollamachat search status- View current search configuration/ollamachat search engine [name]- Show/change search engine/ollamachat search setkey <engine> <key>- Set API key for engines/ollamachat search setcount <number>- Configure result count/ollamachat search addkeyword <word>- Add trigger keywords/ollamachat search removekeyword <word>- Remove trigger keywords/ollamachat search listkeywords- List all trigger keywords
-
Language System Improvements:
- Hot-reload language files with
/ollamachat reload
- Hot-reload language files with
Enhancements
-
Configuration:
- Added complete web-search configuration section with detailed comments
- Engine-specific configuration blocks for Bocha and Brave
- Configurable trigger keywords for automatic search
- Customizable search prompt template for AI context
- Removed config-version for simpler upgrades
-
Performance:
- Asynchronous search operations to prevent server lag
- Efficient result parsing and formatting
- Connection pooling for search API requests
Configuration Example
web-search:
enabled: false
auto-trigger: true
trigger-keywords:
- "search"
- "find"
- "what is"
result-count: 5
engine: "brave"
bocha:
api-key: ""
include-sites: false
include-sites-list: []
exclude-sites: false
exclude-sites-list: []
time-range: 0
freshness: ""
brave:
api-key: ""
country: "US"
search-lang: "en"
ui-lang: "en"
safe-search: "moderate"
prompt-template: "Based on the following search results... {search_results} ... {prompt}"
Permissions:
- New permissions added for search management:
ollamachat.search.toggle- Enable/disable searchollamachat.search.status- View search statusollamachat.search.query- Perform manual searchesollamachat.search.setkey- Set API keysollamachat.search.setcount- Configure result countollamachat.search.keywords- Manage trigger keywordsollamachat.search.engine- Change search engine
Commands Usage Examples
# Enable web search
/ollamachat search toggle
# Change search engine to Bocha
/ollamachat search engine bocha
# Set Brave API key
/ollamachat search setkey brave your-api-key-here
# Perform manual search
/ollamachat search query latest Minecraft updates
# Add trigger keyword
/ollamachat search addkeyword research
# Check search status
/ollamachat search status
# Reload configuration with new language
/ollamachat reload
-
API Keys:
- Bocha API key: Get from https://www.bochaai.com/
- Brave API key: Get from https://api.search.brave.com/app/keys
- Both engines require valid API keys to function
-
Language Files:
- Update language files to include new search-related keys
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:x9fbBzgJ:5v4nxjQ9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x9fbBzgJ:5v4nxjQ9"
}

