ok I got it

another question: I'm lv45 right now, so far there were about 3-4 quest that require playing by hand (a quest ask to collect spider, collect something + fight a sleepy dragon, use the canon...). I wanna ask are there any way to make the bot do this instead of playing manually ? and also what exactly the quest behavior do? If I replace the default one with some others made by others such as
http://www.thebuddyforum.com/honorb...-[quest-behavior]-natfoths-qb-megathread.html will the bot be able to do all those quest itself ?
thank you
Replacing for Natfoth's Megathread would be a
huge mistake--those behaviors are
substantially dated.
Natfoth did a wonderful, wonderful thing--he showed the Community what the CustomBehaviors were for, and how to implement a bunch of them.

They were so popular, that his original behaviors got slurped into the HBcore. When that happened, the behaviors were:
- Abstracted a little to make them more 'general purpose', rather than the point-solutions that many were originally
- Had a bunch of bugs and missing boundary conditions chased out
- Attributes were made consistent across all of the behaviors (e.g., NpcId/NpcID/NPCID/MobId/MobID were all named to 'MobId')
- Got enhanced logging facilities to tell you exactly where a behavior problem lay, and what was wrong.
- 'Silent fails' were eliminated--the behaviors now tell you when they fail
- Have had functionality extended to address even more questing needs
The original behaviors in that thread simply got 'left in the dust'. Also, Natfoth has access to the Quest Behaviors SVN used by the HBcore, and he makes his updates there now, instead of on the Megathread.
It should also be noted that there were many more contributors to the HBcore Custom Behaviors than Natfoth. These include Apoc, Bobby53, Highvoltz, Nesox, and few others (my memory fails and I apologize--no slight to a CB author intended).
The reason quests are not 100% automated is because either there are no behaviors to do them, or the existing behaviors have incomplete functionality. Kick has a long
QQ blog post we work against to try to address the omissions and shortcomings. Unfortunately, it seems all the Community's developers are strapped for time at the moment.
cheers,
chinajade