Apaec

I'm presuming you meant sand crabs since you liked that page, so i've given you a 24h trial. Enjoy! (: -Apa Hey, This script is free to use and is available to use on the SDN here: https://osbot.org/mvc/sdn2/scripts/16 -Apa

Glad it got sorted out! (:

Done, enjoy! (: Hey, it seems you already had a trial earlier in May, however since it looks like you didn't get much progress in, i've given you an additional 12 hours. Cheers! -Apa

Every joe uses it, jagex have probably profiled it!

I would recommend not botting where possible, e.g for alching you can use an autoclicker, or you could splash, etc. That way, on the off chance that you do get banned, it most likely won't be a macro major. Also please don't use an autoclicker like garys hood or w/e!

Not sure what could be causing that as that stack trace doesn't narrow things down! If this happens again, please could you let me know the full error log? Cheers -Apa

To answer your previous question, you will see that our script extends Script. This is an abstract class in the OSBot API and since we are extending it, we have access to all of its attributes. An example of an attribute is inventory, whereby we are calling the super inventory object attribute and using the methods that it provides. As for the stall, you will find that that is initialised just above the snippet you quoted, we're creating an instance of an RS2Object which is an API object describing an ingame object. Hope that makes sense, let me know if you're still unsure. Since you edited the post I would assume you figured this out yourself but I just thought i'd drop a quick reply in to clear it up if you didn't! -Apa

@pallmalled

Looks like Version 2.0 has been released. Give it a go! (: -Apa

You can only have one trial per script (naturally), so in your case you're eligible for a trial in all my scripts other than this one at the moment! (: -Apa

Sure, I've given you a 48h trial as I did to xxgruntxx and will extend it until the latest version (2.0) is available! (see below) -Apa

Hey, sorry for the delay - just got back in! -Apa

Sure, although the latest version (2.0) has not been pushed live yet. I've given you a 48h trial in the hopes that it will be available in that time period, but if not, I will continue to extend the trial by 24 hours until you get to try the latest version, as the script has been re-written from scratch so it would be unfair for the trial not to test what the script really is (: -Apa

\o/ Me! But it took a lot of careful botting with short sessions and no more than 1-2h botting per day.

Yes. I will be looking to re-write the script at some point in the near future to add support for stuff like phials and Rimmington, but for now it only works in Yanille! -Apa

When I give it! (:

PLEASE NOTE: THIS THREAD HAS BEEN UPDATED TO DESCRIBE SCRIPT VERSION 2.0 WHICH WILL BE PUSHED FOR MODERATION TONIGHT. Edit: The update request has been pushed. Version 2.0 should go live once the changes have been checked for malicious content by the bot developers. Considering the scale of this update, this understandably may take some time!

Also seem to be struggling with mouse listeners ): Running on Windows 10: getBot().addMouseListener(....); fires the mouse events when human input is enabled, but does not when human input is disabled. getBot().getCanvas().addMouseListener(....); does not fire mouse events at all, whether human input is either enabled or disabled. The first one worked perfectly for .127, now neither achieve what I was hoping for. Not sure why this is! _____ As a side note, for me the enable/disable human input option is working perfectly and doing its job as it should, thanks for this (: Cheers -Apa Here's a gif illustrating the issue when calling getBot().addMouseListener: http://i.imgur.com/Gl97TOJ.gifv on previous versions, it would respond both when human input is disabled and enabled.

I have no macbook knowledge but I can tell you that it's probably worth investing in a new laptop instead of going for an old one. The way I see it, if you're planning to use it a lot, then it's worth paying a little more and having a nice machine that will last you longer! Apple seem to have pretty poor hardware specs in comparison to competitors, but have very good software optimisation, so if you're looking for super-high numbers then maybe a mac isn't right for you. They're still amazing machines though!

Apologies for the delay. The issue has been fixed in version 2.0! ________________________________________________________________________ I am pleased to announce that APA AIO Smither Version 2.0 is almost ready for release! This means big changes. I mean BIG! The script has undergone a complete re-write from scratch. As a result, you can expect a more reliable structure making it easier for me to implement fixes and updates in the future! Version 2.0 is considerably more powerful and features a fully fledged 'activity' system. This allows you to completely customise how your session runs, enabling you to combine smithing activities in one instance. The activity system relies on a configurable activity target setup, which you customise when you create a new activity. This target setup allows you to move onto other activities when you deem a previous activity complete. To host this activity scheme, i've completely re-worked the user interface and have done my best to make it as intuitive as possible - examples are below: When you start the script, the activity editor pops up. This is the panel in which you configure the script session. The activity editor has a 'settings' button for global script settings such as the ability to move your mouse outside the screen while you are idle - i've left space for more global options in the future. The settings panel also has options for the paint, which has also been re-worked. Yes, you can recolour the paint! You can then add individual activities with the 'Add' button. When clicked, this window pops up: Prompting you to select whether you want to add a forging (turning bars into items), smelting (turning ores into bars) or cannonball (turning steel bars to cannonballs) activity. Depending on which one you select, one of three interfaces shows up, as illustrated below: These interfaces can then be customised with a target and added to the activity queue. Here is an example of a script session: When start is pressed, the script will begin running and process activities from the top down. Here is an example of the new paint and on-screen logger: The logger saves timed messages, so each message only sits on screen for 60 seconds, or until it is pushed off the screen by on-coming messages (the logger height is currently set to 6 lines) The paint objects are completely movable, meaning you can re-locate them to where you desire or move them out of the way of something that you're trying to interact with if you're intervening with the bot. They can also be hidden through the startup settings menu if you so desire. When typing the 'Make-X' messages previously, the script would simply drop a random number. Now, I have implemented a more advanced algorithm to generate 'Make-X' strings which uses gaussian-distributed number generations to configure strings to include suffixes such as 'k' and 'm', commonly typed numbers such as '1234' or '99', randomly generated numbers, round numbers like 9000 and much more. This new system renders the previous manual selection text-box obselete. That about sums up the changes that I have made to the script. Rest assured that all features previously supported by the script have been restored and improved upon, alongside the plethora of new changes I have made in v2.0. I am aiming to have this version of the script released for early next week after I have fully soak-tested the code! -Apa

Read!

it should be! (: -Apa

Hey (: This is caused by a recent osbot interaction update, it seems to be happening for most scripts. I'm not sure if there's much I can do about it without writing my own entire interaction system, which in the end may not turn out to be as reliable as the OSBot system. Perhaps the interactions will be changed in the near future but beyond that there is not much I can do as client work is out of my control! Thank you for bringing this up though. -Apa

Perhaps it's just worldhopping behaviour that was implemented in the script; would that make sense for the script in question?

Is this happening for a specific script ?