Jump to content
This site uses cookies! Learn More

This site uses cookies!

By continuing to use this site, you agree to allow us to store cookies on your computer. :)


WRobot user
  • Content Count

  • Joined

  • Last visited

About Findeh

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Findeh

    Abandoned product?

    True, it's not. But the answer is more likely yes, than no. More abandoned than not abandoned. ))
  2. Findeh

    Abandoned product?

    What exactly have been done already? Let's say, for a past year.
  3. Findeh

    Abandoned product?

    Alot? Pathfinder? Better? 🙂
  4. Okay, another bot did the same thing. Just added an aquatic mount to the settings by itself and stuck.
  5. Findeh

    [TBC] bot only mines once

    It should not be 1 and 2, it's just my example. Try 400-700 or something like that
  6. Findeh

    [TBC] bot only mines once

    This: Then this:
  7. Findeh

    Pathing is completly broken

    Profile 1. From outside of the cam to the vendor inside. Some points are inside (!) the trees. Profile 2. From inside of the camp to ashenvale. Will get stuck like 20 times in logs and trees. Both profiles are attached. WSG Bug1.xml WSG Bug2.xml I can name like 20 more places like this, this 2 was just close to my bot so it was easy to show.
  8. That helped. Thank you. But why did it appear there in a first place? I don't ever change settings by hand, and non of my profiles got aquatic mount setting.
  9. This was reported couple times already, was hoping it was fixed already, but it was not. I'll just try to explayin it with a tones of usless words as i usually do, and hope this will help. 2 situations. 1) Skinning turned off. Bot is targeting mob, killing it, looting, continues run and when the same exact mob is respawning bot is immediately targeting that mob again, without any delay. Everything good. 2) Skinning turned on. Bot is targeting mob, killing it, looting it and then trying to skin it. Skinning cast bar appears. Bot is wait's for ~3 seconds (that's the cast time of a skinning in vanilla) then at the same moment 2 things happens, skinning is finished, and Debug log says: [Looting] Cannot loot the target (MOB NAME), ignore it. It all seems fine, loot is done, skinning is done as well, but when that exact mob will respawn, bot will ignor him. He will just continue his patrol around as if there was no mob available for targeting. After some time of patroling around bot will target that mob again, but if he will skin it, then he will again ignore it for a long time. And that happens withe every mob that you skin. As a result i do often find my bots just patroling without killing anyone for like 5+ minutes, that's a huge waste of time. I got 2 guesses. 1) There is some timer argument during looting process, that is set for 3000ms for skinning, but skinning tooks alittle more (+ ping + looting) and that's why bot ignores the mob becouse timer is less then the process. Solution, increase timer for CurrentSetting.LatencyMax, maybe? 2) This is happens no metter of the any timer, just after any skinning process. Then the question is why is that happens? Should be fixed anyway, i guess.
  10. Bot is spinning in place trying to mount, when he should just swim. Ad a result, he stuck. It was never happened before, so it's most likely recently added bug. My old prifiles with just follow path in wather are broken now. 17 сен 2018 20H53.log.html
  11. I have no idea why is it a thing. As i sayd, it was reported for years. By me as well. And as i also said, previously private realms was a secondary project, now it's a main thing, so i guess it should be watched more, at least for those 3 years old bugs.
  12. There a lot places like this, actually. Just Thoradins Wall and Cenarion Hold are the most noticable. You can try to runn the bot in the Hordes Warsong Gulch camp, it will be even more fun. He ignores an entire mountain.. And will ignor almost every tree near it. Places like this are also exist in Dun Morogh, Badlands, Teldrasil, Winterspring, Tanaris and who knows where else. Also both Thoradins Wall and Cenarion Hold problems were reported many times. It seems like it's more complicated that it seems, so no result yet.
  13. Findeh

    Not a question

    Stop if teleported is working, but not in every situation. They know that and will make the right situation for you, so it was not working.
  14. Findeh

    Botter anti-botter

    This is common thing, yeah. Just report him back. Constantly, like once a day. Also for him. Prices will not go up with you reports, there are always more then you are able to report. But when you help GMs to ban bots, there is higher chance then they will come for yours next (just because there will be less tickets to delay them from doing that). The more work to do they have, the better. If there will be not much tickets they may start to patrol, just because they are bored, and when they patrol, nothing will save you, especially if your bots are the only one that left.
  15. Findeh

    Sudden Pathing problems

    Lost 5 bots because of this. 2 of them level 50+, others 40+.