Installation reference

Versions & Compatibility

Match the Minecraft version, loader and mod build before installing or following a guide.

Documented checkout

Checked October 2, 2026. This is a source snapshot, not a claim that every listed feature is in a published JAR.

Current documentation reference
PropertyValue
Branch / commit26.3neo / 65069046
Mod version property3.0.0
Minecraft / loader26.3 / NeoForge 26.3.0.6-beta
Java25
Optional JEI API31.0.0.11 for Minecraft 26.3
Published 3.0.0 release notes on both CurseForge and Modrinth explicitly include Player Nexus. The six published build combinations are Minecraft 26.3 or 26.2 with NeoForge or Fabric/Quilt, Minecraft 1.21.1 with NeoForge, and Minecraft 1.20.1 with Forge/NeoForge. Choose the file matching your instance; optional companion-mod compatibility still needs its own check.

Choose a download

  1. Check your instance's exact Minecraft version and loader.
  2. Open the Modrinth or CurseForge download listings and select a file explicitly marked for that combination. Follow its dependency requirements.
  3. Use matching Minecraft/loader versions for companion mods as well. Do not install a 26.2 integration JAR in a 26.3 instance.
  4. Back up your world before changing builds. If a documented item or control is missing, compare your file's release notes with the repository history.

The 3.0.0 release entries list builds for all six combinations above. Earlier releases differ; each Changelog entry links its actual Minecraft/loader builds. Follow the download file's compatibility labels and dependencies.

Optional integrations are described in Mod Integrations. The September 21 port notes record no published NeoForge 26.3 builds of Mutant Monsters or Friends & Foes at that time; check current companion-mod listings before installation.

Current source-checked corrections are explained in the IM name reference, Fabric overlap guide, Brute recovery guide and villager Brute model guide. An older published file may not include a later correction.

Spawn compatibility fixes in older ports

These are source-verified corrections for the 1.21.1 NeoForge and 1.20.1 Forge/NeoForge ports, dated October 7, 2026. They are automatic fixes, with no configuration toggle, recipe or required Versus skill. Check the actual download's release notes before assuming a published file contains them; the local Minecraft 26.3 / NeoForge source uses a different mob-color storage mechanism.

Minecraft 1.21.1: first Gift Zombie spawn

The corrected port prepares shared mob-color data before individual mob types initialize. This prevents the earlier crash when the first IM Gift Zombie is created. It is a mob-creation fix, not a change to the Gift Zombie's collection, rewards or combat behavior.

After updating both server and participating clients to a matching corrected 1.21.1 build, restart fully and test a fresh spawn in a backed-up test world. With command permission, use /give @s invmod:gift_zombie_spawn_egg and place the mob, or /summon invmod:gift_zombie. No active Versus match is needed to check basic entity creation. A Nexus-bound egg spawn tests additional binding and equipment behavior separately.

Minecraft 1.20.1: mob spawning and world generation

The corrected port reserves shared mob-color data before mob subclasses register their own data. This resolves the recorded spawn crashes and world-generation stalls caused by colliding Versus color data. The affected shared initialization can run outside a Versus match; disabling a team color or removing a catalyst is not the fix.

Use a corrected 1.20.1 build for your loader, restart client and server, and test both mob creation and newly generated terrain in a disposable world. Confirm that spawning completes and new chunks continue generating. Existing terrain alone does not exercise world generation. This correction does not claim to fix every slow world generation, missing spawn point or unrelated companion-mod error.

Update and diagnose safely

  1. Save and shut down normally; back up the complete world and instance before updating. Keep the Minecraft version and loader unchanged for this check.
  2. Replace the old Invasion Mod JAR with a matching corrected build on the server and clients. Keep only one Invasion Mod JAR in each mods folder, then restart; reloading a datapack cannot apply an initialization fix.
  3. If the same failure persists, retain the crash report and logs/latest.log, note the exact Minecraft/loader/mod builds and the action that triggered it. For a stall, retain the server log and watchdog report if one is produced. Reproduce in a separate test world before changing your main world's configuration.

A successful startup alone does not prove the spawn or world-generation path. Conversely, a blocked invasion purchase can be a normal Versus requirement or spawn-location constraint. Compare the error with the corrected source: 1.21.1 initialization correction and 1.20.1 initialization correction. These checks are a diagnosis procedure; no live-game test is claimed.

For the separate October 8 Skeleton catalog correction, see unique tiers, baby variants and prices.

Version history and evidence

The Changelog records published versions and publication dates from Modrinth, compared with CurseForge. It preserves build-specific notes and distinguishes publication from repository version-setting commits. Source milestones 1.6.0 and 2.4.0 are not treated as confirmed releases; Player Nexus belongs to published 3.0.0.

Sources: Modrinth versions, CurseForge files, snapshot version properties and 26.3 NeoForge port notes. For gameplay, continue with Getting Started.