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

Sell OSRS Gold

wastedbro

Developer
  • Content Count

    2,758
  • Joined

  • Last visited

  • Days Won

    46
  • Feedback

    100%

wastedbro last won the day on March 24

wastedbro had the most liked content!

Community Reputation

757 Excellent

About wastedbro

  • Rank
    TRiBot King
  • Birthday 11/30/1995

Personal

  • Sex
    Male

Recent Profile Visitors

8,792 profile views
  1. On release, the API will be completely open-source. You'll be able to contribute straight away. You can ask any questions on Tribot's discord. I can also assure you that, objectively, Tribot is not "in a hole".
  2. The API will be very, very different since this is a color-based bot. Yes, the scripts can be coded in Java.
  3. It does not require an emulator. You can use your own android phone. And yes, running an emulator that runs OSRS is more resource intensive than running OSRS on desktop.
  4. It was about 14-17 hours per day for a couple weeks. Some days is was lower (like 6 hours). No breaking at all. I basically quit at 30m fletching XP on two accounts. But I'd like to stress test other skills as well. Most of my time goes into the client itself, so my scripts so far aren't particular stable over long periods of time. As we get closer to release, I will focus my time on scripts so that we release with amazing scripts in variety of skills.
  5. Almost exactly one year ago, you posted a scripter application. Here was my response, verbatim: All four points remain true, a year later, with this new application. And I have a few more: Your script threads and script descriptions on the repo are bottom of the barrel efforts. It's okay to only post public scripts for the goal of getting scripter rank, but you need to at least put forth some miniscule amount of effort to show that your scripts are actually meant to benefit users. No descriptions, no setup instructions, no listed features, nothing. Sorry, but that's not a good look for tribot in general. I honestly don't even think they're up to the standards for normal users, let alone a scripter. I think you have the programming skill to become a scripter. But there is a severe lack of effort and seemingly no response to feedback. We make these decisions on what you show us. Whether or not it's your best work doesn't matter. Listen, it's okay to not want to make some of your work free, but that's not an excuse for demonstrating tiny scripts that barely do anything. If you want to show us how amazingly you can code a script without revealing your best work, then make something common. Make an AIO miner or something. There's literally dozens of free AIO miners. Users probably won't even care about yours, so it's a good way to show us how you can make a usable GUI and a multi-featured script with options and variable logic. This is vague and unverifiable information.
  6. In the Oldschool Runescape Client, every player animation is classified by an ID (integer). This value is set by the client and used. Tribot reads this value to tell you what the animation ID is. There is no definition of its values. Any definitions that the OSRS client may have had in source code are completely erased after obfuscation and during runtime (which is where Tribot gets the values). Therefore, the only way to get the definition of an animation is to grab that value, see what it is, look at what the character is doing on screen, then define it yourself. And we aren't going to do that for every single possible animation in the game so that we can put it into the API. It's your responsibility to figure out which animations are which IDs that are pertinent to your script. For most scripts, all you really need to know is -1 is idle and not -1 is animating. The details rarely matter, and when they do, you usually only need to know a couple IDs, which is why it makes more sense to do it on a per-script basis. The same goes for all game values. RSObject IDs, NPC IDs, etc. The tribot API gives you a lot of tools for reading values from the game. However, any cross-referencing to metadata needs to be done by you. To do this, make sure to open the debug menu in Tribot, which will let you visualize these values in real-time.
  7. No, the difference is that I'm working from years of research, development, and trial and error, while you're spouting what sounds like a 14 year old's interpretation of a magazine about artificial intelligence that he skimmed once. PS: Your logic right there only makes sense if playing Runescape meant literally randomly clicking an 800x600 square. Since very obviously it's not, you're logic is thoroughly stupid. It's so nonsensical that I feel like an idiot trying to explain it because I'm still unsure if you're trolling or not.
  8. The impossible conditions you've described are, first of all, very possible for a human to do occasionally. If you don't click the same pixel sometimes twice in 10 minutes, then you are a robot. Second of all, Tribot and all of its premium scripts do not contain any code that would ever make it deliberately do this. All camera movement, mouse movement, and mouse clicks use pseudo-random algorithms to generate random values along a distribution curve we believe adequately matches human data. Each distribution curve is slightly different per account. Every account botted with tribot uses different values to determine these actions, meaning that no two bots will have the same patterns, even over long amounts of time. This is because even human patterns can be botlike. Just because your bot does humanly possible things, it will still look like a bot if it shows the same patterns as 15,000 other accounts. No. Humans aren't random. In fact, they are very predictable. The more random the clicks, the less humanlike they are. For example, when it comes to mouse movement, humans are all pretty similar in the way they do it. This was theorized in 1954 by Paul Fitts, and then later proven on computers by Stuart Card, William English, and Betty Burr in 1978. Since then, plenty more studies have gone on to confirm that Fitts Law remains valid, and studies as new as 2012 have used this law for further research. If you read the math behind it, you'll see that human mouse movement is not random: https://en.wikipedia.org/wiki/Fitts's_law. In fact, humans are so predictable that there is an entire career path dedicated to making software better at adapting to human patterns. It's called UX Design. And it pays very well. Reaction times are similar. Take a look at this study: https://www.frontiersin.org/articles/10.3389/fnhum.2015.00131/full That study looks at reaction times to computer stimuli as a function of age. As you can see, we can predict rough reaction times to certain stimuli based on the age of the person. And even in each age group, it's not random. Take a look at figure 2. Even at each age, the reaction times tend to flow very close together at a bit below center. If we were to model it as a distribution curve, most of these would be considered Inverse Gaussian Distributions (Visualization). All of your ideas are about 13 years behind where we are at now in botting. Try to keep up.
  9. Home IP. Same as my normal botting, but I don't farm.
  10. This will similar to Tribot Looking Glass. You'll have a tribot instance on your PC that can connect to an emulator or even your actual phone, and it won't use your computer's mouse. You'll even be able to connect to many devices from a single computer and bot them all
  11. What is Tribot Mobile? Tribot Mobile is a new client that works on Android's version of Oldschool Runescape. Being in development for over several months, Tribot Mobile is currently in available to Developers and Scripters, and is completely usable. It uses your PC to interact with a connected Android device (physical or emulator) and plays OSRS for you! Unlike the normal tribot client, this client has absolutely no interaction with the OSRS internals. It is strictly color/image based, and provides functionality through its API, as well as popular vision libraries, such as Tesseract and OpenCV. Demo: TribotMobileDemo.mp4 FAQ When will this be available? Most likely this summer (2020) Who will have access? For the public release, only VIP members or higher will likely to be able to use the client at all. Can this run without a PC? No, a computer is required to actually run the bot logic. It connects to your phone via USB, or via an emulator that you're running also on your PC. Being color-based, will scripts be different? Yes. Scripting for color is notoriously more difficult, thus scripts won't be as advanced. Over time, we plan on creating things like a webwalker and using machine learning to find objects/NPCs. However, this is long term and well after the release. How is the banrate? Both myself and others have tried to get banned using this. We can't do it. I gave up at 40m fletching XP on two accounts (my main and a fresh). I'll try again once we develop some more scripts. Tribot Mobile will have tons of antiban. Just like the normal client, it uses algorithms that mimic human clicking patterns to ensure that no botlike behavior can be observed by Jagex. In addition, it never even touches the game client. There is absolutely zero possibility of client detection, or even client suspicion. It's completely invisible. From the ground up, the Tribot Mobile API will have options for realistic reaction times, sleeps, clicking patterns, and more. How are scripts written? Scripting for Tribot Mobile will be roughly similar to the normal client. However, Tribot Mobile is written entirely in Kotlin. This means that writing scripts in Kotlin will be the easiest, but Java can also be seamlessly used if you prefer. Also, the API will be 100% open-source. ---------------------------------------------------------------------------------------------------------------------- If anyone has more questions, be sure to post here, or ask me discord. Happy Botting
  12. You're improving, definitely. Very glad to see it. But as Einstein said, the quality is a bit lacking. I would really prefer that you make one really good script instead of 15 mediocre ones. 1. As Todd said, be sure to include more fail-handling: For example, your scripts will sleep for no reason if something fails: Keyboard.typeString("1"); BooleanSupplier supplier = () -> plantSpace.length > 1 || Player.getAnimation() == -1; GeniuSWait.waitTill(supplier); General.sleep(General.randomSD(600, 1800, 900, 65)); // If the player doesn't do the animation, this sleep still happens. Bad. You need to instead utilize return values (note: you can delete my comments in this code, of course): Keyboard.typeString("1"); // "supplier" is not a good variable name. Let's make it more descriptive BooleanSupplier isPlayerAnimatingFunc = () -> Player.getAnimation() == -1; // plantSpace will never change, by the way, so checking it's length is pointless if (Timing.waitCondition(isPlayerAnimatingFunc)) { General.sleep(General.randomSD(600, 1800, 900, 65)); // Only sleeps if the player ACTUALLY does something } You basically make this same mistake in all of your scripts, everywhere. 2. Need to clean up some sloppiness: This makes me feel like you're a bit too new to programming in general: public static boolean hasGold() { if (Inventory.getCount(995) >= 5000) { return true; } return false; } You can reduce this to: public static boolean hasGold() { return Inventory.getCount(995) >= 5000; } And this.... RSObject[] door = Objects.find(15, "Door hotspot"); GeniuSWait.waitTill((() -> door.length > 0)); That array will never change, so waiting on it to have a length > 0 is very pointless Also, ensure that you're always trying to find better ways to structure your code than "Utility.java" or "Vars.java". Your scripts are very small right now, but if you ever make a large one, keep in mind that these classes will start to get bloated and confusing to follow. 3. Need ABC2 Implementation Sorry, I think I may have missed this the first time. But, frankly, I don't see any ABC in this code. In some of your code, I see that you call on your library for ABC stuff, but you never included the source code to that. I understand that a good number of your scripts don't have features that need to use a lot of ABC-type implementation, but that just means you need to make a script that does. -------------------------------------------------------------------------------------------- PS: You should really include your whole source code. I can't see what you've done with much of the code, because it's all tucked away in "GeniusBanking" or "GeniusWait" or something. Verdict: No But, if you show your ABC2 implementation, and it includes everything and is done correctly, I'll change my vote to a "Maybe".
×
×
  • Create New...