To run an All of Fabric 7 (AOF7) multiplayer server, choose one AOF7 release, download its dedicated server pack, install 64-bit Java 17, launch the supplied Fabric script once, accept the EULA, and have every player use the same AOF7 release on Minecraft 1.20.1. The server pack is the reliable starting point: rebuilding a server from a client installation can leave out required files or introduce mismatched versions.
Running a modpack with friends? Godlike.Host offers modded Minecraft server hosting with one-click modpacks (CurseForge, FTB, Technic) and free DDoS protection.
AOF7 is a large Fabric modpack—its project description advertises 400 mods, more than 1,000 quests, challenges and shaders—so performance depends on the world, view distance, number of players and active machines. There is no published AOF7-wide minimum RAM figure. Start with a sensible heap, watch tick time and memory use, then tune the server rather than assuming one number works for every group.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What you need before installing
All of Fabric 7 targets Minecraft 1.20.1 and uses the Fabric mod loader. CurseForge lists release 2.5.3 as the latest AOF7 release, dated July 14, 2025. The AOF7 server-pack entry also identifies an archive named All of Fabric 7-Server-2.4.1.zip. Those are different pack releases, so do not combine the 2.4.1 server files with a 2.5.3 client, or vice versa.
- A computer or managed host that can keep a Java process running while players are online.
- The exact AOF7 release you intend to run, recorded alongside Minecraft 1.20.1 and Fabric.
- The matching AOF7 server-pack archive, when one is available for that release.
- A 64-bit Java 17 runtime. Fabric recommends Java 17 for Minecraft 1.17 through 1.20.4; Java 21 is recommended for 1.20.5 and newer, which does not apply to AOF7’s 1.20.1 target.
- Permission to open a listening port through the operating-system firewall and, for home hosting, the router and internet connection.
- Enough storage for the pack, generated libraries, logs, configuration and the world. The required amount varies with the pack release and how long the world is played.
Keep the server in a new, dedicated directory. Do not extract it over an unrelated modpack, an older AOF7 release or a client instance. A clean directory makes it possible to identify which files belong to the server and to roll back safely.
#1 Best Overall
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Lock the release and compatibility targets
Before downloading, write down three values: the AOF7 pack version, Minecraft 1.20.1 and Fabric. Use that same combination for the server and every client. A mod that is correct for another Minecraft minor release, or for a different loader, is not a compatible substitute simply because its name looks familiar.
Why the exact pack version matters
A modpack release is a tested collection, not just a label. It pins particular mod versions, configuration files and sometimes loader details. Updating one side independently can produce missing-mod errors, registry mismatches, crashes during login or a world that behaves differently from the one the pack author tested.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Client and server rule
Install the same AOF7 release on the client and server. Compare the actual mod list if a launcher has changed or removed files. Every downloaded mod should be filtered for both Minecraft 1.20.1 and the Fabric loader. A Forge or NeoForge file, or a file built for another Minecraft version, cannot be made compatible by renaming it.
Download and extract the dedicated server pack
- Open the AOF7 project page and select the server-pack entry for the release you chose. For example, the listed archive
All of Fabric 7-Server-2.4.1.zipis a server package for Minecraft 1.20.1 and Fabric. - Create a new folder with a clear name such as
aof7-server-2.4.1. Avoid a path controlled by a game launcher or a folder containing another server. - Extract the complete archive into that folder. Preserve the directory structure; do not move only the jar files into a different location.
- Look for the supplied start script and read it before running it. A Windows batch file, Linux shell script or equivalent may set the intended memory flags and launch the correct Fabric file.
- Keep the downloaded archive in a separate backup location. It gives you a clean source if an update or an accidental edit damages the live directory.
The dedicated pack is preferable to reconstructing a server from a client instance because it is assembled for server use. If no server archive exists for the exact release you selected, verify the project instructions before attempting a manual installation; do not silently substitute a different AOF7 release.
Install and verify Java 17
Install a 64-bit Java 17 runtime on the machine that will run the server. The Java version used by a graphical launcher is not necessarily the version used by a command prompt or a host panel, so verify the runtime in the same environment that will execute the server script.
- Open a terminal or command prompt.
- Run
java -version. - Confirm that the output identifies Java 17 and a 64-bit runtime. If it reports another major version, install Java 17 or change the script or host panel’s Java selection.
- Run the command again from the server directory if your operating system uses different PATH settings for different shells.
A class-version error or a message that the program requires another Java version usually means the launch command is finding the wrong executable. Check PATH, the script’s Java setting and any per-application runtime selector before changing the modpack.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsLaunch the server for the first time
Use the server pack’s supplied start script whenever possible. It may refer to a particular Fabric launcher filename or include options that the pack expects. If you need to launch the Fabric executable directly, Fabric documents this pattern:
java -Xmx2G -jar fabric-server-launcher.jar nogui
Replace the jar filename with the one actually present in the server directory. The -Xmx2G value is an example heap ceiling, not an AOF7 requirement. Increase or decrease it only after observing the workload and confirming that the machine has RAM left for the operating system and other services.
- Start the script or command from the server directory.
- Allow Fabric to download or create missing loader and Minecraft files. Fabric describes its server launcher as an executable jar that first downloads missing Fabric Loader and Minecraft files, then continues by running the game server.
- Read the console output for the point at which startup stops. The first run commonly creates configuration files and then stops because the EULA has not yet been accepted.
- Stop the process cleanly rather than closing the terminal or killing the task. A clean stop lets the server save chunks and metadata.
If the launcher cannot download files, check the machine’s internet access, DNS, permissions and available disk space. Do not copy random libraries from another installation; retry with the intact server pack and the correct Java runtime.
Review and accept the EULA
After the first launch, locate the generated EULA file in the server directory and read it. The server may not continue normal operation until the file records acceptance. Change the acceptance setting only if the operator agrees to Mojang’s terms, then save the file and launch again.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Keep the EULA file with the server backup. Replacing the whole directory during an update can overwrite it, so verify the setting after copying a new pack or restoring a backup.
Configure the basic server settings
Once the EULA step is complete, the first successful run creates the normal server files, including server.properties. Stop the server before editing that file. Make a copy first so an incorrect value can be reverted.
World and gameplay
- World name: choose the directory name for a new world. Do not point a live server at a different world unless you have a tested backup and understand the save’s compatibility.
- Difficulty: set the level appropriate for the group before players begin building.
- View distance and simulation distance: start conservatively for a large modpack. These settings affect how many chunks and entities the server must process and can be reduced if tick time rises.
- Whitelist: enable and maintain it when only invited players should join. Add players through the server console or the administrative interface provided by the pack.
- Online-mode policy: choose the setting appropriate for your account and security model. Changing it after players have joined can affect identity handling and access, so decide before opening the server publicly.
Do not edit a configuration while the process is writing it. Stop, copy the file, make one logical change, restart and test. Mod-specific settings may live in config or defaultconfigs; those directories should be treated as part of the pack, not casually replaced with files from another release.
Start, test and join with a matching client
- Start the server with the supplied script.
- Wait for the console to reach its ready state rather than attempting to join while libraries or the world are still loading.
- On a client, select the same AOF7 release, Minecraft 1.20.1 and Fabric profile used by the server.
- Connect from the same machine or local network first. A local test separates mod and configuration problems from router and ISP problems.
- Join, move through several chunks, open inventories supplied by the pack and watch the server console for errors. Stop the server cleanly after the test.
If a clean client instance of the exact release cannot join, compare the server and client mod directories and configuration files before changing memory or networking. A successful local join is the useful baseline for remote troubleshooting.
Make the server reachable from outside your home
Home hosting requires more than starting the Java process. The operating-system firewall must permit the listening port, the router must forward that port to the correct machine, and the internet provider must allow inbound connections. The exact screens and commands differ by operating system, router model and network layout.
- Confirm in the server console or configuration which port the process is listening on.
- Give the host computer a stable local address, or configure the router’s equivalent address reservation, so forwarding does not point to a different device later.
- Create an operating-system firewall rule allowing the server’s port for the required network profile.
- Create a router forwarding rule for the same port and protocol, targeting the host computer’s local address.
- Test from a different network, such as a phone connection. Testing only from inside the home network can succeed even when inbound traffic is blocked.
- Check whether the ISP uses carrier-grade NAT (CGNAT) or blocks inbound connections. If it does, ordinary port forwarding will not make the server reachable; use a provider feature that supplies an inbound address or choose managed hosting.
Do not publish an address until the whitelist, online-mode decision and administrative permissions are settled. Keep the server software and mods updated within the chosen AOF7 release, and remove forwarding when the server is offline for an extended period.
Memory and performance tuning
AOF7’s large mod count means RAM needs vary with player count, generated terrain, automation, chunk loading and the number of simultaneous machines. No cited AOF7 page publishes a universal minimum, so treat the heap as a tunable limit rather than a promise of capacity.
Choose an initial heap
Use the server script’s existing value if it supplies one. Otherwise, begin with a modest value such as the documented -Xmx2G example for a test, then increase it when monitoring shows the heap is the limiting factor. Never allocate all physical RAM to Java: the operating system, file cache, launcher and other services need memory too.
Rank #4
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Recognize the symptoms
- Out-of-memory termination: the process or operating system reports that Java cannot allocate more memory. Increase the heap only if physical RAM is available, and reduce the workload at the same time.
- Tick lag: players experience delayed block updates or entity movement even though Java is not out of memory. Lower view or simulation distance, reduce concurrent chunk loading and investigate busy machines or dimensions.
- Long garbage-collection pauses: the console shows pauses while memory is reclaimed. Check the heap ceiling and workload; simply assigning more RAM can postpone, rather than solve, an excessive entity or chunk load.
Change one setting at a time, record the result and test with the normal number of players. A value that works for an empty spawn area can fail once several players explore separate regions.
Backups and safe updates
Stop the server before backing up or changing the pack. Copy the world directory, config, defaultconfigs and server.properties. Include the launch scripts and any operator or whitelist files needed to recreate access. Store at least one copy outside the live server directory.
- Stop the process and wait for the console to confirm shutdown.
- Copy the listed directories and files to a dated backup location.
- For an AOF7 update, duplicate the live server into a staging directory.
- Apply the new server pack to the staging copy without deleting the original.
- Start the staging copy, confirm Java and Fabric versions, and test with a client running the same new AOF7 release.
- Only after the test succeeds, schedule downtime, make a fresh backup and migrate the live world according to the pack’s instructions.
Never test an unproven pack directly on the only copy of a world. If the update changes a mod’s data format, restoration may be the only way back to a working save.
Troubleshoot by symptom
“Requires Java” or class-version errors
Run java -version from the same shell or panel that starts the server. Confirm Java 17, verify PATH and inspect the script for an absolute Java path or a different runtime selector. Do not switch to Java 21 merely because it is newer; Fabric’s guidance places AOF7’s Minecraft 1.20.1 target in the Java 17 range.
Missing mod or loader mismatch
Record the AOF7 release on both sides and compare the complete mod lists. Confirm every mod targets Minecraft 1.20.1 and Fabric. Remove a manually added file that belongs to another loader or version, then restore the pack’s original file. If the server archive and client release differ, install matching releases rather than trying to bridge them with individual downloads.
The server starts, but players disconnect
Read the first meaningful error in the server log, not only the final disconnect line. Compare client and server configurations, then test with a clean client instance of the exact release. A clean test identifies whether a local shader, optional mod or edited configuration is responsible.
Out-of-memory errors or severe tick lag
Lower view and simulation distance, reduce simultaneous exploration and pause heavy automation while observing the server. Increase the Java heap only within the host’s available RAM. If the same workload remains slow, the limiting factor may be CPU or a mod interaction rather than heap size.
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 →Remote players cannot connect
Verify that the process is listening, the operating-system firewall permits the configured port, the router forwards to the current host address and the ISP is not using CGNAT or blocking inbound traffic. A successful local connection proves the server is running but does not prove that the public route is configured.
Self-hosting versus managed hosting
Self-hosting gives you direct control over the filesystem, Java process, backups and network policy. It also makes you responsible for extracting the pack, choosing Java, applying updates, protecting the world and troubleshooting the router. Managed hosting replaces much of that infrastructure work with a control panel and provider maintenance, but you trade away some low-level control and must verify that the provider supports your exact software combination.
| Decision factor | Self-hosted server | Managed hosting |
|---|---|---|
| Control | Full access to files, JVM flags, logs and network settings | Panel-based access with provider-defined limits |
| Setup effort | Extract the server pack, install Java, configure backups and networking | Provider handles much of the installation and server management |
| Maintenance | You perform updates, backups, restores and troubleshooting | Provider may supply maintenance tools; confirm what backups and support include |
| Capacity | Limited by your machine, connection and available RAM | Compare allocated RAM, CPU, storage and geographic region |
| Compatibility check | You control Minecraft 1.20.1, Fabric and the selected AOF7 release | Confirm all three are supported before paying |
One published managed-hosting example lists quarterly-billing plans of $10 per month for 4 GB RAM, $15 per month for 6 GB and $20 per month for 8 GB; custom plans start at $5 per month. Prices and availability can change, so verify the current offer before ordering. RAM alone is not a performance guarantee: ask about CPU allocation, storage, location, backups and whether the panel installs Fabric modpacks.
When managed hosting is practical
- You cannot configure inbound connections because of CGNAT or an ISP policy.
- You want a web panel for starting, stopping, console access and file management.
- You prefer a provider to handle the machine, network and some maintenance tasks.
Questions to ask a host
- Does the plan support Minecraft 1.20.1 and Fabric?
- Can you install the exact AOF7 release, including a supplied server pack?
- How much CPU, storage and RAM are included, and are backups automatic or extra?
- Where is the server located, and can you move it if latency is poor?
- Can you download the world and configuration files if you leave?
A reliable operating routine
After the first successful session, keep a short maintenance routine: announce downtime, stop the process cleanly, back up the world and configuration, stage any update on a copy, and test with a matching client before reopening access. Keep a record of the AOF7 release, Java version, heap setting and any deliberate configuration changes. That record turns a future crash or player disconnect into a comparison exercise instead of guesswork.
Recommended Free Tools
The essential compatibility chain is simple: AOF7 release, Minecraft 1.20.1, Fabric loader, Java 17 and matching client/server files. Preserve that chain while tuning performance and networking, and most setup problems have a clear place to investigate.
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.
