Everything posted by Inf3ctious
-
Cooked on warmane
Banned on Turtle WoW before even getting to level 2, they are definitely detecting WRobot. Likely they are sharing the detection mechanism across servers.
-
Add STOP (not close) bot on teleport
It's really fucking obvious when you log out the moment you get teleported to GM island...
-
[AH] [Quest] 1-60 Dynamic grinder
-
[A] [Quest] 1-60 grinder
- 66 comments
- 6 reviews
-
Unstuck routine is a one-way ticket to bantown
7 Oct 2022 09H53.log.html
-
Unstuck routine is a one-way ticket to bantown
Quester. It is on a server with some custom stuff so navmesh can be "wrong".
-
Unstuck routine is a one-way ticket to bantown
Logs: https://pastebin.com/dWQJDWvD Droidz: can you please add a check that prevents the bot from doing the same repetitive motion 10000 times? What happened in the above logs should never happen.
-
Open container routine breaks looting
Not sure. Server is turtle.
-
Open container routine breaks looting
As soon as the bot loots a container and tries to open it, looting will stop working completely - mobs will appear unlootable (loot icon greyed out).
-
Bot thinks it is stuck after charging
How? Don't see it in pathfinder settings.
-
Bot thinks it is stuck after charging
It still does this (1.12.1)
-
Fisherbot won't work in AV
Status says "battlegrounder combination" and the bot does nothing. edit: just found this and it works
-
Instant ban on Project Ascension privateserver. Please help!
Can confirm they are detecting Wrobot specifically. They mentioned it by name when I asked about the ban. Also, renaming the Wrobot executable is not enough to avoid the ban.
-
Bot does not always loot skinned mobsa
Still happening no matter how high I set the latency. It does not seem to affect how fast the bot goes from skinning to eating.
-
wrobot attacking hunter pets
I've seen this too. You can avoid it by turning on the setting of ignore fight with pet, but then it will die sometimes in PvE to mobs that have a pet.
-
Bot does not always loot skinned mobsa
Thank you
-
Bot does not always loot skinned mobsa
Frequently, the bot will immediately start eating after skinning, which results in the skin not being looted. Quite often the bot will leave it and then suddenly come back from like 50 yards away to loot the skinned mob. Either a delay needs to be added or the bot does not skin while holding shift, which it should.
-
cant start quester after newest update
Fixed it by manually running updater.
-
cant start quester after newest update
I see there is an update but still getting same error when trying to run Quester.
-
cant start quester after newest update
Also experiencing this. [E] 08:10:42.107 - Quester.Bot > Pulse(): System.NullReferenceException: Object reference not set to an instance of an object. at .(Boolean , String ) 08:10:42.107 - [Quester] Failed to start [E] 08:10:46.191 - Quester.Bot > Pulse(): System.NullReferenceException: Object reference not set to an instance of an object. at .(Boolean , String ) 08:10:46.191 - [Quester] Failed to start
-
Bot does not detect bugged loot
Note: only know of this happening on vanilla 1.12.1
-
Bot does not detect bugged loot
Sometimes dead mobs bug and show as lootable but the loot button is always gray no matter how close bot is to the dead mob. The bot does not detect this, so it keeps trying to loot the corpse until it despawns.
-
Stop Helping Group Members When Quest Complete
I was hoping someone could develop a small plugin for the Quester module that just disables helping group members in combat when the quest objectives of the current quest are completed.
- Automation Product does not use food
- Automation Product does not use food