Hey guys I'm Scully, and I'm going to write a small guide on average things people should know to code a private server.

I see no need to me to keep writing this. No comments to me seems as though you all know what you're doing.

Index:

1. Starting Supplies

i. Java Tutorials
ii. Server Base
iii. Client Base

2. Simple Changes In Game

i. Server Name
ii. Experience rates
iii. Shops
iiii. Spawning NPCs

3. All about Objects

i. Object Spawning
ii. Object Interaction

4. All about NPCs

i. NPC Interaction
ii. NPC Dialogue
iii. NPC Movement

5. First, you need to learn Java before you start with private server, or learn Java as you are working with them. Java is the programming language Rune Scape Private Severs are coded in. Java requires time to learn and time to understand what you are writing, and better ways to improve your code to make it more efficient. Now, if you feel learning Java is to much for you, then give up now. That may sound harsh to you, but it's the truth.

Secondly, you're going to need to get a server base. Depending on your skill with java, and work with Rune Scape Private Servers, you will want a different base. If you are just starting coding you would want something easier to code, but of course it comes with it's flaws as well. If your past the starting level of coding you're going to want a more efficient base to work with. This would incorporate more classes to work with, but it is also more organized and usually more stable. If you feel you are an expert in both Java, and Rune Scape Private Servers, then you would want to move up with what you work with. These servers consist of a lot of packaging, imports, and more advanced code.

Lastly, you're going to need a client to run your sever on. A client is basically a sender and receiver of incoming and outgoing packets. To log in to your server you need a client. There are two type of clients, Renamed and Non-Renamed or Refactored and Non-Refactored. The Renamed clients are much easier to use and read the code within them.

Suggest Java tutorials:
http://java.sun.com/docs/books/tutorial/

*Note I do not have permission to post the links therefore I will not.
Suggested Beginner Server Sources:
Project Czar
Allstar Scape
Whitescape
WinterLove

Suggested Intermediate Server Sources:
Rich Scape v.4_3
Deltascape
Emulous

Suggested Expert Server Sources:
RS2D
Rs2DV
Shard Revolutions

Client Sources:
Really any client can do it really depends on person preference.




Changing the Name of the server is probably the easiest part of a private server, next to downloading the source. How your going to do this is by clicking the “Edit” button on the tool bar. Then, go down on that list until you see Replace, type in the name of the server's name for search. Then, in replace type in the name of your server. Now remember doing this, and not changing anything else programming wise in the server you will be called a “leecher”. This is not a good thing, and your better off taking your time and coding a server.

Now, shops are a very important part of your server. Shops are what contains all available items without killing monsters. Now keep in mind that if you load a shop full of fish, and a shop full of the best armor in the game no one if going to go out and fish and cook, or kill monsters for those items. The shop set-up in most servers is very simple and done with a configuration (.cfg) file. The set up is easy. Here is an example.

This part here is something you should leave alone, apart from the shop id, and the name of the shop.
Now, as you see, there is a number of an item and the amount of an item.

Spawning NPCs is the same concept as adding item into a shop. This is also done with configuration files. The set up of course is a little different. This is the set up for each NPC.

Here is a code of an NPC.

Now, this code is one of a non moving npc. The spawn = 494, is the id of the NPC you are spawning. The 3256 and 3418 are the coordinates that NPC will be standing at. The next 0 is the height meaning, does the NPC stand on ground level, below ground level, or above ground level. This NPC is standing at ground level. Now the RangeX1, RangeY1, RangeX2, and RangeY2 tell you how many squares this NPC is aloud to walk. This NPC since it has a stationary walk type does not need these coordinates added in. I will show an example of a walking NPC, so you will see an example of how the setup of those coordinates works. Now, the walk type, the walk type tell you whether or not the NPC is going to stand still or walk around in the the square you have formed for them to walk in. Lastly, the description, this is more or less just for your own good to know which NPC you are changing for in future reference.

Here is an example of a walking NPC:
Now, I want you to draw your attention to the second set of coordinates. These are saying that the NPC can walk one square left, and two squares up. The next set of two coordinates is saying the NPC can walk one square right and two squares down. This of course has to be adjusted with the coordinates of your NPC. You can also change change how many squares the NPC can be able to walk. If you also noticed the walk type on the NPC has changed to a 2, this allows the NPC to walk.

Finally, in this section of the guide, I will address changing the players rights in-game. This is very easy, and I almost forgot to add it in it in as it is so simple. This, method will vary throughout servers. One method is to look at your character's saved file, this is probably the most commonly used method, and switch player rights to 1, 2, or 3 (mod, admin, owner.) Another method uses configuration files to set a player's rights. All you have to do write in the player's name and save the configuration file. Lastly, the least common method used, would be to have the rights set up into client.java or IOClient.java. The code will probably look something like this:
With this code all your going to want to change is the name in the parentheses to whatever your name is, or change the player rights if it is not your account. To add another one simply copy that code and re-add it beneath the original.


I see no need to me to keep writing this. No comments to me seems as though you all know what you're doing.