Thread: Dwarf Multicannon, logout on firing

Originally Posted by Armo

@OP

Try adding cannon == null and rotation == null to the top of rotate method

Also post your player.getPA().object method

Replace your rotate method with this see if it helps

Code:

private void rotate(GlobalObject cannon) {
        if(cannon == null || rotation == null)
            return;
        switch (rotation) {
            case NORTH:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 516, 10, -1);
                break;
            case NORTH_EAST:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 517, 10, -1);
                break;
            case EAST:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 518, 10, -1);
                break;
            case SOUTH_EAST:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 519, 10, -1);
                break;
            case SOUTH:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 520, 10, -1);
                break;
            case SOUTH_WEST:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 521, 10, -1);
                break;
            case WEST:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 514, 10, -1);
                break;
            case NORTH_WEST:
                player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 515, 10, -1);
                rotation = null;
                break;
        }
    }

There would be a NPE if the cannon was null.

Originally Posted by Tyluur

There would be a NPE if the cannon was null.

Well then all that's left is whatever is being sent in the player.getPA().object method

Originally Posted by Armo

Well then all that's left is whatever is being sent in the player.getPA().object method

Yeah, if its an out of bounds exception, maybe it's the -1 value?

Originally Posted by soar

The rotating of the cannon is just animating the cannon for the current rotation direction, it looks like you're sending a new object every tick.

Can you post the object method in player.getPA().object

player.getPA().object(cannon.getPosition().getX(), cannon.getPosition().getY(), 516, 10, -1);

The 516 is the animation but could potentially be out of bounds for whatever the correct parameter is supposed to be there.

Guys I already posted this on the last page but you drowned it out.

Originally Posted by soar

Guys I already posted this on the last page but you drowned it out.

^

A bunch of spam aside from this. T2 errors, as most of us know, are corrupt packets. The +-515 ids clearly refer to cannon rotation animation(clear to me at least, despite having written the cannon years ago). This is more than likely caused by the object animation packet not being configured correctly server-side. You'll have to find this packet in the client and match it up to the server.

Either way, show the packet(and the object method) in here. Perhaps some basic googling will be able to find you the correct packet configuration.

From my experience, it could actually be that the packet is colliding with another packet (Happens when multiple packets being sent)

It's possible since the object/cannon function worked fine before?

Also did you change anything in the cache that could be a factor

Originally Posted by Armo

From my experience, it could actually be that the packet is colliding with another packet (Happens when multiple packets being sent)

It's possible since the object/cannon function worked fine before?

Also did you change anything in the cache that could be a factor

Perhaps packet fragmentation could've played a part in this - the multiplexing procedure could've been poorly written in the server.
Can op show the multiplexing procedure?