as i say?d, i cant play by hand, and a afk questing only works with leader communication support Server/Client... so i wait for your update
Set yourself as the leader in the options on the first tab. Your name should be listed in the drop down box.
Emm.... thats frustrating I tested it before uploading and I tested it this morning. I even allowed the auto updater to download the online version and its still working. I'll upload a zipped version to the forums shortly.
Without HB running on the leader? (I know, there would be no communication between leader and slaves, but i want my slaves assist me like braindead monkeys!^^)
No I haven't. You can add whatever encounter logic you want for whatever mob(s) you want in whatever instance you want, with some exceptions. Those exceptions being what I have already indicated above, "void zones" on the ground. Encounter logic does not move out of, or avoid navigating around stuff on the ground. But, the specific encounter you are referring to is beyond the scope of this project. In order to create encounter logic for this specific instance boss you would also need to identify when the characters does not have a given buff THEN run away.
1. Delete your existing folders, both of them (Fpsware's RAF Bot, and Fpsware Library V2) 2. Extract contents of the ZIP to your Bots folder.
Yes. Instructions above state this. If you are running the leader WITHOUT RAF Bot, make sure the slaves RBC setting is disabled.
You will be waiting for a VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY long time for 100% automated AFK leader questing.
I've noticed with Turn in Quests enabled, but "Choose Reward" disabled, the bot still chooses a reward for quests. I was hoping for functionality where the bot would hand any quests in without rewards, but let me choose for the others. If you want to see a log for this, I will get it next time I play.
FPSWare, do you have any idea what I can try to get the RBC Server to work? When I have the slave (client) character out of targeting range of the leader (server), it just stands there and doesn't move to the leader. I've tried the RBC server defaults, localhost and port 8010, as well as a couple other ports. I have those settings on both bots the same, with the leader the server and the follower the client. From the logs, I don't see any specific error message, but I assume that there is no connection being made for whatever reason. I've tried port forwarding on my router, and disabling my firewall or explicitly allowing all port 8010 traffic for all applications or Honorbuddy, no luck seemingly. Just wonder if you have any suggestions I might not have tried, or ways to test the functionality. Logs include a few start/stops trying to get it to work.
Badass, Badass, Badass. Did I mention BADASS. The Beta bot works great (little things act strange, to be expected tho). I can't WAIT as more things are added / tweaked. So happy I donated during your down time;-). BoB
Did you start the leader first and then the slaves? When the slave was started was it within sight of the leader? Does the slave assist the leader in combat properly?
Yup, I've started the leader first. Everything works perfectly as long as the characters are in range of each other in the game world. When I was trying to get it to work prior, I was starting it out of sight of the leader, just because that made it very easy to test. I notice when I am out of range of the leader I get the text in the log "RAF Leader has been set by first available party member" as my characters are grouped. Now I am trying to test it where the follower starts in range of the leader and goes out of range, but that's a bit tricky as I need to keep the follower from following by getting it doing a quest or skinning a bunch of mobs. I did get the RBC location query to work once, so I have ruled out any issue with communication being blocked. But it only happened when I first started the bot and the characters were standing pretty close together: I will keep trying to test and see if I can get it to work. EDIT: [follower skinning.txt log attached, relevant bit is at the end of the log] My follower went to skin a bunch of mobs, so I ran the leader out of view range. "RAF Leader has been set by first available party member" shows up twice in the log after the leader is out of range, and after the follower finishes skinning mobs, it does not make any RBC query to find the leader. When I run my leader back into range, the follower no longer follows the leader or responds when the leader goes into combat. However, it still skins mobs and will defend itself if a mob attacks. [follower skinning plus end bit.txt log] I hit stop in honorbuddy, then start it again. Follower still doesn't follow the leader. With the bot still running, I open bot config and the following is added to the log (names removed): Code: [00:51:02.432 N] Running revision 12 of Fpsware RAF Bot. This is the latest build. [00:51:02.576 N] ==== DEBUG: groupMembers count: 2 [00:51:02.576 N] ==== DEBUG: 1. checking ********** [00:51:02.576 N] ==== DEBUG: 1. checking ********** I see Leader is set to [Automatic] (I think it was set that way to begin with). When I open the drop down and click on that option again, the bot still does not do anything. But as soon as I set the leader to the actual leader by name, it starts following again. Code: [00:52:27.828 N] RAF Leader has been set by prefered name
Woah dude. The first 6 were chill, but 7 is far out of line and completely false. Looks great, used your LazyBoxer to get my army of 90s in record time. I can't wait to test it out.
