#Foraging doesn't always work
11 messages · Page 1 of 1 (latest)
Guessing you are mounted. I have this happen 100% of the time if I start foraging right after letting go of the movement keys, but before the mount has come to a complete stop. Since the mount doesn't stop instantly, and since you can't forage while moving. Have to wait till mount is fully stopped before starting the channeling.
Ya, I was mounted. I'll make sure to come to a complete stop first
Yeah, I get off the horse as the time runs 5 seconds and… nothing. I have terrible hand dexterity and of if I nudge a key at 4.5 seconds I invent new curse words.
Interesting, good eye on being mounted.. The horse used to come to a full stop before foraging would begin, does that not happen anymore? Maybe I broke that with my recent horse-related changes...
This was happening before the recent patch too. Theres just a tiny window where you are permitted to start foraging, while mount is still coming to a full stop, and that forage will fail because you were still moving when it started.
Hasn't that been a thing for like... years (might be a slight exaggeration -- but I definitely noticed small sliding movement will interrupt the gather attempt, even if the bar doesn't cancel out on the client side at least around a year ago)?
Slightly related, but mostly a non issue, I've noticed if I rise or dive while using the control bowl in serbule in the water it'll continue the do-after, but fail to pull up the menu
But can concur with all of this. I don't dismount personally to deal with it, I just tap/hold s a little bit
if you right click whatever you intend to gather the horse will run directly into it and force it to stop and then gather it
Ahh ok, it sounds like it might be a case I never actually handled. If you are far enough away from a gather node when you click it, and your horse auto-moves to it, it will come to a complete stop before gathering. But if you are manually moving and get close to a node and click it while your horse is still decelerating, then thats probably when this bug happens. I'll have to investigate that case!