ncsupanda

Questers can overwrite those settings - can you share what quester you are using?

Normally after patches you have to wait for wrobot to be able to be loaded, as the version will be mismatched.

How many bots are you running? Have you checked the graphics settings on each bot? If you are running them at extreme/highest quality graphics then obviously you'll see some downgrade in your performance.

Note that you would need the buy the subscription that allows you unlimited sessions if you plan to run it on both PCs at the same time, however.

What does your log say after the loot? Does it attempt to skin but fails, or does it not attempt to skin at all.

Been working to add the last boss / chest, as I usually skipped this and just farmed the earlier bosses/trash. If you want to get a trash farmer for uldum w/o the end boss/chest I can get seller status and list it here. Let me know if interested.

The relogger currently only re-sizes the WoW window the first time it launches or if I manually start/stop. If I tell it to loop the same tasks repeatedly (so a farming route for instance) it will launch it in the normal size and not move it to where I've selected. Thoughts?

I have one that runs the entire dungeon minus the treasure at the end (doesn't unlock door and enter). Lose a lot of time and risk stucks doing that. Let me know if interested, or I can try to tweak what I have.

I've finished one of these - willing to demo it for you, let me know :) Considering selling it here

Same error - tried to reinstall wrobot and see if a clean install repaired it somehow. New log - now it get s to archaeology before falling apart. 29 Aug 2017 20H22.log.html

Its not creating a crash log (probably because its Wrobot that is crashing and not WoW)

1. WoW Open, Firewall/Antivirus disabled. 2. 32Bit WoW Window, 64 Bit OS. 3. Bot goes directly into "Error during hook test." Clicking "OK" opens the bot,which then immediately freezes. Note that the name of the character being used does NOT show up correctly - its appended with random characters, usually periods. 4. Close WoW. Bot immediately responds saying the game should be windowed (it is) and that the wow key bindings should be reset (they are). The bot then stays open and can be used but obviously does nothing. Log repeats !Memory.IsProcessOpen.

Maybe this log has more info; the timestamp here is when I close WoW (with the bot running) - there are some successes but its struggling somewhere. 18:54:31 29 Aug 2017 18H53.log.html

Done, same exact errors.