Build the server from the full Better MC [FABRIC] BMC2 Server Pack for Minecraft 1.20.1, not the small launcher manifest. Use 64-bit Java 17, allocate at least 6GB of memory (8–10GB is the practical target for five or more players), keep the files on an SSD, and make every client use the identical pack version and mod list. The steps below cover installation, hosting choices, networking, and lag fixes.
Running a modpack with friends? Godlike.Host offers modded Minecraft server hosting with one-click modpacks (CurseForge, FTB, Technic) and free DDoS protection.
What a BMC2 server is
Better MC [FABRIC] BMC2 is LunaPixelStudios’ Fabric modpack for Minecraft 1.20.1. The pack combines more than 280 mods with overhauled world generation, shader support, new bosses and mobs, hundreds of dungeons and structures, Waystones, XP Storage, Xaero’s Minimap, and more than 100 quests. CurseForge showed 2,155,924 downloads and a January 25, 2026 update when this guide was prepared. The listed release is BMC2 [FABRIC] 1.20.1 v40, with a separate BMC2 Server Pack v40.
As an Amazon Associate I earn from qualifying purchases.
Fabric is important: a Forge server or a different Better MC edition will not accept this pack’s clients. Minecraft also displays the notice that the project is not an official Minecraft product and is not approved by or associated with Mojang or Microsoft.
Choose how the server will run
Your first decision is where the server process lives. The three practical models have different costs, availability, and responsibilities.
#1 Best Overall
| Model | Up-front and recurring cost | Always online? | Technical effort | Control and capacity | Network work |
|---|---|---|---|---|---|
| Managed hosting | Monthly fee set by the provider; plans and promotions change | Usually, while the subscription is active | Lowest; a control panel or one-click installer handles much of the setup | Provider limits CPU, memory, storage, and file access by plan | Usually no home-router port forwarding; the provider supplies an address and port |
| Self-hosting | No hosting subscription, but you provide hardware, electricity, and storage | Only while your machine and server are running | Highest; Java, scripts, firewall rules, backups, and updates are your responsibility | Maximum control over files, mods, backups, and operating-system tuning | Usually requires forwarding TCP 25565 and allowing Java through the firewall |
| LAN hosting | No recurring server bill | No; the world is available only while the host is playing | Lowest for same-network play | Host hardware determines the experience; remote access is not automatic | Players on the same network can connect without exposing the server to the internet |
When managed hosting makes sense
Choose a managed provider when the world must remain available while the owner is offline or nobody wants to administer a computer. The researched guide identifies BisectHosting as LunaPixelStudios’ official hosting partner and says it offers one-click Better MC installation. Select a plan with at least the memory listed in the requirements table, confirm that the current offering supports Fabric 1.20.1, and check the provider’s current price, renewal terms, storage, CPU limits, backup policy, and panel access before paying. Other providers can work, but they must support Fabric and provide comparable memory and CPU headroom.
When self-hosting makes sense
Self-hosting is the best fit if you want direct access to the world, configuration, logs, and mods and already own a suitable computer. It avoids a monthly hosting bill, but you must keep the machine powered on, secure the firewall, forward the port, create backups, and diagnose crashes or slow ticks.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →When LAN is enough
LAN is ideal for a household or local event. Start the server on the player’s computer and keep the game available only during that session. It avoids internet exposure, but friends outside the same network cannot join without additional networking work.
Hardware and software requirements
| Component | Baseline in the configuration guidance | Practical advice |
|---|---|---|
| Java | 64-bit Java 17 | Install the 64-bit build and verify that the command line uses it, rather than an older Java on your path. |
| Server memory | 6GB allocated | Use 8–10GB for five or more players; leave enough physical memory for the operating system and other services. |
| CPU | At least 4 cores | Six or more cores provide more headroom for world generation, mod logic, and simultaneous players. |
| Storage | 15GB free space | An SSD is strongly preferable. The pack, logs, backups, and an expanding world all need room beyond the initial installation. |
| Network | Stable connection | Upload capacity and consistent latency matter when several remote players are exploring different areas. |
If your computer accepts DDR4 memory, a 16GB DDR4 kit is a practical upgrade to search for; verify the motherboard’s supported type and capacity before buying. A 16GB machine can run the server allocation above while retaining memory for the operating system, but larger worlds, shaders, browsers, or other services may require more physical RAM.
Install the BMC2 server pack manually
These steps apply to a Windows, Linux, or macOS machine that will run the server process.
- Select the exact pack. In the CurseForge Files area, choose Better MC [FABRIC] BMC2 for Minecraft 1.20.1 and download the matching BMC2 Server Pack v40. The roughly 50MB launcher manifest is intended for the CurseForge app; it is not the complete manual-install server bundle.
- Create a dedicated folder. Make a folder used only for this server, such as
BMC2-server. Keeping the world, mods, configuration, logs, and scripts together makes backups and upgrades safer. - Extract the server pack. Unpack every file into that folder. Do not run the archive in place or mix it with another Minecraft server’s files.
- Install and verify Java. Install 64-bit Java 17, open a terminal or Command Prompt, and run
java -version. The reported major version must be 17 and the executable must be 64-bit. - Run the supplied launcher once. On Windows, run
startserver.bat. On Linux or macOS, runstartserver.sh. The first launch may stop while it creates files and displays setup instructions; that is normal. - Accept the EULA. Open the generated
eula.txt, changeeula=falsetoeula=true, save the file, and close it. The server will not finish starting until this is done. - Edit basic settings. Open
server.properties. Setmax-playersto the number you actually support, choose the desireddifficulty, and keep port25565unless another service already uses it. If chunk loading overwhelms the machine, setview-distanceto the lower range recommended in the performance section. - Set the Java memory flags. Edit the memory values in the supplied startup script rather than creating a second launcher. Use the allocation appropriate to your player count from the requirements table, and leave unallocated RAM for the operating system. Assigning every gigabyte to Java can cause swapping, crashes, or an unresponsive host.
- Start it again. Run the same script a second time and wait for the console to report that the server has finished starting. Keep this console open while testing; it records connection errors, warnings, and crash details.
- Test locally before inviting friends. From the host computer, connect to
localhostor the host’s local address. Confirm that the world loads, the expected mods appear, and the server remains responsive while moving between areas.
Make remote connections work
Players on the same computer can use localhost; players on the same home network use the host’s private LAN address. Friends on the internet need the host’s public address, a router rule forwarding TCP port 25565 to the server computer, and a firewall rule permitting Java or the server process. If you changed server-port, forward that chosen port instead.
Forward only the game port, not administrative services. Give the server computer a stable local address so the router rule does not point at a different device after a reboot. Test from outside the home network, because connecting from inside can succeed through local routing even when the public rule is wrong. If a connection is refused, check the server console first, then the operating-system firewall, router destination address, port number, and whether the script is still running.
Make every player match the server
Install the same BMC2 release on every client that joins. A minor version mismatch can block a connection, and a client with one extra, missing, or different mod can fail during the handshake or behave unpredictably after joining. Do not add or remove a mod on only one side. If you customize the pack, distribute the resulting mod list and configuration files consistently, record the change, and have every player restart their launcher before testing again.
Keep a written note of the server’s pack version, Java version, port, and any custom files. This small inventory makes it much faster to identify whether a failed connection is a version problem or a network problem.
Reduce lag without guessing
There is no controlled benchmark establishing a fixed percentage improvement for any individual tweak, so treat the following as diagnosis steps rather than guaranteed performance figures.
Free tools Windows power users keep installed
One-click scans. No signup required.
Chunk loading causes freezes
Exploring unfamiliar terrain, especially in a new dimension, can temporarily stall the server while chunks and structures generate. First lower the server’s view-distance to about 8–10 and ask players to reduce their client render distance. Keep the world on an SSD and avoid having several players sprint into unexplored directions at once during testing.
For an established world, use the Chunky mod to pre-generate areas before a busy exploration session. Generate only the regions players are likely to visit; pre-generating an entire dimension can consume substantial time and storage.
Players see low FPS but the server console is healthy
This is usually a client-rendering problem rather than server lag. Lower the client render distance, reduce simulation-heavy visual settings, and disable shaders while troubleshooting. Re-enable visual features one at a time after the server and client remain stable.
The server runs out of memory or crashes
Check the console and crash report for memory errors, then confirm that the startup script is actually using the intended 64-bit Java executable and allocation. Stop other memory-heavy programs, preserve free RAM for the operating system, and move to the higher allocation range in the requirements table when the player count or mod activity warrants it. More memory cannot repair a mismatched mod set or a failing Java installation.
Ticks slow down for everyone
Watch for a pattern: simultaneous exploration points to chunk generation; a slowdown near a large base can indicate concentrated entities or machines; periodic pauses can indicate storage or memory pressure. Keep the server and world on an SSD, avoid filling the disk, and review logs for repeating errors. Change one setting at a time so you can identify which adjustment helped.
Only one player has trouble
Compare that player’s pack files, configuration, Java edition, and client render distance with a working player. A single client-side shader or mod mismatch can look like a server fault even when everyone else is unaffected.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Backups, updates, and safe administration
Back up before changes
Stop the server cleanly before copying the world folder. Keep at least one backup away from the live server machine and include the configuration, scripts, and any customized mods needed to reproduce the installation. Periodically restore a copy to a test folder so you know the backup is usable rather than merely present.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Update deliberately
Do not replace the server files while the process is running. Record the current pack version, back up the world, install the new server pack in a separate folder, and compare configuration changes before moving the world across. Have clients update to the exact same release before opening the new server to everyone. If the new pack causes a problem, the old folder and backup provide a rollback path.
Protect the machine
Use a separate operating-system account where practical, keep the host patched, allow only the game port through the firewall, and avoid sharing the server folder over the network. Review console output after restarts and remove obsolete backups only after a newer verified copy exists.
A practical decision checklist
- Use the Fabric BMC2 1.20.1 server pack that matches the client release; do not substitute the small launcher manifest.
- Verify 64-bit Java 17 with
java -version. - Meet the memory, CPU, storage, and network requirements before troubleshooting mods.
- Choose managed hosting for convenience and continuous availability, self-hosting for control, or LAN for occasional same-network sessions.
- Complete the EULA and
server.propertiesedits before inviting players. - Match every client’s version and mod set exactly.
- When exploration lags, lower view distance, reduce shaders, use an SSD, and pre-generate likely areas with Chunky.
- Back up before updates and keep the server console available while diagnosing problems.
The Bottom Line
A reliable BMC2 server is mostly a matching-version and resource-management exercise: install the full Fabric server pack, run it on Java 17 with adequate headroom, configure the network deliberately, and treat client consistency, SSD storage, and chunk-generation control as part of the server setup rather than optional tweaks.
Quick Recap
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.
