Jump to content

Marshalek

Members
 View Profile  See their activity

  • Posts

    82

  • Joined

  • Last visited

 Content Type 

Everything posted by Marshalek

  1. Marshalek
    Pathing is completely broken, right from the start the bot goes crazy, drops down a cliff and tries to climb the mountain back up as if it were Spiderman. This is so amazingly frustrating, i don't know why I keep paying for this every month... running this bot requires almost as much work as playing the game, with 100x the risk of being banned, and nothing, NOTHING I want to use the bot for ever works as intended Are you guys really from Germany?
  2. Marshalek
    Bot is broken (pathing) in vanilla AV and after many reports, there's no sign Droidz will even look at it...
  3. Marshalek
    Wrobot is abandoned...
  4. Marshalek
    Is Wrobot Vanilla abandoned by devs?
  5. Marshalek
    Same here, pathing is totally broken in vanilla AV. Any suggestions @Droidz?
  6. Marshalek
    Right but it works if I disable PartyBot Helper plugin, how can it be the fightclass' fault?
  7. Marshalek
    @Matenia it appears this plugin causes the bot to ignore the following setting: Settings > Mount Options > Ignore Fighting if in Ground Mount What it appears is that once party member engages in combat, bot will dismount and help party member regardless of the above setting.
  8. Marshalek
    @Droidz
  9. Marshalek
    Having same issue, very frustrating to say the least.
  10. Marshalek
    @Matenia hey just curious, when I run this plugin, my debug logs are constantly bombarded with messages such as: [D] 22:16:25.706 - [PartyHelperPlugin] [PartyFollowerState] Message received: m$ X ankProgress+�,���s thisWeekHonorDsrankdsNorvegant�sis_outdatedbnsrankProgress+�6��sclasssWARRIORslast_checkede[/�s lastWeekHonorD�sstandingD�sRPD sunitIDs mouseovers thisWeekHonorDCsrankdsBilingt�sis_outdated Aylins [D] 22:16:26.037 - [PartyHelperPlugin] [PartyFollowerState] Message received: m$ f u�sPwnajt�sis_outdatedbnsunitIDs mouseoversclasssROGUEslast_checkede[jxs lastWeekHonore�l�sstandingD�srankProgress+����@��sRPDp"s thisWeekHonorDI�srankd Brbafk [D] 22:16:26.539 - [PartyHelperPlugin] [PartyFollowerState] Message received: gatherer_p2p;1.0.0 Nixi;solid chest;0;1;4;34.96;68.83;2;1; Nixi [D] 22:16:26.539 - [PartyHelperPlugin] [PartyFollowerState] Message received: gatherer_p2p;1.0.0 Bloodreigh;soleillette;1;2;21;67.88;35.11;20;1; Bloodreigh [D] 22:16:26.539 - [PartyHelperPlugin] [PartyFollowerState] Message received: m$ X bnsunitIDs mouseoversclasssWARLOCKslast_checkede[~ăs lastWeekHonorD��sstandingd�srankProgress+������sRPD,2s thisWeekHonorDLsrankdsCelebt�sis_outdatedbnsrankProgress+�������sclasssHUNTERslast_checkede[�s lastWeekHono Aylins [D] 22:16:27.204 - [PartyHelperPlugin] [PartyFollowerState] Message received: m$ X re��sstandingD��sRPDygsunitIDs mouseovers thisWeekHonore��-srankdsAvnt�sis_outdatedbnsunitIDs mouseoversclasssWARRIORslast_checkede[Xs lastWeekHonorD>sstandingD sRPD��s Are these just people around me (hopefully) or is my bot receiving messages from every other player using Wrobot on this server? My concern is, if I can see them, they can see me. Sorry if I'm completely off-target.
  11. Marshalek
    Thanks, that plugin is exactly what I was looking for and more. I wasn't aware this existed, probably because there are different plugin repos for each expansion... Droidz should just combine all plugins into a single repository for ease of finding.
  12. Marshalek
    Having this issue, it's quite obvious it's a bot when running party mode. Obviously the bot checks party leader position every X seconds and moves there. The problem is, if the party leader isn't moving, bot invariably stops right on top of the party leader - it's such a perfect stack it's difficult to emulate manually, hence the obvious, instant BOT RED FLAG when anyone sees it. @Matenia @Droidz can you write a plugin to prevent bot from landing right on top of party leader?
  13. Marshalek
    This seems fixed, thanks for the quick fix! @Matenia
  14. Marshalek
    @Droidz @Matenia When using this plugin + grinder, sometimes (very frequently) the bot enter a bugged state where it will ignore corpses and not skin them, then as soon as the next enemy is engaged, the bot will "remember" that abandoned corpse and try to go back to it, mid-fight, to skin it. This creates a situation where the bot keeps trying to fight, and walk, at the same time, making it very obvious it's a bot, going back and forth. It will continue as a chain (the mob killed during the fight/walk phase will be the next abandoned corpse) more or less like this: 1. Bot kills a TargetA and ignores its corpse for skinning 2. Bot starts walking towards next enemy, TargetB 3. As soon as TargetB is engaged, bot starts trying to walk back to TargetA to skin it, while also turning around to continue fighting TargetB FIGHT > WALK > FIGHT > WALK > FIGHT > WALK... 4. Eventually TargetB will die and the bot ignores its corpse as well, and heads get to TargetA and successfully skins it 5. Now, instead of going back to TargetB, the bug repeats itself, and bot starts heading toward next enemy, TargetC 6. As soon as TargetC is engaged, bot starts trying to walk back to TargetB to skin it, while also turning around to continue fighting TargetC FIGHT > WALK > FIGHT > WALK > FIGHT > WALK... This goes on indefinitely, until I disable HumanMasterPlugin's "smart skinning" feature. But then, the bot standard skinning scripts are buggy AF and will randomly ignore mobs. Lose/lose.
  15. Marshalek
    This is awesome. Thanks @Matenia
  16. Marshalek
    To me it was an addon that hid the blizzard cast bar. Once I re-enabled blizz cast bar, bot started working.
  17. Marshalek
    My concern is automated, software-based detection - can this be in place? Using WRobot 2.0.1 (34770) for wow 2.4.3 (~8606)
  18. Marshalek
    Having this exact same issue... any known workarounds?
  19. Marshalek
    Thanks all, it was probably the script I was using then, I noticed it got stuck on "go to town" unable to send mail due to no money.
  20. Marshalek
    GAME.FELMYST.COM
  21. Marshalek
    Tried to bot on Felmyst and got banned rather quickly. Could they be running some form of client-side detection via Warden?
  22. Marshalek
    So my bot dies, then walks back to the corpse. Two different problems: 1. The bot will resurrect on top of the corpse, regardless of whether there is an enemy nearby. Please research/review Honorbuddy and copy their behavior - the bot TRIANGULATES between corpse and closest enemies, to find THE BEST LOCATION TO RESS AT. I mean this is so basic I can't even believe I'm here writing this. 2. The bot will re-engage in griding/fightting BEFORE IT RESTS. PLEASE ENSURE BOT HAS FULL LIFE AND MANA BEFORE RE-ENGAGING, another "DUH" bug. With the two bugs above, bot will engage into chain-deaths until I stop the bot and move it somewhere safe. These bugs prevent AFK botting, especially for weaker characters at lower levels.
  23. Marshalek
  24. Marshalek
    Hi, My bot is getting stuck for hours on what appears to be path finding issues (using gatherer). This happens randomly and I cannot resolve it by adding blackspots. This appears to have started 2 updates ago when there was a change in path-finding and encryption/compression for meshes i think? Not sure. If I stop/start the bot, the issue goes away and the bot starts moving again. Excerpt from the attached logs that show what the bot is doing when it gets stuck for hours: [N] 01:29:38 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:38 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:38 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:38 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:38 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:38 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:40 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:40 - [Path-Finding] Path Count: 2 (1.916143y) [N] 01:29:40 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor) [N] 01:29:40 - [Path-Finding] Path Count: 2 (1.916143y) 15_Jul_2017_20H54.log.html
×
×
  • Create New...