Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Assume

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

Recommended Posts

Well let me know when beta calc is complete, cause i can't run the regular calc with my 900$ Computer 

Atleast needs a blacklist 1-40 defence option till calc is complete.

c96599b074b5834e76fc403d2051c77b.png

You can definitely run the non-beta calculator on your $900 computer. Either use preload and low cpu and deal with the startup lag or deal with the longer calculation times onduel.

Share this post


Link to post
Share on other sites

You're saying the calculator gave you a 99.9% chance of winning and you lost multiple times in a row?

Over the course of 25-30 stakes in which I had over "58% odds" each time, I managed to lose 10 more than I won, emptying my bank. I think the calculator is a cool idea, but honestly, if it has moments like this, I would very much like my points refunded.

 

Despite this, it would be unfair of me not to show you the match-up to aid the development of your calculator. This was the match-up: http://puu.sh/7eAgI.png

Share this post


Link to post
Share on other sites

You can definitely run the non-beta calculator on your $900 computer. Either use preload and low cpu and deal with the startup lag or deal with the longer calculation times onduel.

Yea tried using the non-beta a few times it just lags and dces then does it all over again.I mean sht i can run 4 bots/ watch a stream / and download a movie and i never get the lag that comes with the non-beta calc, not sure why kind of code you put into it but seems like your trying to code some nuclear weapon lol

Edited by Ascension

Share this post


Link to post
Share on other sites

Over the course of 25-30 stakes in which I had over "58% odds" each time, I managed to lose 10 more than I won, emptying my bank. I think the calculator is a cool idea, but honestly, if it has moments like this, I would very much like my points refunded.

 

Despite this, it would be unfair of me not to show you the match-up to aid the development of your calculator. This was the match-up: http://puu.sh/7eAgI.png

Refund denied. I have no control over the outcome of the stake. I stand behind the 58% value it gave you. Over the course of 30 duels you did not have a 1/1000 chance to lose 10 more than you won. Each stake is 100% independent of the prior one (the prior stake has no impact on the outcome of your next stake). Your choice to continue to duel said person after you obviously figured the odds were not in your favor is also not my fault. When using the calculator as a tool, not a script, you have complete and total control over who you duel. The calculator is a guide, not a rule.

19b52dabe0.png

I lost 6 times in a row to that person @ 53% odds in my favor. I think you'd very much agree the odds are in my favor and yet I still managed to lose 6 times in a row. It is not the fault of the script, the calculator, or Jagex. It came down to him getting lucky with Jagex algorithim for generating hits over those 6 duels while I got unlucky. Shit happens.

Edited by Assume

Share this post


Link to post
Share on other sites

Yea tried using the non-beta a few times it just lags and dces then does it all over again.I mean sht i can run 4 bots/ watch a stream / and download a movie and i never get the lag that comes with the non-beta calc, not sure why kind of code you put into it but seems like your trying to code some nuclear weapon lol

You don't need to use preload mode.

Share this post


Link to post
Share on other sites

You don't need to use preload mode.

Why can't we just set in the MIN  levels we want blacklisted until the Beta is complete, like only problem i'm noticing with the Beta is it's giving higher odds on lower defence than it should be, a simple fix would be to add a MIN defence level to stake against. 

Edited by Ascension

Share this post


Link to post
Share on other sites

Why can't we just set in the MIN  levels we want blacklisted until the Beta is complete, like only problem i'm noticing with the Beta is it's giving higher odds on lower defence than it should be, a simple fix would be to add a MIN defence level to stake against.

A customized blacklist system is being written currently that lets you define rules for each person who challenges you. When it is complete this will be available as an option.

Share this post


Link to post
Share on other sites

Refund denied. I have no control over the outcome of the stake. I stand behind the 58% value it gave you. Over the course of 30 duels you did not have a 1/1000 chance to lose 10 more than you won. Each stake is 100% independent of the prior one (the prior stake has no impact on the outcome of your next stake). Your choice to continue to duel said person after you obviously figured the odds were not in your favor is also not my fault. When using the calculator as a tool, not a script, you have complete and total control over who you duel. The calculator is a guide, not a rule.

