Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Yamumsohard

Burning my main anyideas

Recommended Posts

Posted (edited)

Hey there community, i'm pretty much going to either bot it to death or give out for scripting purposes, vorkath bot? lol. Any ideas what to bot? It's max melee, almost range and mage with 96 slayer. Only reason i''m doing this is im over the boring grind, raids just arnt that great and the game itself is kinda boring lol

Edited by Yamumsohard

Share this post


Link to post
Share on other sites

I feel the exact same way with my account. Any GP I make I go to the duel arena with but I don't think I would ever bot it for the simple reason I know i'll always return. I have an ironman which is 100% botted just to skip the early grind. I find the most fun personally when I'm questing. I quested a 1 defence pure. Got all the stats I could from questing then the next part for me is just boring af. literally sat there for hours and hours grinding or afking. I just cba with it but I know I'll always come back. If you're 100% sure and don't think you'll return/don't care about the account use Worthy's zulrah script.

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

Thanks for all the reply, yeah I feel like the only time I enjoy the game is the early grind which is nice for me, almost completely maxed rs3 too while I was at it. But I think imma just death bot it with zulrah like you say and get as much gp out of it, I got 150 more losses than wins at da lol, and I don't like the idea of selling it too

Edited by Yamumsohard

Share this post


Link to post
Share on other sites
21 minutes ago, Yamumsohard said:

Just don't enjoy the game like I used to and prefer not to bot the starting off lol, I'll put up a log sometime 

You'll 100% get banned botting Zulrah, instead buy a throwaway account or make a new account and test certain scripts that you can use to bot your main. I enjoy getting x amount of 99s rather than botting to make gp. Not worth the time or risk of ruining a max main.

Share this post


Link to post
Share on other sites
7 minutes ago, Takesoul said:

You'll 100% get banned botting Zulrah, instead buy a throwaway account or make a new account and test certain scripts that you can use to bot your main. I enjoy getting x amount of 99s rather than botting to make gp. Not worth the time or risk of ruining a max main.

Fair yeah, I got 2 med levels almost mains think I'll burn them first and I'll probably post results 

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/30/2019 at 5:07 PM, xanaxna said:

bot i know that work, naton , nnightmare zone, nmagic, nblast furnace 

Lol i might actually do the blast furnace! actually nb idea man. But i got temp banned a little while ago, made like 70m hopefully it'll keep going without a ban again soon

Edited by Yamumsohard

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • This update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
        • Like
      • 150 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 68 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...