fpsware
Community Developer
- Joined
- Jan 15, 2010
- Messages
- 5,287
Want Support?
Also read post #2, FAQs. <--- This is important
I will not provide support to anyone who has not read the entire contents of this post. If you read this post it will answer a lot of your questions. I will NOT provide support to anyone who does not provide a log file AND a detailed description or the error or expected behavior. Simply saying "it does not loot quest objects" will only result me publicly ridiculing you.
What is LazyBoxer?
LazyBoxer is a feature rich multi-character botbase capable of fulfilling the specific needs of those who want full interaction between multiple characters in a master-slave relationship. To put it another way, LazyBoxer allows you to fulfill your RAF (recruit-a-friend) requirements by enabling your follower(s) to assist a leader, in combat, with questing and follow them where ever they go. LazyBoxer provides support for looting, harvesting (herbs, ore), skinning. If you're within range (user defined) of a harvestable object LazyBoxer will move to and interact with the object, the same applies to picking up quest objects.
It can also be used as an alternative to LazyRaider & RaidBot in that it will provide full combat support utilizing what ever combat routine you use, as well as assisting and following the group tank, or virtually anyone else in the group if you so choose.
How do you use it?
My recommended use, and the purpose for which it was originally designed, is to player the leader (or master) by hand and have the follower (or slaves) assist you. For example I've been leveling a new group of characters, I control the tank and I have slaves assist me. When the master picks up or turns in a quest so do the slaves, that is, if anything is available for them. When I said I control the tank I don't mean I play it by hand, I'm still using LazyBoxer for this but it has not been set to follow another character. Think of it like using LazyRaider or RaidBot, it still does all the combat rotation for you but you also have the added benefit of automation in every possible aspect of play.
You don't even need to be in the same group, if you want to play a low level character and have your high level slave following you around killing the mobs for you that works too. Ideally the master is a character played by hand, either by yourself or another person, but I have seen some mixed results with some success where the master is controlled by HB Questing. Personally I don't recommend as HB Questing does not take into account the fact it is grouped with other characters, its just out to do the quests as fast as possible.
Profiles?
LazyBoxer does NOT use any profiles. You can not load a questing profile or a grinding profile and hit start. It is primarily designed to assist and follow a leader.
Boss encounter logic?
LazyBoxer does NOT provide any boss encounter logic, it will not get out of void zones, it will not react in anyway to shit on the ground.
Navigation and following the leader.
LazyBoxer slaves will follow the assigned leader at a distance of your choice, you can even choose to keep line of sight (LoS) on your leader at all times if you want, this is ideal for instances. ALL navigation is provided by HB, that is to say if it is not navigating properly then it is not the botbase which is at fault. Though you do have the option to utilize HB's mesh navigation or use click-to-move. If using CTM, when the slave needs to navigate to an object or to the master they will do so in a straight line.
What Combat Routines does this work with?
I strongly recommend the use of Singular as your combat routine when using LazyBoxer. Many other routines have proven to be problematic or resulted in erratic behaviour when used with LazyBoxer.
For CC developers, LazyBoxer utilizes the following behaviors: RestBehavior, PreCombatBuffBehavior, PullBehavior, HealBehavior, CombatBuffBehavior and obviously CombatBehavior.
Credit where its due.
Some parts of LazyBoxer have been gleaned from other projects and various sources. The original botbase that inspired me to write LazyBoxer was LazyRaider, developed by Bobby53. The majority of the quest pick up and turn in code is from MultiBox Suit. RaidBot by Apoc was the original source of the framework. The stylized horizontal tab control was developed by Cyotek.
Too long, didn't read? Features at a glance.
* Slaves follow and assist the leader
* Automatically pick up and turn in quests
* Use Singular as your combat routine
* Looting, harvesting and quest object interaction
* Alternative to LazyRaider & RaidBot
* RAF the way it was meant to be
* Does not use profiles of any kind
* Does not provide boss encounter logic of any kind
Lets get started.
If you've used my Combat Routines in the past you will be familiar with my style of UI. While LazyBoxer uses a slightly different UI, the simplicity and visual appeal is still a key feature. You won't find a UI cluttered with a vast assortment of controls and tick boxes that leave you bewildered at how on earth you configure it.
I'm not going to explain every setting, most of these are self explanatory, and most settings have tool tips. The below screen shots are taken from a slave configuration. When you first start LazyBoxer most settings will be disabled, it only takes a couple of minutes to fully configure all settings and have you up and running.
Leader & Following
Leader: [Default None] This list is automatically populated with the names of all players in range. You can either set this to Automatic, in which case when you're in a group the character will follow and assist the first available tank. Or, you can choose a specific player to follow and assist. I suggest you logon to your leader character before setting this in the UI. If set to None, the default, the character will not follow or assist anyone. If you're the Tank leave this set to None.
Maintain Leader LOS: [Default Never] If enabled will always move so you have line of sight on the leader. Best used when in instances.
Targeting & Movement
Targeting: [Default Assist Leader] There are a number of ways LazyBoxer can select a valid target to attack, my suggested setting is Assist Leader. If you're the tank set this to Lowest Threat.
Navigation System: [Default HB Navigation] Either use HB's mesh navigation or CTM movement.
'Stuck' Handler: [Default Enabled] Here you can enable or disable HB's stuck handler. I've seen all too many instances where HB thinks the character is stuck and performs the dreaded unstuck behavior. When the character is simply running in a straight path!
Looting & Harvesting
You have 2 settings for harvesting range, World and Instance. When inside an instance you don't want the character running off 40 yards to gather a herb and pulling half the instances.
Questing
NOTE: Slaves will only interact with an NPC when the leader targets them. If the leader has targeted an NPC it is checked to see if they have any quests to pick up or turn in, if they do, the slaves moves to and interacts with the NPCs. Depending on your settings quests are automatically picked up and turned in as appropriate.
Interact with NPCs: [Default Always] If disabled will prevent LazyBoxer from picking up or turning in quests, and even moving to interact with the NPC.
Object Interaction: [Default Ignore] This for quest objects that need to be picked up and quest boards. The Loot Range on the Looting & Harvesting tab is used to determine how far a character will scan for items.
QUEST FETCH: [Default Ignore]: If enabled characters will automatically look for NPCs that have available quests or quest that can be turned in. With this setting the leader does not need to target the NPC. Use with caution.
Chat Commands
NOTE: Due to a bug in HB, currently only SAY chat is recognized
Chat commands are an alternative way for the leader to 'control' how the slave behaves without modifying the setting in the UI.
Key Bindings
Global key bindings apply to ANY window where Local key bindings must to pressed when the specific WoW has focus. I will be adding a lot more global key bindings in the coming days.
Automation
Death
Advanced
Force Combat Start: [Default Never] Some combat routines do not work as well as can be expected with LazyBoxer. The most common behavior is when the leader is in combat and the slave does not engage the target. Typically this is because the CC does not support PullBehavior, and in such cases you need to give the combat routine a slight nudge. LazyBoxer does this by casting the most basic spell available to your class. Typically once this is done the combat routine performs as expected.
Combat Assist ONLY: [Default Never] Sometimes, regardless of your settings, you just want your slaves to follow you and perform their combat rotation. In essence LazyBoxer becomes a basic combat bot that follows the leader, and that is all it does; Combat & Follow.
Installation instructions
NOTE: There is a possibility that a file required by the UI may not be installed on your computer, System.Design.dll. When you run LazyBoxer if it fails to compile or fails to show the UI properly you MUST run the HB Installer application, link found here.
Extract the contents of the zip file to your ...HB\Bots folder. When done correctly it will look like this.
[2 Oct 2013] New build uploaded
Also read post #2, FAQs. <--- This is important
I will not provide support to anyone who has not read the entire contents of this post. If you read this post it will answer a lot of your questions. I will NOT provide support to anyone who does not provide a log file AND a detailed description or the error or expected behavior. Simply saying "it does not loot quest objects" will only result me publicly ridiculing you.
What is LazyBoxer?
LazyBoxer is a feature rich multi-character botbase capable of fulfilling the specific needs of those who want full interaction between multiple characters in a master-slave relationship. To put it another way, LazyBoxer allows you to fulfill your RAF (recruit-a-friend) requirements by enabling your follower(s) to assist a leader, in combat, with questing and follow them where ever they go. LazyBoxer provides support for looting, harvesting (herbs, ore), skinning. If you're within range (user defined) of a harvestable object LazyBoxer will move to and interact with the object, the same applies to picking up quest objects.
It can also be used as an alternative to LazyRaider & RaidBot in that it will provide full combat support utilizing what ever combat routine you use, as well as assisting and following the group tank, or virtually anyone else in the group if you so choose.
How do you use it?
My recommended use, and the purpose for which it was originally designed, is to player the leader (or master) by hand and have the follower (or slaves) assist you. For example I've been leveling a new group of characters, I control the tank and I have slaves assist me. When the master picks up or turns in a quest so do the slaves, that is, if anything is available for them. When I said I control the tank I don't mean I play it by hand, I'm still using LazyBoxer for this but it has not been set to follow another character. Think of it like using LazyRaider or RaidBot, it still does all the combat rotation for you but you also have the added benefit of automation in every possible aspect of play.
You don't even need to be in the same group, if you want to play a low level character and have your high level slave following you around killing the mobs for you that works too. Ideally the master is a character played by hand, either by yourself or another person, but I have seen some mixed results with some success where the master is controlled by HB Questing. Personally I don't recommend as HB Questing does not take into account the fact it is grouped with other characters, its just out to do the quests as fast as possible.
Profiles?
LazyBoxer does NOT use any profiles. You can not load a questing profile or a grinding profile and hit start. It is primarily designed to assist and follow a leader.
Boss encounter logic?
LazyBoxer does NOT provide any boss encounter logic, it will not get out of void zones, it will not react in anyway to shit on the ground.
Navigation and following the leader.
LazyBoxer slaves will follow the assigned leader at a distance of your choice, you can even choose to keep line of sight (LoS) on your leader at all times if you want, this is ideal for instances. ALL navigation is provided by HB, that is to say if it is not navigating properly then it is not the botbase which is at fault. Though you do have the option to utilize HB's mesh navigation or use click-to-move. If using CTM, when the slave needs to navigate to an object or to the master they will do so in a straight line.
What Combat Routines does this work with?
I strongly recommend the use of Singular as your combat routine when using LazyBoxer. Many other routines have proven to be problematic or resulted in erratic behaviour when used with LazyBoxer.
For CC developers, LazyBoxer utilizes the following behaviors: RestBehavior, PreCombatBuffBehavior, PullBehavior, HealBehavior, CombatBuffBehavior and obviously CombatBehavior.
Credit where its due.
Some parts of LazyBoxer have been gleaned from other projects and various sources. The original botbase that inspired me to write LazyBoxer was LazyRaider, developed by Bobby53. The majority of the quest pick up and turn in code is from MultiBox Suit. RaidBot by Apoc was the original source of the framework. The stylized horizontal tab control was developed by Cyotek.
Too long, didn't read? Features at a glance.
* Slaves follow and assist the leader
* Automatically pick up and turn in quests
* Use Singular as your combat routine
* Looting, harvesting and quest object interaction
* Alternative to LazyRaider & RaidBot
* RAF the way it was meant to be
* Does not use profiles of any kind
* Does not provide boss encounter logic of any kind
Lets get started.
If you've used my Combat Routines in the past you will be familiar with my style of UI. While LazyBoxer uses a slightly different UI, the simplicity and visual appeal is still a key feature. You won't find a UI cluttered with a vast assortment of controls and tick boxes that leave you bewildered at how on earth you configure it.
I'm not going to explain every setting, most of these are self explanatory, and most settings have tool tips. The below screen shots are taken from a slave configuration. When you first start LazyBoxer most settings will be disabled, it only takes a couple of minutes to fully configure all settings and have you up and running.
Leader & Following
Leader: [Default None] This list is automatically populated with the names of all players in range. You can either set this to Automatic, in which case when you're in a group the character will follow and assist the first available tank. Or, you can choose a specific player to follow and assist. I suggest you logon to your leader character before setting this in the UI. If set to None, the default, the character will not follow or assist anyone. If you're the Tank leave this set to None.
Maintain Leader LOS: [Default Never] If enabled will always move so you have line of sight on the leader. Best used when in instances.
Targeting & Movement
Targeting: [Default Assist Leader] There are a number of ways LazyBoxer can select a valid target to attack, my suggested setting is Assist Leader. If you're the tank set this to Lowest Threat.
Navigation System: [Default HB Navigation] Either use HB's mesh navigation or CTM movement.
'Stuck' Handler: [Default Enabled] Here you can enable or disable HB's stuck handler. I've seen all too many instances where HB thinks the character is stuck and performs the dreaded unstuck behavior. When the character is simply running in a straight path!
Looting & Harvesting
You have 2 settings for harvesting range, World and Instance. When inside an instance you don't want the character running off 40 yards to gather a herb and pulling half the instances.
Questing
NOTE: Slaves will only interact with an NPC when the leader targets them. If the leader has targeted an NPC it is checked to see if they have any quests to pick up or turn in, if they do, the slaves moves to and interacts with the NPCs. Depending on your settings quests are automatically picked up and turned in as appropriate.
Interact with NPCs: [Default Always] If disabled will prevent LazyBoxer from picking up or turning in quests, and even moving to interact with the NPC.
Object Interaction: [Default Ignore] This for quest objects that need to be picked up and quest boards. The Loot Range on the Looting & Harvesting tab is used to determine how far a character will scan for items.
QUEST FETCH: [Default Ignore]: If enabled characters will automatically look for NPCs that have available quests or quest that can be turned in. With this setting the leader does not need to target the NPC. Use with caution.
Chat Commands
NOTE: Due to a bug in HB, currently only SAY chat is recognized
Chat commands are an alternative way for the leader to 'control' how the slave behaves without modifying the setting in the UI.
Key Bindings
Global key bindings apply to ANY window where Local key bindings must to pressed when the specific WoW has focus. I will be adding a lot more global key bindings in the coming days.
Automation
Death
Advanced
Force Combat Start: [Default Never] Some combat routines do not work as well as can be expected with LazyBoxer. The most common behavior is when the leader is in combat and the slave does not engage the target. Typically this is because the CC does not support PullBehavior, and in such cases you need to give the combat routine a slight nudge. LazyBoxer does this by casting the most basic spell available to your class. Typically once this is done the combat routine performs as expected.
Combat Assist ONLY: [Default Never] Sometimes, regardless of your settings, you just want your slaves to follow you and perform their combat rotation. In essence LazyBoxer becomes a basic combat bot that follows the leader, and that is all it does; Combat & Follow.
Installation instructions
NOTE: There is a possibility that a file required by the UI may not be installed on your computer, System.Design.dll. When you run LazyBoxer if it fails to compile or fails to show the UI properly you MUST run the HB Installer application, link found here.
Extract the contents of the zip file to your ...HB\Bots folder. When done correctly it will look like this.
[2 Oct 2013] New build uploaded
Last edited:
