#503 - #667 RSPS Configuration

For anyone developing 727 revision, I have managed to refactor almost all of the packets from going client->server and server->client. I would gladly accept any help with refactoring this as it has been a very fun project so far. I know that the index 36 packets have something to do with vorbis and those are the only packets I'm not too sure of. Client->Server Client Packets Server->Client Server Packets Also some eye opening information as to how frameworks like Matrix do not utilize all the bandwidth saving and efficient "update zone" packets. Every single framework I have seen so far only utilizes the packets jagex calls "specific" packet…

add discord od #0995

If your a dev hmu

Dumped a while ago, thought I'd share. // Dump by: Pax M {2531=4, 2532=0, 2533=Headbutt mining, 2534=-1, 2535=17083, 3303=17083, 4743=4721, 3304=-1, 3306=1, 3307=You begin bashing at the rock with your dense skull.} {2531=4, 3363=0, 2532=0, 2533=Chi-Blast Mining, 2534=-1, 2535=17310, 3303=17310, 2536=17312, 3304=3304, 2537=72910, 3306=1, 3307=You begin to chi-blast the rock.} {2531=4, 2532=0, 2533=Blast Mining, 2534=-1, 2535=17947, 3303=17947, 2536=17949, 3304=241, 2537=79543, 3306=1, 3307=You begin to blast the rock., 2540=200, 3320=3918} {2531=4, 2532=0, 2533=Strongarm Mining, 2534=-1, 2535=20284, 3303=20284, 2536=20285, 3304=3998, 2537=72130, 3306=1, 3307=Yo…

Now I'm sure tons of you have seen ganodermic beasts, new chickens, and grotworms sliding around in a T-Pose when they should be animating while walking. I am sure some of you have seen this wonky hardcode fix going around (this example is from Matrix 3's polypore npc code) @Override public void processMovement() { super.processMovement(); if (realId == 14696 && getNextWalkDirection() != -1) { this.setNextAnimation(new Animation(15465)); this.setNextForceMovement(new NewForceMovement(this, 1, null, 0, Utils.getAngle(Utils.DIRECTION_DELTA_X[getNextWalkDirection()], Utils.DIRECTION_DELTA_Y[getNextWalkDirection()]))); } } …