Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
Grooms

Why is nobody discussing a revenant bot?

Recommended Posts

3 minutes ago, Grooms said:

As the title states... 

Mainly because it would have to support anti-pk. Since there is so many people, combat level based anti-pk (player combat level +/- wilderness level = enemy combat level) will not work, even if it did, it would spend more time hopping than actually getting profit. And with more people there, the gp/hr varies since you won't always get the kill. If you want a equipment based anti-pk (if they are wearing this equipment = log out/world hop), the gear people use mainly for pking is black d'hide, which is also the main gear that people use at rev caves. Sadly, if you want one without anti-pk, you would render yourself very vulnerable. Possibly even lose money from it. If there are any other type of anti-pk let me know.

Share this post


Link to post
Share on other sites
23 minutes ago, Grooms said:

You have a very valid point. However, how do green dragon bots combat the same issue? 

It's a shame :( could be insane loot with low requirements - perhaps with low level accounts less susceptible to pkers? Say around level 20-40 killing the lower level revs

I've messed around with it, and with how crowded it is, you need to be using 90+ range accounts minimum or you don't get any kills. Perhaps you could camp the spawn of the ones with 15-20hp or so and hope you hit it first, but even then.

Surprisingly, you don't get pked that much. (for me it was about once per hour that I'd die). The real problem is world-hopping. You have to world-hop at the first sign of a pker, and you spent easily 1/4 of the time world-hopping. That said, it's still really profitable.

Most of my deaths were from getting tele-blocked from non-skulled players, or if I happened to be in combat and the script was unable to log off fast enough.

Green drag bots combat the issue by not being in multi-combat. It's less popular to pk green dragon bots, and you generally have less GP in the inventory. It's lower wilderness too, and because it's single target, they have to choose between TB/Ancients. If they freeze you, you insta tele out. If they TB you, you pray mage and start running.

Share this post


Link to post
Share on other sites

I think it is because it would be very hard to make a rev bot that actually looks like a human playing. Think about how much more vulnerable you are at revs than killing green drags or something. Its also multi combat.

Edited by Naton

Share this post


Link to post
Share on other sites
1 hour ago, Grooms said:

You have a very valid point. However, how do green dragon bots combat the same issue? 

It's a shame :( could be insane loot with low requirements - perhaps with low level accounts less susceptible to pkers? Say around level 20-40 killing the lower level revs

Well, the people have answered your question. What both of them said are true. I wouldn't do revs with a bot sadly. I haven't personally done it but there are too many factors to consider and obviously you get unlucky at times. Even with death walk, if they know you are coming back, you will be fucked until you world hop. World hop too much then you have cool down. What i saw was if you are a pretty maxed main, go in black d hide and elder maul, you hit pretty high on first hit and can cause you to get kill a lot of the time. This method was tested by nothinglasts on youtube.

Share this post


Link to post
Share on other sites

At one point in time i guess a Rev bot would be a completely viable option, but as of right now, the cave is waay too packed to make it in any shape or form profitable with a script. I mean, i don't even know the first thing about coding, but that just came as common sense. Also on the Green dragons bots, they are essentially pretty dead content by now, and it's easy to kill them without losing that much on death/not losing anything at all.

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.

Sign in to follow this  

  • Our picks

    • 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
      • 61 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
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



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

    No registered users viewing this page.

×
×
  • Create New...