Thread: Dwarf Multicannon, logout on firing

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.

Originally Posted by Tyluur

Nah that'll be a lot harder to find the error prone lines.

I was thinking of adding a try exception to where the error occurs, sometimes a cheap fix for client-disconnect issues.

And if the try exception stops a feature from working, it narrows it down to what is actually causing the error.

Originally Posted by Armo

I was thinking of adding a try exception to where the error occurs, sometimes a cheap fix for client-disconnect issues.

And if the try exception stops a feature from working, it narrows it down to what is actually causing the error.

In my experience it's better to get directly to the root cause of the issue. Sometimes you forget that you cheap-fixed something and it impacts another process later on.

Originally Posted by Tyluur

In my experience it's better to get directly to the root cause of the issue. Sometimes you forget that you cheap-fixed something and it impacts another process later on.

Well maybe he should at least try it and see if it stops a function of the cannon, that would narrow down exactly what is causing it and the line of code to look at then remove the try exception after

Originally Posted by Armo

Well maybe he should at least try it and see if it stops a function of the cannon, that would narrow down exactly what is causing it and the line of code to look at

You guys aren't helping, this has nothing to do with the client at all.

Originally Posted by soar

You guys aren't helping, this has nothing to do with the client at all.

If the client is dropping that means you can look at the client and pinpoint what error the server is causing..

Originally Posted by Armo

Well maybe he should at least try it and see if it stops a function of the cannon, that would narrow down exactly what is causing it and the line of code to look at then remove the try exception after

That's one solution. Personally I would've gone through the stacktrace and figured out what packet I'm sending from the server to the client that causes the crash.

Originally Posted by Armo

If the client is dropping that means you can look at the client and pinpoint what error the server is causing..

It's dropping because of an out of bounds exception, which means the server is incorrectly sending something to the client, so how does looking at the client code help fix the issue of the server shitty code?

Originally Posted by soar

It's dropping because of an out of bounds exception, which means the server is incorrectly sending something to the client, so how does looking at the client code help fix the issue of the server shitty code?

You can find what server code is being sent if you look at the client code.