phoenix222

here are some suggestions for additional product settings and bugfixes for the party bot in the next wrobot release to make it more useful in PvP: additional settings: - when chasing an enemy, stop chasing after reaching a specific distance away from the player/partyleader defined at "follow by player name" and return to him | yes/no, enter XX meters range - dont chase any enemy, stop attacking when target gets out of range, always follow partyleader | yes/no - keep following the player/partyleader defined at "follow by player name" even in combat | yes/no - automatically attack any attackable enemy target that is in XX meters range, dont wait until it starts attacking anyone in the party | yes/no, enter XX meters range - prioritize enemy players over their pets / do not attack enemy player's pets | yes/no - prioritize the target of the player/partyleader defined at "follow by player name" over the current target / switch to his target as soon as he starts attacking it | yes/no bugs that need to be fixed: - when the character dies high up in the air (for example while sitting on a flymount) the bot releases the spirit too fast, causing the corpse staying in the air and making it impossible to reach it anymore for resurrection. please add a wait time of a few seconds between dying and spirit release. - in openpvp combat, the dps bot sometimes keeps targeting and trying to attack neutral players with yellow or blue name (which is impossible) who have set their pvp status to inactive. it mostly happens when the neutral player is currently fighting against someone/something (for example dueling another neutral player). - in Healer mode, the bot stops following the player/partyleader defined at "follow by player name" as soon as it gets into combat. it should keep following him even in combat. - the commands: wManager.Wow.Helpers.Fight.StopFight(); wManager.Wow.Helpers.MovementManager.StopMove(); simply dont work when the dps partybot is trying to chase someone, when executing them, the bot neither stops fighting nor does it stop moving/chasing.

the window alignment feature of the relogger application doesnt work with wow WOD client (6.2.4), and with older client, for example 4.3.4 cata client it only works when manually clicking on start button of every single profile, when using the "start checked" button, most of the windows dont get aligned, too.

the buff check under spell conditions believes that passive abilities in the spellbook count as active buffs too. example: as a disc priest i use the talent "Surge of Light", it will give a passive ability in spellbook and an active buff when the proc happens. i add the spell "Flash Heal" to the fightclass with buff condition "Surge of Light" true, so it only casts flash heal when the surge of light buff proc happens, but it keeps spamming the spell even if the proc buff is not active. the same thing happens if i enter the name of other passive abilities in the spellbook to the buff check.