AgalarMC Create Server

Hello, again! This is the server-side version of AgalarMC Create. It has all the files you need to set up a dedicated server for the modpack; and an in-depth setup guide covering hosting provider or self hosting options, port forwarding, and offline server support. Check the full description below for detailed instructions. Here are your options to set your server up:

Option One: Hosting Provider

1. Pick a server hosting provider. Free providers most likely won't be able to handle this modpack, so using a paid one will likely be necessary.
2. Go to the server settings and find the installation or loader section. It's called something different depending on the host, but basically you need to find the place to change your modloader settings. If your host has a modpack option, select that and find AgalarMC Create Server.
3. If your server host doesn't have a modpack option, or the modpack option doesn't include this modpack, you'll have to set it up manually. Set the modloader to the latest NeoForge 1.21.1, convert the server-side modpack file from .mrpack to .zip, unzip it, then drag and drop the contents into your servers directory.
4. Lastly, open an additional port at 24454 for Voice Chat.

Option Two: Self Hosting

1. Download the latest 1.21.1 version of NeoForge and set it up somewhere safe using the server installation option.
2. Download the server-side pack from the modrinth app(or any launcher that supports .mrpack downloads) and go to its folder.
3. Move those files to your server's location.
4. Run the server using run.bat. After accepting the EULA, you can open your server to your LAN.
5. Port forward your PC using the default ports: 25565 (TCP) for Minecraft and 24454 (UDP) for Simple Voice Chat. Once that's done, you can share your IP address, and your friends can join using it. If you don't know how, here's a step by step guide:
   • If you're on Windows, first find your PC's local IP address by opening Command Prompt and running ipconfig, then looking for "IPv4 Address."
   • It's a good idea to give your PC a static local IP so the forwarding rules don't break later. Log into your router's admin panel (usually 192.168.1.1 or 192.168.0.1 in your browser) and set your PC's IP as static, using the address you found above.
   • In your router's admin panel, find the section usually called "Port Forwarding," "Virtual Server," or "NAT Forwarding," and create a rule forwarding external port 25565 to internal port 25565 over TCP, pointing to your PC's static local IP.
   • Create a second rule the same way for port 24454, this time over UDP, also pointing to your PC's static local IP. Save and apply, some routers need a reboot for this to take effect.
   • Allow both ports through Windows Firewall. Open "Windows Defender Firewall with Advanced Security," go to "Inbound Rules," click "New Rule," choose "Port," then enter 25565 as TCP and create the rule. Repeat the process for 24454 as UDP.
   • [OPTIONAL] Test everything by starting your server and using a site like canyouseeme.org to check if port 25565 is open, or having a friend outside your network try to join using your public IP. If it doesn't work, double check that the local IP, the forwarding rule, and the firewall rule all match up exactly. If you have done everything correctly, you won't need this step.
6. Depending on your server's render distance or the number of players joining, the default RAM allocation might not be enough. If so, open the user_jvm_args.txt file and uncomment the line with the -Xmx (maximum) and -Xms (minimum) values, then adjust them to fit your needs. For example, -Xmx8G means the server will use a maximum of 8 gigabytes of RAM. If your server isn't allocating the maximum RAM properly and you're running into issues, set the Xms value equal to the Xmx value. Don't allocate all of your free RAM. Leave several gigabytes of headroom.
7. [OPTIONAL] For a more secure and convenient setup, you can point a domain you own to your IP. Your IP still isn't fully hidden: if someone pings that domain, your IP will show up. But your friends won't know it unless they use a specific website or tool to check. It also just looks better to have a server address you chose yourself, instead of a set of numbers.
   • If you want your friends to join using just the domain, without typing a port number at the end, you can set up an SRV record for your domain pointing to your Minecraft port. Check your domain provider's DNS settings for this option.
   • Most home internet connections don't have a fixed public IP, so yours can change over time. If that happens, your domain will point to the wrong IP until you update it. Some ISPs offer a static IP as a paid add-on to your internet subscription, which is one way to avoid this problem entirely. If yours doesn't, or you'd rather not pay extra, you can use a Dynamic DNS (DDNS) service instead, which automatically keeps your domain pointed to your current IP whenever it changes.
8. If you're unsure about any step, look it up for yourself to avoid running into any issues in the future.

Setup specifications

• In order to utilize C2ME's chunk generation fully, the dedicated server will need a CPU with a high core count; as the mod utilizes additional cores, normally unused by vanilla Minecraft, to severely speed up chunk generation. However even on a lower-end CPU, your server's performance will still be higher than vanilla.
• Allocating at least 6 gigabytes of RAM -or more- is recommended for a smooth gameplay.
• Keeping the render distance at 15-20 range is recommended for both performance and player view, if you have a good pc you can go higher.

For offline servers

1. Setting up an offline server means you'll have to use an authentication mod and a whitelist mod, to keep your server safe from griefers and account stealing. I suggest using cwhitelist and directauth because of their extra features.
2. Open server.properties file and change the line online-mode=true to online-mode=false
3. In your server panel enter /cwhitelist add name <nickname> and /cwhitelist add UUID <player UUID> separately, for each player you're planning to invite.
4. Whitelisted players will be able to join and after registering, they will be able to login. Players with online accounts will then be able to bypass having to use the login command everytime they join, via using the online command once. Turning their accounts back to online-mode.
5. Now this setup specifically will allow you to use Mojang's authentication systems to let players with online accounts join alongside players with offline accounts.
6. [OPTIONAL] You can use a mod like SkinsRestorer to let offline players use their skins as well, otherwise they will see all players including themselves as default skins.

Keep in mind that port forwarding does open your connection up to the internet, so only forward the ports you actually need, and only share your IP or domain with people you trust. I'm not responsible for anything that goes wrong on your end from this. That said, don't stress too much, if you follow the guide and keep those two things in mind, you're good to go.