Welcome!

EthanOpia updated OpiaSpiritualMages with a new update entry: OpiaSpiritualMages v1.0.6 Released! Read the rest of this update entry...

EthanOpia updated OpiaWineGrabber Lite with a new update entry: OpiaWineGrabber Lite v2.2.4 Released! Read the rest of this update entry...

EthanOpia updated OpiaWineGrabber with a new update entry: OpiaWineGrabber v2.2.4 Released! Read the rest of this update entry...

EthanOpia updated OpiaSpiritualMages with a new update entry: OpiaSpiritualMages v1.0.5 Released! Read the rest of this update entry...

EthanOpia updated OpiaTelegrabLeveler with a new update entry: OpiaTelegrabLeveler v1.2.5 Released! Read the rest of this update entry...

EthanOpia submitted a new resource: OpiaTrollKiller - Levels accounts by killing trolls Read more about this resource...

EthanOpia submitted a new resource: OpiaWineGrabberUltra - Telegrabs wines for ~900k-1.1m PH Read more about this resource...

The starting a new instance code is already implemented. The code to bind a client to a bot is implemented. The code to check if a session is over is implemented. How much do you actually value the time it would take to combine them? I know I would be buying a lot more hours if I could code this...

Raising the dead because I was about to request this same feature. With the existing ability to change the bot alias we are using, we could have a bot switch aliases, but never need to restart the bot.

Did closing and restarting your RuneMate client fix the problem?

I had the exact same thing happen to me this morning. Turns out the problem is that you did not restart your RuneMate client after the Runescape update. Restarting the RuneMate client should fix this problem. It is not a bot problem.

Nothing shows up in the runemate log except a connection refused by host error after the RS client crashes. After research, I think it might be this: r/runescape - RS Client Crash when world hopping. I've lowered my memory allocation down to what that thread recommends and will post again if...

I've added a world hopping mechanism to my bot using WorldHop.hopTo(); I've noticed that it crashes the RS3 client about 50% of the time. I've tried increasing Java's memory, increasing RuneMate's memory, and increasing RuneScape's memory. None of those have fixed the problem. Any idea what...

I've got RuneMate credits and looking to trade them for RS3 gp. PM me the number of millions you are willing to trade and how much RuneMate credits you expect per million. If your offer is fair, I will message you back.

np, glad you got it fixed.

The bot doesnt go kill mages, it just stands still and ?? is displayed forever? Sounds like it got stuck loading the character's levels or could not detect the player.

It should be ?? until the bot starts running. If it stays ??, but is actually doing the tasks, the UI had some problems loading.

EthanOpia updated OpiaTelegrabLeveler with a new update entry: OpiaTelegrabLeveler v1.2.4 Released! Read the rest of this update entry...

EthanOpia updated OpiaWineGrabber with a new update entry: OpiaWineGrabber v2.2.3 Released! Read the rest of this update entry...

EthanOpia updated OpiaWineGrabber Lite with a new update entry: OpiaWineGrabber Lite v2.2.3 Released! Read the rest of this update entry...