[scenario]

Hi, so recently i haven't been able to use any of the bots i've tried. I have tried Cooking, Fletching, Fishing, Smithing, Thieving, Mining etc. and none of them seems to work. I have tried different bot authors without luck either. I was just wondering if anyone else have experienced the same issue? Im in desperate need of help!

I have tried uninstalling RuneMate completely but it didn't resolve the problem.

 

[cloud]

Are there any exceptions?

 

[jjaykus]

Hi, so recently i haven't been able to use any of the bots i've tried. I have tried Cooking, Fletching, Fishing, Smithing, Thieving, Mining etc. and none of them seems to work. I have tried different bot authors without luck either. I was just wondering if anyone else have experienced the same issue? Im in desperate need of help!

I have tried uninstalling RuneMate completely but it didn't resolve the problem.

same problem

 

[arbiter]

@scenario @jjaykus

What bot are you guys running that triggered this? Did you restart RuneScape after updating?

Also can you provide the full error message? You can find the log files from Help > View Logs in the main menu.

 

[scenario]

@scenario @jjaykus

I have had the problem for weeks now, so i dont think its because of updates. I have tried several different bots, but with same problem. I can try an upload a couple of logs.

These are just some of the ones i have had issues with.

 

[arbiter]

@Cloud

 

[cloud]

I have had the problem for weeks now, so i dont think its because of updates. I have tried several different bots, but with same problem. I can try an upload a couple of logs.

These are just some of the ones i have had issues with.

Those logs didn't really show much (although it looks like it failed to setup a few callbacks on RS3). Could you send over respective RuneMate.log files, shared.log files, and anything else that may have logging from those sessions.

 

[scenario]

Not sure which files to upload. Perhaps these?

 

[ponasdievas]

Same here. Also waiting for fix 3 weeks. I have issue on all 3 PCs

 

[mangofam]

Not sure which files to upload. Perhaps these?

These are the files he needs yeah. Goodluck on getting it fixed, I don't know enough to help you sadly.

 

[cloud]

Not sure which files to upload. Perhaps these?

You may want to contact those bots authors.

 

[scenario]

You may want to contact those bots authors.

I tried contacting one of them but no matter what he did, he could not replicate the errors i was getting.
 
I tried with Galaxy Fisher as well now, but without any luck. Here is the logs.
 
Bump. Still need help!

 

[whuutever]

My spectre wont launch a client...or scan for the open one. idk

 

[oooooooos]

regal miner paid version won't bank ores at all just gets stuck however when i manually go to the bank and bank it will return to the mining spot any help greatly appreciated

 

[scenario]

Dont know if the issues above is associated with my issues, but i still need help. I have money on my RuneMate account as well, so it kinda sucks not to be able to use them.

 

[oooooooos]

i know what you mean so do i mate I'm still using it lol just manually banking

 

[johnbuell]

None of the following bots are working. They either crash or don't interact with Runescape at all.

Alpha Fighter
ApexMiner
ApexSmither
Nano Crafting
Nano Dungeoneering
Nano Fletching
QuickChopper

Below is an example of a crash.


java.lang.NullPointerException
at author.IIIiIIIIii.break(ab:185)
at author.iiIiIiIiII.failureTask(lb:150)
at com.runemate.game.api.script.framework.tree.TreeBot.onLoop(vqc:128)
at com.runemate.game.api.script.framework.LoopingBot.run(pfc:53)
at com.runemate.game.api.script.framework.AbstractBot.start(llc:395)
at nul.IIIIIIiiIIiIi.run(tad:107)

 

[oooooooos]

yoooooooos

 

[johnfuckingdenver]

no bots will walk on their own or bank but if i walk to bank the bot opens bank for me

several bots ive tried all have the same problem, is there fix?

 

[scenario]

Im still looking for a fix as well. No one seems to know how to fix it :/
 
The issue seems to have resolved itself now, i guess updates of the client might have had a influence.