19b52dabe0.png

I lost 6 times in a row to that person @ 53% odds in my favor. I think you'd very much agree the odds are in my favor and yet I still managed to lose 6 times in a row. It is not the fault of the script, the calculator, or Jagex. It came down to him getting lucky with Jagex algorithim for generating hits over those 6 duels while I got unlucky. Shit happens.

 

You're contradicting yourself. You're saying it's my fault for trusting in your calculator, which I paid money for and assumed would be accurate? That can't bode well for future buyers...

 

6 times in a row @ 53% odds is MUCH, MUCH more likely to occur than 10 times overall with a 30 sample group at 58% odds. Instead of defending yourself, maybe you should at least consider that defence may be weighted incorrectly.

Share this post


Link to post
Share on other sites

You're contradicting yourself. You're saying it's my fault for trusting in your calculator, which I paid money for and assumed would be accurate? That can't bode well for future buyers...

 

6 times in a row @ 53% odds is MUCH, MUCH more likely to occur than 10 times overall with a 30 sample group at 58% odds. Instead of defending yourself, maybe you should at least consider that defence may be weighted incorrectly.

You paid money for the calculator and it works. 

If you roll a dice 6 billion times and it lands on 6 every time, what's the odd of it landing on 6 for the next roll? It's still 1/6.

You lost money staking while the odd were in your favour. It happens. Stop crying.

By the way, there is a guy on my black list at the moment because of max losses, and it was at 85%, and you're crying about 58%? ...

Edited by basmith

Share this post


Link to post
Share on other sites

A customized blacklist system is being written currently that lets you define rules for each person who challenges you. When it is complete this will be available as an option.

Awesome, defense is currently being over valued at the moment and an update like this would be great.

Share this post


Link to post
Share on other sites

Version 2.7.0_0 has been pushed.

