Verity Mod Ollama Local AI Setup

What the Ollama option changes

Ollama runs a language model service on your computer. Stable Verity JE 5.7.4 on Forge 1.20.1 connects through a local LiteLLM gateway instead of using Groq for conversation. This removes the need for a Groq key for the language-model request, but adds hardware, storage, model, service, and configuration requirements. The 6.0.0 beta family changed this setup; its removal of LiteLLM does not apply to the stable instructions below.

Use Ollama only after the base Java mod works. Minecraft should launch with the correct loader, Verity should load in a clean profile, and the documented in-game interaction should appear. If the game crashes before the title screen, solve the loader or dependency problem first.

Check whether local inference fits your computer

Local models use disk space, memory, processor or graphics resources, and power. Larger models generally need more resources and may answer more slowly on modest hardware. The right model is one that Ollama can load reliably while Minecraft is also running.

Before installing a large model, review the current Ollama documentation and the model’s published size. Keep enough free disk space for the download and enough memory headroom for both applications. A system that can run Minecraft smoothly may still struggle when a model and a modded game compete for memory.

Start with a small model for the standalone service check below. This verifies Ollama, not that the model can reliably follow Verity’s gameplay instructions. Once the connection is stable, compare models one at a time.

Install Ollama from its official source

Install Ollama for your operating system from the official download page. Avoid repackaged installers or bundles promising a preconfigured Verity model. Open Ollama, then open a terminal on macOS/Linux or PowerShell on Windows.

Use these documented Ollama CLI commands, one at a time:

ollama pull qwen2.5:1.5b
ollama ls
ollama run qwen2.5:1.5b "Reply with one short greeting."

Expected results: the download completes, ollama ls includes qwen2.5:1.5b, and the final command prints a generated greeting. The wording varies. This 1.5B model is listed in Ollama’s library and matches 5.7.4’s configured default model. That default is not a guarantee of hardware performance or gameplay quality.

If the CLI cannot connect to Ollama, start the installed app or run ollama serve in a separate terminal and leave it open. Do not start a second server if one is already listening. If ollama is not recognized, reopen the terminal after installation and check the platform’s installation instructions.

Record the exact model name displayed by Ollama, including any tag. Similar-looking names can identify different models or versions. “Model not found” often means Verity requests a name that is not installed, not that the mod itself failed.

Verify the local service

Ollama’s API documentation uses http://localhost:11434/api for its native local API. Check the service without Minecraft:

curl http://localhost:11434/api/tags

In Windows PowerShell, use curl.exe http://localhost:11434/api/tags to run the curl executable. The documented response is JSON with a models array. Look for the model you downloaded. An empty array means the service answered but has no listed models; connection refused means the service or address still needs attention.

This is a diagnostic URL, not a universal Verity config value. Ollama’s native /api routes, its OpenAI-compatible /v1/ routes, and a separate LiteLLM gateway are different entry points.

“Localhost” means the same computer as the process making the request. If Minecraft runs in a virtual machine, container, remote desktop environment, or separate server, localhost may point to the wrong machine. Keep the first test on one computer. Remote exposure introduces firewall and security decisions that are outside the simplest Verity setup.

Do not open the Ollama service to the public internet merely to fix a local connection. A local firewall rule should be as narrow as the setup requires. Follow official Ollama guidance for any non-local deployment.

Start the LiteLLM gateway for 5.7.4

Leave Ollama running. The LiteLLM quickstart currently recommends this isolated CLI installation with the uv package tool available:

uv tool install "litellm[proxy]"

The current package requires Python 3.10 or newer; the documented uv route can provision a compatible Python. If you already have LiteLLM, use litellm --version to check that the command is available. Installation alone does not start the gateway.

Start the gateway in a terminal and leave it open:

litellm --model ollama/qwen2.5:1.5b --api_base http://127.0.0.1:11434 --host 127.0.0.1 --port 4000

This combines LiteLLM’s documented Ollama model prefix with its CLI host, port, and API-base options. Expected result: a running proxy listening on 127.0.0.1:4000, with Ollama as the upstream service on port 11434. The explicit loopback host keeps this local test off public network interfaces.

In a second terminal, run the quickstart’s standalone request test:

litellm --test

Expect a generated chat-completion response. If it reports connection refused or a missing model, fix the gateway or Ollama first.

Configure stable Verity JE 5.7.4

The maintainer’s published 5.7.4 artifact defines these exact controls and defaults:

