2006-Scape/apollo
1
0
Fork 0
mirror of https://github.com/2006-Scape/apollo.git synced 2026-07-03 00:38:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update readme.

Browse Source
This commit is contained in:
Major-
2013-11-03 19:49:30 +00:00
parent 43c5a23851
commit 74235be71f
1 changed files with 29 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README
+29 -41
View File
@@ -1,55 +1,43 @@
Apollo is a RuneScape emulator which aims to encourage a fundamentally-different alternative to the way in which private server development is done today. It consists of a high-performance, modular server written in Java as well as a collection of utilities for managing the data files and plugins.
Currently people download a server, read through tutorials and apply their modifications or write their own code on top of it. They'll then host it or release it. The result is we currently have a complete mess of servers (this includes every current base - Hyperion, rs2hd, winterlove) all created from cobbled-together code.
Currently people download a server, read through tutorials and apply their modifications or write their own code on top of it. This will eventually be released and repeated - resulting in a complete mess of servers, all created from cobbled-together code.
Apollo is going to change that through its plugin system. Instead of throwing everything into one big application, Apollo consists of:
A small 'core' application which provides features necessary for the server to operate.
A set of plugins, and the tools to manage them (install, uninstall, publish, download, etc).
Some additional tools and utilities for managing the data files.
A small 'core' application which provides features necessary for the server to operate.
A set of plugins, and the tools to manage them (install, uninstall, publish, download, etc).
Some additional tools and utilities for managing the data files.
This will make it much easier for everyone to develop a private server, no longer restricting it to people who can (or can't as the case is here) program. Instead of messing around copying and pasting lines of code from a woodcutting tutorial, people will simply have to download and install a woodcutting plugin.
This will make it much easier for everyone to develop a private server, no longer restricting it to people who can program. Instead of copying and pasting lines of code from a woodcutting tutorial, people will simply have to download and install a woodcutting plugin. There is also going to be a plugin repository and a set of tools to make the experience very much like a package manager on Linux. Plugins themselves are currently written in Ruby, although other languages could be added.
There is also a plan to have a plugin repository (or maybe multiple repositories) and a set of tools to make the experience very much like a package manager on Linux.
This system also means applying updates to the core server is very easy. Users will just have to download the new jar, overwrite the current one with the new one, and reboot their server. This also means that inexperienced users are protected from making fatal mistakes in the core.
It also means updates can be provided for the core server (e.g. security, stability, optimizations) very easily. Users will just have to download the new jar, overwrite the current one with the new one, and reboot their server.
Some of the technically significant core features include:
And best of all, inexperienced users are protected from making fatal mistakes in the core and are kept away from stuff that they shouldn't be editing at their experience level.
Plugins are currently written in Ruby, however, in the future other languages could be added.
Core Features
Some of the significant (technically) current core features include:
Packet encoding/decoding has been split from the representations of the packets themselves. This allows the potential for encoding/decoding to go on in parallel and also allows multiple revisions to be supported. Currently 317 and 377 are both completely supported.
Update server support (JAGGRAB, ondemand and HTTP).
Packet handler chaining: this allows multiple plugins to be able to intercept a single packet and deal with it appropriately. For example, a quest plugin could intercept searching a bookshelf for instance, if the behaviour needed to change in certain cases.
Parallel execution of player updating for multi-core machines - this has a significant benefit on my dual core machine used to test the server.
Packet encoding/decoding has been split from the representations of the packets themselves. This allows the potential for encoding/decoding to go on in parallel and also allows multiple revisions to be supported. Currently 317 and 377 are both completely supported.
Update server support (JAGGRAB, ondemand and HTTP).
Packet handler chaining: this allows multiple plugins to be able to intercept a single packet and deal with it appropriately. For example, a quest plugin could intercept searching a bookshelf for instance, if the behaviour needed to change in certain cases.
Parallel execution of player updating for multi-core machines.
As well as that, it has the bog standard stuff:
Login
Appearance updating
Multiplayer
Walking/running
Rights management
Travel back algorithm for movement
Character design
Chatting
Commands
Inventory support
Equipment support
Animations
Graphics
Facing/turn to
Action system
Working distanced actions
All data types implemented
Task scheduler based on game ticks
Saving/loading with a custom binary format
Skill levels/experiences
Plugin management
Reads item information from the cache
Login
Multiplayer
Walking/running
Rights management
Travel back algorithm for movement
Character design
Full player updating
Npcs (and full npc updating)
Commands
Inventory support
Equipment support
Action system
Working distanced actions
Task scheduler based on game ticks
Saving/loading with a custom binary format
Skill levels/experiences
Plugin management
Item, npc and object information reading (from the cache)