Jump to content

FNV316

Members
  • Posts

    250
  • Joined

  • Last visited

Everything posted by FNV316

  1. You dont have to change your monitors settings. Just lock WoWs frame rate:
  2. I tried running your code, but it is only functioning if I only run this quest alone. It doesn't function if it's embeded in the whole profile. @Droidz Can other quests / general killing of mobs effect the objective counter? Is there a way to force reset the objective counter without stopping the bot, before pulsing this quest?
  3. It's worth nevertheless to have "close if teleported" on. Sure, if a GM is already confident that he has chatched a bot and teleports it to GM island, you are going to get banned for sure. Still better to just close the bot, than running around in this room like a headless chicken. You could be around, log on again and try to talk your way out, even if the chances are pretty small. Sometimes they just teleport characters a few yards, to see your bots reaction. Even if it may look fishy to just log off, the odds of getting banned are higher if there is no reaction at all. Disconnects / crashes can happen from time to time. I don't see any benefits, if the bot just continues.
  4. You click the link Droidz provided and click on the blue underlined 'Main.cs'. Put it in the plugins folder, restart bot and activate the plugin within the "Plugins" menu.
  5. Looks good so far (lvl 18), combat functions much better. Dead range only happend to me in rare occasions. Caves remain bad, but its far away from broken and tolerable. Serpent Sting is not used when fighting elemental units, but still against mechanicals.
  6. Hello, I have some major issues with the quest "The People's Militia" . The bot won't recognize that the quest has been completed and just continues grinding the specified mobs. It doesn't change if I use manual objective count, it doesn't change if I use full C#, it doesn't change if I use custom complete condition. Furthermore, Quest.GetQuestCompleted and Quest.IsObjectiveComplete always return false, even if the quest is complete. The Current Quests Memory info does display weird values as well, as you can see on the picture below (quest was complete in quest log). First value increments by 64 sometimes, sometimes by 1. The second one does increment by 1 if the first counter goes too high(?). The state there says "complete", but has no effect. It's just this one quests. I recorded several hundreds of quests over the last months, but the only quest with this issues has been PPM part 1. The following similar quests of this chain function without any issues. Version is vanilla. Someone an idea, why this specific quest causes so much trouble? PPM_2.xml 3 Feb 2018 13H03.log.html
  7. wManager.Wow.Bot.Tasks.GoToTask.ToPositionAndIntecractWithGameObject(new Vector3(XXX.xxx, YYYY.yyy, ZZZ.zzz), OBJECT_ID); Use as "Run Code" step and insert coords + corresponding object id. If it's an unit and not an object, check out this post:
  8. Nice! I'll give it a try asap and report back. :)
  9. Has to be: wManager.Wow.Bot.Tasks.GoToTask.ToPositionAndIntecractWithGameObject(new Vector3(2552.44, 856.9836, 51.49502), 148917); Dots instead of commatas for the minor values.
  10. wManager.Wow.Bot.Tasks.GoToTask.ToPositionAndIntecractWithGameObject(new Vector3(XXX, YYYY, ZZZ), OBJECT_ID); "Run code"-step and insert coords + object id. Edit: I was assuming you use it in Quester. I doubt you can do that in Gatherer or Grinder.
  11. Exactly this. Settings are saved for each character individually in the settings folder. But it should be possible to just copy an existing save and change the characters name / server name to the default one, wRobot creates for a new character.
  12. The bot should load and execute your specified next profile, when reaching the "Load profile" step. However, that won't affect the chosen profile in settings. After stopping the bot, you have to either select the next profile by hand (three clicks), or let it run through that currently selected profile again, until it reaches "Load profile".
  13. Does function. Just execute it via quester and use it as a template. And don't forget to set "Not required in quest log" to "true". RouteHStoSW.xml
  14. Well, if your ping is too high, you'll lose connection to the server. I also experienced that the bot won't turin quests correctly if I delay my latency to 800+. But getting kicked for a too high latency like in a FPS doesn't make sense in a MMO, that has players all over the world. Outside of groups and PvP, a high latency only (negatively) effects your own gameplay. Sweetspot seems to be between 300 and 500 ms. I myself used NetLimiter and NetBalancer. No idea about CfosSpeed. Just give it a try or do some google research.
  15. Afaik it's just executing lua movement functions, instead of simulating mouse clicks or keyboard input.
  16. No, your real latency to the server. Bot settings latency is only for the bots internal processing. Certain programs let you do this. Or you could just download a lot of porn.
  17. Delay your latency to 300+, so other players won't recognize it. Doesn't solve it, but is a handy workaround. Helps to hide other bottish behaviour as well.
  18. Damn, that sucks! All fine, take your time. Just wanted to let you know. Get well soon!
  19. 1.0.1 runs overall better (Cheetah, less chain pulls by backpedal), but I experienced that the bot is getting stuck frequently in dead range, where it can't use ranged attacks nor melee. Worked much better in 1.0.0.
  20. private bool useSerpent(WoWUnit unit) { return unit.CreatureTypeTarget != "Mechanical" && unit.CreatureTypeTarget != "Elemental"; } if(useSerpent(ObjectManager.Me.TargetObject)) Not tested, but similar code works for warrior.
  21. That does indeed look weird. Have you tried downloading wRobot again? Maybe a corrupt file. As a workaround you could use a program like Sizer to make the window larger by force.
  22. Which resolution do you use? Problem is probably not the bot, but your system settings. This may help:
  23. Hello, why gatherer? Using quester and just setting up a route (follow path) seems more reasonable. Activate "Current quest complete at last position" makes sure the bot just stops when reaching the end. You can execute your custome code there pretty easy too. To force bot on using taxi:
×
×
  • Create New...