-
Posts
12434 -
Joined
-
Last visited
Reputation Activity
-
Droidz got a reaction from Jechtshot in WRobot for private servers, new versions supported
Hello,
Now, WRobot for private servers support also Wow versions 5.4.7.18019 (mop) and 6.2.3.20886/20779 (wod).
Complete list of supported versions (tooday):
Warlords of Draenor: 6.2.4.21742 and 6.2.3.20886/2077. Mists of Pandaria: 5.4.8.18414 and 5.4.7.18019 Cataclysm: 4.3.4.15595 Wrath of the Lich King: 3.3.5a.12340 The Burning Crusade: 2.4.3 8606
View full article
-
Droidz got a reaction from blackbyte in Druids Broken
Hello, sorry for the trouble, I just fix the problem, update WRobot.
-
Droidz got a reaction from Florinus in WRobot for Wow 7.1.5 bugs reports
About druid problem: http://wrobot.eu/forums/topic/4237-druids-broken/?do=findComment&comment=19642
-
Droidz got a reaction from MrBottie in Druids Broken
Hello, sorry for the trouble, I just fix the problem, update WRobot.
-
Droidz got a reaction from olek83 in Update Status - Patch 7.1.0 Build 22900
Hello,
I start to work on this patch
ps: More info about this version: http://www.wowhead.com/g00/news=257057/patch-7-1-survival-guide-return-to-karazhan-suramar-campaign-raiding-with-leashe
-
Droidz got a reaction from cgeorg13 in Update Status - Patch 7.1.0 Build 22900
Hello,
I start to work on this patch
ps: More info about this version: http://www.wowhead.com/g00/news=257057/patch-7-1-survival-guide-return-to-karazhan-suramar-campaign-raiding-with-leashe
-
Droidz got a reaction from AudreyH in Update Status - Patch 7.1.0 Build 22900
Hello,
I start to work on this patch
ps: More info about this version: http://www.wowhead.com/g00/news=257057/patch-7-1-survival-guide-return-to-karazhan-suramar-campaign-raiding-with-leashe
-
Droidz reacted to Arcangelo in Legacy servers
http://blue.mmo-champion.com/topic/778451-classic-server-update/
Update -
-
Droidz got a reaction from syees in Bot Freeze after X minutes
Hello, try to remove folder "WRobot\Data\Meshes\".
-
-
Droidz got a reaction from mkeagy in Sky golem fixed yet?
I'll add this feature. If you can help me to complete list of all mobs spawn by the herbs:
http://www.wowhead.com/npc=98232/withered-hungerer http://www.wowhead.com/npc=98234/nightmare-creeper -
Droidz got a reaction from razilein in Request (Bot statistics at the end of log file)
Hello, I'll add it. I comeback here when is done.
-
Droidz got a reaction from da8ball in Sky golem fixed yet?
Hello, do you have try to active option "Ignore fighting during farm if in druid form" in advanced general settings tab "farming..."?
-
Droidz reacted to KnightRyder in Interact with NPC with no Objective count
The "Auto detect Objective" doesn't seem to work either. There's probably another (better) way but I got it to work.
Since the NPC ID changed after interacting, I was able to use the "Is complete condition" and put the following code in:
return ObjectManager.GetWoWUnitByEntry(88889).Count == 1; The new NPC spawns after being interacted with, therefore marks it complete and can go to next step.
-
Droidz got a reaction from Arcangelo in A little clean up in the bot + features
Hello,
I have keep note of your suggestions, I'll look it when I'll work again on tbc version.
but since last update, WRobot save quest turnin (quester works)
-
Droidz got a reaction from Arcangelo in Use emotes in quests
Hello,
Use quest type "InteractWithNpc", add position and stolem rams id, in "Macro when interact" put:
RunMacroText("/whistle")
-
Droidz got a reaction from KnightRyder in Re-use item to get buff
Hello,
You can create plugin (change id in this plugin: http://wrobot.eu/files/file/517-potion-of-luck/ )
Or, if it is only for one quest, add step type 'RunCode' before 'pulse' (and after 'PickUp') quest with code:
Thread t = new Thread(() => { uint itemId = 62899; int questId = 93351; uint buffId = 135855; while (robotManager.Products.Products.IsStarted) { if (Conditions.InGameAndConnectedAndAliveAndProductStartedNotInPause) { if (!Quest.HasQuest(questId)) break; if (!ObjectManager.Me.HaveBuff(buffId)) { ItemsManager.UseItem(itemId); } } Thread.Sleep(500); } }); t.Start(); (ofcourse, change itemId, questId and buffId)
-
Droidz got a reaction from kunfuninja12 in Last Detection Date?
Hello,
WRobot was never detected.
Yes you can use WRobot only for rotations (With 'WRotation' product).
-
Droidz reacted to eeny in Patch 7.1 - 2 weeks away
For those who didn't know, incoming blood of sergeras trader
http://www.wowhead.com/news=256536/patch-7-1-ptr-preview-profession-and-blood-of-sargeras-updates#blood-of-sargeras-trader
Finally something for the 'gathering' community =).
Anyone got tips- i was going to wait it out for a month for prices of mats to stable out ( im expecting them to crash) then trade off100 blood at a time for whatever will sell,
-
Droidz got a reaction from Bobbleswaggr in Freezes when getting attacked on sky golem
You have two choise:
By default (with default wrobot settings), WRobot dismount if you are attacked and near the node to kills mobs (if you are not near node, mobs are ignored).
Or you activate option "Ignore fighting during farm if in druid form" (in advanced general settings tab "Looting and..." and WRobot skip nodes when your character is attacked (and skip fight also) if you are in sky golem).
-
-
Droidz reacted to nightmist in Safe Botting
Being a veteran of the botting world here are some tips and tricks. Some are common sense but want to make this as comprehensive as possible.
Intro:
Blizzard uses big data analytics and customer reporting to catch botters. For the analytics portion they crunch numbers that flag an account. For example if your account is active 19 hours a day you will get points added to your account. Customer reports add more points. Unusually interactions methods get another. Once you accumulate enough points you are flagged for investigation. Investigations could be turning on various anti cheat processes to record whats in your memory or what processes are running. Other investigations teleport your toon or get them stuck to see how they respond. So to sum up, Blizzard crunches numbers associated to various activity to see if you are a worthy target for investigation by live people. There are automatic methods to catch botters that are in use. Usually perm bans involve a direct blizz employee investigating your toon and temp bans are generally automated systems.
Tips
Bot a realistic number of hours. Include actual playtime into the calculations. For example don't bot for 9 hours then play for 6.
When botting use plugins that mimic player behavior if at all possible. There are some risks with these so use them with caution. Thank you to the authors of the plugins, great job http://wrobot.eu/files/file/519-me-human/ http://wrobot.eu/files/file/515-random-jumper/ http://wrobot.eu/files/file/359-whisper-reply/ http://wrobot.eu/files/file/303-move-during-combat/
Play your bot if at all possible. Many people have farm toons so its ok not too however playing your bot will remove analytics against it. Just queue up for some dungeons a couple of times a month or so. If you are dungeon botting (just don't, dungeon botting will get you caught so quickly) then farm with the bot or quest, do something different.
Bot in the after hours on your server. Botting during prime time causes two issues. First, you will be very inefficient with your botting since so many others are farming Second, you increase the risk of getting caught
Name your botting toon something generic and something that isn't easily remembered. If you name your toon SirButtFarmer that will get a chuckle and then reported once someone sees it a billion times running around a zone. Name it something close to a popular guild on your server, so it will blend in.
Create your own routines. For gatherer go to product settings then profile creator. Click record path, run around the zone (use a farming addon like FarmHUD) and stop recording when done, save and use it. Blizz doesn't flag toons running specific paths or locations. It isn't practical to record that much data for so many toons. They would need to store, process and analyze tremendous amounts of data points and the costs make it unjustifiable. So its ok to run shared profiles.
Use the wonderful relogger application. Seriously the thing is AWESOME. See more on that below
As said previously don't dungeon bot, I see so many bad dungeon botters, you will get reported and you will get caught.
When a new blizz update lands, hold off on botting for 24-48 hours. Sometimes updates are to catch certain things or add world bosses that can break paths. Be careful
Watch your bot on new profiles and check in on it. Once you run it for a few days with close eyes you can leave it running for long periods of time.
Relogger
I run relogger as my tool for farming, its amazing. For example here is what you can do:
Run a task such as gatherer for X amount of time. Run a second task called wait to close wow and wait. This wait could be a break, such as I just played wow for 3 hours time to get up and stretch for 15 minutes. It makes you appear human Run a task to log back in and run your farmer. Then add another task to wait again this time to sleep for 7 hours or so. Do more farming and eventually but in a final wait and list the time at 9000-9999 which will keep it closed. That gives you time to manually shut down operations or do whatever after the maximum time has been reached. See the picture forming here. Use relogger, its a powerful tool that will maximize your botting time while keeping the analytics down against you. There are numerous excellent tutorials on the forums so just search for them.
-
-
-
Droidz got a reaction from da8ball in Milling not working!
Sorry for delay. I just release update. Restart WRobot and accept update.