Jump to content
Frequently Asked Questions
  • Are you not able to open the client? Try following our getting started guide
  • Still not working? Try downloading and running JarFix
  • Help! My bot doesn't do anything! Enable fresh start in client settings and restart the client
  • How to purchase with PayPal/OSRS/Crypto gold? You can purchase vouchers from other users
  • lfscomic

    Members
    • Posts

      33
    • Joined

    • Last visited

    • Days Won

      1

    Everything posted by lfscomic

    1. I'm sorry I didn't see this reply until now. I'm at the Guild of Warriors bank It should have been 3.14.2.4 Has this issue been fixed in subsequent releases?
    2. "Specific" is a very vague word. Let's talk about the simplest reason why there are some robot clients that haven't died in this wave. To return to the previous sentence, if the system is changed, the network is changed, even the hardware is changed, only the robot client is not changed, but still banned, in this case, how does jagex know who is the "farm"? The only thing he could find was abnormal data. Finally, the client is "safe", if this wave of bans bans manual players as well, then can prove that the client is secure. Otherwise, manual players are not banned, but bot users are banned. How can the client be safe? This means that jagex can still tell who is a player and who is a bot statistically. By the same token, even if all clients have problems, including private clients, then what you should do is to get us out of this ban, and not just assume that if everyone else has problems, I should have problems, right? Where is the value in embodying technology if everyone is banned? Isn't it the equivalent of, "I can ban you whenever I want, and all your countermeasures are useless to me?" Taking the ban for granted is the worst. I hope Dreambot keeps getting better because I use it all the time and even after the massive ban I still renewed my VIP subscription and chose to keep believing in Dreambot. We are not jagex's technical team, and neither are you. Even if it's just 'the right thing happened at the right time', even if it's a coincidence, it's not normal for a player to walk around on a map, or go to the wall with his bank card for hours. Both are reported with a high probability, and unfortunately these issues did not occur prior to version 3.14, so personally, I do not understand the point of your dropping the old API. Even if it's going to help in the future, at least you can test it and release it, instead of updating it multiple times a day and testing us like rats. If you say that there will also be a steady stream of people coming to Dreambot from other clients, well, I congratulate them, they are about to become a new batch of guinea pigs.
    3. Hey bro, I have been out of action for many days, and now I have only two poor accounts killing frogs in Lumbridge, but predictably they will soon be gone,LMAOOOOOOOOO
    4. Yes, the hardware keyboard and mouse are very important, and ring0 is much better than ring3. I would have developed it myself if time hadn't allowed.
    5. It clicks on the top left corner of the minimap for no apparent reason
    6. Bank#open interacts with bank NPCS, whereas bank #closest interacts with bank booth, So, Bank#open has a chance of getting stuck on the wall, but Bank#openclosest has no problem. Can you fix this problem?
    7. Similarly, I've been working on the script recently, and a couple of survivors got short-term bans the other day, but unfortunately, within 20 hours of their release, they got permanent bans.Lmaoooooooooooooo
    8. Yes, not every robot client has these problems. I am absolutely certain of this because I have tested it and I think I have some say in it. Out of respect for dreambot, I can't name the other platforms, I'll just say the test results. I ran two accounts on the same machine with the same IP address. The first one was a certain platform and the second one was dreambot. Using an account on another platform, practiced the battle level to 70 for 36 hours in the Free world, and so far, it is still alive. Banned 5 hours after leaving Tutorial Island using dreambot account. Both accounts are manually completed tutorial islands and fight in the same world in the same location, so if reported, it's impossible for the player to report only one of them, which is pretty bizarre. It is worth mentioning that for the account of a certain platform, I used the public free script without any interruption and AntiBan, which means I was constantly beating monsters, while for the account of dreambot, I used the script written by myself with many random operations and breaks. Before version 3.14, it almost never had any problems. The most embarrassing thing is that I don't have VIP on the other platforms, I just use their free model, while I use covert mode on the dreambot client. I don't know what's going on, the development team turns a blind eye to all these people talking about it. And still naively think, this is only a few cases. It's amazing.
    9. I'm here to call for the removal of all the new content from 3.14, urge the return of all the deprecated methods, and urge the engineers to seriously consider users' opinions and stop using us as guinea pigs. I don't want to wait for you to update and experiment again and again, it is meaningless. Again, I love using db, the community is great, the API is convenient, and everything is wonderful, but I need something to live and hope for, or I'll have to give up. After all, I have to survive, too.
    10. Yes, I am the same way, every day I keep being banned, before this, I can keep my robot alive for a month or more, all the measures have not changed, but it is banned. I changed the proxy ip, reinstalled the system, and used accounts that had been cooled for more than 180 days, but that didn't work and the vast majority of accounts didn't survive 24 hours before they were banned. I don't know what else I can do. As the user of the db, I don't know whether because of version 3.14 has led to all of these cases, however, did not happen before 3.14 so frequently banned, I hope the developer serious to think about the future, whether to back version, not for some unnecessary functions, the user as a test of rats.
    11. I have a piece of good news to share with you. Just now, all my robots have been banned. Before that, they were stable for a month.lol
    12. Same, you're not alone in this fight. I have now been looping an operation, manual tutorial island 10 accounts ==> Practice combat skills ==>Banned down to just three. Remaining account to purchase membership ==> The next day there are only 0. Repeat the above operation again. Before this, I was safe, even with a 100% survival rate, yes you read that right, 100% cheers.
    13. There's no way around it. I've long advised against abandoning old apis. I told them it would lead to a huge loss of customers, but they didn't listen, so I can only console myself. The right thing to do is to mix the old with the new, and let those who are willing to try it, and those who aren't, do so at their own risk, rather than forcing code simplification to satisfy their own obsession. Life is like rape, since you can't resist, you can only enjoy with your eyes closed,LMAOOOOOOOOO
    14. That's what I don't understand at all. If it's basically the same, why does it keep getting stuck in the wall... Warriors' Guild,the cook to the bank. Kourend Castle,the baker to the bank. Keldagrim,the builders to the bank. I think it's the pathfinding algorithm. Replace the new wayfinding algorithm with "Bank# openclosure "if possible.
    15. Warriors' Guild. Kourend Castle. Keldagrim. The probability of getting stuck varies, depending on where you start your walk. In the less than 12 hours since I posted, three accounts have been banned. I don't know the exact reason, maybe it's a coincidence, maybe it's not...
    16. "Bank.open" is always stuck on the wall. However," Bank.closest" everything is normal. But, stubborn developers abandoned it. I don't see any benefit from the new api. It increases my workload, prevents getting stuck on the wall, I have to calculate the route, go to the safe tile, and then call "open", reduces the efficiency of the bot, and increases the risk of being banned. Because there's still a chance it gets stuck on the wall It's not cool.
    17. It's ready to go. Please ignore.
    18. The dreambot is not available. How long will it take to use?
    19. My script uses "if (Inventory.count("Coins")< 2000)", but when I have 2m, it triggers this condition
    20. Yes, it is completely stationary after a period of time. Loading.... is displayed in the upper left corner of the screen "Indicates that you are jumping the world. My other scripts that don't use world hopping are fine, and I can confirm that my proxy is slow So, do you think it's a scripting problem or a network problem? If the problem is the network, what is a better solution? thank you
    21. As the title suggests, is there any other way than to write your own third-party program to constantly monitor whether the screen is refreshing? My robot always freezes while jumping worlds, even when I add lots of time delays, judge widgets, judge game states, and wait randomly after jumping worlds. My script is completely standard, whether using nodes or AbstractScript, and any world-hopping operation involved will randomly cause the client to freeze within minutes to hours. I attribute this to my network issues, but what I'd like to know more is that in a bad network environment, Are there any other means to prevent this phenomenon from happening? I feel very depressed now.
    22. Thank you, Sir. My main purpose for switching worlds is to switch worlds if there are players around. So let's say I meet my condition at 330, and when I switch to 331, 331 also meets my condition, then I can't increase my waiting time in between because he meets my condition, so I have to "run away" immediately. If you're referring to the wait time after you've successfully jumped to the world, I've added it, but unfortunately, it doesn't solve the problem of randomly logging out of the login screen. Finally, thank you for your reply.
    ×
    ×
    • Create New...

    Important Information

    We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.