How to make your own RSPS: an overview for beginners

1. Choose a revision and a base

Most people start from an existing open-source server base for a revision like 317, 718 or a recent OSRS build (see revisions explained). Bases are typically written in Java or Kotlin. Check a base's licence, how active it is, and whether it has known security issues before building on it.

2. Skills you will need

• Java or Kotlin, plus Git for version control.
• Basic Linux server administration and a database such as MySQL or PostgreSQL.
• For custom content: cache editing tools, 3D models and scripting.

3. Hosting

A small server runs on a VPS or dedicated machine with a few GB of RAM. Add DDoS protection early; popular servers attract attacks. Keep regular off-site backups of the database.

4. Client and website

Players need a client (desktop .jar or launcher, optionally Android) and a website for downloads, rules, news and voting. Sign your launcher if you can, and publish checksums so players can verify downloads.

5. Community and growth

• A Discord with clear rules and staff roles.
• Vote rewards through toplists (see our server owner docs).
• A steady update schedule: players stay where things change.

Costs and risks

Expect ongoing costs for hosting, a domain and DDoS protection, plus a lot of time. RuneScape content belongs to Jagex, and taking money for a server adds legal risk; read are RSPS servers legal? first.

When you launch, you can list your server here for free.

Frequently asked questions

How hard is it to make an RSPS?

Getting a base running locally takes a day or two for a programmer. Running a stable, secure, popular server takes months of steady work.

What programming language are RSPS written in?

Most server bases use Java or Kotlin. Clients are usually Java too, with some using C# or web technologies.

How much does it cost to host an RSPS?

A small VPS and domain are a modest monthly cost; DDoS protection and bigger player counts raise it.