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

Assume Staker ONE HOUR FREE TRIAL [-2.147B - 2.147B/HR][40B+Profit][116Hr+][DDS/Whip/Box/Scim]

Recommended Posts

An extremely important new change to combat that affects staking is the fact that PID changes every few minutes now, will you be updating the script to take that into account? This has a huge influence on whether or not you win.

Edited by cybris

Share this post


Link to post
Share on other sites
2 hours ago, cybris said:

An extremely important new change to combat that affects staking is the fact that PID changes every few minutes now, will you be updating the script to take that into account? This has a huge influence on whether or not you win.

It changes literally nothing so no.

Share this post


Link to post
Share on other sites
2 hours ago, cybris said:

An extremely important new change to combat that affects staking is the fact that PID changes every few minutes now, will you be updating the script to take that into account? This has a huge influence on whether or not you win.

3 years isn't new... Unless you're referring to hasta / d war hammer which does have an impact.

Share this post


Link to post
Share on other sites

I'm referring to the fact that they literally just recently updated how PID works, so now its possible to know whether or not you have PID over someone, which determines who hits first and gives you an advantage. There are people maxing several accounts just so they can stake on whichever one has PID over their opponent.... it really does make a difference.  "instead of randomising the priority each player is given every game tick, priority is now only randomised once every 100 - 150 game ticks (60 - 90 seconds)."   http://services.runescape.com/m=news/bank-placeholders--pid?oldschool=1

Edited by cybris

Share this post


Link to post
Share on other sites
4 hours ago, cybris said:

I'm referring to the fact that they literally just recently updated how PID works, so now its possible to know whether or not you have PID over someone, which determines who hits first and gives you an advantage. There are people maxing several accounts just so they can stake on whichever one has PID over their opponent.... it really does make a difference.  "instead of randomising the priority each player is given every game tick, priority is now only randomised once every 100 - 150 game ticks (60 - 90 seconds)."   http://services.runescape.com/m=news/bank-placeholders--pid?oldschool=1

Are you saying interface checking is back like rapier staking back in 2011?  If there is no way to detect before the stake I don't see how it would matter.

Share this post


Link to post
Share on other sites

I'm not entirely sure if there is a way to tell before fighting someone, whether or not you had PID over them, but I had been told by a tribot scripter that people were making multiple staking accounts to ensure they'd use the one with PID... however like I said, Idk how you'd know.

Share this post


Link to post
Share on other sites
On 5/4/2016 at 9:02 AM, cybris said:

I'm not entirely sure if there is a way to tell before fighting someone, whether or not you had PID over them, but I had been told by a tribot scripter that people were making multiple staking accounts to ensure they'd use the one with PID... however like I said, Idk how you'd know.

I'm assuming it's just d warhammer staking so when you don't have pid in the fight you use d war hammer.  When you do have pid you just whip.  Just assuming I've been out of that world a little while.

For example when there was still a 50% chance you would have random pid it wasn't worth risking using a d war hammer.  Now that you know throughout the entire if you're not going to have pid fight it's worth using d war hammer / hasta (or d war hammer hasta even with random stakes tbh if they don't at least have a hasta).  

That would make sense.

 

I can't see the advantage of making many stakers based on the update alone  unless they just want one for every combat range.

Edited by Diabolic

Share this post


Link to post
Share on other sites

They said they updated it due to the fact that combat was more unpredictable with PID changing every few ticks, and now it changes about every minute and a half so you can more accurately pk knowing whether you have PID or not.  I just thought it was worth mentioning, since I had also heard people making accounts to make sure they had PID on one for an advantage.... not sure if they were right at all in doing this though.

Share this post


Link to post
Share on other sites
3 hours ago, cybris said:

They said they updated it due to the fact that combat was more unpredictable with PID changing every few ticks, and now it changes about every minute and a half so you can more accurately pk knowing whether you have PID or not.  I just thought it was worth mentioning, since I had also heard people making accounts to make sure they had PID on one for an advantage.... not sure if they were right at all in doing this though.

It honestly doesn't matter and is ridiculous people are freaking out about it. It is randomized before every single duel. It is not based on IP like prior.

Share this post


Link to post
Share on other sites
3 hours ago, Snailham7 said:

I'm using this scripts normally work fine, but at the moment the calculator isn't showing the stats of the opponent in the log almost like it's not looking them up successfully? any ideas buddy?

Unfortunately you didn't give me enough information to make an educated guess. My best bet is the RS high scores are down.

Share this post


Link to post
Share on other sites

would you ever consider rewriting the calculator? An account that is 80 80 80 80 dds/whipping a maxed account is going to have more then a 2.6% chance of winning. Non accurate calculator =Not possible to get stakes or make money.

 

