[Bot] Fpsware's LazyBoxer - RAF the way it was meant to be

How do I open this? Lol

Looks awesome from reading, exacterly what I've been looking for.

 

There are clearly detailed instructions on the first page.

 

Awesome, thanks, +rep!

 

View attachment 8556 2013-07-01 01.07.txt Can't get it to work, it just stands there doing nothing ..

 

As you've probably not read all of the first post...

1. Is the leader selected?
2. Have you tried Force Combat Start?

 

I have a new build just about ready for release, but before I do does anyone have any issues or bugs that need to be addressed?

 

Hey fpsware,
so far i have to say that this is an awesome plugin! Thanks for that!

Nevertheless i have some problems with it.
I am playing a warrior tank by hand and let the slave (hunter) follow. It was no problem while i was questing my way up to level 15 but the problems started when i began to run instances. Sometimes my slave doesnt follow and just stands there doing nothing. And sometimes he follows but doesnt assist me (the tank) i tried so many different settings but the problem is still there... :/

Could it be a CC problem? I am using TuanHA Hunter set to Fully AFK. I even tried it with Dungeon Mode but i got the same problems.

I hope u can help me

Edit: Added the log

 

I don't know how you guys do it /grovel

 

http://www.thebuddyforum.com/honorb...loged/125520-auto-partymount.html#post1211503

here you go fpsware, you can steal my code for dual mounting

 

There are a number of CC errors in the log and there are NUMEROUS navigation issues. You are aware of the navigation issues with HB when you zone in and out of instances? Its a bug in HB, if its running when you zone into or out of an instance navigation stops working. You have to close and reopen HB for navigation to work again.

 

Thanks mate, very very much appreciated.

Two minutes and its implemented into the botbase

 

But it takes ages to reopen HB on my machine ... Furthemore its really annoying that i have to restart HB after each instance ... :/ isnt there a solution for this problem?

 

This is a bug in HB, it is nothing to do with me or LazyBoxer. But yes there is another way, and it takes just as long. Choose another botbase, hit start, hit stop, choose your original botbase and hit start, navigation SHOULD be working again.

 

Hmm okay thanks
Its working just fine now when i am restarting HB after each instance

Thank you very much

 

Hey Fps, another awesome release. I was just thinking about working on something like this, but I fear you've done it better

Anyways, with the following flight paths there is Styx.CommonBot.FlightPaths.TakingPathTo
I haven't look at your code, or tested those variables in CommonBot.FlightPaths at all.

-Panda

 

As there is absolutely no communication between characters so there is no way for the leader to tell the slave they are taking a flight or where they are flying to.

This could be possible if I were to use addon chat channels, but this would almost guarantee that Blizzard could detect types of messages from the botbase and freely hand out bans.

 

How are you getting them to accept/turn-in quests with the leader then?

 

When the botbase detects the leader has targeted an NPCs it checks if that NPC has available quests or can turn in quests, if it can it moves into interact range and interacts with the NPCs. The rest is handled by events; when the NPC dialog is open the botbase checks for available quests, if there are any it accepts / turns in as appropriate.

The only thing the leader does is target the NPC.

EDIT: Here is the entire quest code: #8101301 - Pastie

 

Easy enough. What if all members would have to loot their own items? Just loot if there is loot available on followers?

 

If there are lootable mobs within range then they go and loot it, simple enough.

[C#] using System; using System.Linq; using System.Windows.Forms; using CommonBeha - Pastebin.com


EDIT: There is also some very crude handling of looting items that are locked because multiple people are looting the same item. Basically, just press ESC and try to loot it once more. It works 99% of the time in raids / instances