01

What Client & Server proves

It indicates the project is intended for both sides. It does not prove compatibility with every hosting panel, proxy, modpack, AI provider, or other mod.

02

Match matrix

A multiplayer launch is only valid when these fields agree.

FieldServerEach client
MinecraftExact supported versionSame version
LoaderForge or NeoForge buildCompatible matching loader
Verity projectExact project and releaseSame required release
DependenciesAll required server relationsAll required client relations
ConfigurationServer-owned settingsNo conflicting local assumptions
03

AI and secret handling

Determine whether the selected project expects the provider on the server or client before adding a key. Never distribute a shared API key inside a public modpack or ask players to paste it into a website.

04

Isolation test

Start with Verity and its required dependencies in a clean server. Join with one matching client, create a disposable world, test the documented behavior, then add other mods in small batches.

05

Evidence to capture

Record project ID, release, game version, loader build, dependency versions, host, server log, and whether failure occurs at startup, join, world load, entity behavior, or AI response.

FAQ

Questions

Does Client & Server mean every player can join without the mod?

No. Follow the exact project's requirements; in a modded environment clients commonly need matching loader, mod, and dependencies.

Can one API key be bundled for all players?

Do not distribute a secret in a pack. Verify where the project expects provider configuration and keep credentials private.