01

Before opening the panel

Choose the project first. Verity JE 5.7.2 requires the Forge 1.20.1 route; Verity Revamped 0.1 requires NeoForge 1.21.1 and GeckoLib. Do not select a loader based only on the word Verity.

02

Aternos sequence

Install the matching server software, set the supported game version, search the Mods section for the exact project, install its required dependencies, then have every player mirror the compatible client setup.

  • Confirm exact project name and ID
  • Match Minecraft and loader
  • Install required dependencies on the correct side
  • Start clean before adding other mods
  • Keep the first complete crash/server log
03

Availability versus compatibility

Aternos documents that mods and dependencies must be installed for the selected software. A listed item can still be outdated, absent for one loader, or incompatible with another mod. The platform listing is a distribution signal, not a test result.

04

Deprecated branch warning

Do not use the deprecated Verity JE NeoForge branch merely because you need 1.21.1. Compare it with the separate Verity Revamped project and use an isolated server before moving a world.

05

When to stop

If the exact project or required dependency is unavailable, do not upload a mirrored file or rename another build. Record the missing item and choose a supported host/path or wait for catalog support.

FAQ

Questions

If Verity appears in Aternos, is it guaranteed to work?

No. You still need a compatible server software version, loader, release, dependencies, clients, and mod set.

Can I upload a Verity file that is not in the catalog?

Do not use a mirror or reupload. Follow Aternos rules and the project license; choose a supported route if the exact item is unavailable.