fall0ut

uncheck 'attack before being attacked' and check 'don't start fighting' on the class/fights tab in the general settings. this will make it so you only attack if you are first attacked. if that doesn't work you could blacklist the nodes with enemies around it. Droidz comment below is a better solution than blacklisting nodes.

welcome to the forums. so there are two things you will need. you will need a fight class, this is a set of instructions to tell wrobot what spells to use for your character and talent spec. you can find some fight classes here. if a fight class for your class and spec does not exist, you can create one, or request someone make one here. the next thing you will need is a profile. depending on the product you are using (grinder, gatherer, etc.) a profile is a set of waypoints wrobot follows to move your character through the world (of warcraft). the profile may also contain information as to what to attack and what to not attack along the way. wrobot.eues with some profiles. you can also create your own or find user created profiles here. in the tutorials section of the forums you will find guides for creating your own fight classes and profiles.

so with the update yesterday, i noticed the frames per second option in the fight class editor. what is the ideal fps for melee vs caster? I also noticed wrobot is trying to cast the same spell 3 or 4 times before it is actually successful and moves to the next spell, which it tries to cast three or four times. not sure if i am skipping spells, but the log is cluttered with multiple casts of the same spell.

Thanks for your reply! You led me to try some different conditions, specifically the lua scripts. Sadly I am unable to figure it out. The Stop Auto Attack option in the interface menu is only for switching targets, and does not affect the current target. The priority of the spells should be: Shadowstep, Ambush, Sinister Strike. I am a little unclear what happens when wrobot casts a spell from the priority list, When Shadowstep is successful, does wrobot begin checking spell conditions from the top of the list again? or does it continue checking conditions from the last good spell cast? If it started at the top then the correct priority order would be Ambush, Sinister Strike, Shadowstep. I haven't tested this second order (at work and just thought of it). I tried adding lua scripts to the conditions and also tried adding lua scripts as spells. The lua scripts as spells would cause the autoattack to stop, but wrobot would immediately reengage the auto attack. I believe wrobot simulates a user right clicking to select targets, this would make the player run to the target and start auto attacking. because of the way wrobot targets is it even possible to stop auto attacking permanently? if i wanted to stealth shadowstep behind a target and just stand there and not attack but with the target selected, is that possible?

So a big problem I have seen with my rogue and ambush is wrobot starts auto attacking too soon. Specifically I shadowstep and before ambush can be cast my toon has already started attacking, breaking stealth and turning the mob to face me. The only sure fire way I have found to get ambush to cast is via the talent where casting ambush/cheap shot/garrote from a distance automatically shadowstep your toon behind the mob. Because of the weird auto attacking I usully just let wrobot shadowstep and attack without using the "from stealth" spells. Shadowstep is nice in case your rogue gets stuck while trying to path to the mob.

if you are wanting to play the auction house buying and selling game. download the legit addons called market watch and auctionator. scan the ah with market watch for a few weeks and it will show you trend data for items you follow. since i have market watcher i know which days of the week ghost iron ore sells the highest and which days it sells the lowest. i use a custom gatherer profile that files around the entire pandaria continent 24/7 mining ore. i only sell ores when the market is high. even if i didn't bot to get ores, i could be totally legit and buy all the ghost iron ore low. i know the price will rise in a couple days and sell high. you can do this consistently every day with as many of the gathering items you can manage and have storage for. the real problem is i am lazy, and this all requires effort. does anyone know places to grind for high gold output solely from looting gold and vendoring trash? the one time drop of big selling items is great but not consistent enough to be ruled as a way to make lots of gold. i just want to start the bot and only stop it to occasionally mail gold to my main.

I am a very new user to wrobot, but I am a long time bot user in warcraft. In my opinion the more life like a bot can be the more impressive it is. Every bot I have ever used was too perfect and followed obvious rules. After going from 1-600 in both herbalism and mining with wrobot, here are some ways I think the gathering ai can be improved: Do not land directly on top of the node. Human players typically land next to the node then farm, they certainly do not land on top of the node every single time. It would be more realistic if wrobot landed say 5-10 yards from the node and ran up next to the node to farm it. This could potentially lead to pathing issues if the node is on a hilltop or if there is a tree or something in the path. In the case of getting stuck fly and land on top of the node. If a mob attacks the player before the node has successfully been farmed, wrobot will fight/kill the mob. When the mob has been killed wrobot mounts, immediately dismounts and begins to farm the node again. This is silly no human player would do this. When the mob is killed wrobot should immediately farm the node and not mount until the farm is complete. When straying from the flight path to farm a node, do not return to the last known point on the flight path before continuing to follow flight path. Let me explain: Currently wrobot follows a set of way points defined by the user. When wrobot detects a node to farm, it strays from the user defined points and farms the node. when the farm is successful, wrobot returns to its last known user defined point and continues on its path. in my opinion this appears very calculated, not human-like. I think a fix for this would be, instead of returning to the last known point, skip x amount of points ahead to return to the path. In theory wrobot would not backtrack then continue on its path... It would instead always be traveling forward around its path. I have found if there are 2 or more nodes to farm in very close vicinity of each other, wrobot will farm one node, mount and fly to the next node only a few yards away. wrobot should instead not mount, but just run to the next node as long as it is within x yards from current location otherwise mount. I have played very little with the fight classes on a training dummy. I am very impressed thus far with the conditions. Although as a rogue I would like to see a condition "if behind target". Also it would be cool, if the target has a buff (like stunned or sapped) wrobot will move the player behind the target. You guys have done a fine job designing this program. If you ever implement automated questing I would be happy to test and build profiles from 1-90. Edit because im a noob... found this topic about checking for behind target.. going t otry it when i get home... made me start thinking there are some other conditions for combat that may be possible already if not would be neat to add for human like actions. a universal wrobot spell to move player behind target if condition is met. example: some mobs cast spells where the player must run behind the target to avoid damage or to attack successfully. so a universal wrobot spell for move behind target would be rad. also something very similar except to move away from the target for x amount of yards. if condition is met, turn 90 degrees right and strafe right x amount of yards and stop until condition is not met then resume combat. again some mobs cast an aoe the player should move out of to avoid massive damage.