[aidden]

java.lang.IllegalStateException: Cannot get an instance value from an instance of a non-assignable type (WidgetNode.id)
 at app.zP.goto(spb:60)
 at app.zP.goto(spb:262)
 at app.zP.goto(spb:80)
 at com.runemate.game.api.hybrid.local.hud.interfaces.InterfaceComponent.true(gxb:92)
 at com.runemate.game.api.hybrid.local.hud.interfaces.InterfaceComponent.getBounds(gxb:126)
 at com.runemate.game.api.hybrid.local.hud.interfaces.InterfaceComponent.getBounds(gxb:260)
 at app.gp.goto(mgc:97)
 at com.runemate.game.api.hybrid.Projection.coordinateToMinimap(yac:48)
 at com.runemate.game.api.hybrid.location.Coordinate$MinimapCoordinate.getInteractionPoint(bfc:540)
 at com.runemate.game.api.hybrid.location.Coordinate$MinimapCoordinate.getInteractionPoint(bfc:1097)
 at com.runemate.game.api.hybrid.location.Coordinate$MinimapCoordinate.contains(bfc:1705)
 at app.fQ.goto(wec:75)
 at app.fQ.goto(wec:265)
 at app.fQ.move(wec:212)
 at com.runemate.game.api.hybrid.input.Mouse.move(wg:181)
 at com.runemate.game.api.hybrid.input.Mouse.move(wg:90)
 at com.runemate.game.api.hybrid.input.Mouse.click(wg:32)
 at com.runemate.game.api.hybrid.location.Coordinate$MinimapCoordinate.click(bfc:769)
 at com.runemate.game.api.hybrid.location.Coordinate$MinimapCoordinate.interact(bfc:1795)
 at com.runemate.game.api.hybrid.location.navigation.basic.BresenhamPath.step(kdc:152)
 at com.runemate.game.api.hybrid.location.navigation.Path.step(qyb:167)
 at com.runemate.maxiscripts.looping.woodcut.MaxiWoodcutter.chop(MaxiWoodcutter.java:242)
 at com.runemate.maxiscripts.looping.woodcut.MaxiWoodcutter.onLoop(MaxiWoodcutter.java:157)
 at com.runemate.game.api.script.framework.LoopingScript.run(ctb:47)
 at com.runemate.game.api.script.framework.AbstractScript.start(fxb:122)
 at app.jm.run(ypb:270)
Caused by: java.lang.IllegalStateException: Cannot get an instance value from an instance of a non-assignable type
 at app.zP.goto(spb:1541)
 at app.zP.goto(spb:75)
 ... 25 more

2 days ago
@Cloud

 

[cloud]

Looks like a mismatched hook somewhere, but the logging in this version for that specific error isn't good enough to resolve it. Let's hope it doesn't happen again, but if it does the next release will have more information.