How to Set Up a RuneScape Private Server From a Source and Client (2026)

I remember the first time I tried to set up my own RuneScape private server. I downloaded a random .zip file, double-clicked a .bat, watched a black window flash closed, and spent three hours convinced my computer was broken. It wasn’t. I just didn’t understand what a source and client actually were, or why Java mattered so much.

This guide on how to set up a RuneScape private server from a source and client fixes that. I’ll walk you through every step I wish someone had walked me through: choosing a server base, installing Java the right way, importing a source project into Eclipse or IntelliJ, compiling it, running the server, configuring a client, and getting your friends connected. By the end, you’ll have a working RSPS running on your own machine, and you’ll understand what every piece does.

Whether you want to learn Java, run a private server for your household, or launch the next big RSPS community, the process starts here. No prior coding experience is required, just patience and a willingness to read error messages.

What Is an RSPS and Why Should You Build One?

A RuneScape Private Server (RSPS) is a player-run server that replicates the gameplay of Jagex’s RuneScape. Instead of connecting to Jagex’s official servers, your client talks to a server you (or someone in the community) built. That server reads game logic from source code you can edit, so the rates, items, NPCs, and even whole regions of the map can be customized.

Most RSPS projects target the older “317 protocol” era of RuneScape, which is much easier to emulate than modern Old School RuneScape. That means you’ll be playing something that feels like 2008-era RuneScape, which is exactly what most RSPS fans want.

People build private servers for three main reasons. First, it’s one of the most enjoyable ways to learn Java programming because you get instant visual feedback every time you change a line. Second, you get total control over the game: max cash stacks, custom weapons, instanced bosses, anything you can code. Third, you can run a server just for friends on a LAN, or open a public community with hundreds of players.

If any of that sounds appealing, keep reading. The setup itself takes 30 to 90 minutes the first time you do it.

Choosing a Server Base for Your RuneScape Private Server

You don’t write an RSPS from zero. You start from a “server base,” which is a pre-built source code package that already handles login, walking, combat, and basic NPC dialogue. You then customize it. Picking the right base saves you weeks of debugging.

Here are the four most common bases beginners run into, and what each one is best for.

• Project Insanity (PI): The classic 317 base. It is heavily modified, easy to compile, and has thousands of tutorials written for it. Best for absolute beginners who want the largest pool of community help.

• Hyperion: A more modernized 317 base with cleaner code structure, better caching, and more stable performance under load. Best for learners who want to study well-organized code.

• Apollo: A polished 637/718-era base that supports higher-resolution graphics and modern client features. Best for people who want a more current OSRS-style experience.

• RuneSource / OSRS bases: Open-source projects aimed at emulating Old School RuneScape specifically. Best if you want OSRS-accurate content rather than 2008-era content.

For your first server, I’d recommend Project Insanity or Hyperion. They are forgiving, well-documented, and you will find a forum thread or YouTube video for almost any problem you hit.

Prerequisites: What You Need Before You Start

Before you download anything, make sure your machine meets a few basics. Almost any desktop or laptop made in the last decade will work for a small private server.

• Operating system: Windows 10 or 11 is the path of least resistance. macOS and Linux work too, but most pre-built clients and .bat files assume Windows.

• RAM: 8 GB minimum. 16 GB is comfortable if you also want to run the client on the same machine.

• Storage: Around 2 GB free for Java, the IDE, source, and client.

• Java JDK: A Java Development Kit, not just the JRE. Most 317-era bases expect JDK 8 (also called Java 8). Newer OSRS-style bases sometimes need JDK 11 or 17. Check the base’s README before installing.

• An IDE: Eclipse (free, classic choice for RSPS) or IntelliJ IDEA Community Edition (free, more modern). Either works.

• A stable internet connection: Only required if friends outside your home will connect. For LAN-only play, you can skip the internet entirely.

Pick Java 8 unless the base’s documentation says otherwise. Mixing Java versions is the single most common source of errors in beginner RSPS setups.

How to Set Up a RuneScape Private Server From a Source and Client

This is the core walkthrough. Follow these eight steps in order. Each step has a short explanation of what you’re doing and why, so the process actually makes sense instead of feeling like copy-paste magic.

Step 1: Download a Server Source and Client

Find a server base you trust. Reliable places to look are the official Rune-Server forums, the RSPS subreddit’s pinned server list, and established GitHub repositories like the open-source rsbox project. Avoid random MediaFire links from 2012; they are often broken or worse.

You will end up with two folders: one containing the source (the server code, in .java files) and one containing the client (the actual game you run, in .class files plus a launcher). Keep them in a clean directory like C:RSPSMyServer so paths don’t break later.

Step 2: Install Java JDK and Set Environment Variables

Download the JDK that matches your base. If your base expects Java 8, grab the JDK 8 installer from Oracle or from Adoptium (Eclipse Temurin). Run the installer with default options.

Next, set your JAVA_HOME environment variable. On Windows, open Start, search “Edit environment variables for your account,” click Environment Variables, and add a new system variable named JAVA_HOME pointing to your JDK install path, for example C:Program FilesJavajdk1.8.0_xxx. Add %JAVA_HOME%bin to your PATH. Open a fresh command prompt and type java -version to confirm it works.

If you skip this step, your IDE and your .bat files will not know where Java lives, and you will get “Java not recognized” errors immediately.

Step 3: Set Up Your IDE (Eclipse or IntelliJ)

Download Eclipse IDE for Java Developers or IntelliJ IDEA Community Edition. Both are free. Eclipse is the traditional RSPS choice because most tutorials reference it. IntelliJ has a friendlier interface and better error messages.

Install with default settings. When you first launch it, it will ask where to keep your workspace. Point it to a clean folder like C:RSPSworkspace.

