FNV316

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:

28 minutes ago, arkhan said:

Strange that it needed a relaunch to take the change on.

Sometimes plugins aren't fully disposed when stopping the bot. Probably what happened.

Np.

Can you share log of this one too? Did it make its way to the vendor earlier or has nothing changed at all after disabling the plugin.

.

Try to disable the HumanMasterPlugin and check if it it's working. I had some issues with it too, if automatically choose vendor is enabled.

Please post your log file.

You have to copy the exact path, as you can see it in the profiles selection within the "Product Settings", and paste that into the "Load Profile" step.

Hello, I would recommend reading trough these two threads below and take a look into the code of free questing profiles provided here. There is no wiki or API. In my experience, wRobot is learning by doing. If you have a specific question and cannot find a solution in the forum, feel free to create a new topic.

It's not just the game. CPU usage also depends on profile, fight class and plugins. It's not the same version of wRobot for each expansion too. For me on vanilla, it uses up to 15% CPU during fights per instance on a faster CPU than yours. 1% maybe when waiting to resurect.

11 hours ago, Crespo said:

The quest that hunter does at level 10, only these pets he is trying to attack untill they turn quest in or something, i doubt its the fight profile, because both pally_C and mcro rogue have this happening (orc and dwarf zone)

Profiles can modifie settings. I had this problem on my hunter as well, but got rid of it by disabling attack before being attacked. It should cause the bot to only attack mobs that are already attacking the bot or that are specified as target in the profile.

You could try to force ignore combat completely, as shown in this snippets. Run the code to disable combat before taming and enable it right after turnin:

17 minutes ago, codek said:

Ich mein ja man soll keine Items oder Gold zwischen den beiden Charakteren handeln aber wofür bottet man dann?

Weil's Spaß macht?

Das Problem ist, GMs sind nicht so dämlich, da keinen Zusammenhang herzustellen. Niemand verschenkt grundlos größere Mengen Gold / Items an Wildfremde, ohne Hintergedanken. Auch Goldseller werden erkannt und gebannt. Goldkäufer seltener, aber wenn's dumm läuft ebenfalls.

Eine Möglichkeit die mir in den Sinn kommt ist, auf einem Account eine gewisse Menge Gold / Items anzusammeln, den Account dann für einige Wochen / Monate ruhen zu lassen, sprich nicht botten. Vielleicht noch gelegentlich einloggen, um Aktivität zu simulieren. Wird der Account innerhalb dieser Zeit nicht gebannt, Gold und Items auf den Main-Account traden ( + vlt. noch einen Chatverlauf schauspielern, damit es authentisch wirkt) -> Accountaufgabe. Botten solltest mit dem dann aber in absehbarer Zeit nicht mehr.

Möglich wären auch Umwege über das (neutrale) Auktionshaus. Trotzdem bringt all das immer noch ein gewisses Risiko mit sich. Wenn du Gold / Items 100% sicher transferieren möchtest, dann lass es.

Jeder halbwegs ambitionierte GM wird die Logs überprüfen und feststellen, dass du einseitig Werte von einem (als solchen erkannten) Bot-Account an einen anderen (mutmaßlichen Main-)Account transferierst. Da nutzt auch ein dritter Account als Zwischenhändler nicht viel. Selbst wenn alle Accounts über unterschiedliche IPs laufen (wovon ich ausgehe), wirst du mittelfristig auffliegen. Spätestens, wenn der zweite oder dritte Account gebannt wurde, der dir ohne Gegenleistung Items oder Gold zuschickt.

Wenn du deinen Main-Account behalten möchtest, würde ich dir dringend davon abraten, Items oder Gold zwischen Main und Bot auszutauschen. Höchstens kleinere Beträge, in unregelmäßigen Abständen und mit längeren Pausen dazwischen. Oder zumindest halbwegs logische Geschäfte. Also zum Beispiel Kräuter / Erze in großen Mengen zum halben Preis. Wobei das trotzdem ein hohes Risiko birgt.

16 hours ago, Crespo said:

