Jump to content

Marshalek

Members
  • Posts

    82
  • Joined

  • Last visited

Everything posted by Marshalek

  1. @Matenia How can I choose which drink the bot buys automatically? Currently the bot is buying the highest usable drink, but there is no need for that, it's just a waste of gold, I could be using a drink that's 1 tier below, which would cost less. How can I choose this?
  2. Pulling groups and chain dying to ogres at Camp Boff in Badlands for quest "Scrounging". Also talking to wrong NPCs to pickup/turnin Badlands quests.
  3. @Andoido grinding on the Witherbark trolls in Arathi is not working out, the area is too densely populated and pretty much most of the time I have 2-3 mobs on me, which leads to chain dying.
  4. Droidz already went as far as rebranding Wrobot with "Bot for private servers" so I don't think he's even planning on trying...
  5. Well, if they forced HB and WR out of business (with regards to retail) I think they have the upper hand on this game...
  6. Private botting community? I thought Blizzard had found a way to catch all bots regardless of user count?
  7. @Bambo more like, the best minds in botting (not me) don't know something, so it can't exist.
  8. @Droidz @Matenia @Andoido @Bambo for insight if wanted... Is it correct to assume that whatever methods Blizzard currently uses to detect bots in retail (BFA) will also be used for Classic WoW? Do we have any hopes of a working bot that's undetectable for Classic WoW?
  9. Sometimes the bot butt-pulls unintended mobs while already fighting one... can't the bot be made to back off a little when there is a group of mobs nearby, to avoid such butt pulls? Kind of like what a human would do..
  10. I'm using 77 search and 1 max units, but was still running into packs of Murlocs. So is this the profile's fault?
  11. If they caught HB and WR, how do you geniuses figure they wouldn't get an amateur dev making a "private" bot? Stop dreaming, botting on retail is over.
  12. @Svartben this is just how Wrobot works, there is nothing that can be done to stop the idiotic pulls / chain dying, it's just how this bot works.
  13. This stupidity is still a reality 01/15/2019, chain dying on lvl 22 Murlocs in Wetlands, using TBC Wrobot. I am not using Bambo's profile nor fight class. @Droidz do you actually use/test Wrobot or is all your development/bugfixing purely theoretical? There's NO WAY you wouldn't know how broken Wrobot is if you tried to use it for SIMPLE THINGS such as grinding. All I can see you telling people is to show logs/reinstall Wrobot - but then they do, you say "wait till next release" and nothing ever gets fixed, bot is always the same broken mess as always... wtf dude can't you fix this stuff? I spend more time MANAGING THE BOTS CONSTANT SHORTCOMINGS than it would take for me to level manually? WTF?
  14. Bot constantly ends up in totally unrelated places, usually dying from much higher lvl mobs everywhere. Examples being ending up in Burning Steppes during Duskwood grind at lvl 22, and ending up in Southshore at lvl 23, when it's supposed to be in Wetlands
  15. @Droidz can you publish the code for this profile? At its current form it seems unusable and I'd like to try and fix it... thanks.
  16. Quest and Objective IDs are good, let me do some more testing on this and I'll post back. Thanks @Droidz
  17. Greetings fellow wroboters, I'm trying to include a "RunCode" step in my quest profile, to run some code only IF the objectives on a certain quest haven't been met yet. This is what I have for the RunCode param so far: if (!Quest.IsObjectiveComplete(2, 9999)) { wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(9999.262f, -9999.587f, 999.8167f)); } The above doesn't work - the code is run every time I get on that step, regardless of whether objective is complete or not. How can I make this work? This is what it looks like in the profile: <QuestsSorted Action="RunCode" NameClass="if (!Quest.IsObjectiveComplete(2, 9999)); { wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(9999.262f, -9999.587f, 999.8167f)); }" />
  18. should just report him ingame since you know what his bot will be doing get those accounts banned
  19. This is so very essentially stupid that I can't believe I'm having to ask. Is there a way to prevent wrobot from instantly releasing from body when I die? This is one of the most obvious ways to spot a bot... Just create a random delay between 1-5 seconds for release? It would look so much more human-like. Is there a super-genius, einstein-level marvel of innovation, visionary developer who could have had a revelation about this very elusive, difficult to even notice, troubling aspect of Wrobot and made a simple plugin to create said delay when releasing from body after death?
×
×
  • Create New...