Changes: (I don't remember everything)

Custom blacklist manager. Find it by going Logger -> File - > Blacklist -> Open Manager

Fixed poking bug (should never happen again unless world lag)

Fixed a bug that would cause the script to crash in the middle of a duel if your cash stack < maximum bet

Some other shit I don't remember.

Share this post


Link to post
Share on other sites

Refund denied. I have no control over the outcome of the stake. I stand behind the 58% value it gave you. Over the course of 30 duels you did not have a 1/1000 chance to lose 10 more than you won. Each stake is 100% independent of the prior one (the prior stake has no impact on the outcome of your next stake). Your choice to continue to duel said person after you obviously figured the odds were not in your favor is also not my fault. When using the calculator as a tool, not a script, you have complete and total control over who you duel. The calculator is a guide, not a rule.

19b52dabe0.png

I lost 6 times in a row to that person @ 53% odds in my favor. I think you'd very much agree the odds are in my favor and yet I still managed to lose 6 times in a row. It is not the fault of the script, the calculator, or Jagex. It came down to him getting lucky with Jagex algorithim for generating hits over those 6 duels while I got unlucky. Shit happens.

 

purple's 58 percent win percentage is highly inaccurate.

Share this post


Link to post
Share on other sites

You paid money for the calculator and it works. 

If you roll a dice 6 billion times and it lands on 6 every time, what's the odd of it landing on 6 for the next roll? It's still 1/6.

You lost money staking while the odd were in your favour. It happens. Stop crying.

By the way, there is a guy on my black list at the moment because of max losses, and it was at 85%, and you're crying about 58%? ...

Um, I understand that that's how odds work? Of course every instance of a gamble is unique and independent, but the odds of a series of gambles occurring in a certain way is not a flat "58%" or "42%," as I assume you are stating. Out of the many, many ways that my 30 stakes with this person could have gone, the odds of a combination of outcomes occurring in which I lose 10 more than I win happening is less than 1/1000. Other people in this thread are complaining that defence is being calculated wrong, so I am not the only one experiencing this. 

 

For all we know, that person you had 85% odds on had huge unlogged stats on you (e.g. going from 1 to 45 defence with quest experience in an hour and then not logging out so the hiscores don't show the level ups), so I'm going to disregard it for now. Speaking of which, Assume should probably look into having the bot do a combat level calculator check on people it stakes, because that happened to me once before.

Share this post


Link to post
Share on other sites

Came here to report another bug... honestly I'm not that mad that the calc has issues since it works a good portion of the time and is only 10 bucks, but I'd appreciate if you took the issues more seriously. I expected the calc to be pretty damn solid since people are trusting bots to be left alone with it.

 

This matchup says I have 52% odds: http://puu.sh/7f9Ur.png

But if I give MYSELF an EXTRA 3 attack levels, it says I have 48% odds http://puu.sh/7fa46.png

 

Not sure what causes this, but it looks like it could cause some problems.

Share this post


Link to post
Share on other sites

Um, I understand that that's how odds work? Of course every instance of a gamble is unique and independent, but the odds of a series of gambles occurring in a certain way is not a flat "58%" or "42%," as I assume you are stating. Out of the many, many ways that my 30 stakes with this person could have gone, the odds of a combination of outcomes occurring in which I lose 10 more than I win happening is less than 1/1000. Other people in this thread are complaining that defence is being calculated wrong, so I am not the only one experiencing this.

For all we know, that person you had 85% odds on had huge unlogged stats on you (e.g. going from 1 to 45 defence with quest experience in an hour and then not logging out so the hiscores don't show the level ups), so I'm going to disregard it for now. Speaking of which, Assume should probably look into having the bot do a combat level calculator check on people it stakes, because that happened to me once before.

It does do a combat check. The +- is just showing the difference between their levels and yours.

Share this post


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

  • Our picks

    • Gradle is a build tool used to accelerate developer productivity.

      We recently setup a Maven repository (TRiBot Central) to make it easier for scripters to create scripts. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-central/-/packages

      Furthermore, we've released a simple Gradle project to make it easy to run TRiBot and develop scripts for it. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher

      The goals of TRiBot Central are to:

      Deliver updates to TRiBot faster


      Better organize TRiBot's dependencies (AKA dependancies)


      Make it easier to develop scripts for TRiBot


      Make it easier to use and run TRiBot


      Note: TRiBot won't be able to run scripts from within this project until TRiBot's next release.
        • Like
      • 8 replies
    • Hi everyone,

      I'd like to thank everyone for their patience in this transition period. Since last week, we've worked out the remaining bugs with this integration.

      Some users have still been having issues with connecting their forums account to their Auth0 account. To resolve this, we've imported all forums accounts into Auth0.

      Unfortunately, the accounts which were imported today were using an unsupported password hashing algorithm. Hence, random passwords were set during the import.

      What does this mean for me?

      If you've previously linked your forums account to your Auth0 account, you don't have to do anything. Nothing changes for you.


      If you haven't logged in via our new login yet,

      Try logging in with your forums email address and the last password you used


      If you are unable to login, please use the "Forgot password" tool on the login page:
      Follow the instructions to reset your password
       
        • thonking
        • Like
      • 14 replies
    • Hello everyone,

      Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

      Important changes

      When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

      Note: 2FA is still handled through your forums account (for the time being)



      Changes for existing users

      You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


      Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



      Important notes

      Make sure to verify your email address upon creating a new Auth0 account


      When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below
      • 81 replies
    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored


      You'll be able to login via Facebook, Google, and others in the future


      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


      To centralize all user accounts in one area


      To ensure that the client login doesn't go down when the forums are having problems


      To speed up our development


      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


      It's not possible to change email addresses for the time being (this will be resolved this August)


      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 11 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!


      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...