iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Godlike.Host offers modded Minecraft server hosting with one-click modpacks, a built-in mod installer and up to three free backups a day.
To host BigChadGuys+ without Cobblemon, install the pack’s dedicated server archive—not the regular client download—then launch it with the supplied Fabric scripts. For the current BCG+ NC 2.14.1 release, the matching environment is Minecraft 1.20.1, Fabric 0.17.3 and 301 mods. Allocate at least 4 GB of RAM for a dedicated server, add 1 GB for each player beyond the first two, and have every player install the same client version.
This guide covers downloading and checking the correct files, launching on Windows or macOS/Linux, sizing memory, allowing LAN or internet connections, pre-generating terrain, and moving the server to a managed host.
What BigChadGuys+ Non-Cobblemon includes
BigChadGuys Plus (Non Cobblemon!), commonly abbreviated BCG+ NC, is a Fabric modpack for Minecraft 1.20.1. Its catalogue describes a cozy adventure experience with built-in shaders, multiplayer features, quests, recipes, exploration, Vanilla+ content and technology mods. CurseForge lists BCG+ NC 2.14.1 as the main file and a separate server-files entry. The catalogue snapshot reports 297,482 downloads and an update dated October 30, 2025; those figures can change as the project receives new releases.
A modpack is a matched client-and-server system. The server must use the server archive for the exact pack version, while each player’s launcher must use the corresponding client profile. Mixing releases, Fabric versions or mod lists can produce missing-mod errors, failed handshakes or a world that behaves differently for different players.
#1 Best Overall
Prerequisites and a sizing decision
Software and account requirements
- A legal Minecraft Java Edition installation capable of running version 1.20.1.
- The BCG+ NC client profile for every player, with the same release number as the server.
- The dedicated server archive downloaded from the pack’s Files page.
- A computer or managed host that can run the supplied Fabric server launcher and scripts.
- Permission to create a folder, run a Java server process and allow it through the operating system firewall.
The hosting example in the project’s instructions uses a Java 17 runtime. On a managed service, select that provider’s Java 17 option when available; on a home machine, use a Java runtime supported by the supplied Fabric launcher and verify that the startup script points to it.
How much RAM to assign
The project’s official guidance recommends a minimum of 4 GB for a dedicated server. After the first two players, add 1 GB for every additional player. The documented examples are:
| Players online | Recommended server RAM | Calculation |
|---|---|---|
| 1–2 | 4 GB | Minimum allocation |
| 4 | 6 GB | 4 GB + 1 GB for each of two players beyond the first two |
| 6 | 8 GB | 4 GB + 1 GB for each of four players beyond the first two |
These are allocation recommendations, not a guarantee of a particular frame rate or tick rate. Leave memory for the operating system and other applications. If the host computer has only 4 GB total, it cannot safely dedicate all 4 GB to Minecraft; close other programs or choose a larger machine.
Download the correct BCG+ NC server archive
The most common setup failure is downloading the client archive. Follow this path on the pack’s CurseForge project page:
- Open the project’s Files page.
- Select the BCG+ NC version you intend to run, such as 2.14.1.
- Open Additional Files.
- Choose the entry named Server Files.
- Download the file labeled BCG+ NC 2.14.1 Server Files (or the equivalent version you selected).
The official FAQ specifically warns against downloading the ordinary BigChadGuys Plus [Version].zip client file. The server archive is a separate download and is the one that contains the launcher, libraries and server-side layout.
Verify the archive before you run it
Extract the ZIP into a new, dedicated server folder. A correct archive should contain these four directories:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesconfigmodslibrariesresourcepacks
It should also contain these files:
fabric-server-launch.jarserver.jarstart.batstart.sh
If the extracted download contains only a config directory and overrides.json, you have the client archive. Delete or move that folder, return to Additional Files, and download the entry explicitly marked Server Files. Do not try to turn the client ZIP into a server by uploading its contents blindly.
Set up a self-hosted server
Windows
- Place the extracted server folder somewhere with a short, stable path, such as a dedicated Minecraft directory. Avoid moving individual files out of the folder.
- Open
start.batin a text editor. Find the Java memory option containing-Xmx4G. - Change the value to the allocation you selected. For example, a six-player target based on the project’s guideline would use
-Xmx8G. Keep theGsuffix and do not allocate more RAM than the computer can spare. - Save the file without changing its
.batextension. - Double-click
start.batto launch the server. A command window may open and close on the first run while the server creates its files.
If the first run stops because the Minecraft EULA has not been accepted, close the window, open eula.txt, change the acceptance setting as instructed in that file, save it, and run start.bat again. Only accept the EULA if you agree to its terms.
macOS or Linux
- Extract the archive into its own directory and confirm that
start.sh, both JAR files and all four directories are present. - Open
start.shin a text editor and adjust the existing-Xmx4Gvalue to the RAM target you calculated. - Run the matching shell startup file from a terminal in that directory. If the operating system reports that the script is not executable, grant execute permission, then run it again.
- Complete the EULA step in
eula.txtif the first launch stops for that reason.
Keep the server process running while players connect. To stop it safely, use the server console’s normal stop command rather than closing the terminal abruptly; this gives Minecraft time to save the world.
Keep client and server versions identical
Install BCG+ NC 2.14.1 on the server and on every client, or use another single release consistently. The selected catalogue file identifies Minecraft 1.20.1, Fabric 0.17.3 and 301 mods. If a player updates the client while the server remains on an older release, have that player return to the server’s profile or update the server and all clients together.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
Let players connect
Players on the same Wi-Fi
People on the same home network can connect without changing the router. Start the server, find the host computer’s local address using the operating system’s network information, and have the other player enter that address in Minecraft’s multiplayer screen. The host’s firewall may still ask whether Java can accept private-network connections; allow the server process on the private network you trust.
Players connecting over the internet
Remote players need a route to the server. The project FAQ identifies two approaches:
- Router port forwarding: forward the Minecraft server port from the router to the computer running the server, then give friends the public address and port. Reserve the host computer’s local address if your router supports it so the forwarding rule does not break after a reboot. Restrict the rule to the required port and keep the server software updated.
- A tunnel: use a service such as ngrok or Cloudflare Zero Trust when you cannot change the router. The FAQ notes that ngrok is free up to 1 GB of bandwidth. It describes Cloudflare Zero Trust as free but requiring payment details and client software. Tunnel addresses and connection steps can vary, so follow the service’s current instructions.
Do not publish your public address in an open forum. Give it only to people you trust, and turn off forwarding or the tunnel when the server is not in use.
Connection checklist
- Confirm the server console has finished loading before a player tries to join.
- Check that everyone is using the same BCG+ NC release, Minecraft version and Fabric profile.
- Verify the host firewall permits Java on the intended network.
- For internet play, confirm the router rule points to the correct local computer, or confirm the tunnel client is running.
- Ask a remote player to use the public address or tunnel address, not the host’s private Wi-Fi address.
Pre-generate terrain with Chunky
Exploration can trigger heavy chunk generation, especially when several players travel in different directions. The official FAQ recommends Chunky to generate terrain before players explore it. Run these commands in the server console:
Recommended Free Tools
- Set the desired radius:
chunky radius 1000 - Start generation:
chunky start
Generation can take substantial CPU, memory and disk time. Perform it before inviting players, or during a maintenance window. To interrupt the process, use chunky pause to pause it or chunky cancel to stop it. Let the server finish saving before shutting down.
Rank #4
Move the pack to managed hosting
A managed host can remove the need to keep a home computer online and can provide a web panel, but it must support custom Fabric files. The project’s instructions describe this general migration:
- Create the server instance with the provider and select the Java version required by its current instructions. The project’s example uses Java 17.
- Extract the official BCG+ NC server archive locally.
- Upload the extracted folders, JAR files and startup-related files by FTP or the provider’s file manager. Preserve the directory structure.
- Configure the provider to launch the custom Fabric JAR rather than a stock server type.
- Start the instance and watch the console for missing files, Java errors or mod-loading failures.
Example panel workflow
The FAQ gives BisectHosting as an example, not as a universal interface. In that example, operators rename fabric-server-launch.jar to customjava17.jar, open the panel’s JAR menu, choose Custom, and enable Custom Java 17. Panels change over time, so verify the provider’s current naming and Java-selection instructions before uploading or renaming anything.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Do not assume that a provider’s one-click Fabric template contains this exact modpack. The server files, mod list and configuration must match the clients. If the host does not allow custom JAR uploads or FTP access, it may not be suitable for BCG+ NC.
Self-hosting versus managed hosting
The right choice depends on whether you value direct control or reduced maintenance. The project documentation establishes the following practical differences; it does not state current provider prices or uptime guarantees.
| Decision area | Self-hosted computer | Managed host |
|---|---|---|
| Files and Java | Full control of folders, scripts, Java runtime and backups. | Control depends on whether the provider permits custom Fabric JARs, FTP and Java selection. |
| Network setup | You handle firewall rules, router forwarding or a tunnel. | The provider normally supplies a public endpoint; you still configure the server and access rules in its panel. |
| Recurring cost | No hosting price is stated; you provide the computer, electricity and internet connection. | No current price is stated in the project documentation; check the provider for region, plan and billing terms. |
| Backups and uptime | You are responsible for scheduled backups, recovery and keeping the machine online. | Backup tools and uptime policies vary by provider and must be checked before purchase. |
| Scaling RAM | Increase the -Xmx value only within the physical machine’s available memory. |
Choose a plan with enough memory for the player count, then change plans if the provider allows it. |
| Custom launch support | The supplied start.bat or start.sh runs directly. |
The provider must support a custom Fabric launcher and the correct Java version. |
Backups, updates and routine operation
Before changing the pack
- Stop the server cleanly and copy the world directory and configuration files to a separate location.
- Record the exact BCG+ NC version, Minecraft version, Fabric version and RAM setting.
- Install a new release in a separate folder first instead of overwriting a working installation.
- Have every player switch to the new client profile only after the server has started successfully.
During normal play
- Watch the console after startup for errors before sharing the address.
- Keep free disk space for world growth, logs and pre-generated chunks.
- Run backups when no one is building or exploring, and test that a backup can actually be restored.
- Stop the server before moving files, changing the modpack or editing configuration.
Troubleshooting common failures
The server window closes immediately
Run the script from a terminal or command prompt so the error remains visible. Check that Java is installed and that the script can find it. Confirm that the archive contains fabric-server-launch.jar, server.jar and the libraries directory. If the files are missing, re-download the dedicated Server Files archive.
The download has only config and overrides.json
This is the documented sign of a client archive. Do not upload it as a server. Return to the pack’s Files page, open Additional Files and select the version-specific Server Files entry.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe server reports an EULA problem
Stop the process, open eula.txt, follow the acceptance instruction in that file, save it and launch again. If the file is regenerated, check that you edited it in the same directory as the startup script.
Players receive a mod or version mismatch
Compare the server release with each client profile. For the documented release, check Minecraft 1.20.1, Fabric 0.17.3 and the 301-mod set. A player on a different BCG+ NC release must switch profiles or wait until the server is upgraded and tested.
The server runs out of memory or becomes unstable
Check the -Xmx value against the player count and the computer’s total RAM. Start with the project’s 4 GB minimum and add 1 GB per player after the first two. Do not allocate all system memory; close competing applications, reduce simultaneous exploration and consider a larger machine if the workload remains above the available resources.
Friends cannot connect from outside the house
Verify that the server is running, the firewall allows Java, and the router forwarding rule targets the host computer’s current local address. Remote players must use the public endpoint, not the private Wi-Fi address. If router access is unavailable, run and configure a tunnel client, then share the tunnel endpoint.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Chunky is using too many resources
Pause it with chunky pause while players are online, or stop it with chunky cancel. Resume or restart during a maintenance period and monitor disk space as the radius is generated.
A managed host starts the wrong server
Confirm that all extracted folders and both JAR files were uploaded, then select the custom Fabric launcher in the provider panel. Follow the host’s current Java instructions; the documented BisectHosting example requires the renamed customjava17.jar and the Custom Java 17 option, but another provider may use different labels.
Quick Recap
Final launch checklist
- Download the version-specific Server Files archive, not the client ZIP.
- Verify
config,mods,libraries,resourcepacks, both JAR files and both startup scripts. - Set
-Xmxto at least 4 GB, adding 1 GB for each player beyond two. - Run the matching startup script and complete the EULA file if prompted.
- Install the identical BCG+ NC client release for every player.
- Use local networking for same-Wi-Fi play; configure forwarding or a tunnel for remote players.
- Pre-generate a suitable area with
chunky radius 1000andchunky startif exploration causes avoidable lag. - Back up the world before updates and confirm that any managed host supports custom Fabric JARs and the required Java version.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
