What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

RaF: 2Bot FAIL! Warrior/Paladin

krizzl3

New Member
Joined
Jul 11, 2010
Messages
127
Reaction score
2
Setup 2 Bots: 1.9.5.5
Group 1
Bot1 = Warrior (Default CC), horde-1-60-modified.xml, Grind Bot, Party Leader
Bot2 = Paladin (Default CC, Convalesce 3.3 b3.1), horde-1-60-modified.xml, RaF Combat Assist

Bot1 Grinds along just fine, although he gets very confused on loot when it is set to group loot, set to FFA loot to fix the issue,

Bot2 Tries to loot if set to Group loot, he cannot loot fast enough. problem with BOTH CC, im almost wondering if its HB thats the issue because its consistent glitch with either CC.

What is happening is Bot2 follows Bot1. As soon as Bot1 targets and pulls bot2 reports Pulling targetX then stands still until the battle is over once the enemy is downed Bot2 will move to Bot1 then remain at the death site of the downed mob until the next pull is downed. then repeat

If i am on Bot2 and manually target Bot1 during the fight Bot2 will run in attack/heal(assist) bot1 then return to his slump. this occurs on BOTH CC Classes.

Also if Bot2 grains agro from a patrol during combat Bot1 will ignore the threat and move on to seak a new Mob that is not already engaged.

I will post a log when i get home from the office today.
 
Last edited:
thats fine, and understandable as to why Bot1 will not Assist Bot2 on agroed patrols. it does not however explain how Bot2 is failing life at simply following/assisting Bot1. Bot2 can't tell if Bot1 is player or not. he's just failing at life.

The reason i am posting this thread cause if you read the board deep enough you will see this problem over and over and over with various CC not just paladins. and everyones response is "CC is broken talk to CC developer"

I am hoping this thread will become a discussion as to why so many people are Having issues with the Majority of the Combat Classes RaF Assist mode. is the problem really the CC or is HB_RaF Assist not functioning aswell as people would like to think it is.
 
Just making sure you have Bot 2 set to RAF mode, and just a little FYI, i believe Bot2's CC needs to support RAF. so you might want to check on that, and if Bot1's class has a CC that supports RAF, i'd suggest moving Bot2 to lead and Bot1 to RAF follow

Also, you usually have to configure the CC for RAF so don't forget to do that
 
1 needs raf and 1 needs grinding, you can't put 2 on raf and expect it to grind...

edit: Leader should be the grinding, follower = raf.
 
I have same problem with RaF - Combat Assist. I don't use it at all anymore. I find the the best way to run two bots together is put them in a group and set loot on free-for-all. Have both bots run in Grind mode and set one of them to skip looting.
 
Just making sure you have Bot 2 set to RAF mode, and just a little FYI, i believe Bot2's CC needs to support RAF. so you might want to check on that, and if Bot1's class has a CC that supports RAF, i'd suggest moving Bot2 to lead and Bot1 to RAF follow

Also, you usually have to configure the CC for RAF so don't forget to do that

if youll see in the origonal post Bot2 iss setup in RaF and Bot1 is in grind mode.

Bot2 w/Convalesce 3.3b.31 DOES support RaF follow heal/dps and whos same symptoms as the default CC.

i have also tried the OneCC in RaF mode with the Warrior setup as RaF and the Paladin setup as Leader same results occured.
 
Basically put, RaF has never worked in HB2, if you want to use RaF, download HB1, which has a brilliant system, the only problem will be getting profiles and meshes now (get HB1 here http://www.buddyforum.de/showthread.php?6732-HB1-for-WoW-Patch-3.3.5a ). I believe the devs are aware of the RaF fail in HB2, i've seen numerous posts from Hawker and Bossland about how you should use HB1 if you want to RaF. Like everyone else, I'm waiting for HB2 to get sorted out.
 
RaF in Hb currently sux. No way around it. Both my CCs now support RaF however HB is very bad at it. Seems RaF took a back seat to questing.
 
RaF in Hb currently sux. No way around it. Both my CCs now support RaF however HB is very bad at it. Seems RaF took a back seat to questing.

I'm not a dev. now would i tell one how to do there job, but wouldn't you want to polish off existing features before adding new ones?
 
I'm not a dev. now would i tell one how to do there job, but wouldn't you want to polish off existing features before adding new ones?

Hmm I think you got that backwards - Raf was in HB1 not questing, so by your logic they would need to polish off RAF in HB2 (the existing feature) before adding (the new feature) questing.
 
Hmm I think you got that backwards - Raf was in HB1 not questing, so by your logic they would need to polish off RAF in HB2 (the existing feature) before adding (the new feature) questing.

thats what i said.
 
*************************************************
does anyone know of a workaround or a CC that supports RaF
and ACTUALLY works? maybe i can find something. at first i thought
it might be something to do w/targeting checks but i removed the
targetting checks from the CC so it would just assume it was the
correct target.. still fail
 
It would be enough if the follewer ( RAF Char ) just loots and Follows the Grindchar so it wont get out of sight, thats the problem atm at my configs.....they seperate too far and then the whole RAF system crashes :(
 
im using HB1 to RaF w/ its a real pain in the ass since i cant seem to find any meshes.
 
Seems RaF took a back seat to questing.

I'm just waiting for the 2 to join forces :)

Why don't you have HB2 as the leader, and HB1 as follower, it worked for me with Mage, Warlock, and Warrior.
 
I'm just waiting for the 2 to join forces :)

Why don't you have HB2 as the leader, and HB1 as follower, it worked for me with Mage, Warlock, and Warrior.


thats what i've been doing but it requires alot of maintinence, as i cannot find any meshes for HB1 i thought i made one but it doesn't seem to want to res. so i gotta manually res each time.
 
Back
Top