Step 4: Import the Source Project

In Eclipse, click File, then Import, then Existing Projects into Workspace. Browse to the source folder you downloaded and select the project. Make sure “Copy projects into workspace” is unchecked unless you want a duplicate.

In IntelliJ, click Open, then select the source folder directly. IntelliJ will detect it as a Java project and start indexing.

Once imported, you should see a tree of packages like server.model.players, server.model.npcs, and server.net. These are the core systems of your server.

Step 5: Configure the Classpath

The classpath tells Java which libraries (JAR files) your source depends on. Most RSPS bases ship a libs or lib folder containing JARs. Right-click your project, choose Build Path, then Configure Build Path, and add those JAR files as libraries.

If you skip this, your source will not compile, and the error will say “cannot find symbol” pointing to a class that obviously exists. That error almost always means a missing JAR on the classpath, not a bug in your code.

Step 6: Compile the Source Code

Most bases include a Compiler.bat file in the source folder. Double-click it. A black console window opens, lists every .java file, and produces a compiled folder full of .class files. If you see “BUILD SUCCESSFUL” or no red errors, you’re done.

If you see errors, the most common culprit is the wrong Java version. Re-check the JDK you installed matches what the base expects.

Step 7: Configure Server Properties and Run

Open the compiled folder. You’ll find a Run.bat or Start.bat. Open it in Notepad and look at the contents. It usually looks like java -cp bin;lib/* server.Server. That tells Java where to find your code and the main class to launch.

Many bases also include a server.properties or in-code constants for the server’s IP, port (default 43594 for 317), max players, and experience rates. Edit those to taste. Double-click Run.bat. A console window opens and starts logging player connections. If you see “Server is now online,” your server is running.

Step 8: Configure the Client to Connect

Open your client folder. You’ll find a launcher .jar plus a folder of cached game files. Open the source for the client (if you have it) or the configuration file, and update the server IP to 127.0.0.1 for local testing. Recompile if needed, then run the client.

Type a username, password, and click Login. If the client connects and you see the login screen populated, congratulations. You now have a working RuneScape private server running from source and client.

Port Forwarding and Network Setup

If you only want to play with people on the same Wi-Fi network, you don’t need to do anything else. Other devices on your network can connect using your computer’s local IP (usually something like 192.168.1.x) plus port 43594.

If you want friends from outside your home to connect, you have two options. The first is port forwarding: log into your router (usually 192.168.0.1 or 192.168.1.1), find the port forwarding section, and forward external port 43594 to your computer’s local IP on the same port. Then give your friends your public IP (find it at whatismyip.com) and the port.

The second, easier option is a virtual LAN tool like Hamachi, Radmin VPN, or ZeroTier. Everyone joins the same virtual network, and you connect using the host’s Hamachi IP. No router configuration needed, and it works behind any ISP that blocks port forwarding.

For most beginners running a server for a handful of friends, Radmin VPN is the smoothest path. It is free for up to 10 players, which is plenty for a private RuneScape private server.

Common Troubleshooting Issues

Almost every RSPS setup hits at least one snag. These are the four issues I see beginners run into most often, and how to fix each one fast.

• “Java not recognized” or “javac not found”: Your JAVA_HOME or PATH is not set, or your command prompt is still using the old environment. Close all terminals and reopen them.

• “Connection refused” when the client tries to connect: The server isn’t running, the client is pointing at the wrong IP, or your firewall is blocking port 43594. Add a firewall rule allowing Java through on that port.

• “Cannot find symbol” compile errors: Almost always a missing JAR on the classpath. Re-check Step 5.

• Outdated tutorial with broken links: This is depressingly common. Stick to base-specific tutorials from the last 2 to 3 years, and verify download links with multiple users before trusting them.

If you get stuck, the RSPS subreddit and the Rune-Server forums are still active communities where people post fixes daily. Search your exact error message in quotes before posting a new thread.

Legal Considerations: Is Running an RSPS Allowed?

Three questions come up constantly, so let’s address them directly.

Are RuneScape private servers legal? In most countries, yes. RSPS projects use decompiled or rewritten code that does not copy Jagex’s actual assets directly. You are running your own software on your own hardware. That said, distributing Jagex’s copyrighted game assets (maps, music, certain models) can violate copyright, which is why most RSPS projects use custom or open-source assets.

Does Jagex allow private servers? Officially, no. Jagex’s terms of service prohibit connecting to or promoting third-party RuneScape servers using official clients. In practice, Jagex focuses enforcement on large public RSPS that infringe their trademarks, not small private servers run for friends.

Is using OSRS private servers bannable? It can be. If you log into an official OSRS account while running an RSPS, or if you connect to an RSPS using the official OSRS client, Jagex can and does ban accounts. Always use a separate RSPS-only client and never reuse your OSRS login credentials.

The safe pattern: keep your RSPS small, use custom assets, never touch your real OSRS account on the same machine, and you will avoid the small risk of any action entirely.

Frequently Asked Questions

Final Thoughts on Building Your Own RSPS

Setting up a RuneScape private server from a source and client is one of those projects that looks intimidating from the outside but turns out to be a series of small, well-understood steps once you start. Pick a beginner-friendly base, install Java the right way, import the source into an IDE, compile, run, and connect. That sequence has worked for thousands of community members over the last decade and it will work for you.

Once your server is running, the fun really begins. Tweak drop rates, add a custom NPC, change a few item stats, and watch your changes appear in-game the moment you recompile. That feedback loop is what makes an RSPS such a powerful learning tool for Java, and it’s why the community is still active after 15 years.

Start small, expect a few compile errors on your first attempt, and you’ll have a private RuneScape server up and running by the end of the day.