Everything posted by Jigsaww
-
Paid 1-60 questing profiles gone
Great job you're doing there, really appericate that. Awesome work that's worth it's money.
-
Paid 1-60 questing profiles gone
Waiting for it :P excited alot
-
Paid 1-60 questing profiles gone
It would be nice to see the actual stage of the bot, like where is he moving to, whats next, etc. Sometimes I don't know if that bot will ever turn in for quest again, got alot of question marks but not even sure if it will ever been turned in again.
-
Paid 1-60 questing profiles gone
For now my character stucked with lvl 1-40 Script. Really disappointed actually. Died around 50 times over Night way to ashenvale with 22 Running through lvl 30 mobs. Really weird :( and now keep dieing in barrens..
-
Paid 1-60 questing profiles gone
Arcangelo does already have a 40-60 quest script but no sure how good it is, you can find it on his sellfy.
-
Demon / Affliction lock 1-60 by Eeny
Works good so far, but not perfect yet. - It is not using healthstone at all (would be nice to use one at 20-35% life) - Sometimes summoning randomly voidwalker, even if I do already control a voidwalker - Not using fear-spell - Summoning voidwalker after resurrection even if character gets attacked (mostly dies by this, since the casting time of VW is to long) - Would be nice to cast unending breath befor going to swim so you don't die by doing underwater quests Overall it seems to be a very nice base-script to work on
- 90 comments
- 10 reviews
-
Wrobot not login after disconnect
Inside the log files there is nothing related to this, this is just an semi-bug from Wrobot. Once the WoW-server crashs, wrobot crashs. I wrote a batch-file for this to make relogger.exe possible to restart wow.exe and wrobot.exe. (Expecting the wow-server crashs once a hour) WerFault.exe is the crash report from windows, which im trying to close multiple times to make sure it's not existing anymore. WoW.exe has been also closed multiple times to make sure there is no client running at all. @echo off echo Make Relogger possible to restart WoW :loop echo WoW will be closed in 1 hour timeout /t 900 >null echo 45 minutes left... timeout /t 900 >null echo 30 minutes left... timeout /t 900 >null echo 15 minutes left... timeout /t 900 >null echo Closing all related exes taskkill /F /IM WerFault.exe taskkill /F /IM WerFault.exe taskkill /F /IM WerFault.exe taskkill /F /IM WRobot.exe taskkill /F /IM WRobot.exe taskkill /F /IM WRobot.exe taskkill /F /IM WRobot.exe taskkill /F /IM WoW.exe taskkill /F /IM WoW.exe echo WoW has been closed after 1 hour running. goto loop With this batch file it is possible to make relogger do his work correctly.
-
Wrobot not login after disconnect
The private server I am playing on, is randomly crashing sometimes which kicks me back to main screen (befor characters-list) and displays me the Disconnected error pop-up. After that Wrobot won't login into my account again, after I did it manual, its possible to bot again. Any help here?
-
Paid 1-60 questing profiles gone
Great news, can't wait for it, GJ!