Realm Relay /tq

**Nisuxen** · 10-17-2013

People seemed interested and I had a spare 30 minutes. On a side note, anyone know how to manipulate quiver or shuriken shots? They use both the use item packet and the player shoot packet. Changing the location in the former and the angle in the latter doesn't seem to do anything.

Code:

// tq.js

var ID_CREATE_SUCCESS = 47;
var ID_PLAYER_TEXT = 80;
var ID_UPDATE = 66;
var ID_TELEPORT = 67;
var ID_NEW_TICK = 50;
var ID_QUEST_OBJECTID = 48;

var questObjectId = -1;
var questLoc = null;
var playerLocs = {};
var myId = -1;

function onClientPacket(event) {
	var packet = event.getPacket();
	switch (packet.id()) {
		case ID_PLAYER_TEXT: {
			var text = packet.text.toLowerCase();
			if(text == "/tq"){
				event.cancel();

				if(questObjectId == -1 || questLoc == null){
					break;
				}
				var minDist = questLoc.distanceSquaredTo(playerLocs[myId]);
				var toTp = myId;
				for(var player in playerLocs){
					var distToQuest = questLoc.distanceSquaredTo(playerLocs[player]);
					
					if(distToQuest < minDist){
						minDist = distToQuest;
						toTp = player;
					}
				}
				if (toTp != myId){
					//send tp packet
					var tp_packet = event.createPacket(ID_TELEPORT);
					tp_packet.objectId = toTp;
					event.sendToServer(tp_packet);
					break;
				}
			}
			break;
		}
	}
}

function onServerPacket(event) {
	var packet = event.getPacket();
	switch (packet.id()) {
		case ID_CREATE_SUCCESS: {
			myId = packet.objectId;
			break;
		}
		case ID_UPDATE: {
			// New objects
			for (var i = 0; i < packet.newObjs.length; i++) {
				var objectData = packet.newObjs[i];

				var type = objectData.objectType;
				if(type == 768 || type == 775 || type == 782 || type == 784 || (type >= 797 && type <= 806)){ // player classes
					playerLocs[objectData.status.objectId] = objectData.status.pos;
				}else{
					if(objectData.status.objectId == questObjectId){
						questLoc = objectData.status.pos;
					}
				}
			}

			// Removed objects
			for (var i = 0; i < packet.drops.length; i++) {
				var droppedObjectId = packet.drops[i];

				if(playerLocs[droppedObjectId] != null){
					delete playerLocs[droppedObjectId];		
				}
				else if(droppedObjectId == questObjectId){
					questObjectId = -1;
					questLoc = null;
				}
			}
			break;
		}
		case ID_NEW_TICK: {
			for (var i = 0; i < packet.statuses.length; i++) {
				var status = packet.statuses[i];

				for (player in playerLocs){
					if(status.objectId == player){
						playerLocs[player] = status.pos;
						break;
					}
				}
			}
			break;
		}
		case ID_QUEST_OBJECTID: {
			questObjectId = packet.objectId;
			break;
		}
	}
}

**DeVoidCoder** · 10-17-2013

Thanks, it looks good. I have a few minor suggestions.

This bit of code has no effect because newObjs will never be null. If there is nothing in it, it will have a length of 0.

Code:

if(packet.newObjs == null)
	break;

Instead of using distanceTo, since you don't really need to know exactly what the distance is, you could use distanceSquaredTo. The difference being that the square root operation is not performed. It is an insignificant optimization in this case, but I just wanted you to know for the future in case you do some heavier processing to do with distance.

**Nisuxen** · 10-17-2013

Originally Posted by DeVoidCoder

Instead of using distanceTo, since you don't really need to know exactly what the distance is, you could use distanceSquaredTo. The difference being that the square root operation is not performed. It is an insignificant optimization in this case, but I just wanted you to know for the future in case you do some heavier processing to do with distance.

I appreciate the insight. It's a nasty habit of mine to null check incessantly due to other javascript projects I've worked on. I suspected it was unnecessary but didn't bother checking.