[idontwantto]

RuneMate Version: v4.17.10 (Game API 1.38.16)

Error:
java.lang.IllegalArgumentException: Width is 0, but width must be greater than 0.
at com.runemate.game.api.hybrid.local.hud.InteractableRectangle.<init>(InteractableRectangle.java:23)
at com.runemate.game.api.hybrid.local.hud.InteractableRectangle.<init>(InteractableRectangle.java:17)
at com.runemate.game.api.hybrid.local.hud.interfaces.InterfaceComponent.getBounds(InterfaceComponent.java:59)
at com.runemate.game.api.hybrid.local.hud.interfaces.InterfaceComponent.getInteractionPoint(InterfaceComponent.java:407)
...
at com.runemate.game.events.osrs.OSRSLobbyHandler.run(OSRSLobbyHandler.java:47)
at com.runemate.game.api.script.framework.LoopingBot.run(LoopingBot.java:78)

 

[american express]

Just a heads up, this gets asked a lot. When the game updates, it can break RuneMate. That’s normal. This has been happening since the very first RuneScape bot was ever published in the 2000s.

RuneMate is like a remote control, and the game client is the TV. When the game updates, it’s like the TV suddenly changes how it receives signals - so the remote stops working.

Then a developer has to reprogram the “remote” so it can talk to the updated game again. That takes time, and there’s no ETA given on how long it can take to resolve.

This is a very normal part of botting on OldSchool RuneScape.

Best thing you can do is keep an eye on the Discord for updates - that’s where you’ll hear about it first: Join the RuneMate Discord Server!

 

[party]

Should be fixed in the next 20 mins!

 

[idontwantto]

fantastic, i appreciate the info! new to the dev side. In the future are the errors after update wanted and if so whats the preferred method to get it to you?