Someone mind explain to me how to setup the death waypoint in pve in accordance with the alive waypoints?
Someone mind explain to me how to setup the death waypoint in pve in accordance with the alive waypoints?
Me either, I disabled all my addons and what not. Does yours wait to res at gy? or does he run to the corpse and res there? Since mine doesnt wait at the gy, he ends up run into a wall trying to get somewhereIm using 1.7 as well if that helps. I love this bot and would gladly even pay for it lol since i hate the grind for honor every season on four of 80s i have
He doesnt run into a wall for me, everything works perfect.
When alive, he just makes a cirlce at the graveyard left of Iceblood Tower und waits there. But he still is using his Anti-AFK (moving). When a Horde player gets in range, he dismounts and starts to fight. After fight (when dead everything runs well and he's starting to storm enemy base again!) when I am still alive he just stands there doing nothing. When BG is over, he waits the 2 minutes, back in town he queues again. Everything works pretty good, except this "Graveyard-Stand-Still-Bug".
Maybe you can have a look into it _natt.
i made the alliance wps, ill take a look at that iceblood thing tonight when i get home. Also i have finished the SOTA wps, Natt will ahve to test them first but then theyll be in aswell![]()
Great to hear! If you need any more information about the "Iceblood-Thing" feel free to ask. Thanks!
thanks for sharing your computer-scan results in my thread...
just make your deathwaypoints run from the greaveyard to closest alive waypoint, and the bot will start run the normal path for your corpseSomeone mind explain to me how to setup the death waypoint in pve in accordance with the alive waypoints?
Last edited by natt_; 02-15-2010 at 06:49 AM.
Could you please reply my question? Thanks
I'Ve got a little problem here, I wanted to try PvP part, but everytime it joins Arathi Basin, it just stays at the beggining:
LOG:
Code:
[16:34:38] #> Silly Tarre.nu 1.7
[16:35:36] [DEBUGGER] P_Queue current status: 0
[16:35:36] [PVP] Queue for bg: 2
[16:35:44] [PVP] Waiting to join
[16:35:45] [PVP] Joining!
[16:35:45] [PVP] Waiting for start!
[16:35:58] [PVP]: Current location: abastart
[16:35:58] [DEBUGGER] The section: abastart was not read-able
[16:35:58] Pvp mode
[16:35:58] #> Silly Tarre.nu 1.7
[16:36:01] [PVP]: Current location: abastart
[16:36:01] [DEBUGGER] The section: abastart was not read-able
[16:36:01] Pvp mode
[16:43:25] #> Silly Tarre.nu 1.7
[16:43:27] [DEBUGGER] P_Queue current status: 0
[16:43:27] [PVP] Queue for bg: 2
[16:43:36] [PVP] Waiting to join
[16:43:40] [PVP] Joining!
[16:43:40] [PVP] Waiting for start!
[16:43:53] [PVP]: Current location: abastart
[16:43:53] [DEBUGGER] The section: abastart was not read-able
[16:43:53] Pvp mode
...
It seems Arathibasin start is not in your. Please post 0.ini for me
edit: replace 0.ini with this:
http://pastebin.com/d77891e1b
Last edited by natt_; 02-15-2010 at 11:41 AM.
Fine, waypoints works well now. But I've got second, smaller problem :/
But even thought i have both set to find AB, it always starts finding WSG, dunno why :/. Yesterday i had same problem, but it couldnt start finding WSG, just AB, wtf? :/;1 = av, 2 = wsg, 3 = ab, 4 = eots... alt_bg if you would like to join 2 battlegrounds and join the first
bg=3
alt_bg=3
Last edited by Coreey; 02-15-2010 at 03:11 PM.
That's because of your keybindings are not set correctly. Was disscussed few pages ago.
Nope. I thought so to but i had it happen to me yesterday for no reason. Only happened the one time, i saw, and hasen't happened again.
I always do /g when i log on so that way any crazy shit gets sent to your guild channel. Only if it's your guild or someone you trust ofc. Habit i got into years ago and has saved my ass more than a few times on different bots.
Usual cause would be lag. Putting a delay of a couple more ms before typing the message wouldn't hurt. Not saying that Is the issue here just another 2c worth
Meant to add script.cfg works great now![]()
Last edited by Baelzebub; 02-15-2010 at 06:25 PM. Reason: script.cfg
That didnt fix it as I said Forke..
Could you help us out on that Natt?
Also seems that if you die and rez quickly in the BGS the bot doesn't know you died so keeps trying to run to the last known co-ords. That's what causes the wall running. At least it looks that way at my end.
natt, do you have any idea what is wrong with mine? he ques and all that fine but once he dies he runs away from the gy as a ghost and ends up running to a wall and getting afk. he doesnt wait for spirit to release him. maybe you can teach me how to make him jump once every 30-40 sec so even in ghost as long as noone report him, he will be all good. please sir and ty