Jump to content

Apaec

Scripter III
  • Posts

    11155
  • Joined

  • Last visited

  • Days Won

    91
  • Feedback

    100%

Everything posted by Apaec

  1. Hmm, I will take a look into these for you guys, not sure what could have caused this. Perhaps thursdays update although it's unlikely. Cheers apa
  2. task/state you can call it whatever you want I guess. A simple way to do it is have an enum of states and switch between them, although this results in two potentially large blocks of code which is not ideal. You can split these states into classes if you really wish, and have condition/execute methods but that's really just another way to achieve the same thing. How you structure a script really depends on the function you require, whether it's AIO etc..., there's no one way of doing it really. Getting the structure right is the hardest part to get a good balance of code readability and flexibility. It's definately worth trying to get right at the start! apa
  3. Perhaps try using some classes instead
  4. Not sure why it wouldn't drink the super strengths, could you please let me know, what are the values displayed in the paint when the script is running? specifically the potion counters
  5. What if you're not at a bank
  6. I would highly recommend against that. Although you might have gotten lucky in the past, using while loops like that means the risk of getting stuck is high. There's no perfect solution but it's important to design your scripts as to minimise this risk!
  7. Apologies haha, it's a sure way to end up in an infinite loop, perhaps consider a for loop or a different design such as integrating a method relying on the onLoop's delayed loop to retry!
  8. You can't rely on an api method to execute correctly first time, low-cpu or not (The reason for this is the bot is dealing with a live game, so latency fluctuations / dcs etc also have a say in the script execution). For this reason, writing scripts in a heavily 'recipe' style is not recommended (e.g bank#open, then bank#withdraw assuming the bank is open after calling bank#open) Try and design your scripts such that it will do whatever it needs to do and repeat if necessary to reach the desired in-game situation. (tip: try the if statement) ~apa D:
  9. I will add it to the list of places to add. Still working on the re-write, but running into some structure issues which means the update is taking longer than I would have liked. Hopefully everything should be in place for next seasonal though!:) ~apa
  10. Ah, apologies. I put through a trial request but it appears to have been denied due to the trial you recieved on the 12th march 2016. As the script has been through a bunch of new versions since then, i've given you a new 24h trial starting now. Cheers! apa:)
  11. There are no requirements whatsoever, and I would say that sandcrabs are better xp as sandcrabs have 60hp (compared to rock crabs' 50hp). Also, sandcrabs have a larger choice of camp locations so you have less down-time running around spawning new crabs. Cheers! ~apa
  12. I've had a few requests for this, however I concluded I probably wouldn't add this for a few reasons. Firstly, I do not wish to clutter the gui further - it is already quite busy and adding this would require a significant number of components. Secondly, a large amount of the userbase for the script run with pure accounts, and there is currently no code to do with switching attack styles. For fear of the script messing up for whatever reason and ruining pures, I concluded it would be a risk worth avoiding! Thanks for the suggestion though, let me know if you have any further queries!:) ~apa
  13. https://www.youtube.com/user/Slothiq
  14. I don't think it does actually, but it might do, i'm not sure. If it doesn't, I can always add it - I'm working on a re-write as we speak so I will put it on the list of things to do Whenever you want a trial, just let me know ~apa
  15. Because a bot is alot more risky + you're risking macro major
  16. Unfortunately not, sorry!
  17. Hiya! I've just started your 24h trial. Sorry for the delay, Just got back in. Hopefully it's what you're looking for ~apa
  18. I think it actually selects a number in a range starting larger than 28, I don't want to give away the upper limit though! Either way, sometimes it will use 2 or 3 digit numbers too. May even use 5 digit numbers too
  19. Sure, apologies I only just woke up! ~apa
  20. Hey, glad you like it Unfortunately there's not much that I can do about this. I tried to make the reset paths avoid other spots so that at least other users of the bot don't cause this, but there isn't much I can do other than let the script wait for them to respawn (which doesn't take too long either way!) Cheers! Done, enjoy!
  21. Yep, hold CTRL and select both in the startup ui. Hey You can customise the intervals and deviations on the randomised camera/mouse movements to your liking, as well as setting it to always moving the mouse outside the screen when idle. Was that what you were asking? As for the bank pin, that is handled by OSBot and as a result I cannot adjust the code running to solve the issue. Whenever the screen goes red, that means that OSBot has taken over (login, bank pins, ...) Cheers! ~apa
  22. As programerz said, you can disable random dismissing in the settings As for your question on pathing, the script follows the same predefined path each time, however it will extremely rarely click the same positions on your game screen as factors like server latency, camera angle, and jagex's anti-mouse recording sequence counter this. The script will as a result also not end up clicking on the same exact tiles on the path and will alternate which tiles it even aims for. I would not worry about being banned via the behaviour of the pathwalking, especially as the bot doesn't spell all that much time doing it. As far as I can see, OSBot's walking code is pretty reliable! As for how jagex actually detect bots, no-one really knows. I for one think they know everyone who's botting anyway and they only selectively ban, but I could be wrong. At the end of the day it's your timings and in-game hours which I think play the biggest role in preventing bans. Be generous with your breaks and try not to bot for too long in a single sitting - be sure to give this thread a read! osbot.org/forum/topic/45618-preventing-rs-botting-bans/ (*EDIT Oh I'm on Claw Island spot 3 and It looks like to me its going to the same spot at the tip of the claw every time. Would it be difficult to allow us to highlight lets say 6x3 tile area of our choice and the bot runs to one of the tiles randomly each time? It already does this, but for a pre-defined region. Selecting that region yourself would be an unnecessary complication which i'm sure alot of users would rather not go through, but it could potentially done. The nature of the CCI3 reset path end means that the script will mostly enter this region from one direction and so the first tile normally triggers it, but not always. Either way I still stand by what I mentioned previously!) Cheers ~apa
  23. Hi there! Cheers for getting in touch. I've given you a 24h trial, and to answer your questions: 1: Can you set the mouse to move off screen? Like it drags away after clicking as if you're working on something else on the desktop. Yes, there is an option for this on the Gui. The script will, whenever idle, move the mouse out of the screen. 2: Can you set the camera move time and random clicks to high random variables like 2 minute to 30 minutes? Yes - you can set the interval and the deviation. This means that you can set the interval to 20 minutes and the deviation to 15, and it will perform a random action anywhere between every 5 and every 35 minutes. 3: Does the bot always eat once the percentage of health set is gone? Or can it eat eat at like 30%-60% The bot will eat as soon as you drop below the threshold. However, i'm looking into adding deviation to this at some point in the near future. 4: How random is the refresh rate and can it be for 3+ minutes? The bot detects when it needs to refresh, and as soon as it does it starts a timer for a random duration (I believe around 1 - 60 seconds although I don't want to give the exact figures away!). If this timer is extended any further, then the bot risks being logged out from inactivity consistently (this sometimes already happens anyway with the current timer, and it can be argued that this might make it look more realistic!) Hopefully that answers any questions you may have had. If you would like to know anything else please let me know! Also, the bot will not loot anything unless you specifically configure it to (the bot can loot ammo and easy clues). Thanks! ~apa
  24. Working on it! Also hoping to re-write the framework so potential ETA is the weekend but no promises. Cheers for swinging by!:) apa
×
×
  • Create New...