Nexus UHC

 

Nexus UHC — Experimental Test Release

Nexus UHC is an experimental multiplayer UHC project featuring customizable matches, built-in survival bots, optional Ollama integration, firearms, special scenarios, cosmetics, and a persistent incremental mini-game.

This upload is a public test build. Features, balance, bot behavior, and compatibility are still being improved. Bugs and unfinished behavior may occur. Please back up your worlds before testing and report any problems with your logs and reproduction steps.

Requirements and installation

• Minecraft Java Edition 1.21.1
• NeoForge, tested with version 21.1.265
• Java 21
• Install the same Nexus UHC JAR on the server and every client.
• For dedicated servers, enable pvp=true in server.properties; Nexus manages the match’s PvP grace period itself.

This version does not support Fabric, Forge, or other Minecraft versions.

Nexus is designed for a server dedicated to UHC matches. It creates its own lobby and temporary match dimensions, so no separate map download is required.

Custom UHC matches

Prepare matches through a custom in-game interface rather than a chest inventory.

The host menu includes scenario search, categories, icons, detailed descriptions, favorites, active-scenario filters, presets, and match settings.

Configure match duration, starting border size, PvP timing, border movement, teams, and supported scenario settings. Operators and players granted the Nexus host permission can manage matches.

Core features include:

• A persistent lobby with glass that changes color beneath players’ feet.
• A separate arena with a new seed for each match.
• Dispersed starting positions, with teammates grouped together.
• Glass starting cages, temporary protection, and a common release.
• Configurable PvP grace periods and a shrinking world border.
• Ultra Hardcore health rules: food does not normally regenerate health during standard UHC matches. Golden apples and explicitly enabled healing scenarios provide recovery.
• Spectator support, elimination announcements, death messages, and match results.
• Victory celebrations, a separate podium area, and final rankings.
• Restoration of saved player inventories and relevant player state when returning.
• Cleanup of temporary match dimensions after the game.

Certain scenarios intentionally change normal UHC rules.

Built-in survival bots

Nexus includes its own server-controlled bots. No separate bot mod, external Minecraft accounts, or Ollama installation is required for native bot behavior.

Open /nexus bot as an authorized host to choose the number of bots and their difficulty.

The system supports a configured maximum of 200 bots. This is a limit, not a guarantee that every server can run that many smoothly.

Bots can:

• Join the lobby and appear in the player list.
• Use Minecraft profile skins when available.
• Participate in matches and teams.
• Collect resources and items.
• Mine and craft equipment.
• Use furnaces when required.
• Equip tools, weapons, and armor.
• Eat food and use golden apples.
• Walk, sprint, navigate locally, and react to nearby threats.
• Fight human players and opposing bots.
• Respect teammates, spectators, starting protection, and PvP restrictions.
• React to the border and attempt to move toward safer areas.

Difficulty changes aspects of reaction, combat, and survival behavior. Difficulty alone does not grant a free equipment kit; selected scenarios may still provide starting equipment.

Eliminated bots are removed rather than automatically returning to the lobby.

Bot AI remains experimental. Difficult terrain, unusual seeds, and scenario combinations can cause inefficient decisions or navigation problems. Bots are not guaranteed to reach full diamond equipment or behave like experienced human players.

Optional Ollama AI integration

For players who want to experiment with a local language model, Nexus includes optional Ollama integration.

The model provides strategic guidance. Native Minecraft code still handles movement, collisions, mining, crafting, combat, and rule enforcement.

In-game configuration

Open:

/nexus bot → Ollama / Local AI

The administrator can:

• Set the Ollama server address.
• Discover installed models.
• Select a model from the detected list.
• Configure request timing and timeouts.
• Enable or disable model guidance.
• Use Test Connection to request a real response from the selected model.
• Inspect connection results, latency, and activity information.

Ollama must already be installed and running. Nexus does not download models or start the Ollama service.

The connection is made from the Minecraft server, so the configured address must be reachable from that machine.

Shared planning instead of one request per bot

Nexus uses a shared planning system:

• Only one global request is in flight at a time.
• Bots are organized into groups according to their situation.
• The model returns bounded instructions for those groups.
• Native AI continues handling immediate actions between responses.

This avoids sending an independent model request for every bot.

The model can guide decisions such as gathering, mining, crafting, retreating, regrouping, attacking a valid target, or moving toward the center.

