Droidz

j'ai pas retrouvé le log, mais je vais relancer le bot sur ce profil tout a l'heure on vas voir si il le refait, sinon en mettant lae radar 3d, j'ai vu qu'il bloqué sur le chemin pour retourner sur le circuit du profil

I figured I would write this after using the bot for one month, just to get out how I feel about going forward.  I want to buy an unlimited subscription to this bot, but after this month, I am going to, for now, only purchase one more month's worth of time.  I will get into the reasons as to why, bear with me. 
 
I like this bot, I really do, it has great potential and the community is active, friendly, and just plain good people.  I like that I can choose to create a fight class the "cookie cutter" way by using the bot itself and setting rotation priorities, OR I can write a fight class using C++.  Pasterke, I hope you don't mind but at the moment I am revamping your Blood DK fight class and may share it here within a week or two once I have the bugs out.  Your foundation was awesome, don't get me wrong, but, being an ex hardcore raider, I am extremely picky when it comes to rotations and as to when to pop cool downs, so I used your already awesome Blood DK .cs file and tweaked it a bit. 
 
Profile recording is a breeze, and honestly, I created some pretty intensely huge profiles in multiple zones, I mean literally ALL of Outland, ALL of Pandaria, ALL of Northrend, profiles that took me hours to create, and this bot handled these profiles with absolute ease.  There was no lag or stuttering due to an oversized file, no pausing for mesh updates, no double-backing on the path because the profile was recorded "too close" in proximity to other waypoints, it just works flawlessly. 
 
The biggest, and I am going to start with the BIGGEST reason here, the biggest reason I am waiting another month before purchasing the unlimited is because of stuck detection.  In Zangarmarsh, for example, with the huge mushroom-tree things, if the bot detects a node and is flying above that mushroom-tree line, the bot will dive down on top of the mushroom cap, once it hits the cap it will fly back up about 10 feet, then spiral down back to the mushroom cap top, rinse and repeat over and over, each fly up/spiral down takes about 3-4 seconds, so imagine if a player was watching the bot do this every 3-4 seconds for a minute or more....
 
This particular situation happens on many obstacles in the game.  If the bot detects a node and there is a rock or crystal formation between the path of the node and my character, the bot will literally just fly into the rock or crystal or whatever obstruction is in the way, it will not attempt to move, fly up, nothing, just keeps flying straight into the obstruction.  I don't want to compare this bot to any other bots, but for the sake of constructive criticism, I am going to, sort of. 
 
The last bot I used had decent stuck detection, though I don't know how the code was written, I was never shown the source, I can tell you what the bot did for stuck detection.  If the character became stuck, in flight, due to an obstacle, first it would try flying left and right 15-20 yards to get "around" the obstacle.  It attempted once to the left, once to the right.  If this failed, the bot would fly the character straight up, as if the player was holding the spacebar, about 100 yards, then forward about 35 yards, then do the left/right thing and try flying back down.  If it was still stuck at this point (you could set the amount of "stuck" tries in the bot in case you didn't want to go through this more than once...), it would fly up 50-75 yards higher than it did the first time, then forward/ left/right and try landing again.  It would repeat this, each time flying a little higher to try and clear the obstruction until it either succeeded or the specified amount of attempts had been reached and it simply just moved on to the next waypoint in the profile.
 
Fortunately, I keep a close eye on the bot when I am using it.  I am not the type to let it run for 12 hours without watching it, I think the longest I have run it for straight was 8 hours, and even then I am watching it at least 70% of the time while doing other things.  Honestly, I can live with skipping nodes.  I can live with not gathering a node after combat is finished, these are small glitches and, honestly, in the grand scheme they really don't affect production.  Not having a good stuck routine, however, that can lead to players reporting you and getting you banned. 
 
This is my concern.  I am not always going to be able to watch the bot like a hawk, honestly, let's face it, the point of botting is to "not" have to be in front of the game, at least that's what my end goal is.  This cannot happen, unfortunately, if a player is continuously nose diving in spirals into a huge mushroom cap in Zangarmarsh or flying into a crystal formation in Hellfire.  Even in Jade Forest and Kun Lai Summit I catch the bot just flying into a bamboo tree or stuck on a ledge.  All I have to do sometimes is simply press the spacebar once quickly, sometimes that's all it takes, and bam, not stuck anymore, but I know this can be detected from within the bot and an automation can be written for it.  
 
Once this happens, honestly, I won't even wait for my month to be up whenever it is, I will buy the lifetime license outright, however, until action is taken in this area, I am going to use this bot and pay for it on a month to month basis.  This may be more financially taxing to me in the long run, however, one fix of one issue is all it would take. 
 
