[aidden]

@Cloud

java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
 java.net.SocketException: Connection reset
 at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
 at sun.rmi.server.UnicastRef.invoke(Unknown Source)
 at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Unknown Source)
 at java.rmi.server.RemoteObjectInvocationHandler.invoke(Unknown Source)
 at com.sun.proxy.$Proxy8.fp32(Unknown Source)
 at nul.iiiiIIiiIIIi.getHighPrecisionPosition(fob:154)
 at nul.iIIIiIiIIiii.getHighPrecisionPosition(cvb:141)
 at nul.iiiiIIiiIIIi.getPosition(fob:47)
 at nul.iIiiiIiIIIIi.const(svb:141)
 at nul.iIiiiIiIIIIi.const(svb:7)
 at com.runemate.game.api.hybrid.region.Region.getCollisionFlags(hi:72)
 at com.runemate.game.api.hybrid.location.Coordinate.getReachableCoordinates(fhc:51)
 at com.runemate.game.api.hybrid.location.navigation.web.WebPath.getNext(wdc:161)
 at com.runemate.game.api.hybrid.location.navigation.web.WebPath.step(wdc:39)
 at com.runemate.api.Walking.walkTo(Walking.java:62)
 at com.runemate.api.Walking.walkTo(Walking.java:38)
 at com.runemate.maxibots.looping.woodcut.MaxiWoodcutter.chop(MaxiWoodcutter.java:210)
 at com.runemate.maxibots.looping.woodcut.MaxiWoodcutter.onLoop(MaxiWoodcutter.java:127)
 at com.runemate.api.framework.MaxiLoopingScript.run(MaxiLoopingScript.java:21)
 at com.runemate.game.api.script.framework.AbstractScript.start(bvb:1)
 at nul.iiiiiIiiIIii.run(dzb:225)
Caused by: java.net.SocketException: Connection reset
 at java.net.SocketInputStream.read(Unknown Source)
 at java.net.SocketInputStream.read(Unknown Source)
 at java.io.BufferedInputStream.fill(Unknown Source)
 at java.io.BufferedInputStream.read(Unknown Source)
 at java.io.DataInputStream.readByte(Unknown Source)
 ... 21 more
2.0.1.1 - RS3

 

[cloud]

This looks like the result of someone manually starting a game client and then running spectre for the first time. The first time spectre binds to a client, it needs to be started before the game client. After that the order doesn't matter.

 

[arbiter]

This looks like the result of someone manually starting a game client and then running spectre for the first time. The first time spectre binds to a client, it needs to be started before the game client. After that the order doesn't matter.

Can we catch, show an appropriate error to the user, and then suppress from Exception Log?

 

[cloud]

Our usage of Lomboks sneaky throws makes it so that we can't catch it.

 

[aidden]

Suppressed in V2.0.3