Context and fallback behavior

Nexus supplies information about relevant game rules, active scenarios, equipment, health, hunger, resources, threats, and border conditions.

A generated reference includes the scenario catalogue, weapons, ammunition, and supported game systems. Targeted lookups can retrieve additional information, including recipes from the server.

This is contextual guidance, not a model trained to understand every possible Minecraft mod or situation.

If Ollama is disabled, unavailable, too slow, or returns an invalid response, bots fall back to native behavior. The model cannot execute arbitrary server commands or freely create items.

Model quality and hardware affect response speed. Ollama integration does not guarantee perfect strategy or better server performance.

35 firearms and 16 ammunition types

The arsenal includes 35 original game weapons, with custom 3D models and different ammunition, magazines, firing rates, ranges, and reload times.

Weapon names:

Cobalt P9, Mistral .45, Viper 10, Titan .44, Volt 9, Nebula 9, Spectre .45, Comet 10, Ranger 5.56, Kestrel 5.56, Cyclone 5.45, Sentinel 7.62, Bastion 12, Breacher 12, Tempest 12, Atlas DMR, Orion 6.5, Raven Scout, Eclipse .338, Horizon .50, Aurora Compact, Falcon .45, Meridian 5.7, Pulse 5.7, Quasar 9, Dusk 4.6, Nomad 5.56, Zenith 6.8, Draco 7.62, Rampart 12, Cinder 20, Solstice DMR, Voyager Scout, Monolith .408, and Leviathan Support.

Features include:

• Left-click firing.
• Automatic fire for supported weapons.
• Right-click aiming.
• Scoped zoom and reticles on supported precision weapons.
• Reloading with R.
• Traveling projectiles and server-controlled collision checks.
• Recoil, spread, and movement-related accuracy changes.
• Custom weapon sounds audible at different distances.
• A compact ammunition display attached visually to the held weapon.
• Reconfigurable left/right leaning controls.

Weapon and ammunition crafting is enabled during matches only when an appropriate firearm scenario is active.

The included audio is original synthesized audio; this build does not include the previously discussed external soundpack.

Scenario catalogue

The build contains 242 selectable entries, including gameplay rules, starting kits, permanent effects, terrain variants, and special systems.

Players can consult the in-game scenario guide to read the active rules. Hosts can search the complete catalogue through the configuration interface.

Scenario families cover:

• Resource collection: CutClean, Timber, Timber+, TimberPVP, VeinMiner, Double Ores, TripleOres, FastSmelting, OreMagnet, and more.
• Mining risks and restrictions: Blood Diamond, Blood Gold, Blood Cycle, Goldless, Diamondless, OreLess, Barebones, Quadrant Balance, and MeetupOres.
• Combat and elimination effects: No Clean, No Cleanup, Timebomb, GraveRobbers, Golden Head, Kill Heal, Kill Strength, Kill Regen, Siphon, Rewarding Kill, and Rewarding Longshot.
• Equipment restrictions: Bowless, Shieldless, Pearlless, Totemless, Rodless, No Sword, No DiamondArmor, No Anvil, and No Enchant.
• Teams and social rules: UHC Loup-Garou, Kings, School, Market, Switch, Shared Health, Bonded Hearts, Team Inventory, Team Directions, FirstHitLove, and Love at First Sight.
• Information and identity: Anonymous, Identity Theft, Hidden Scenarios, Paranoia, Quadrant Paranoia, Sonar, Self Diagnosis, and Xenophobia.
• Terrain and dimensions: Amplified Terrain, Flatland, Big Crack, ChunkApocalypse, Void Mineshaft, Separates Worlds, MeetupWorld, Tier Progression, and Netheribus.
• Special rewards and events: Genie, Investments, OreJackpot, FlowerPower, GoneFishing, Loot Crates, Meteor Shower, and Gapple Roulette.
• Starting kits and permanent effects: equipment presets, Speed, Haste, Strength, Resistance, Night Vision, and numerous positive or negative effects.
• Time, weather, and pacing: permanent day/night variants, weather rules, Acid Rain, SkyHigh, Fast Border, Tiny World, and meetup-related rules.

Some rules use configurable Nexus adaptations rather than reproducing another server’s implementation exactly. Not every combination has been validated.

Firearm scenarios

