Skip to content

Server Configuration & Setup Guide

HenryMM Gaming offers a suite of 5 distinct client-side modpacks. Because all included modifications run purely on the client side, every modpack is fully compatible with any standard Minecraft server that accepts vanilla or modded connections. You do not need to install additional server packs to play.

Disclaimer: The information provided in this guide serves as a general recommendation. For specific technical support regarding server platforms or individual plugins, please consult their respective official channels.



If you only plan to play casually with friends, setting up a dedicated server core may be unnecessary. Additional Mods allow you to host singleplayer worlds over the internet seamlessly:

  1. Download “e4mc” from Modrinth or CurseForge.
  2. Launch your singleplayer world.
  3. Open the pause menu (Esc) and select Open to LAN / Open to Internet.
  4. Adjust your desired game rules and confirm by clicking Open to Internet.
  5. Copy the connection address generated in your chat window.
  6. Share this address with your friends. Connected players must run the same Minecraft release version, though identical modpack setups are not required.

Choosing the right server core significantly impacts performance and stability:

  • High-Performance Spigot Forks: Paper and Purpur provide substantial performance enhancements over standard Spigot while retaining full compatibility with Bukkit/Spigot plugins.
  • Fabric Server Core: If you prefer a Fabric backend, you can install a native Fabric Server and complement it with server-side performance mods.
  • Hosting Options: Using Minecraft Realms is generally discouraged due to unconfigurable chat monitoring. If you require dedicated server hosting, third-party providers like BisectHosting, Nitrado or GPortal offer managed server slots.

Minecraft version 1.19.1 introduced player chat reporting managed by Mojang. Most multiplayer communities choose to disable chat signing to protect players from unfair global bans.

Status Indicators in HenryMM Gaming Modpacks

Section titled “Status Indicators in HenryMM Gaming Modpacks”

When connecting to a server, an icon in the lower-right corner of the chat input box indicates the current chat privacy state:

  • Minecraft 1.18.2 or older (or via ViaVersion): Displays optional. Chat reporting is completely disabled at the engine level.
  • Minecraft 1.19+:
    1. Server-side protection active: Displays disabled. Chat messages cannot be reported by any player.
    2. Standard configuration: Displays unknown until your first message is sent.
      • If enforce-secure-profile=true (default): Displays enabled. All messages are cryptographically signed and reportable.
      • If enforce-secure-profile=false (recommended): Displays optional. Modpack users’ messages remain unsigned and cannot be reported.
  • Realms Infrastructure: Displays realms. All chat traffic is logged and reportable.

To protect your player base, apply the settings relevant to your server architecture:

  • 1.19+ Server Backends: Set enforce-secure-profile=false in your server.properties file. This allows clients to join without forcing cryptographic message signatures.
  • Proxy Networks:
    • Velocity: Set force-key-authentication = false inside velocity.toml.
    • BungeeCord: Set enforce_secure_profile: false inside config.yml.
  • Paper / Purpur / Spigot Software: Install the FreedomChat plugin. Set rewrite-chat and send-prevents-chat-reports-to-client to true in its configuration file to ensure modpack clients receive full privacy confirmation (disabled).
  • Fabric / Forge / NeoForge Server Modpacks: Install No Chat Reports directly into the server’s mods folder.
  • LAN & World Host Sessions: Hosting directly with e4mc: Adding No Chat Reports to the host client protects all connected guests automatically.

Protocol translation plugins allow players using different client versions to join your server seamlessly, preventing downtime when new Minecraft updates release:

  • ViaVersion: Allows clients running newer game releases to connect to an older server core (e.g., joining a 1.19.2 server with a 1.19.3 client).
  • ViaBackwards: Allows clients running older game releases to connect to a newer server core (e.g., joining a 1.19.4 server with a 1.8 client).

Recommendation: On multi-server proxy setups, install ViaVersion and ViaBackwards on each individual backend sub-server rather than strictly on the proxy layer.


To allow Bedrock Edition players (mobile, console, Windows 10/11) to join your Java server, install GeyserMC. Keep in mind that mechanical differences between Java and Bedrock Edition may occasionally trigger false positives with aggressive anticheat plugins.


When drafting rules for allowed client modifications, formulate guidelines around gameplay behavior rather than specific mod names or arbitrary counts:

  • Avoid: “Only OptiFine is permitted.”
    • Better: “Client-side performance and graphic optimization modifications are permitted.” (Allows HenryMM Gaming modpacks without ambiguity).
  • Avoid: “Maximum limit of 15 mods allowed.”
    • Better: (Omit numerical mod limits entirely). (Mod counts are arbitrary and do not reflect client advantage or server impact).
  • Avoid: “Only Minimap Mod X allowed.”
    • Better: “Minimap mods are allowed, provided entity/player radar features remain disabled.”
  • Avoid: “Only Forge clients permitted.”
    • Better: (Focus strictly on prohibiting unfair behavior). (Discriminatory mod loader restrictions harm user flexibility).

To maintain server integrity and prevent client-side exploits:

  1. Keep server cores, mod loaders, and plugins routinely updated.
  2. Implement robust anticheat solutions for Paper/Spigot or Fabric/Quilt.
  3. Deploy crash prevention patches such as CrashExploitFixer.
  4. Utilize active moderation tools and staff spectating to maintain a fair playing environment.