1. From Minecraft’s title screen, open Mods > Verity > Config. Expect Verity Configuration.
2. Open Local LLM and turn Use Ollama on. In this release it overrides AI Settings > AI Provider, even if that menu still says GROQ.
3. Set LiteLLM URL to http://127.0.0.1:4000/v1/ and Ollama AI Model to ollama/qwen2.5:1.5b. These are the shipped defaults and match the gateway command above.
4. Keep Thinking Mode (Qwen3 Models only) off for this Qwen2.5 test. Apply the changes and reopen Config to check them.

The stored field names are AISettings.use_ollama, AISettings.ollama_url, and AISettings.ollama_ai_model. Verity appends chat/completions to the configured base URL. Do not paste /api/tags into LiteLLM URL, replace port 4000 with 11434 while keeping these gateway settings, or remove ollama/ from this model field.

For a different installed model, change both the gateway’s --model and Verity’s Ollama AI Model, keeping the ollama/ prefix before the exact name from ollama ls. Leave speech services unchanged until typed replies work.

Keep the release boundary explicit: the older Ollama video is titled “up to 5.7.3.” The maintainer’s 6.0.0-beta.1 notes from July 29, 2026 announce a changed config menu and removal of the LiteLLM requirement. That beta change is not evidence that stable 5.7.4 can skip the older gateway setup. The currently linked 6.0.0+ tutorial is for the beta family, and beta.9 reworked AI configuration again.

First end-to-end test

1. Start Ollama and LiteLLM, and confirm both standalone tests answer.
2. Start the clean Verity JE profile.
3. Open a new test world.
4. Once Verity appears, open Minecraft chat with T, type Verity, say hello., and press Enter. Keep General > Immersive Mode off while testing.
5. Watch the Minecraft log and gateway output for the request.

A response in Ollama but not Minecraft suggests a Verity configuration or response-handling problem. No request reaching Ollama suggests the provider selection, endpoint, service availability, or firewall. A model-not-found response identifies the name or missing download. A very slow response may be resource pressure rather than a broken connection.

Wait for one request to finish. Sending many prompts can queue local work, consume more memory, and make the mod appear less responsive.

Common Ollama failures

Service is not running: the model may be installed but no process is listening. Start Ollama using the current operating-system instructions and verify again outside Minecraft.

Exact model is missing: run ollama ls. For the default model, Ollama must list qwen2.5:1.5b; the gateway command and Verity field must both use ollama/qwen2.5:1.5b.

Wrong endpoint: for this stable setup, Ollama listens on 11434 and the LiteLLM gateway on 4000. Verity’s base URL is http://127.0.0.1:4000/v1/. Watch for a stopped gateway, an accidental https scheme, or a remote hostname copied from another tutorial.

Profile mismatch: confirm that the Verity configuration belongs to the launcher instance you actually start.

Memory pressure: close heavy applications, use a smaller model, lower other game resource demands, and observe operating-system memory rather than repeatedly reinstalling.

Firewall or isolation: verify that the Java process can reach the local service. In managed environments, follow network policy rather than disabling security controls.

Text before speech

Test text responses before microphone input or text-to-speech. A local model response proves that Ollama, the endpoint, model name, and Verity request path work. Voice features add operating-system permissions, input devices, speech recognition, audio output, and language behavior.

The Verity JE page notes that AI text can support multiple languages while speech-to-text and text-to-speech were tested in English. Use short English text during the first diagnosis. If text works and voice does not, keep the Ollama setup unchanged and troubleshoot the audio features separately.

Privacy and security boundaries

Local inference can reduce the number of prompts sent to a cloud model, but it is not a blanket guarantee that the entire game session is offline or private. Review the behavior of Minecraft, the launcher, Verity, other mods, and update tools. Avoid placing passwords, private documents, or sensitive personal information in prompts.

Keep the Ollama service local unless you intentionally design and secure a remote deployment. Do not expose it through a router, public tunnel, or unrestricted network interface as a quick fix. Logs can still contain prompts and local paths, so inspect them before sharing.

Decide between Ollama and Groq

Choose Ollama when your machine can run an appropriate model and you prefer local inference. Choose Groq when local resource use or model management is impractical and you accept a cloud provider. Neither option fixes a wrong loader, missing dependency, or unsupported Minecraft version.

Keep a record of the working model name, Ollama version, service address, Minecraft version, loader, and Verity release. After any update, test Ollama alone, then Verity in a clean world, before returning to an important save.