Cuppa MotherlodeMine [LITE] 1.4.81

The only MLM you can trust.

  1. CuppaJava
    Basically the exact same thing as Cuppa MotherlodeMine[Premium] except with a 2 hour weekly limit.

    For more info or how to use the bot, see the premium version page.
    emensity and guapgecko like this.

Recent Reviews

  1. Kyla717
    Kyla717
    3/5,
    Version: 1.4.74
    Worked nicely but received a perma-ban in less than 1 hour.
    1. CuppaJava
      Author's Response
      I'm sorry you got banned. Unfortunately, despite my best efforts, bans are always a possibility, as you know.

      If you have any further feedback on specific ways you think the bot could be improved/to reduce risk (eg. unnatural behavior or getting stuck at all), please feel free to let me know. Otherwise it's a bit tough for me to make actionable changes.
  2. Leafy
    Leafy
    3/5,
    Version: 1.4.67
    Great bot. Used for 1.5 hours and got banned.
  3. Tyrasehexeg
    Tyrasehexeg
    3/5,
    Version: 1.4.67
    bot gets stuck when starting "unloading ores"
    1. CuppaJava
      Author's Response
      Hi :) The bot seems to be working for me, sometimes it can have these temporary bugs though.

      If you're botting on RuneLite, please try using the regular client, as RuneLite support still has some bugs.

      Otherwise, this sounds like the type of issue that is usually a temporary Runemate bug, often cache related. You may be able to fix it by restarting OSRS & Runemate before trying the bot again. Otherwise, try clearing your OSRS game cache & restarting OSRS/Runemate again (instructions on this page https://support.runescape.com/hc/en-gb/articles/360001441169-How-to-clear-your-cache-#OSWin).

      If the issue persists or this doesn't help, let me know.
  4. lmao3cb
    lmao3cb
    4/5,
    Version: 1.4.61
    Been running other bots this week with no issues, go to start this one today and it disconnects right away, even after trying all the fixes. Worked before so i give 4 star
  5. delabyss
    delabyss
    5/5,
    Version: 1.4.59
    Ran this for 40 hours on my main. No bans, got full prospector. Flawless script.
  6. A_moneyy7
    A_moneyy7
    3/5,
    Version: 1.4.34
    Everytime I start the bot, it gives a red warning saying "No pickaxe detected" and closes bot. Worked great up until this happened.
    1. CuppaJava
      Author's Response
      Hey :) The bot does definitely work, this bug is a temporary bug with Runemate that happens rarely. What's happening here is that Runemate is unable to detect the inv/equipment items.

      Often issues like this can be fixed by restarting both OSRS & Runemate and trying again, especially after game updates.

      But if that doesn't work you can also try clearing your game cache by:
      1) Closing OSRS/Runemate
      2) Clear your OSRS game cache
      3) Open OSRS & Runemate back up
      On windows, the OSRS cache can be found by clicking start and pasting into the search bar:
      %USERPROFILE%\jagexcache\oldschool\LIVE

      Feel free to pm me or post on the thread if you have more issues.

      Don't forget to update or add a new review if when works for you again ;)
  7. djmargus
    djmargus
    5/5,
    Version: 1.4.31
    20,5 mil xp now @ main acc =) and another account 87 mining =)
  8. Varonico
    Varonico
    5/5,
    Version: 1.4.11
    great bot ty
  9. Bayern11
    Bayern11
    3/5,
    Version: 1.4.2
    Had the same issue as zylice, tried the bot and came back to see it has been dropping and picking up pay dirt for at least 10 minutes in the 3rd trip when the bag is 3/4 full.
    1. CuppaJava
      Author's Response
      This is a known bug right now. It will be fixed in the next update. There's a fix in queue right now, should be approved within the next day or two :)
  10. Depth
    Depth
    4/5,
    Version: 1.4.2
    solid bot script, but it got stuck dropping pay dirt in the lower west when the sack was full when i came back after letting it run for 15 minutes, dont know what caused it
    1. CuppaJava
      Author's Response
      Ah yes, this is a known bug right now. It will be fixed in the next update. There's a fix in queue right now, should be approved within the next day or two :)