Verity Mod Multiplayer: Servers and Aternos Checks

Can you play Verity Mod in multiplayer?

Verity JE is listed for client and server environments, but multiplayer support must be checked for the exact release and hosting setup you use. The Verity JE project, owned by VarmiteYT with Project ID 1591438, is the Java project discussed here. A similar Bedrock add-on name does not identify the same software.

The stable and beta files in the box above both target Minecraft 1.20.1 with Forge; the NeoForge 1.21.1 listing belongs to a different, older branch. Every player and the server must use the same file, not just the same branch. Do not combine a server from one branch with clients from another merely because both files say Verity.

This guide helps you decide whether a host can run your chosen setup and isolate failures when a friend joins. If you meant a browser game rather than Minecraft multiplayer, see playing Verity online or free. You still need Minecraft for the Java mod; a hosting control panel does not replace the game client.

What is confirmed, and what is still missing?

Release or feature	Confirmed by its primary source	Not established by that source
Verity JE 5.7.4	Forge 1.20.1 release; its changelog fixes a missing Groq model	Which machine sends multiplayer chat requests and where dedicated-server credentials belong
Verity JE 6.0.0-beta.9	Forge 1.20.1 beta; its changelog reports reworked AI configuration	Whether it preserves 5.7.x multiplayer configuration or key placement
JE Extra Host Mode	Author describes host-generated speech shared with nearby players	Guaranteed dedicated-server support or control of every chat and transcription request

The 5.7.4 release page and beta.9 release page do not provide a dedicated-server configuration recipe. The project’s environment label is not enough to fill that gap. This page therefore offers compatibility checks and a generic Minecraft LAN procedure, not a validated Verity server installation tutorial.

If your goal is a supported public server, obtain instructions for your exact release from the maintainer before buying hosting. Ask specifically whether chat, speech recognition, and voice generation run on each client or on the host, and which configuration controls each one. A single answer about “the AI” may leave two of those jobs unresolved.

Prepare two compatible Java clients

Use two legitimate Java accounts on computers connected to the same trusted local network. Both players should launch the agreed Minecraft 1.20.1 Forge profile, with the same Verity release and compatible required dependencies. Use the Java installation guide to prepare those profiles. Do not update Minecraft to a newer major version merely because a general Minecraft help page recommends the latest release; the mod still needs its supported version.

Before connecting, each player should be able to start a disposable single-player world without a missing-mod error. Note whether that player’s existing configuration can produce a typed response. This is a comparison for later, not proof that each multiplayer participant must own a separate API key. Do not exchange credentials to make the two installations look identical.

For a 5.7.4 single-player comparison, the configuration screen is Mods > Verity > Config. The cloud choice is under AI Settings, while Local LLM > Use Ollama takes precedence when enabled. Those local controls are not evidence of dedicated-server behavior. For beta.9, follow the current 6.x setup instructions instead of copying 5.7.4 field names into a server file.

Use a new world for the connection attempt. Keep optional voice extensions and unrelated modpack additions out of the first comparison. Record the exact Minecraft, Forge, Verity, and dependency versions in a note containing no secrets. If a participant has a different build, correct that mismatch before moving on.

Open a local world and join it

These are Minecraft’s normal Java LAN controls, documented in Mojang’s multiplayer guide. Applying them to your Forge profile lets you attempt a connection; it does not certify Verity’s conversation or voice behavior.

1. Host: Launch the prepared Forge profile and enter the disposable world through Singleplayer.
2. Press Esc > Open to LAN. Choose the guest game mode and command permissions appropriate for the test, then select Start LAN World. Do not grant commands solely to repair an AI error.
3. Guest: Launch the matching profile, choose Multiplayer, and wait for local-network scanning. Select the host’s LAN world and join it.
4. Keep the host’s game open. Confirm that both players can see each other before trying a Verity interaction.

If the world does not appear, stop at the connection problem. Verify that the host actually started LAN sharing and that both computers are on the same local network, rather than one on a guest network or mobile hotspot. A cloud API key cannot make the LAN world discoverable. Do not disable the entire firewall or expose your router to the internet as a blanket workaround.

For a useful comparison, try the same LAN procedure in a separate, unmodified Minecraft 1.20.1 profile and disposable world. Do not open a modded save without its mods. If the unmodified test also fails, address Minecraft account or local-network access first. If it succeeds but the Forge setup fails, keep the displayed disconnect message and compare the mod versions rather than changing network settings indiscriminately.

LAN means the same local network. It is not an invitation link for a friend in another house, and the procedure above does not install a dedicated server. Avoid installing an unrelated networking extension during the first attempt; that would introduce another software dependency before you know whether the local setup works.

Check Aternos before attempting an installation

Aternos’s mod installation instructions require mod-capable server software, the desired mod, its dependencies, and a compatible local client. Aternos installs mods from its library; it does not accept arbitrary mod files uploaded from your computer.

Search that library for the exact project and then inspect the available release. This guide does not confirm that Verity JE, JE Extra, or all their required versions are currently available there. A project existing on CurseForge or Modrinth is not confirmation of an Aternos listing. Check each dependency too; finding the main mod alone is not enough.

