Thread: The 3rd Quadrant Project | Goal: Memory Restoration

Powered By:




NOTICE

3DQ Inc. is now under new management, the team has not changed in any way. By request of 3QD, I am now handling the "business" side of things, I have my own local company that I run, and in my spare time I will be answering questions, submiting requests to the team and being the middle man between 3DQ Inc. and everyone else.

Thanks,
"Az"
A.C.E Business Management.

3rd Quadrant

3DQ Inc. is a small organization headed by [Only registered and activated users can see links. ] and [Only registered and activated users can see links. ], both very hard workers along with me and my friend.

We used constantly look for good servers to play, when one day it hit us, just about every single server out there is crap. So we decided "What the heck? Why not make our own?" and that is when the adventure began.




Information

First off, feel free to post any questions/information that you feel you should, this is supposed to be a "community server".

I am so sick of people taking other more completed versions of servers and are like "omfg i am awesoem coder!" when they really just leeched it. So I am going to prove that built from the ground-up is the way to go, not leeching crap.

3Q is a new, rapidly advancing RSPS that is based on one of the most stable bases released to date. The server is aimed at providing as many players as possible the best and smoothest RSPS experience possible.

Some info about the base:

"Hyperion is a Java gameserver suite server which aims to provide an excellent, stable, quality base with advanced features such as update server (to stream the cache to the client) and login server (for multi-world support with cross world messaging).

The server has been developed completely from scratch, even the ISAAC cipher code is scratch (as the one used by most is copyrighted Jagex - from a deob).

There are lots of unique ideas: we are spending time making the server good and high quality instead of cramming lots of features in a small amount of time.

Also, for those working on their own servers, there is documentation on the login, update and in-game protocol, and information about the updating and walking procedures."





Credits

Server Developers:

• Anthony [I Rogue I]
• Ben [X0xox0]
• Greg
• Megan

Base Developers:

• Graham
• Blake
• BrettR

Features

Green = Complete
Orange = Under development
Red = Not yet started

World server

• Login
• Updating
  • Rendering
  • Multiplayer
  • NPCs
  • Update masks
  • Region system
• Communication
  • Public chat
  • Commands
  • Chat options
  • Friends/ignores/private chat
  • Report abuse
• Inventory/item support
  • Item class
  • Container class
  • Interface container listener
  • Equipment container listener
  • Weapon container listener
  • Swapping/equipping/etc
  • Banking
  • Action and action queue system
• Clipping and path finding

Login server

• Saving/loading/online checking
• World password check
• PM and friendslist

Originally Posted by Graham

Unique features

Action system:

The action system is another first which is going to prove quite unique as it is developed. There is an Action class and ActionQueue class. The ActionQueue will queue and process actions for a player.

Since a lot of actions share code (i.e. woodcutting and mining are extremely similar), there are some abstract classes such as AbstractHarvestingAction which will contain code common to both.

These allow rapid development and easy bug fixing, as well as just looking cool.

Cached update blocks:

Say you had 100 players in a region, and then a new one logs in. In a traditional server, each 100 players will reconstruct the new player's appearance update block when they login. This server will cache update blocks for the duration of the cycle, so it only happens once, at the expense of slightly more memory usage.

This should give some improvements when there are a lot of players in an area, especially if the updates are large (like appearance blocks).

Pooled player updating:

Player updating is a read only task. This means you can execute it in multiple threads safely. The server creates a thread pool with the same number of cores as the current computer it is running on, and dispatches update tasks to this pool.

To prevent threading issues, the main thread will block until all the updates are complete. Then the main thread may run as usual, processing packets and performing reads and writes safely with little worry of thread-safety.

This can give vast improvements when you have a PC with multiple cores and/or processors. If you look at the screenshot above, which was taken on a dual core PC, the server is using around 80% of the CPU which means it is taking advantage of both cores (otherwise it would be at or below 50%).

There are classes allowing you to do this as well (namely the ParallelTask class), however, there are few remaining cases in which this is possible to do safely.

Update server:

The update server uses the ondemand and a HTTP/0.9-like protocol to stream the cache to the client just like a popular MMORPG. This gives a few advantages: when the cache is modified, it can be pushed out to all new clients very easily with minimum bandwidth used up by subsequent updates (the files in the cache are only updated when the client deems it necessary). Also, no client modifications are needed to make it work (assuming you are using the original deob).