Marshalek

Right but it works if I disable PartyBot Helper plugin, how can it be the fightclass' fault?

@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.

@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.

This seems fixed, thanks for the quick fix! @Matenia

@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.