its off already :(

Not sure if I understood your problem correctly: The bot tries to attack your own pet respectively other hunters pet? Does this issue occur with another profile / fight class?

2 minutes ago, Crespo said:

I don't think you understood what I mean, the pets that hunter does as a quest at level 10, they are like 30-50% hp, green bar, but bot is still trying to attack them, in both vanilla and tbc, and this plug-in didn't work.

Try to disable "Attack before being attacked".

tl;dr There is no API, so you need a decompiler.

wManager.wManagerSetting.CurrentSetting.UseSpiritHealer = true;

Hello, you can add this code (Run Code as quester step):

wManager.wManagerSetting.CurrentSetting.LootMobs = false;
wManager.wManagerSetting.CurrentSetting.Selling = false;

On 10.1.2018 at 11:46 PM, arkhan said:

Is it because i play on the same ip than the first account ?

Most likely this one. Use a proxy to have a separate IP for each WoW instance. Never bot on the same IP as your main account.

Try that: Download Nvidia Inspector (or the AMD equivalent, depending on your graphics card), add vanilla wow.exe to profiles, set Frame Rate Limiter to 60,7 and V-Sync to Force on.

Works fine as well.

Dein Posting wirkt unseriös. Daher ist Misstrauen auf jeden Fall angebracht, insbesondere bei einem neuen User ohne bisherige Beiträge. Ob es das am Ende auch ist, steht auf einem anderen Blatt. Am besten du gehst den offiziellen Weg, testest dein Profil und bewirbst es erst im Anschluss. Dadurch vermeidest du Situationen wie diese.

1.) You could blacklist this area for the specific profile, so the bot doesn't move trough there in the first place. Or disable "Attack before being attacked", disable "Ignore combat with all pets" and enable "Ignore fight with players" (if that is what you mean by hunter pets). Try what fits your needs best.

2.) No. Either something with the server or probably started eating before being in combat? Or do you have a pet? You can still be out of combat, even if your pet is in combat. Never experienced on LH or Elysium. Can you provide some logs?

1 minute ago, Theosis said:

Tried closing team viewer, and starting it, no difference, still the same problem.

Restart your computer, make sure TeamViewer is not running in the background and only start WoW + wRobot. If the problem still occurs, keep your head down, take cover under a table and wait for Droidz to solve your problem.

1 hour ago, Theosis said:

5 Jan 2018 12H54.log.html

Have you tried closing TeamViewer completely?

Hello and welcome, newcomer.

You can "fix" this with a workaround: Set values for using Holy Light in the settings to a low value like "10% to 30%" (or get rid of it completely), so that it won't get triggered very often and let the fight class do the healing for you. You have to change your fight class for that -> f.e. add out of combat, heal yourself up to 80% if below 80% . So you either heal before drinking or right after. Fight class should not interrupt regen state.

Nice list you created there, especially for users new to botting. Let me add some additional points:

-You can start Tracker before any other modul and select humanoids, so it's much easier to keep track of nearby players on the mini map, even if they are out of sight (humanoid NPCs will be displayed as well tho). Tracker should stay active until WoW has to reload.

-Especially for grinding, going back to town on a regular base can help to reduce the risk of other players monitoring you for a longer time or running into the bot over and over again. The chance getting caught while doing non bot related stuff is pretty low in my experience.

-Don't bot seven days a week, let it sleep a couple of days every other day.

-If someone invites you into a group to do a quest with them, don't just log out (-> bottish behavior). Move to a safe spot and let the bot paused (-> /AFK) for long enough to be sure the player has moved on.

-Addons like TinyTip allow you to see other players target by just hovering over them. If you see someone targeting you, target them back.

-Wrobots remote function allows you to monitor your bots without staying at your computer all the time (f.e. via smartphone).

-Avoid areas with a high density of quests if possible. Don't grind on mobs related to quests.

-Use tools to increase your latency to ~300-500 ms (personal preference). This helps to hide bottish movement / behavior.

-Never use more than one IP for each bot instance or even your main account. Set up a proxy or get yourself a fresh IP.

Just a short update: I tested it with different characters and it's now working reliably. Good job!