If the required project is absent, use the host’s suggestion process. Its review considers distribution, activity, and technical requirements, and acceptance is not guaranteed. Do not rename another mod, place a file in a world folder, or use a plugin slot to bypass the library restriction.

Even if the files are listed, ask whether the plan supports the additional configuration your chosen AI arrangement needs. A dashboard that can install Forge may not let you run a separate model process or edit every relevant setting. Get a specific answer before transferring a valued world. A tutorial about ordinary Forge mods cannot establish these Verity-specific hosting capabilities for you.

Where should the API key and Ollama run?

The sources checked here do not establish base Verity JE’s multiplayer request ownership for either 5.7.4 or beta.9. Therefore, do not move a working client’s key into a server configuration, copy it to every friend, or assume the host pays for every request based on this guide. Keep existing credentials private and ask the maintainer for the exact release’s arrangement when that information is missing.

You can collect useful evidence without sharing a key. Have one participant send one harmless typed prompt while both players note the time. Compare the relevant local game logs and any server log for that attempt. Each account owner can privately check whether their provider dashboard records usage. A request shown in one account is a clue about that test, not proof that all future speech and chat requests use the same account. Do not turn this into repeated paid calls if the first attempt reports an authorization or rate-limit error.

There is one narrower documented case: JE Extra Host Mode describes host-generated speech audio. That statement concerns an optional add-on’s voice feature, not every base-mod AI request. It cannot establish where chat keys or speech-recognition credentials belong. Keep these questions separate when reading a tutorial or reporting a problem.

For Ollama, the address has an unambiguous meaning even when the mod’s request ownership is unknown: 127.0.0.1 refers to the machine making the request. If a guest client sends it, that address targets the guest’s computer. If a remote server sends it, it targets that server, not the host’s home PC. A working local single-player URL is consequently not a portable multiplayer service address.

Ollama’s documentation describes its default loopback binding and separate network configuration. Do not expose a model service to the public internet as a quick fix for a connection error. Use the local AI guide to understand your version’s integration, and choose a supported authenticated network arrangement before allowing remote access.

Once joined, check conversation and speech separately

Use a disposable world and keep a backup of any existing world before switching software or mod versions. The following is a suggested diagnostic sequence, not a claim that this site has tested your particular host.

1. Host interaction: Have the host use the same Verity interaction that worked in single-player. Record whether the text interface opens, a response arrives, and audio plays.
2. Guest interaction: Have the guest repeat it. Record the three results independently; a host’s audible response does not prove the guest heard anything.
3. Reconnect: Let the guest leave and rejoin, then repeat the successful interaction. Keep the settings fixed during this check so a reconnect failure is distinguishable from a configuration change.

Do not interpret a successful join as a complete test. For a conversation-focused session, the useful result is that the intended players can interact and receive the expected text or audio without exposing credentials. If only text works, it may still be enough to play while you diagnose voice separately.

Diagnose the failure you can actually observe

Symptom	First comparison	Where to continue
A player cannot join	Minecraft, loader, required mods, and versions	Resolve the join error before testing AI
The server fails before accepting connections	Server log and the last added dependency	Crash troubleshooting
Only one player has no interface	That client’s mod list and the working client’s list	Interaction troubleshooting
The interface works but text never arrives	Request error and the configured provider	API connection errors
Text appears but one player hears nothing	Local playback and speech configuration	Talking to Verity
Replies slow down when more people talk	Request volume, provider limits, and model load	Reduce simultaneous tests and inspect the reported error

Collect evidence from the side that fails. A server log alone may not contain a player’s local audio error. A screenshot of a guest’s disconnected screen may omit the server’s explanation. Ask for the time of one failed attempt and a short relevant excerpt, then compare both sides of that same attempt.

Do not use administrator permissions as a universal repair. Giving every guest elevated privileges does not correct a missing dependency or an unauthorized AI request. Change permissions only when the exact action and the project’s instructions establish that they are required. Keep a test server private while diagnosing it.

Shared voice with Verity JE Extra

Verity JE Extra is an optional third-party add-on, not a requirement for ordinary Verity installation. Its author describes Host Mode as generating speech on the host and sharing audio with nearby players, but explicitly labels the feature as still being tested. That does not certify dedicated-server or Aternos compatibility.

The add-on requires a compatible Verity 6.x installation. Do not add it to a stable 5.7.4 group setup and expect it to work. Create a separate test combination if you need its features. Get basic joining and typed interaction working before enabling shared voice, then compare the host and guest results with the feature disabled and enabled.

If the optional feature fails, return to the working base setup and report the exact combination to the add-on author.

Ask for the missing release-specific instructions

A useful support request names the project, release, Minecraft and Forge versions, host type, number of affected players, and the first failing action. Include whether the same test works in single-player and whether optional add-ons were disabled. Ask which machine should run chat, transcription, and speech output, and request the configuration location for that release. Redact keys, personal paths, private server addresses, and conversation content before sharing logs. These details help the maintainer answer a specific setup question instead of guessing from “multiplayer does not work.”