I think it's because I have a trial account on my blizzard account, so first select the my real account but then when I entered the world believe that it is already inside "loading screen": p
I am having a little trouble getting it (The relogger) to enter the realm I play on. What happens is it opens wow... logs in... Then it simply reverts back to the "Select a Realm" and it has the "Suggest Realm" button... However if I open the wow.exe client manually it selects my server...
It also seems to close down my wow window before starting HB2 (Questing) for some reason... It's so close! I know it's something small... Any help?
Edit: More info...
Server was set, and also not set... Neither helped.Code:00:47:12 Starting WoW/Bot's 00:47:12 Press Alt+F5 to stop the script 00:47:12 Server: 00:47:12 Character slot: 1 00:47:12 Waiting 5 seconds before login 00:47:25 Waiting 7 seconds before enter world 00:47:32 Trying to enter world. 00:47:35 Loading screen.. (timeout after 100 seconds) 00:47:43 Change WoW titlename to: Mysetcharactorname... ;) LOL! 00:47:43 Bot path: D:\Gaming\World of Warcraft Related\WoW BoTs\Honorbuddy\HB II - 4\mirc.exe 00:47:43 Waiting of HB..
I also noticed in the config.wtf that this relogger makes... it doesn't set the DX API to 9!!!! EEK!
If I manually select the server (United States) realms, and hit "suggest realm" it gets to the last part in the log above and closes out the WoW window on me...
My computer is plenty fast to load wow in about 3 seconds flat to the login screen.
Hello bryt,
Could you add mail or msn or IRC notification on event? For example "too much restarts", "mailing done", "crazy moves" etc? It would be cool :}
Can you make it so it chose which wow account?
cuz I have 4 diffrent wow accounts on same, so i need to chose the 4rd one.
How can I can I do that`?
just wondering is it possible to modify this script so that it will start WoW with NO ADDICTION speed hack?
Sorry I don't know what you mean with settings under 2, when you type in number 5, it should use the settings from account 5, and you should always click replace config before you start wow or a bot from test functions. And for the problems with sorting bots, is that only for HB or GB? I've also made a small change for HB in the new version for sorting.Thanks for news. However I am noticed problems with test function(for example if I type number 5, relogger don't starts acc with settings under 2, but last used settings) and sometimes relogger don't sort all bot windows properly.
3.2.9:
- small fix in wow error detection (a random account was closed everytime, when a wow error occurred)
- added a irc bot, it will connect to a irc network and join a channel. The bot will log some messages in that channel, and you can also use some remote commands. You will find a command list in settings -> IRC Logging or by typing help in that irc channel.
*note: I have only tested it with quakenet, it may not work on other networks.
- added SET gxApi "D3D9" to replace config function
- many changes in the alternate waiting methods, also getting window handle is improved
Hello.
I got a problems, I got this message : "could not get the bot handle". Everthing work fine before I update to the new versions :s
The relogger don't push the start button of the bot, I already try the other method to lauch bot, without any success :/
3.3.0:
- manual wait time after starting bot is working again
17:48:45 Starting WoW/Bot's
17:48:45 Press Alt+F5 to stop the script
17:48:45 Server: XXXXX
17:48:45 Character slot: 1
17:48:45 Changing WoW language to: enGB
17:48:47 Waiting 20 seconds before login
17:49:15 Waiting 7 seconds before enter world
17:49:23 Trying to enter world.
17:49:23 Waiting 20 seconds before starting GB/HB
17:49:43 Change WoW titlename to: XXXX
17:49:44 Bot path: C:\BLABLABLA\Gatherbuddy.exe
17:49:47 Wait time after starting bot: 10 seconds
17:52:57 could not get the bot handle
I try again with others options, and the relogger don't push the "start" button :/
That's crazy because it work fine before the other update :/
Edit :
I try again with a fresh install of the relogger, I got the same error