Apaec

Hmm - the reason I asked is because the lock you mentioned didn't sound like a ban... I worry there might be attempts to try and recover the account? Worth being a bit cautious here. Glad there haven't been any problems since though! -Apa

Sure, trial activated -Apa

Sure - trial activated! -Apa

Is there a reason given for stopping in the console logger? Normally the script print out a reason for stopping there, so worth taking a look -Apa

Did you purchase the account? Normally being banned for botting is either a 'macro minor' or 'macro major' ban - the account isn't normally locked. I'm not sure if a VPN would fix this, unless you think your IP might be flagged from previous botting (e.g., on other accounts).

Hey, Could you give a little more info? Generally if the script isn't doing what you expect, it could be a misconfiguration error. If you open the console logger, there will be some more information available to you there. Hopefully that solves your issue, but if not, do let me know. -Apa

Sorry to hear that - that is very unusual though! Have you been using other bots on the account?

Sure, trial activated. Hope the script lives up to expectations! -Apa

Looks like Jagex have changed this interface recently. I've just fixed this in version 3.21 which I've just pushed. Thanks for raising this! -Apa

Usually the script will log the reason for exiting in the console logger. I imagine it might not be able to find the right potion in your bank? Worth taking a look at the logs. If there's an error there, let me know and I can investigate :) -Apa

Trial activated

Thank you!

I've had a look and haven't been able to recreate this on my test account as the account has the quest complete and the interface is different. I don't currently have access to an account without the quest complete; please could you kindly drop me a screenshot of the interface (with widget debug turned on) with your mouse hovering over the cook button?

Interesting! Thanks for the gif. I'll try and recreate this on my end and get back to you. -Apa

Ah right- the script has a separate option for poison karambwans. If you select that, it should work just fine -Apa

Have replied to your PM

Hmm, that's a bit odd. I'll do a test run, but just to check - are you cooking poison or thorough karambwans? Have you completed the quest that allows you to cook them?

Woo, some amazing progress! Thank you for sharing -Apa

Both trials started -Apa

Sure - trial activated -Apa

Sure, happy to set you up with a trial. Which script are you interested in? -Apa

Quick update on this for you @OSRSteph: I've had a look into this, and the issue is actually due to the presence of anchovies and shrimp in your inventory. It's actually a fun and really weird quirk of OSRS: if you have more than one cookable item in your inventory (e.g., shrimp and anchovies), the cooking interface will show cooked variants of those fish as options. If you only have one cookable item in your inventory, the cooking interface will show the raw version of the fish. Test this out yourself- it's interesting! I've just pushed a script update: v3.20. In this update, the script will now search for both raw and cooked variants of the fish in the interface. This should solve all of the problems you were experiencing. The script already correctly banks items that you do not plan to cook, so this should not be a problem. Good luck! -Apa

I see, that makes sense. I hadn't realised you were using a third-party script manager to queue scripts. I'd say it's potentially risky to rely on a successful transition between scripts - though this script does use the built-in webwalker to get to the range/bank, it's generally best not to rely on this. It might be safest manually transition between the two. I'll take a look at the script and see what changes are necessary to automatically reset to a known start state

Thanks for this follow-up information; the script currently makes the assumption that you're starting with an empty inventory. The intended use-case of this script is batch-cooking of a stack of raw food items. I'm keen to understand a little more about your use-case - why do you need to start the script with items in your inventory? Can you not manually clear the inventory before starting up the script? -Apa

In the future, if you run into this kind of issue, open the console logger - the script will display the reason for stopping here Firstly, sorry that I missed your trial request! This sounds like it might be an issue with resource allocation. Does your bot have sufficient RAM/CPU? Are you running in low cpu mode? -Apa