Server Configuration: `mustard.gorgarath.net`

This document describes non-default server and game-related configuration changes for this server.

This document focuses on intentional configuration changes and the reasoning behind them. Default configuration values are not documented unless they are relevant to a decision.

Document Scope

This document covers:

Intentional non-default server and game-related configuration changes.
The current values of those settings where relevant.
The reasoning behind configuration decisions.
Review conditions for settings that may need to change later.

It does not document Pterodactyl deployment settings, JVM startup arguments, the complete mod inventory, or default values that are not relevant to a documented decision.

Configuration Philosophy

This server is designed as a long-lived heavily modded NeoForge world emphasizing exploration, stability, and sustainable progression.

Configuration changes are made with the following goals:

Maintain long-term world stability.
Reduce unnecessary server load.
Preserve intended modpack gameplay.
Avoid changes that significantly alter the intended player experience.

Testing Configuration

This server is used for testing before production deployment or for evaluating configuration changes. Settings documented elsewhere in this file may intentionally differ from the expected production configuration.

Review configuration changes before production deployment.

Server Configuration

All configuration file paths in this document are relative to the Pterodactyl container working directory:

/home/container/

Server Configuration File

Configuration file:

server.properties

Setting	Default	Current	Reason
allow-flight	false	true	Allows legitimate flight-related behavior without the server disconnecting players for flight checks.
difficulty	easy	normal	Selected to provide a reasonable survival challenge while maintaining the server's focus on exploration, construction, and long-term world development.
enforce-whitelist	false	true	Ensures the whitelist is enforced when enabled.
force-gamemode	false	false	Deliberately disabled during temporary Create and Aeronautics testing so operators can switch between Creative and Survival. The intended future normal-play value is `true`.
gamemode	survival	creative	Deliberately set to Creative temporarily so large Create and Aeronautics contraptions can be built and tested without resource gathering. The intended future normal-play value is `survival`.
motd	A Minecraft Server	Mustard Testing Server	Provides the server name in the vanilla MOTD field. The displayed MOTD is currently overridden by miniMOTD.
simulation-distance	10	8	Reduces server workload by limiting entity and block simulation distance.
sync-chunk-writes	true	false	Improves write performance at the cost of reduced protection against data loss during unexpected shutdowns.
view-distance	10	8	Reduces server workload while maintaining acceptable player visibility.
white-list	false	true	Enables the server whitelist.

Game Mode Lifecycle

Mustard currently uses gamemode=creative and force-gamemode=false as a deliberate temporary testing configuration while large-scale Create and Aeronautics construction and capability testing continues.

The intended normal-play configuration is:

gamemode=survival
force-gamemode=true

Survival is required to evaluate actual progression, resource acquisition, economy and balance, gameplay pacing, and the practical viability of Create and Aeronautics systems under normal play. The switch is planned for a future world rebuild after the current testing phase is sufficiently mature; no specific rebuild or date is committed.

Maintained Mod Configuration

Mustard has a curated set of intentionally retained mod configuration in Git:

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

Only the reviewed Mustard configuration set is maintained there. Configuration outside that set normally regenerates from mod defaults and is not implicitly source-controlled.

The curated set covers selected performance and compatibility behavior, backup policy, gameplay and presentation settings, voice chat, and server-specific identities. Detailed file-level values, preservation notes, and validation limits remain in the canonical configuration README.

Future Review

Review these settings if:

The installed mods, plugins, or extensions change significantly.
Mods are updated.
The runtime environment changes.
Server hardware changes.
Performance issues appear.
A new game instance or map is created.
Default configuration files change after updates.

Document	Purpose
`modpack.md`	Modpack role and compatibility architecture
`mod-management.md`	Normal mod and compatibility-artifact maintenance
`server-management.md`	Routine server maintenance workflow
`server-backup-strategy.md`	Backup layers and recovery boundaries
`server-environment.md`	Server deployment configuration, resources, storage, and environment settings
`server-startup.md`	JVM arguments, Java runtime configuration, and startup settings
`disabled-mods.md`	Mods intentionally disabled and the reasons they are disabled

Change History

2026-09-25

Reaffirmed the current Creative and unforced testing state, retained Survival with forced game mode as the intended future normal-play configuration, and clarified the distinction during cleanup of an older Mustard backup.
Replaced the stale empty mod-configuration section with the curated Git-maintained configuration model and linked the new operational documents.

2026-09-19

Standardized document structure and Markdown style to match repository conventions.
Removed leftover template placeholder content from the live Mustard configuration document and clarified how future mod-specific configuration changes should be recorded.

Server Configuration: mustard.gorgarath.net