Java-Bedrock Crossplay Aternos Server, on my own pc
- User
Java-Bedrock Crossplay Aternos Server, on my own pc
Assistant
Okay, let's break down how to set up a Java-Bedrock crossplay Aternos server on your own PC, focusing on clarity and addressing the common pain points.
Understanding the Challenge
- Java and Bedrock Differences: Minecraft Java Edition and Bedrock Edition use completely different codebases, account systems, and server protocols. They can't directly connect.
- Aternos Limitations: Aternos provides free server hosting, which is fantastic, but it has certain limitations. We'll need to work within those constraints.
- Your PC's Role: You're not hosting the actual Minecraft server on your PC. Aternos is doing that. Your PC is primarily for configuring the Aternos server and connecting to it.
- Crossplay Requires a Bridge: To make the connection, you need a bridging solution that translates between the Java and Bedrock protocols. GeyserMC is the most common and well-supported solution for this.
Steps to Set Up Your Crossplay Server on Aternos
-
Aternos Account and Server Creation
- Go to https://aternos.org/ and create an account (if you don't have one).
- Create a new Minecraft: Java Edition server.
-
Install GeyserMC and Floodgate (Crucial)
- Log in to your Aternos account.
- Go to your server's "Software" section.
- Choose "Bukkit," "Spigot," or "Paper" (Paper is generally recommended for performance). You must use one of these options because GeyserMC is a plugin that needs a plugin-compatible server type.
- Go to the "Plugins" section.
- Search for and install GeyserMC.
- Search for and install Floodgate. Floodgate handles Bedrock player authentication. It's essential for Bedrock players to log in without Java accounts.
-
Configure Floodgate (IMPORTANT)
- Important: Once Geyser and Floodgate are installed, start your server once. This will generate the configuration files.
- Stop your server.
- Go to the "Files" section of your Aternos server.
- Navigate to the
plugins/Floodgatefolder. - Open the
config.ymlfile in the editor. settings.link-accounts: false: Make sure this is set tofalse. If you want players to be able to link their bedrock accounts to Java accounts you can set this to true but it may require additional configuration.settings.allow-name-spoofing: true: Set this to true so Bedrock usernames are shown properly in the Java Server.- Save the
config.ymlfile.
-
Start the Server
- Start your Aternos server. It may take a few minutes.
-
Bedrock Connection Information
- Java Server Address: This will be the standard server address that Aternos provides for your server (e.g.,
yourservername.aternos.me). Java players connect to this directly. - Bedrock Server Address: This is usually the same as the Java address (yourservername.aternos.me).
- Bedrock Port: The default Geyser port is 19132. This is the standard port for Bedrock. However, Aternos doesn't allow custom ports. Geyser will automatically listen on the Java server port, which is what you should use on bedrock.
- Java Server Address: This will be the standard server address that Aternos provides for your server (e.g.,
-
Connecting from Bedrock Edition
- Open Minecraft: Bedrock Edition.
- Go to "Play".
- Go to the "Servers" tab.
- Click "Add Server".
- Server Name: (Anything you want)
- Server Address: Enter your Aternos Java server address (e.g.,
yourservername.aternos.me). - Port: Enter the Aternos Java server port.
- Click "Save".
- You should now see your server in the list. Click on it to join.
Important Considerations and Troubleshooting
- Aternos Server Limits: Aternos is free and has resource limits. If your server has too many players or complex plugins, it may lag or crash.
- Firewall Issues: Make sure your PC's firewall (and any router firewalls) aren't blocking connections to the Aternos server. However, this is usually only an issue if you were hosting the server on your PC. Since Aternos is hosting, this is less likely to be the problem.
- Aternos Queue: Aternos uses a queue system. You may have to wait in line to start your server.
- Server Console: The Aternos server console is your friend. Check it for error messages, especially when you're first setting things up. It can provide clues if something is going wrong.
- GeyserMC Documentation: Refer to the official GeyserMC documentation for in-depth information and troubleshooting: https://geysermc.org/
- Floodgate Documentation: https://geysermc.org/documentation/floodgate/
- Username Conflicts: If a Java player has the same username as a Bedrock player, there might be conflicts. Floodgate helps manage this, but it's something to be aware of. Suggest players choose unique names.
- Plugin Compatibility: Not all Java plugins are compatible with GeyserMC or Bedrock players. Test plugins carefully to ensure they work as expected.
- Geyser Updates: GeyserMC is actively developed. Keep it updated to ensure compatibility with the latest Minecraft versions. Aternos usually updates plugins automatically.
- Check Geyser Configuration File: If you are still having problems, check your geyser configuration file by going to the file manager and browsing to the geyser folder.
Example
plugins/Floodgate/config.yml:settings: # Should Floodgate link Bedrock players with a Java account? # # Enabling this will disable auto-linking feature, # so Bedrock players can verify themselves if they want to. link-accounts: false # Allow Bedrock players to use Java accounts' name? # # Note: We don't support 3rd-party plugins that do anything with # players' names on Java Edition. # # Note: If a Java player has the same name as a Bedrock player, # the Bedrock player will have "(BE)" tag at the end of their name. # # Default: false allow-name-spoofing: true # Force Bedrock players to verify their XUID to be able to join? # # Bedrock players are able to skip verification but they won't be # able to join your server unless they verify. # # Java players will be able to see the XUID of verified Bedrock players. # # Default: true force-verification: false # What should be the message when Floodgate verification is enabled but the Bedrock player hasn't verified yet? verification-message: "Please verify your XUID to play!" # Should Floodgate hide the player's real IP Address? # # Note: If your proxy is configured correctly, then you don't need this. # # Default: false hide-player-ip: false # Is this server a proxy server? # # You can only enable this if you are using a proxy that supports # the Floodgate API. (e.g. Waterfall) # # If you are enabling this without a proper proxy, Bedrock players # will be able to bypass Floodgate. # # Default: false is-proxy: false # How Floodgate should obtain the player's ip address. # # Possible values: # - default (Use the default Bukkit method to get the IP Address) # - x-forwarded-for (Grab the IP Address from the 'X-Forwarded-For' header) # # Default: default ip-forwarding-method: defaultIn summary, the key steps are:
- Set up your Aternos Java server.
- Choose Spigot, Bukkit, or Paper as the software.
- Install GeyserMC and Floodgate plugins.
- Configure Floodgate (especially
link-accountsandallow-name-spoofing). - Start the server.
- Connect with the Aternos address and the Aternos Server Port.
- Troubleshoot using the Aternos console and GeyserMC documentation.
Good luck! Let me know if you get stuck on any particular step.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.