Search the Community
Showing results for tags 'problem'.
Found 2 results
-
Been having some issues with one of my combat scripts, it died seemingly random. buy i finally managed to be at the PC when the script was messing up. What happened was that when the client tried shift dropping a vial, it instead normally clicked on it so basically it clicked "use" on it. and then went on to proceed with the script. it's just that it wont be able to interact with anything since all the interact options is now replaced with use vial > on. And for some reason the osbot wont notice this which results in the bot doing nothing since it cant use any interactions in either the game window or in the inventory. which means even though i have super strict priorities in the script to always eat and teleport away above anything else, it cant execute it cause it cant interact with anything cause the vial is highlighted for use and replace all the items other interactions. So i was thinking, I'll just add a check for it; if something is highlighted. but how do i do that? And also is this a osbot bug i should report, cause im 99% sure the logic in my script isn't causing this. I'm sure this isn't a big problem if your script involves walking around alot since it would simply normal click in the game window and the "use" would go away. but my script is in a super crowded area and walks between 2 tiles that has mobs on them which means it pretty much allways relies on right click>walk here which it cant do when the item is highlighted. to sum it shortly: highlighted(use) item is fucking my script. -
I have just started creating some very basic scripts, at first I was able to export them into my Osbot scripts folder, they'd show up in client and i could run them. Then somehow something broke and now only the local Woodcutter V- 0.1 shows even though I have 3 scripts in my script folder. Also if I remove the script that has the code for the Woodcutter it still stays in the Script Selector. So for example there will be GoblinKiller and Script1 in the Script folder and the Woodcutter will still show(it's named Script Update Tester in the folder in the screenshot) but it won't be runable. I've tried redownloading osbot, removing the osbot.jar build path and re-adding it but no luck. Has anyone had any similar issues? image of my situation -