Droidz

Hello, do you have few log files of bugged bot sessions please.

Hello,

To install the bot, you can find the link and notice here : https://wrobot.eu/files/file/2-wrobot-official/

You can found profiles here https://wrobot.eu/files/categories/

This video can help you : https://wrobot.eu/forums/topic/3633-getting-started-with-wrobot-video/

I'm pretty sure your code is not running, but I don't know why. it could be due to a bad quest ID or something else.

Your code is in the quest "EnvoytotheHorde" ?

The code is not executed, at no time in the log file is there a path lookup for the position of your code.

your code or my code should work. Can you share log when the bot should run this code please

Hello,

You don't need to wait (while (MovementManager.InMovement)) with gototask.

You can directly interact with a game object with code like :

var pos = new Vector3(9992.634, -7113.402, 47.70632);
int clickonobject = 184502;
bool result = GoToTask.ToPositionAndIntecractWithGameObject(pos, clickonobject);
return result;

Do you have any error in your log when bot run this task ?

You can try to fix manually in "Npc DB" the positions of bugged flight masters. Or, if you use a quester profile which must often take flightmasters you can add the necessary steps that the profile uses them itself.

Can you try to remove all elements of your taxidb (you can found button "Taxi DB" in the tab "Tools") and when bot try to take flightmaster check again element of this list. These elements seem correct (you can send a screenshot) ? It's the same flightmasters that on the original server? Your game client is unmodified?

Hello,

Look https://wrobot.eu/files/file/481-combine/

Hello,

You won't be able to easily manage the character's movements from a quest profile when the character is dead.

One of the possible approaches (untested code):

robotManager.Events.FiniteStateMachineEvents.OnRunState += (engine, state, cancel) =>
{
    if (state is wManager.Wow.Bot.States.Resurrect)
    {
        if (ObjectManager.Me.IsDead)
        {
            MovementManager.Go(PathFinder.FindPath(new Vector3(819.1201, 541.1679, 34.26245, "None")), false);
            while (MovementManager.InMovement &&
                   Conditions.InGameAndConnectedAndProductStartedNotInPause &&
                   ObjectManager.Me.IsDead)
            {
                Thread.Sleep(100);
            }
            // cancel.Cancel = true;
        }
    }
};

You need to run this code only once and add your own conditions for it to run at the right time.

Hello, do you have try without game addons ?

Hello, in battlenet put your game account name

Hello, you should use Wow lua event : https://wrobot.eu/byme/doc/html/E-wManager.Wow.Helpers.EventsLuaWithArgs.OnEventsLuaStringWithArgs.htm

Hello,

Try renaming the file to 'Wow.exe'.

But, I think the problem is because the server is using a modded version of the client, WRobot only works with the non-modified game client.

I'm not home for 2 weeks, I'm watching this again when I get home. If you can just try with a new installation of WRobot (one relogger instance, even with a wow account that does not exist to see if the freeze this product from time to time or not).

In relogger general settings, "wait after launch" option has correct value for your computer? Do you use the option "Lock when launch.... (only this relogger process)" ?

If you launch only one instance you get also this probleme from time to time ? Do you have try to remove wow cache ?

I can't reproduce the problem.

I tried with one and several clients (several dozen times, maybe even a hundred).

I start a profile (or several) and click on "Kill All" when all are in game.

Are you sure it's not a wow addon that's causing the problem or a relogger configuration? Have you tried with a default wrobot (just installed with one of the relogger profiles)? Antivirus can also cause this problem.

You get the problem all time at same moment of login screen ?

Hello,

These errors are most likely caused by the game being closed. 

Do you have the complete log file? Do you have this problem often or not? After how much time ?

Hi,

Without stop/start often you have this problem? If I stop/start manually can I reproduce this problem? When you stop the relogger do you close all instances (games/bot)?

Hello,

To see how to detect, the idea would be to look at the characteristics of the character that WRobot can extract with and without impairing movements.

To extract character info go to tab "Tools", click on the button "Dev... tools" and click on "all memory info". To check differences if you haven't application for that you can use website like https://www.diffchecker.com/text-compare/

If you don't found useful value, check Wow lua API.

Download and move the file in the folder "wrobot/plugins". Launch (or restart) bot, in the tab "Plugins" enable it.

Hello,

And this plugin : https://wrobot.eu/files/file/411-auto-accept-wow-popup-window/

You need to wait after movementmanager usage :

        MovementManager.Go(PathFinder.FindPath(new Vector3(819.1201, 541.1679, 34.26245, "None")), false);
        while (MovementManager.InMovement &&
               Conditions.InGameAndConnectedAndProductStartedNotInPause)
        {
            Thread.Sleep(100);
        }

But, I don't think the quester executes this code from a runcode step when the character is dead.

Hello, can you share the party of your code? You call it from where ? GoToTask by default doesn't work if your character is dead, but if you use movementmanager you shouldn't have this problem.