eeny

I assume you want the bot to grind mobs till it finds the item that starts a quest. take a look at the below profile.. The first pulse is a kill and loot, however the <iscomplete> condition is: <IsCompleteCondition>return ItemsManager.GetItemCountById(113578) &gt;= 240;</IsCompleteCondition> What that does is checks you bags for ITEMID- in this case 113578 and if its bigger than or equal to 240 the quest is complete. All i would do is change the ITEM id to the quest start object and set value to =1. the next quest profile step will be to "pick up the quest" . In the Quest you need to set true "pickup from item" and add the item ID. ( pic attached). Without doing it for you i cant give you much else- hope that helps

Its actually Arch Linux.....jk of course its Win10 =P

Fresh install of wrobot on the new SSD (G:/Wrobot).. all working fine at this time.... shrugs Same OS, same profiles no crash. The old install has been running pretty hard for a few months.. maybe something just got messed up

Its all over Kalimdor. One bots failing in StoneTalon mountains, another in Valley of trials. initially i thought meshes were the problem because i saw one log file crash trying to load one, so i deleted all the kalimdor meshes and it still crashed. Im installing a new SSD later today. il put a fresh install of wrobot on that and see where i land

So i have made a quest profile thats ~ 500 steps and 500kb in size. In quests editor it passes the 'check errors' with no probs. however when i load it 50% of the time my bot will crash with the following .Net and application crash. Taking a look at the .net error i assumed it was a mesh issue so i deleted all the meshes for the continent- however it came back immediately. also cleaned out the logs folder of 900mb of logs however still having odd crashes. Currently 2 bots will load the profile and run it, 2 are just chain crashing. is there an issue with a maximum profile size- or do i just move down the repair install of Wrobot / .NET? 25 Jul 2016 21H35.log.html Log Name: Application Source: Application Error Date: 25/07/2016 9:29:13 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-9CQIFVD Description: Faulting application name: WRobot.exe, version: 1.0.0.28188, time stamp: 0x578e2d99 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0d45b157 Faulting process id: 0x1d34 Faulting application start time: 0x01d1e667b2f7fc67 Faulting application path: C:\WRobot\WRobot.exe Faulting module path: unknown Report Id: 5eabbba5-43c8-41d3-b85b-ddadec0b0550 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-07-25T11:29:13.363226100Z" /> <EventRecordID>3904</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-9CQIFVD</Computer> <Security /> </System> <EventData> <Data>WRobot.exe</Data> <Data>1.0.0.28188</Data> <Data>578e2d99</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>0d45b157</Data> <Data>1d34</Data> <Data>01d1e667b2f7fc67</Data> <Data>C:\WRobot\WRobot.exe</Data> <Data>unknown</Data> <Data>5eabbba5-43c8-41d3-b85b-ddadec0b0550</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-07-25T11:29:13.302552900Z" /> <EventRecordID>3903</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-9CQIFVD</Computer> <Security /> </System> <EventData> <Data>Application: WRobot.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at &lt;Module&gt;.dtNavMesh.addTile(dtNavMesh*, Byte*, Int32, Int32, UInt64, UInt64*) at RDManaged.RD.AddTile(Byte[]) at wManager.Wow.Helpers.PathFinderClass.Pather.LoadTile(Int32, Int32) at wManager.Wow.Helpers.PathFinderClass.Pather.LoadAround(robotManager.Helpful.Vector3) at wManager.Wow.Helpers.PathFinderClass.Pather.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3, Boolean ByRef, Boolean ByRef, Int32, Single, Boolean) at wManager.Wow.Helpers.PathFinder.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3, System.String, Boolean ByRef, Boolean, Boolean) at wManager.Wow.Helpers.PathFinder.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3, System.String) at wManager.Wow.Helpers.PathFinder.FindPath(robotManager.Helpful.Vector3, robotManager.Helpful.Vector3) at wManager.Wow.Class.QuestGrinderClass.Pulse() at wManager.Wow.Class.QuestsSorted.Run() at Quester.Bot.Ewiqaileitega.Run() at robotManager.FiniteStateMachine.Engine.Baura(robotManager.FiniteStateMachine.State) at robotManager.FiniteStateMachine.Engine.Pulse() at robotManager.FiniteStateMachine.Engine.Axuca(System.Object) at System.Threading.ThreadHelper.ThreadStart_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart(System.Object) </Data> </EventData> </Event>

Seen this exact issue. This is especially a problem while leveling as the bot may walk into a high lvl area to sell / repair and just chain die.

Looking for some input for people who launch multiple instances of Wow. Currently i run 4-5 acc's with relogger- farm for 2 hours on / 2 hours off. When all 4 are open i find my CPU / graphics card at 100%, without turning this into a "my computer can handle that" contest, the Issue: when i change the max background FPS and picture quality to a low setting my CPU can run 4 wow at 20%. Once they relog for the second farm the setting go back to normal and my CPU will be pegged again at 100%. Does anyone have tricks to get wow to keep the settings after a relog?

You folks going ally or horde?

With the price of my staples : leather / herbs / feblight falling to almost vendor prices.. Tanaan isnt the best place to send my bots atm. What are you guys doing to fill the gap before legion drops? anything we should be farming to prep us for legion?

42 minutes.. nice EDIT: your the man!

is there an issue with reading memory for some quests in 7.0.3 (22267) I knew legion was going to mess up a lot of my profiles with the changing quest ID's/ locations etc so i went back to my newest (and best) trying to get it 100% for legion. However my bot wont read the quest ID's correctly for some quests, the bot will just sit and trying to pick up the quest. In the screenshot the second quest does not get enumerated properly so in the attached log the bot stayed for 3 minutes trying to pick up the expected quest ID. What should also be noted- as your quest log changes- the quest ID (for the broken one) will change a little bit. Sidenote- no addons Brand new character. *shrugs* Profile: Eeny_Horde_1-60_V1_4.xml Logfile: 20 Jul 2016 18H21.log.html

Just tried it on WoD...No dice even if i do this manually the bot will stop eating and stand up /shadowmeld.... hope BC is different

Put it in the fight class?? Just have shadowmeld in the fight class with a condition that the bot needs to be eating to cast it.

Assuming its WoD- Confirm that "auto-dismount in flight" is Enabled. its in the interface > Controls menu second option down.

Use item on dead mob ( after looting) Use like the use item on weakened mob- you need to modify the item ID and Quest ID for your quest. Thread t = new Thread(() => { uint itemId = 9618; int questId = 25336; while (robotManager.Products.Products.IsStarted) { if (Conditions.InGameAndConnectedAndAliveAndProductStartedNotInPause) { if (!Quest.HasQuest(questId)) break; if (ObjectManager.Target.IsValid && ObjectManager.Target.IsDead) { ItemsManager.UseItem(itemId); } } Thread.Sleep(500); } }); t.Start();

Driodz- any movement here- this is killing me (literally)

Jumping is possible for people who write profiles in C# i think. Using flight class editor: For instances like this i simply make a second Shadow bolt entry up the top of the rotation with a "has buff : shadow trance = true". Honestly- some times the bot will do something else instead .... but realistically its a bot.. most of the time it will do the right thing, if it skips a proc...meh

Glad thats it- looking at the profile i can see you have the concepts down. One thing that bettersister showed me was the quest helper tools >dump all quests. In the Quest Editor > tools > quest Helper... will make sure you get the right quest ID every time (wowhead had 10 you could choose from for this quest)