- Joined
- Dec 28, 2013
- Messages
- 190
- Thread Author
- #21
Nah, at least not for me.
Fixed in the next version. I'll post here once the update is reviewed and pushed out to you all.confirmed. does not loot or bank nests
By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!Nah, at least not for me.
Fixed in the next version. I'll post here once the update is reviewed and pushed out to you all.confirmed. does not loot or bank nests
Fixed in the next version. I'll post here once the update is reviewed and pushed out to you all.
Possibly! I have quite a few bots out now (and one almost ready for public release) that I want to get perfected before getting started on any more projects.This is why I like to use your bots, you have variety and get fixes out ASAP. I hope you stay here for a while, you should maybe focus on an "All Smithing" bot for OSRS next, there is only one right now (Quality Smithing) and it's high priced/slighty buggy.
Omni Woodcutter updated to v1.0.2.
1. What do you have to click before it starts working again? Close the bank? Start walking?I have noticed two more bugs whilst cutting at the Woodcutting guild..-
1. Many times it opens the bank, deposits mt Yew Logs and then just sits there. Not trying to click off or run away, it kicks back in once I manually click it.
2. On the way to the bank, sometimes it clicks outside the room and runs up the left side of the bank instead of going inside to the bank chest. Normal if it happened a few times but it consistently happening now for me.
Hope you fix them ASAP!
1. What do you have to click before it starts working again? Close the bank? Start walking?
2. Just the bot randomizing the click coordinate, nothing to worry about. It won't effect XP/log rates by any noticeable amount.
The current version of RuneMate apparently has an issue that can cause it to hang at select times (due to mouse movements). If the hanging problem persists after the next RuneMate update I'll look into this further.Close the bank then start walking.
Are you 1000% sure that it's "PlayerSense" causing this bot to constantly run up the side of the bank? It's becoming MORE than a coincidence, it's at least two out of five times it tries to bank. I don't care about the XP, I am worried about getting banned for being too consistent with a mistake.
Loots perfectly fine for me. I'll see if there's any weird cases when it doesn't and report back.this still doesnt loot or bank the nests... nests drop from tree and it just lets it disappear... not worth premium man if it doesnt loot nests
not working at seers maples. thats what i use. where does it work? I wouldn't think it should matterLoots perfectly fine for me. I'll see if there's any weird cases when it doesn't and report back.
Just updated to support looting bird nests with clues. This should resolve any issues.not working at seers maples. thats what i use. where does it work? I wouldn't think it should matter
Then where was it? I need a more detailed bug report if you expect me to fix anything. I run this bot myself daily.02:51:39 TRACE [Login handler] Logging in
02:51:45 DEBUG Interface Closer - Play Button has been activated!
02:51:45 TRACE [InterfaceCloser] Clicking the unwanted component "Play Button"
02:56:47 DEBUG Login Handler has been activated!
02:56:47 TRACE [Login handler] Pressing Existing User
02:56:48 TRACE [Login handler] Entering username
02:56:50 TRACE [Login handler] Entering password
02:56:52 TRACE [Login handler] Logging in
02:56:55 TRACE [ControlPanelTab] Opening COMBAT_OPTIONS using component: null
02:56:56 DEBUG Interface Closer - Play Button has been activated!
02:56:56 TRACE [InterfaceCloser] Clicking the unwanted component "Play Button"
03:01:58 DEBUG Login Handler has been activated!
03:01:58 TRACE [Login handler] Pressing Existing User
03:01:59 TRACE [Login handler] Entering username
03:02:02 TRACE [Login handler] Entering password
03:02:03 TRACE [Login handler] Logging in
03:02:07 TRACE [ControlPanelTab] Opening COMBAT_OPTIONS using component: null
03:02:08 DEBUG Interface Closer - Play Button has been activated!
03:02:08 TRACE [InterfaceCloser] Clicking the unwanted component "Play Button"
This bot is scuffed... Ran 6 hours and only did 1 invent of seers yews and got stuck. Came home and it was not at graveyard yews like I had it set to... rip. Too many flaws man it should be flawless wc for premium especially since there are others.
it was at yews near catherbyThen where was it? I need a more detailed bug report if you expect me to fix anything. I run this bot myself daily.
We use essential cookies to make this site work, and optional cookies to enhance your experience.