Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!
It won't repair the strut when it's not working. I put a hammer in my inventory and the bot just dropped it. And I'm not seeing an option for repair. Am I doing something wrong?
cuppajava
cuppajava
It should definitely be repairing the strut. But it'll only do so if there's already ore in the waterway that it needs to move through to deposit more or collect.

It drops the hammer because you don't need on at all times. If it needs it, it can collect one from the crate.

There's no option to repair because that's the default behavior. There is a toggle for world hopping instead of repairing though if you want.

Sounds like everything is working as intended :) But feel free to dm me with any other concerns.

And please consider writing an updated review if everything is working properly for you, as I think it is.
Botted 30-99 no issues. Awesome script. Only suggestion is for jagex launcher, when it gets 6 hour log it usually gets stuck and wont log back in.
cuppajava
cuppajava
<3

That is strange, although honestly logging back in is handled by Runemate/the client itself and may have some quirks with the launcher.

It's possible this can be avoided by taking breaks slightly more often to avoid the 6 hour log?

Either way I can try to look into it, and I'm glad it's working well for you overall.
Used just for Prospector on one and prospector/~70-99 on another.

I kept the accounts on the lower level just to avoid conflict, worked like a dream :) Another quality Cuppa bot
70 - 99 done. No bans! Smooth like a criminal.
I've used it for around 10 hours total now and I'm happy overall. There are a few small things I wish were improved:
- slightly faster wheel repair, for example one time someone was ahead of me at repairing and the bot stood still at the wheel for several seconds instead of just moving on
- an option to repair both wheels instead of one because even though it's less efficient, it's what most players will naturally do including myself
- slightly faster ore banking and more accurate clicks (this could be on my end), if the bot misclicks the cart, sack or deposit box it will sit a bit too long next to it

Other than those small things, it's really another great Cuppa bot. It reacts very well to other players mining at the same spot.
Is it possible to make it avoid veins near other players as well? Looks weird if i mine right next to a guy.
cuppajava
cuppajava
Hey, so the bot uses a pretty complicated & robust system where it will pick a pseudo random wall based off a lot of factors like:
- players nearby
- distance to walls
- rocks to mine on the way
- being on the same surface
- etc

The bot will pretty much never mine the *same* wall as another player downstairs, as it depletes faster. But it will sometimes mine a wall near someone else if it's randomly selected/nearly optimal, as it doesn't inconvenience them.

It's aiming to be human like, and lots of players will mine near-but-not-on other players, some of the time.
52-99 mining achieved. This is a very reliable bot. I really like the break enabler, it really helps staying under the radar imo.
Very solid sript, no issues. Nothing ele to say.
Having issue with banking. Ran few times and doesn't seem to? issue on my end?
cuppajava
cuppajava
Hey, the bot should definitely be working. This may be a temporary Runemate issue?

Often these kinds of issues can be fixed by restarting OSRS & Runemate (or your PC). Also make sure to disable any plugins which may be interfering with the bot.

Feel free to test using the lite version so you don't get charged, and let me know if the issue persists.
Great script, no issues running it for the entirety of the time in Motherlode. No effort for 380 golden nuggets.
perfect
Great script for MLM - I'm a man of maximising xp/hr so this isn't my go to script for fast mining levels however on my road to maxing my account I used this to unlock everything MLM had to offer in approx 36 hours 1 go no breaks.
Does this wash ore? and Bank? Cheers
cuppajava
cuppajava
Yeah. Mines it, washes, banks. Supports all the unlocks etc too.
30-99 without any ban
30-80 With it, 0 issues so far. Solid bot
cuppajava
cuppajava
<3 <3 <3
Amazing script. Left it running 16 hours per day (regular hours everyday, no switching it up) with breaks on/random afks on. 70-99 mining in around 364 hours, no issues. Cuppa is a beast.
cuppajava
cuppajava
<3 <3 <3
63-94 never ban and never problems
Worked great for a few days but was hit with a ban. Only botted it a few hours aday on that account but last couple times I left it alone i came back and was logged out due to 5 minutes of inactivity so seemed to of kept getting stuck which probably led to the ban
cuppajava
cuppajava
Hey, I'm sorry you got banned. Unfortunately, despite our best efforts, this is always a possibility.

Have you botted on the account before? It's always possible for Jagex to use delayed bans.

For whatever it's worth, I don't think the idling randomly would cause Jagex to become suspicious honestly. I understand it's annoying when bots aren't working correctly, but from Jagex's side it'd just look like you got up and stopped playing & afk'd logout.
10/10 bot, but it needs a update, it's glitched at the withdrawl sack, & gets stuck (just started today)
cuppajava
cuppajava
Runemate was broken today due to a Runelite update, but client devs have fixed it, so it should be working again if you restart osrs & RM.

If issues persist, please feel free to DM me.

If the bot works for you again, please consider writing an updated review :)
DO NOT use the diary shortcut area. I came back to people talking about me being a bot because it just runs back and forth. Ban likely incoming. Other than that, the other areas work well.
cuppajava
cuppajava
Hi, I'm really sorry the bot did that. Hopefully it works out fine; Honestly it might, sometimes Jagex just doesn't pick up on seemingly obvious bot behavior.

Do you know if it seems to happen every time using the shortcut? Can you dm me a log (found in help > view logs) of the session where this happened? I'd like to get it fixed, but I often can't reproduce these types of bugs.
Top