Scavengers of Ancient Power

Use ATLauncher's built-in "Create Server" function to create a server pack. Test the server pack by running it locally. There may be a few libraries that need to be installed manually. It will tell you which libraries are needed in an error code popup window when you try to launch it. Adding those libraries can be done using the "Add Mods" button. You can also use this to customize your install with other server-sided mods if desired. After that, you can use the server pack normally.

This modpack (and almost all 1.20.1 modpacks) requires Java 17 (an older version of Java) to run. Vanilla Minecraft's launcher has this included when you install it, but most modpack launchers do not. The easiest way to fix this will vary based on your launcher.

The most popular launchers to play Modrinth modpacks right now are Modrinth Launcher and Prism Launcher.

Modrinth Launcher (download link at the top of this webpage) comes with a convenient way to download Java 17 in its Settings. Simply find "Java 17 Location" in settings and click "Install Recommended" to automatically download the correct binaries. Then, you should be able to launch SAP.

Prism Launcher, like Modrinth, allows Java 17 installation in Settings. Go to Settings > Java > Management > Download, then select Java 17. Select the most recent version from this menu (any listed source will work), then click "Download". Then, you should be able to launch SAP.

Most other launchers require manual installation of Java 17. Instructions can be found below for Windows, MacOS, and Linux.

Java 17 installation methods for launchers requiring a manual install are listed below.

| Windows (.msi) or MacOS (.pkg) | Ubuntu-based Linux | Fedora Linux | | --- | --- | --- | | Download Installer, and make sure "JRE" is selected before downloading. | ``sudo apt install openjdk-17-jre` | `sudo dnf install java-17-openjdk`` |

For a Server:

• I recommend 10 GB for a small server with 2-5 of your friends. I also recommend pre-generating your world using the included mod "Chunky" to ensure smooth performance when loading new chunks, though this is optional.
• If you want to run a larger server, I would recommend starting at 12 GB and adding increments of 2 addition GB periodically to see if you get improved performance.
• It is not recommended to just allocate as much RAM as you have available for a server, that strategy does not work well with Minecraft servers. Often, this will create tick lag if there is an excess of unused RAM. Incremental adjustments and testing are best, and everyone's server will be different.
• If you do not want to have to think about all that, just use 16 GB for a larger server.

For a singleplayer world:

• I recommend at least 6 GB, though this is certainly suboptimal. 8-10 GB is about optimal.
• Many launchers will default users to 4 GB maximum ram allocation. The way you change this will vary based on your launcher.
• SAP will tell you how much RAM you have allocated on the early loading screen. As of V7.4, the game will also warn you if you are below the minimum recommended amount when loading the main menu or a new world.

| Bug | Fix | | --- | --- | | Very rarely, loading a world will return the error "Invalid Player Data" or "Disconnected", returning the user to the multiplayer connect screen. | To fix this, simply load the world again. There are no known instances of this bug being permanent. | |Very rarely, generating a new world can cause a freeze without actually hanging or crashing. | To fix this, re-launch the game. The world should load normally after this. | | Rarely after casting spells, runes will not be detected in the player's inventory, making spells uncastable without spell infinity | To fix this, drop the runes in your inventory and pick them up again. | | Rarely, identical stackable items will not stack. | To fix this, drop the items and pick them up again. |