Jump to content

Paultimate

WRobot user
  • Content Count

    37
  • Joined

  • Last visited

About Paultimate

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Make a fightclass where the heal goes off on party members.
  2. Took me 20 tries just to get this thread to load. Something is happening to his website and likely his bots authentication for some or many people. Im getting the same error and it started when his website started to have connectivity issues. All other sites for me work fine. Perhaps Droidz can let us know what happened and if we can expect more outages
  3. I tried this, had the bit pickup quest, then RunCode step, then pulse to go do the quest (set 4 towers on fire, 30 sec cooldown between each use if item) After it picked up teh quest the log spits out [D] 16:05:44.288 - [Quester] RunCode[29]: robotManager.Events.FiniteStateMachineEvents.OnRunState += (engine, state, cancelable) => (and the rest of the code you posted above) and then just sits there doing nothing, i waited a few min and nothing else happened. If i remove the code the bot will go and do the quest (and fail due to the item cooldown)
  4. Alright got past that as well. I did it by disregarding the NPC i wanted to take the flight path from and simply doing a turnin (like before) and letting the bot get to the turnin NPC by whatever means it desires. I feel like this sort of "let the bot fill in the gaps" leaves a lot of chances for the bot to get completely lost. What if the bot doesn't take that flight path and decides to walk? Why isnt there a clear way to force the profile to take the flight path from that NPC then continue to the next quest action? Im a noob and dont see it (other than doing custom code. but for s
  5. Getting to and through the portal isn't the problem, its after the portal the bot was freaking out thought it was stuck started running to bad places etc. I got it working now by continuing a path forward after the portal and forcing the bot to not confuse itself. At that point then the "Current quest will be complete at last position" worked by forceing the bot not to skip the movement phase and not disallowing the turnin action like it was before (maybe becuse the bot confused itself and never got to that point?) He then walked to the turnin npc, turned in, and picked up th
  6. Getting to and through the portal isn't the problem, its after the portal the bot was freaking out thought it was stuck started running to bad places etc. I got it working now by continuing a path forward after the portal and forcing the bot to not confuse itself. At that point then the "Current quest will be complete at last position" worked by forceing the bot not to skip the movement phase and not disallowing the turnin action like it was before (maybe becuse the bot confused itself and never got to that point?) He then walked to the turnin npc, turned in, and picked up th
  7. Hi, new at questing work and learning how to use it for fun. First task is simply i want to: 1. Talk to the NPC outside of the Dark Portal (before you enter Outland) √ Complete 2. Collect the quest he has. √ Complete 3. Walk to the Dark Portal and go through it X Lolnope So what I tried first was to make a quest with followpath. The npc i turnin to is on the other side of the portal. I ran this and the bot collected the quest and started to try to run to outland via northrend 🤣 instead of walking to the portal. Bot ignored my followpath and proceeded directly t
  8. This isnt a quest profile, this could really be done better by grinding hotspots and level conditionals
  9. This is still a problem. Was any fix found? This is not a profile issue. When bot is going to a profile location from across the map for instance, it takes ground rout on a flying mount instead of direct rought in the air. This is very very risky and looks like a bot 100%
  10. Yes I do not use the ascension launcher for this, and I can login with the ascension.exe manually. The relogger allows this too as long as I dont select "relaunch if wow or bot crash". If I select that then the relogger thinks ascension.exe has crashed. Likely because its a modified wrath wow.exe that wrobot doesn't fully recognize as a working version of the wrath client, even though it functions fine ingame.
  11. So after more testing, i believe the relogger thinks the bot crashed and tries to reload it. Unticking "Relaunch if wow or bot crash" allows the bot to get fully running and not trigger it thinking its crashed. However this now makes it so the bot wont relaunch if actually does crash, but at least we know whats wrong. This is still much better than it was this morning. Thanks Droidz.
  12. Log: [D] 03:34:32 - [Info] Log file created: 2 Jun 2021 03H34.log.html 03:34:32 - Relogger 1.2.0 (21544) started. [D] 03:34:32 - [Info] Offical website: https://wrobot.eu/ [D] 03:34:32 - [Info] Operating System Details: Windows 10 Enterprise [D] 03:34:32 - [Info] Lang: English (United States) 03:34:32 - Tips: To improve CPU usage, it is recommended to minimize this window when unused. 03:35:45 - Start profile Profile name. 03:35:45 - Profile Profile name, Run task[1]: Run (Run) [D] 03:35:45 - Profile Profile name, running task for 62.2196562784815 minutes. [D] 03:35:46 - Profile Profile na
  13. This is much better great plugin! However what is happening now is it opens wow, does its thing well with renaming, then opens wrobot. Wow finishes logging in and then 1 of 2 things happends: 1. Wrobot doesn't fully finish launching to its main window ("launch bot" and "please connect to the game" window) Before wow can finish loading up, relogging quits wow and quits wrobot and tries again 2. Wow finished loading and i get ingame, and 5 or so seconds later wrobot also loads and starts playing the tasks i have it play. Then relogger force-quits wow and wrobot and this als
×
×
  • Create New...