I would buy your script every month if the calculator was actually accurate

Edited by Illuminati666

Share this post


Link to post
Share on other sites

I seem to be having a problem with this, when it gets to the second screen of the duel request it just sits there, then in the logger, it'll post:

  • [3:52:53 PM] Stopping setting listener
  • [3:52:53 PM] Stopping bet listener

Then go back to requesting things from Jagex on other players.
Probably an error on my end or something, pretty new to this.

Share this post


Link to post
Share on other sites
2 hours ago, Illuminati666 said:

would you ever consider rewriting the calculator? An account that is 80 80 80 80 dds/whipping a maxed account is going to have more then a 2.6% chance of winning. Non accurate calculator =Not possible to get stakes or make money.

 

I would buy your script every month if the calculator was actually accurate

I have no clue what you are talking about. You listed the stats of one account and a %.

Share this post


Link to post
Share on other sites
2 hours ago, Innocence said:

I seem to be having a problem with this, when it gets to the second screen of the duel request it just sits there, then in the logger, it'll post:

  • [3:52:53 PM] Stopping setting listener
  • [3:52:53 PM] Stopping bet listener

Then go back to requesting things from Jagex on other players.
Probably an error on my end or something, pretty new to this.

That is not an error. 

Share this post


Link to post
Share on other sites
7 hours ago, Assume said:

I have no clue what you are talking about. You listed the stats of one account and a %.

your calculator says a 80 atk/str/def/hp account has a 2.6% chance of winning vs a maxed account (whipping/ddsing)

 

This script could easily have 100+ users if you actually listened to other people

Edited by Illuminati666

Share this post


Link to post
Share on other sites
7 hours ago, Illuminati666 said:

your calculator says a 80 atk/str/def/hp account has a 2.6% chance of winning vs a maxed account (whipping/ddsing)

 

This script could easily have 100+ users if you actually listened to other people

I have no problem with that calculation. An account with 20+ stat advantage across every skill is a insane favorite. And once you get past ~30% chance of winning, it becomes irrelevant what the percent chance is. Variance is going to make xing worthless due to the odds of him running train on you for your stack being high. Also, no one sets their % below 50% anyway. 

Share this post


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

I have no problem with that calculation. An account with 20+ stat advantage across every skill is a insane favorite. And once you get past ~30% chance of winning, it becomes irrelevant what the percent chance is. Variance is going to make xing worthless due to the odds of him running train on you for your stack being high. Also, no one sets their % below 50% anyway. 

How is the % irrelevant under 30%? I wish small percents didn't matter for every other form of gambling. i was just looking to see if your calculator was !00% accurate +-3% as you claim it to be. You're also wrong about the whole variance and xing thing but w/e.

 

If you don't want to put some time into this script then your sales are going to stay the same. I will NOT be purchasing this script until you update it.

Share this post


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

How is the % irrelevant under 30%? I wish small percents didn't matter for every other form of gambling. i was just looking to see if your calculator was !00% accurate +-3% as you claim it to be. You're also wrong about the whole variance and xing thing but w/e.

 

If you don't want to put some time into this script then your sales are going to stay the same. I will NOT be purchasing this script until you update it.

If you are betting 5% of your bank roll @ a 40% house edge even with the xing returning your to even money, variance will bite you in the ass and you will lose everything. I do not care if you do not buy the script. I do not care if you do not trust my calculations. I find them to be accurate. Make your own if you disagree. I offer three calculators already.

Share this post


Link to post
Share on other sites
43 minutes ago, Assume said:

If you are betting 5% of your bank roll @ a 40% house edge even with the xing returning your to even money, variance will bite you in the ass and you will lose everything. I do not care if you do not buy the script. I do not care if you do not trust my calculations. I find them to be accurate. Make your own if you disagree. I offer three calculators already.

why would you ever invest 5% of your bankroll into anything???? For poker i keep around 60 buy ins for cash games at all times, and if i run bad ill just drop down stakes.

I haven't been cleaned on rs3 or 07 in years but idk what this whole thing is or how it works :s

Share this post


Link to post
Share on other sites
Just now, Illuminati666 said:

why would you ever invest 5% of your bankroll into anything???? For poker i keep around 60 buy ins for cash games at all times, and if i run bad ill just drop down stakes.

I haven't been cleaned on rs3 or 07 in years but idk what this whole thing is or how it works :s

Standard for poker is 20 buy ins. At 60 you're just being nitty and should move up stakes (unless you don't think you can beat them). People tend to bet significantly more than 5% per stake on RS. I recommend 5% as max bet and .5% as minimum.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • 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
      • 59 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...