Mustard Modpack

This document provides an operational overview of the Mustard modpack, its design direction, compatibility layers, and canonical source boundaries. It is not a complete mod inventory or a replacement for source-specific maintenance records.

Document Scope

This document covers:

The Mustard server identity and modpack role.
The high-level gameplay and testing direction.
The maintained compatibility architecture.
Current client-pack compatibility components and deployment roles.
The boundary between operational documentation and maintained project source.

Detailed fix implementations, build procedures, artifact identities, and validation semantics remain with the maintained source in minecraft-projects.

Server Identity

Item	Value
Server	Mustard Testing Server
Minecraft	1.21.1
Mod loader	NeoForge
Role	Testing the eventual long-term gameplay environment

server-environment.md remains authoritative for the deployed NeoForge point version and hosting environment.

Design Emphasis

Mustard is designed around:

Create-heavy automation and large contraptions.
Aeronautics and vehicle capability testing.
Exploration.
Long-term world stability.
Eventual Survival progression and balance testing.

The server is currently in a deliberate Creative testing phase while large Create and Aeronautics systems are built and exercised. The current and target game-mode lifecycle is maintained in server-configuration.md.

Target Long-Term World

Mustard is a testing and compatibility environment for an eventual long-lived Survival world rather than the final production world itself.

The target world is intended to emphasize:

Long-term Survival play with progression that remains meaningful over time.
Create-centered automation, transport, factories, and large infrastructure.
Aeronautics and other vehicle systems as practical parts of exploration and logistics rather than novelty features.
Large, meaningful oceans that encourage ship and submarine use before players simply bypass them with late-game flight.
Exploration across multiple dimensions without making the Overworld feel disposable.
Large permanent bases and infrastructure projects that can grow over months or years of play.
Support for different player interests, including engineering, building, exploration, farming, magic, transport, and resource gathering.
Economy and progression systems that reward normal play without allowing easy shortcuts to undermine the rest of the pack.
Stability and compatibility sufficient for keeping the same world for the long term rather than routinely resetting because of mod or world-generation issues.

Mustard is used to test the mods, configuration, compatibility layers, world generation, progression, and server rules needed to reach these goals before the production world is created.

Maintained Compatibility Architecture

Mustard combines downloaded upstream mods with several maintained compatibility layers:

Layer	Responsibility	Canonical source
Downloaded mods	Upstream runtime dependencies	Deployment artifacts outside Git
Curated mod configuration	Intentional Mustard configuration retained across rebuilds	Mustard config source
mustard-fixes	Server datapack compatibility and data corrections	mustard-fixes source
mustard-rules	Maintained server rule enforcement	mustard-rules source
mustard-tree-fixes	Dynamic Trees compatibility overrides	TreePack source
Server compatibility projects	Server-only and both-sides Java compatibility work	Server compatibility source
Client compatibility projects	Client-only Java compatibility work	Client compatibility source

Implementation details and individual fix inventories remain in the linked source collection READMEs.

Current Client-pack Compatibility Components

The owner-confirmed client pack currently uses:

Artifact	Deployment role
mustard-immersive-weathering-client-compat-1.0.1.jar	Client-only
mustard-sable-udp-compat-1.0.0.jar	Client-only
mustard-mpuc-ui-compat-1.0.0.jar	Client-only
mustard-powergrid-tfmg-compat-1.0.0.jar	Both-sides/common

PowerGrid/TFMG uses the same byte-identical JAR on the client and dedicated server. Additional Mustard-owned server-only compatibility projects exist and are maintained in minecraft-projects; their implementation and validation records are not duplicated here.

Canonical Source

The canonical maintained project area is:

https://github.com/Gorgarath/minecraft-projects/tree/main/servers/mustard

Project source, curated configuration, datapacks, TreePacks, compatibility projects, generators, and source-specific tools live there. This repository owns documentation for the deployed environment and operational workflow.

Built JARs, downloaded mods, deployed datapacks, runtime worlds, generated data, logs, and backups are operational artifacts rather than preferred authoring source.

Document	Purpose
server-configuration.md	Current testing configuration and future gameplay lifecycle
server-environment.md	Pterodactyl environment and current deployed platform
server-startup.md	Java runtime and startup configuration
disabled-mods.md	Mods intentionally excluded from the active environment
mod-management.md	Normal mod and compatibility-artifact maintenance
server-management.md	Routine server maintenance workflow
server-backup-strategy.md	Backup layers, source boundaries, and recovery considerations
chunky-pregeneration-guide.md	World pregeneration guidance

Change History

2026-10-10

Removed the resolved NeoForge point-version discrepancy and restored server-environment.md as the sole authority for the deployed loader version.
Added the accepted Mustard MPUC UI compatibility shim to the current client-pack compatibility components.

2026-10-09

Added the Target Long-Term World section describing the intended production-world goals and Mustard's role in testing and preparing for them.

2026-09-25

Added the Mustard modpack overview, compatibility architecture, source boundary, current client compatibility roles, and explicit NeoForge point-version discrepancy.