• Gun Rush: start with a loaded Ranger and reserve ammunition.
• Pistols Only: pistol starting equipment and handgun restrictions.
• Snipers Only: precision starting equipment and weapon restrictions.
• Random Arsenal: a random loaded weapon and reserve ammunition.
• Ammo Supply: periodic ammunition for the held weapon.
• Quick Reload: shorter reload times.
• Arsenal Crafting: enable firearm and ammunition recipes without requiring a starting weapon kit.

Spectator-controlled Roulette

Roulette is a scenario controlled by a designated host.

The selected roulette master becomes a spectator instead of a normal fighter. They can select a participant manually or randomly, teleport to observe them, and launch a bonus-or-penalty roll.

The selected player receives a notification.

An animated, case-opening-style card strip appears at the bottom of the screen while the master can still observe the game. The server determines and applies the result.

The catalogue contains 85 outcomes, divided into four rarity tiers:

The legendary probability is shared across legendary outcomes; it is not the probability of each individual legendary item.

Roulette includes synchronized ticking sounds, a reveal sound, target validation, and a cooldown. Ordinary players cannot operate the roulette controls.

Nexus Skyboxes

Enable Nexus Skyboxes to introduce supply crates dropping at configurable intervals.

Opening a crate launches five stacked reward roulettes and requires 40 seconds of exposure.

The system includes:

• A custom crate model.
• Opening animations and announcements.
• Interruption handling when the opener leaves, dies, or disconnects.
• Preserved crate rewards after an interrupted opening.
• Tracking of reward beneficiaries until elimination.

In this build, tracking uses both the scoreboard and a compass. The scoreboard-only replacement belongs to later development.

Nexus Astral — persistent incremental mini-game

Nexus Astral gives players something to progress while waiting in the lobby or spectating a match.

It is available to ordinary players and spectators through:

• I, reconfigurable in controls.
• Escape → Nexus Astral
• /nexus clicker
• /nexus incremental

Click the central core to generate energy, purchase producers, research upgrades, complete achievements, and ascend for permanent progression.

This build includes:

• 12 producer families.
• Purchases of 1, 10, 100, or a bounded MAX amount.
• Passive production while connected, even with the interface closed.
• Four research paths, each with 25 levels.
• Ascension/prestige progression.
• 197 achievements.
• One-time achievement rewards granting cosmetic coins.
• Individual saves associated with each player’s UUID.
• Responsive layouts for smaller windows.

Version 2.1.1 also includes reduced, capped offline production. Its removal is part of later development and is not included in this upload.

The mini-game does not pause the world. Living participants remain exposed to the match while using it.

Coins and cosmetics

Human victories award coins, and Nexus Astral achievements provide additional cosmetic rewards.

The lobby shop contains 48 cosmetic variants across four families. Purchases and selections are saved per player.

A lobby leaderboard and top-three skin statues are implemented, but their display currently has reported issues being addressed in development.

Cosmetic progression does not provide combat equipment.

Custom interface and accessibility

Nexus includes custom interfaces for match preparation, scenarios, bots, Ollama, roulette, cosmetics, and the incremental game.

Additional features include:

• A custom match HUD.
• A custom TAB player list with health, kills, and latency information.
• Overhead player health displays.
• A compact F3 display with expanded diagnostics.
• Scenario activation announcements.
• Adjustable text size.
• Higher-contrast and reduced-animation options.
• A mod-specific French/English language setting.

Some older messages may still require translation or presentation improvements.

Administration and permissions

Operators can manage matches. Permission integrations can also grant host access through:

modded_uhc.host

The mod uses NeoForge’s PermissionAPI. LuckPerms is optional and is not bundled.

Administrative features include match preparation, bot management, roulette control, PvP controls, border controls, timing settings, and revive tools.

Permissions and gameplay actions are checked on the server.

Testing status and known limitations

This is an experimental test release, not a finished competitive platform.

Important limitations include:

• Bot navigation and long-term survival remain under development.
• Large bot populations can be demanding.
• Ollama quality and latency depend on the selected model and hardware.
• Some interfaces and visual effects have reported issues.
• Leaderboard and statue rendering require further fixes.
• Some scenario combinations can conflict or produce unexpected behavior.
• Compatibility with unrelated rendering, networking, and gameplay mods is not guaranteed.
• Long-term incremental balance and large numbers of simultaneous users have not been fully measured.

developped by n2styles