ScripterQQ

There are some things that I can't understant too, for example I noticed on battleground my Priest Fight Class once ressed does this:
Inner Fire > Mount > Dismount > Vampiric Embrace > Mount > Dismount > Fortitude > Mount > Dismount > Spirit..and so on. I set all buffs on top priority, combat only = false, can cast on mount= false, and still I get this weird behaviour.
It should ress corpse, Inner Fire, Vampiric Embrace, Stamina, Spirit, Shadow Protection, Fear Ward, and THEN mount. I don't know.

testcounterFIXED.xml

Just wanted to say that the new WRobot layout is very, very good, I totally love it.
Nice Job :)

If you want just grinding mobs, use Automaton, 55-60 is a joke put it in Silithus and enjoy. I used Automaton 1-80 and it works pretty good.

Where do I start? Do I start with you're not subscribed to WRobot and probably using a hacked version or selling an account that may be flagged as a botter to an unknowing person who may lose an account they paid for?

I took another peak at his code, in fact on the first ship he didn't add a control basically because the ship is always in the zone, but the second ship actually appears/disappears from the zone and goes through "portals", so yea he added a check
ObjectManager.GetWoWGameObjectByyId(ID).Count == 0 I guess both options are valid, I just didn't think about the item ID going out of the zone. Now I stick with the null check and I'm fine, the result is the same :)
Still I prefer his code rather than the classic "Catch Zeppelin/Ship", but that's a matter of preferences

I think it might be crashing  because FirstOrDefault is not returning an instance of an object. So, you'll need to check if the object returned is null or not before checking its distance property.
For example:
var tram = ObjectManager.GetWoWGameObjectByyId(176082).FirstOrDefault(); if(tram!=null){ var distance = tram.GetDistance(); if(distance<=25){ Logging.Write("Tram is within 25 units"); } else{ Logging.Write("Tram is farther than 25 units"); } } else{ Logging.Write("Tram is null"); }  
Also, to be safe, you can wrap the entire thing in a try catch block. This will prevent WRobot from crashing.
try{ var tram = ObjectManager.GetWoWGameObjectByyId(176082).FirstOrDefault(); if(tram!=null){ var distance = tram.GetDistance(); if(distance<=25){ Logging.Write("Tram is within 25 units"); } else{ Logging.Write("Tram is farther than 25 units"); } } else{ Logging.Write("Tram is null"); } } catch(Exception e){ Logging.Write("Uh oh... something happened:"+ e.ToString()); }  
 
 

I tried 3 different accounts on Outland, botted for an hour. Didn't get banned. Pretty sure it's NOT server side detection.

Hello, start to use only NPC of your profile:
(use step "RunCode" to run all code)
wManager.Wow.Helpers.NpcDB.AcceptOnlyProfileNpc = true; It is not easy way, but add NPC with C# code like this (use this code when you change zone to select good npc for current level/zone):
wManager.Wow.Helpers.NpcDB.ListNpc.RemoveAll(n => n.CurrentProfileNpc); // Remove in NPCDB all Npc added on current profile var npcRepair = new wManager.Wow.Class.Npc // Npc repair info { Name = "Npc name", Entry = 1234, Faction = wManager.Wow.Class.Npc.FactionType.Neutral, ContinentId = wManager.Wow.Enums.ContinentId.Azeroth, Position = new robotManager.Helpful.Vector3(1, 2, 3), CanFlyTo = true, Type = wManager.Wow.Class.Npc.NpcType.Repair, }; wManager.Wow.Helpers.NpcDB.AddNpc(npcRepair, false, true); // Add npc repair to npcdb var npcVendor = new wManager.Wow.Class.Npc // Npc vendor info { Name = "Npc name", Entry = 1234, Faction = wManager.Wow.Class.Npc.FactionType.Neutral, ContinentId = wManager.Wow.Enums.ContinentId.Azeroth, Position = new robotManager.Helpful.Vector3(1, 2, 3), CanFlyTo = true, Type = wManager.Wow.Class.Npc.NpcType.Vendor, }; wManager.Wow.Helpers.NpcDB.AddNpc(npcVendor, false, true); // Add npc vendor to npcdb If you want force WRobot to go to vendor/repair:
wManager.Wow.Bot.States.ToTown.ForceToTown = true;  

I was kinda whiny time ago, specially for the lack of documentation about what does "this thing" do and what does "the other", I myself spent more time testing features and trying to understand the behaviour, than botting overall. But think about that, right now it's kinda easy to create profiles and stuff once you learned what to press, but imagine having a product 100% "noob-friendly", it would not last long, this robot was (and still is) one of the strongest talking about server detection,
About making a human like fight class, for sure you can implement C# but imho you will never obtain a perfect rotation, my suggestion is yes, implement as many features as you can to protect your bot and not look like a machine after 2 seconds of watching you, but always keep an eye on the bot, never leave it alone.

