Same issue as the above. As far as I'm concerned this shouldnt be a premium bot till this is fixed...
If you'd actually read my comment, it's an issue in the client. I literally cannot do a single thing about it.
So when the bot banks, 4 out of 5 times it will spam open and close the bank. Is this a known issue or something I can fix in settings? I just baby sit it and manually bank every time because of it lol
Same problems here, will continuously open/close the bank even though it has the required food. Has been charging me entire time but yet not going anywhere or conducting any games.
Sat for two hours opening up the bank then closing the interface. I watched it for a while this time - something to do with having a burma torch equipped and it still wants to remove a tinder box, then bank loops. Second time I noticed this, can't help but feel like its hit or miss, wasting cents.
Sat for two hours opening up the bank then closing the interface. trying to equip a ring of life but i dont have and need one
bugged out when i first started it. grabbed tinderbox when i already have the torch. and then just kept opening and closing the bank interface..
bugs out every now and then when withdrawing food after it withdraws the food it clicks the bank and exit and do this over and over and over
Banned after 3 hours of use, first time using bot on that acc. Big waste of my first ban on the acc...
keeps walking in and out of doors when the counter is up for the next game, not sure if its my settings or a bug? Edit - also waits for a while before banking after the game and once it gets back to the minigame the boss is on around 75% health
There's a setting to wait if the game progress is below X. Look at that in the UI, ideally you want it set around 60%
I havent read all the other messages, but where is the food option: Potato with cheese for us ironmans?
New issue after today's update for me. It can't find any of the tools in my bank. --- Double Post Merged, Oct 27, 2021, Original Post Date: Oct 27, 2021 --- It also unfortunately seems as though I was charged for the 6 attempts I did to try to get it to work.
Spoiler: View log 05:58:24 DEBUG Attempted to hover Burning brazier [1620, 3997, 0] since InteractablePoint(522, 452) was less than 4 pixels away (success: true) 05:58:24 DEBUG Hovered MenuItem{1 : "Feed" : "Burning brazier" : Burning brazier [1620, 3997, 0]} on the first attempt. 05:58:26 DEBUG [BurnLogs] Executing task 05:58:26 DEBUG Attempting to hover Burning brazier [1620, 3997, 0] since the target of InteractablePoint(525, 436) is less then 4 pixels away. 05:58:26 DEBUG Attempted to hover Burning brazier [1620, 3997, 0] since InteractablePoint(525, 436) was less than 4 pixels away (success: false) 05:58:26 DEBUG We're not hovering Burning brazier [1620, 3997, 0] according to Interactable#isHovered() but our position does equal the desired target. 05:58:26 DEBUG Hovered Burning brazier [1620, 3997, 0] on the first attempt. 05:58:28 DEBUG [BurnLogs] Executing task 05:58:28 INFO Burning logs... 06:02:00 DEBUG [ReflexManager] New loop delay determined at 360 minutes 06:02:00 DEBUG [ReflexManager] Generated fatigue at current interval is 1706 06:02:00 DEBUG [HexisBot] Changing our delay from 1736 to 1706 06:17:00 DEBUG [ReflexManager] New loop delay determined at 375 minutes 06:17:00 DEBUG [ReflexManager] Generated fatigue at current interval is 1981 06:17:00 DEBUG [HexisBot] Changing our delay from 1706 to 1981 06:32:00 DEBUG [ReflexManager] New loop delay determined at 390 minutes 06:32:00 DEBUG [ReflexManager] Generated fatigue at current interval is 1816 06:32:00 DEBUG [HexisBot] Changing our delay from 1981 to 1816 06:47:00 DEBUG [ReflexManager] New loop delay determined at 405 minutes 06:47:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2044 06:47:00 DEBUG [HexisBot] Changing our delay from 1816 to 2044 07:02:00 DEBUG [ReflexManager] New loop delay determined at 420 minutes 07:02:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2326 07:02:00 DEBUG [HexisBot] Changing our delay from 2044 to 2326 07:17:00 DEBUG [ReflexManager] New loop delay determined at 435 minutes 07:17:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2264 07:17:00 DEBUG [HexisBot] Changing our delay from 2326 to 2264 07:32:00 DEBUG [ReflexManager] New loop delay determined at 450 minutes 07:32:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2438 07:32:00 DEBUG [HexisBot] Changing our delay from 2264 to 2438 07:47:00 DEBUG [ReflexManager] New loop delay determined at 465 minutes 07:47:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2799 07:47:00 DEBUG [HexisBot] Changing our delay from 2438 to 2799 08:02:00 DEBUG [ReflexManager] New loop delay determined at 480 minutes 08:02:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2751 08:02:00 DEBUG [HexisBot] Changing our delay from 2799 to 2751 08:17:00 DEBUG [ReflexManager] New loop delay determined at 495 minutes 08:17:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2673 08:17:00 DEBUG [HexisBot] Changing our delay from 2751 to 2673 08:32:00 DEBUG [ReflexManager] New loop delay determined at 510 minutes 08:32:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2618 08:32:00 DEBUG [HexisBot] Changing our delay from 2673 to 2618 08:47:00 DEBUG [ReflexManager] New loop delay determined at 525 minutes 08:47:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2360 08:47:00 DEBUG [HexisBot] Changing our delay from 2618 to 2360 09:02:00 DEBUG [ReflexManager] New loop delay determined at 540 minutes 09:02:00 DEBUG [ReflexManager] Generated fatigue at current interval is 2784 09:02:00 DEBUG [HexisBot] Changing our delay from 2360 to 2784 09:17:00 DEBUG [ReflexManager] New loop delay determined at 555 minutes 09:17:00 DEBUG [ReflexManager] Generated fatigue at current interval is 1955 09:17:00 DEBUG [HexisBot] Changing our delay from 2784 to 1955 09:32:00 DEBUG [ReflexManager] New loop delay determined at 570 minutes 09:32:00 DEBUG [ReflexManager] Generated fatigue at current interval is 1651 09:32:00 DEBUG [HexisBot] Changing our delay from 1955 to 1651 09:47:03 DEBUG [ReflexManager] New loop delay determined at 585 minutes 09:47:03 DEBUG [ReflexManager] Generated fatigue at current interval is 2010 09:47:03 DEBUG [HexisBot] Changing our delay from 1651 to 2010 Bot got stuck for 4-5 hours last night, this is the log. When i woke up it was at 10 hours 15 minutes... Created a new acc to suicide as i suspect my previous account was reported by "friends", so far so good other than the few hours last night, it was sat at the login screen when I checked up so no worries, just missed out on 0.50$ worth of bot time. Bit annoyed tho, just noticed it has the pet haha. Edit: The account made it to 99 Firemaking no problem, time for fishing next.