Otherwise, as I stated above, this is literally the smoothest running bot I have ever used, I really do like this bot a lot!!!
 
Waldo
 
 

Hello it is to track in wow minimap object/npc by type: 

NOPE! not gonna happen. While botting on wotlk you will never get better xph before 60lvl by questing than you can by grinding. Grinding profile incoming soon
https://www.youtube.com/watch?v=5FjWe31S_0g

It is because you use cracked version

It is because you use cracked version

https://gaming.youtube.com/channel/UCW4t5cMSvhxXJ1ZLfy6ujMg/live

I have added WRobot TBC: http://wrobot.eu/files/file/2-wrobot-official/ if someone can test it.

I don't found how to get quests completed list (Wow 2.4.3 has not function similary at GetQuestsCompleted()), I'll release without quest support (I'll try to  bypass this problem after, but without GetQuestsCompleted() , the quester product will be less easy to use). I'll start to work on Battleground bot.

I continue to work on it, I need to finish to correct Quests and PVP API. I think release the beta version this weekend or during next week.

Because I get many request, I will try to add TBC support at WRobot  (I have not release date for the moment, but I progressing well)

hello, http://wrobot.eu/bugtracker/profile-generators-possibility-to-override-min-range-of-45-example-useitemon-r411/?do=findComment&comment=2844

yeah!
A->B->C-> C#:wManager.wManagerSetting.ClearBlacklist(); ->A->B->C-> C#:wManager.wManagerSetting.ClearBlacklist(); ->A
I solved the problem.
It is fantastic

Hello, yes after farm WRobot add spot to blacklist for 120 secondes if you use flying mount, or 60 seconde if you use ground mount. You can use this plugin to clear automaticly blakclist (blacklist is clear all 2 sec by default, replace "2" by "60" line 16 if you want clear all 60 secondes): http://wrobot.eu/forums/topic/2747-clear-session-blacklist/?do=findComment&comment=12547

For the moment I have not found two WRobot features, "Aura.Owner" (I ignore if in BC npc can get several time the same buff casted by several player) and "WoWUnit.CastingCanInterrupt".

Because I get many request, I will try to add TBC support at WRobot  (I have not release date for the moment, but I progressing well)

Because I get many request, I will try to add TBC support at WRobot  (I have not release date for the moment, but I progressing well)

Because I get many request, I will try to add TBC support at WRobot  (I have not release date for the moment, but I progressing well)

There we see a great admin again. Listening to his users :)

Because I get many request, I will try to add TBC support at WRobot  (I have not release date for the moment, but I progressing well)

Because I get many request, I will try to add TBC support at WRobot  (I have not release date for the moment, but I progressing well)

Hello, sorry I did get some problems during website upgrade but now problem is resolved.
Regards.

After "var msg = chat.ReadMsg();" (line 34) you can add this line: 
Logging.Write("Channel = " + ((int)msg.Channel) + " (message: " + msg.Msg + ")"); (this line writte in log tab the channel number, when you get channel number, you can remplace 49 in "(int)msg.Channel == 49" by your channel number)

Hello,
To disable detection when player is attacked, use this c# code: http://wrobot.eu/forums/topic/2681-snippets-codes-for-quest-profiles/#comment-13088
To use this code, you have a lot of ways, the more easy ways is to add this on your profile like this: http://wrobot.eu/forums/topic/2202-profile-positions-and-action-column/ or you can run this code in tab "Tools" > "Dev... tools" > paste code in textbox and click on button "Run c# code...".

On WOTLK "UnitGroupRolesAssigned" change, try this (not tested):
public WoWPlayer GetPartyTank() { WoWPlayer tank = new WoWPlayer(0); var lua = @" for groupindex = 1,MAX_PARTY_MEMBERS do if (UnitInParty('party' .. groupindex)) then local isTank, isHealer, isDamage = UnitGroupRolesAssigned('party' .. groupindex); if isTank then local name = UnitName('party' .. groupindex); return name; end end end return ''; "; // Get tank name string tankName = Lua.LuaDoString<string>(lua); if (!string.IsNullOrEmpty(tankName)) { tankName = tankName.Trim().ToLower(); //foreach (var p in Party.GetPartyHomeAndInstance()) foreach (var p in ObjectManager.GetObjectWoWPlayer()) { if (p != null && p.IsValid && p.Name.Trim().ToLower() == tankName) { tank = new WoWPlayer(p.GetBaseAddress); break; } } } return tank; }