I was kinda whiny time ago, specially for the lack of documentation about what does "this thing" do and what does "the other", I myself spent more time testing features and trying to understand the behaviour, than botting overall. But think about that, right now it's kinda easy to create profiles and stuff once you learned what to press, but imagine having a product 100% "noob-friendly", it would not last long, this robot was (and still is) one of the strongest talking about server detection,
About making a human like fight class, for sure you can implement C# but imho you will never obtain a perfect rotation, my suggestion is yes, implement as many features as you can to protect your bot and not look like a machine after 2 seconds of watching you, but always keep an eye on the bot, never leave it alone.

It doesn't care of distance. It iterates "states". It checks if each state needs to be run, if true that state is run until it is finished.
Then it continutes to the next state that needs to be run. ToTown and Trainers are 2 different states, so I was talking about priority here.

Hello,
New WRobot update (for private servers) add security features to bypass new detection vectors used on some private servers.
Don't forget to keep WRobot updated.
For the plugins/profiles/fightclasses creators:
I change some methods in "MemoryRobot.dll" and removed "fasmdll_managed.dll".

View full article

Their is a Emulator Project based on 3.3.5, maybe that suits your needs, not sure tho. You can add Bots and queue for a dungeon and stuff.
https://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-emulator-servers/wow-emu-general-releases/560737-single-player-project-tc-r2.html

Hello, it is c# or xml fightclass?
To get faster reactions you need to "unlock FPS limit" (in advanced general settings, you can also try to activate option "Improve combat rotation speed (this option can skip spells)"), if you use XML fightclass put bigger FPS (in your fightclass settings) (or remove sleep time in c# fightclass).
What is slow is to use LUA (or WRobot functions that inject code), try to avoid if you can, for lua if you cannot remove it try to combine scripts. You can use debug option (in xml fightclass) to found slow spells.

you can't just quit botting

General Settings > Enter Advanced Settings

If you can try again

Hello, I took note of your request

Not sure if I'm posting in the correct forum, so if not please forgive me and move the topic .
As the title says, I was thinking about creating some bg profiles, specially for SoTA and IoC that are very tricky, with blacklist zones included in the profile, should we hope to see this feature someday?
I know you kinda don't invest time in the bg product (at least as far as I remember, some admin said like the bg feature was kinda a mistake) but I ask anyway.
I know there is the blacklist zone in the "tools", but having a specific list included in the profile  (just like the grinding one) would be nice.
Thanks for reading

Not sure if I'm posting in the correct forum, so if not please forgive me and move the topic .
As the title says, I was thinking about creating some bg profiles, specially for SoTA and IoC that are very tricky, with blacklist zones included in the profile, should we hope to see this feature someday?
I know you kinda don't invest time in the bg product (at least as far as I remember, some admin said like the bg feature was kinda a mistake) but I ask anyway.
I know there is the blacklist zone in the "tools", but having a specific list included in the profile  (just like the grinding one) would be nice.
Thanks for reading

You can do some research with dnSpy. Download dnSpy.zip, unpack, run and open wManager.dll - and you will see how robot works. New versions are obfuscated, and is impossible to understand what's going on inside, but old are pretty clear (if you know c# or resembling language). Using old and new versions you can find similar places in code and even do patch, for example, change this 45f to 60f. Or understand, is it possible to customize robot with plugin

45f is hardcoded in FightBG private function. 
Do you have decompiler? Try to find old, non-obfuscated robot and open function used in FightBG.StartFight. You will see something like this:
if (woWUnit.Position.DistanceTo(position) > 45f) { Logging.WriteDebug(BlackListSerializable.Icaleodoarea()); return Int128.Zero(); } In old versions you can change this value and recompile, new versions are obfuscated, only byte-patch can help

Best choice is always create your own profile, to minimize the bans, to maximize your playstyle.
Select Grinder mode and start recording a path, where there are mobs..Don't forget to add every type of mob in the "to kill" list. Once you have done stop recording your path and enjoy the grinding. You can also add repair npc and you can create multiple grinding zones based on your character level (for example tanaris 40-44, un'goro 44-46 and so on)

Yep. So you start near the graveyard or the entrance to the BG. Both paths would have to include the graveyard. You then make the rest of your loop so giant, that you are unlikely to return  to the graveyard (this more or less needs to be done anyway, because wRobot always tries to find a straight, retarded path back to the first spot you record at the end, when it reaches the last spot).

You can just run in circles 5 or 6 times, if you have to. Just make sure you definitely die BEFORE it tries to run back to the GY.