Server Environment: mustard.gorgarath.net

This document describes the hosting environment for this Minecraft server, including the Pterodactyl configuration, resource allocations, container image, storage mounts, and network configuration.

This document reflects the current deployment environment for the Mustard Testing Server and serves as the reference for its Pterodactyl configuration.

Server startup arguments, JVM tuning, and Java runtime configuration are documented separately in server-startup.md.

Node hardware details and Pterodactyl infrastructure information are documented separately in infrastructure.md and the corresponding node documentation.

Document Scope

This document describes:

• The Pterodactyl server configuration.
• Resource allocations.
• Container image selection.
• NeoForge egg configuration.
• Storage mounts.
• Network configuration.
• Backup configuration.

It does not document:

• JVM startup arguments (documented in server-startup.md).
• Host hardware details (documented in infrastructure.md and node documentation).
• Pterodactyl panel or Wings versions (documented in infrastructure.md).
• Node hardware configuration (documented in the corresponding node documentation).
• Minecraft gameplay configuration.
• NeoForge or mod configuration.

Those topics are documented separately where appropriate.

Server Overview

Operational procedures, startup configuration, backup configuration, and world pre-generation recommendations are documented separately in the related documentation listed later in this document.

Pterodactyl Deployment

This server is deployed using a self-hosted Pterodactyl installation running on the pterodactyl Wings node.

Current deployment:

Platform:
Pterodactyl

Wings Node:
`pterodactyl`

The server may be migrated to another Wings node in the future. If migration occurs, this document should be updated with the new node assignment.

Node-specific hardware information is documented separately in the corresponding node documentation.

Egg Configuration

The server uses a community-maintained NeoForge egg from the Pterodactyl Eggs repository. The egg has not been modified or customized for this server.

Current egg:

The startup command supplied by the egg has been overridden with a custom JVM configuration documented in server-startup.md.

Container Image

Configured container image:

ghcr.io/ptero-eggs/yolks:java_21

This image provides the container environment and Java runtime used by the server.

The Java runtime version and JVM configuration are documented in server-startup.md.

When changing Java versions, the container image and JVM arguments should be reviewed together.

Resource Allocation

Configured Pterodactyl resource limits:

CPU Allocation

CPU Limit

The CPU limit is configured as:

0

No Pterodactyl CPU quota limit is enforced.

CPU availability is instead restricted through CPU pinning.

CPU Pinning

The server is pinned to the following logical CPU threads:

0,2,4,6,8,16,18,20,22,24

On the current host, these logical CPUs correspond to five physical CPU cores on a single CPU socket and their corresponding SMT sibling threads. See the node documentation for the hardware topology source.

The configured topology mapping is:

This configuration allows the server workload to remain localized to a single CPU socket while utilizing both logical threads of each assigned physical core.

The CPU numbering and topology are specific to the current host hardware. If the server is migrated to another node, CPU pinning should be reviewed.

Memory Allocation

The configured memory allocation is:

32768 MiB

The Java heap allocation documented in server-startup.md is configured as 20 GB.

The remaining memory is reserved for:

• Java non-heap memory.
• Native libraries.
• NeoForge overhead.
• Mod libraries.
• Operating system and filesystem cache.

The Pterodactyl memory allocation should remain higher than the configured Java heap size.

Swap Allocation

Swap is disabled:

0 MiB

Disabling swap helps prevent severe performance degradation caused by Java memory being paged to disk.

OOM Killer

The Pterodactyl OOM Killer setting is disabled.

This prevents Pterodactyl from automatically terminating the server when memory usage exceeds the allocation.

Adequate memory allocation and monitoring are therefore important.

Storage Configuration

Container Storage

The server operates within the standard Pterodactyl container filesystem:

/home/container/

Files referenced by startup arguments are relative to this working directory.

Mounted Storage

The server currently uses the following mount:

Purpose:

This mount stores SimpleBackups data outside of the container filesystem.

This prevents Pterodactyl backups from recursively including SimpleBackups archives while allowing SimpleBackups data to persist independently.

Networking

Network configuration:

The server uses DNS SRV records so players can connect using only the server hostname.

Simple Voice Chat uses UDP.

Backup Configuration

Pterodactyl Backups

Configured backup limit:

10

Backups are currently created manually during the testing phase. Automatic backups will be configured for the production server.

The configured backup storage location is:

/mnt/backups/wings/

SimpleBackups

SimpleBackups data is stored using the external mount documented above.

This separation prevents SimpleBackups archives from being included recursively in Pterodactyl backup operations.

Security Configuration

Current deployment characteristics:

• Private server.
• Whitelist enabled.
• No reverse proxy.
• Self-hosted infrastructure.
• Trusted player environment.

Related Documentation

The following documents provide additional information about this server and the infrastructure on which it runs.

Future Review Considerations

Review this document whenever any of the following change:

• Pterodactyl server allocation.
• Wings node assignment.
• Egg version.
• Container image.
• Minecraft version.
• NeoForge version.
• Resource limits.
• Storage mounts.
• Network configuration.
• Backup configuration.

Change History

2026-08-03

• Updated the Related Documentation section for improved clarity and organization.
• Updated document references to use the server- prefix where appropriate.
• Removed the (planned) notation from server-configuration.md and added the documentation link.
• Corrected broken links to documents outside of the server directory.

2026-08-03

Reviewed and refined the server environment documentation.

Updated the document structure to match the current server documentation standard and clarified Pterodactyl configuration details, resource allocation, storage mounts, network configuration, and related documentation references.

2026-07-26

Initial documentation created for the current Pterodactyl deployment configuration.

This document records the deployed server environment and does not cover historical hosting configurations.