To add to the above Dantron I went back and looked for the guide I seen before cant find it but it seams when people used simple follow over a VPN they had both the leaders and followers bind address set to the local ip of the leader. So try the following after portforwarding and making sure there is no firewall in the way:
1) both leader and followers bind address as the local ip (within the VPN) of the leader.
2) both the leader and followers bind address as localhost.
3) the leaders bind address as localhost and the followers as the local ip (within the VPN) of the leader.
see if one of those 3 works best help I can give at this point if one works tell me so I know for the future.[/
I just want to clarify that I am on a local wireless network with no firewalls.Yet this plugin does not work. I lack the knowledge to trouble shoot it.
[Plugin] AutoFollow 1.260.1
- Thread starter xzjv
- Start date
-
- Tags
- accounts added adventurer autofollow bot bots bug circumstances constructive decide depending diablo3 disabled download events farm features friends game games https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=p6anv9wsupuu8 https://www.paypalobjects.com/en_us/i/btn/btn_donate_lg.gif including invite join joining leader leaders licenses list local loot multiple normal party player players plugin quickjoin receive recommended reports requirements rewritten run search security server split trinity
I found a problem during GR runs, as soon as they fresh enter a new GR, the followers immediately turned around and hit the gate to return to town, then it ran into a loop which the followers will enter the GR then return to town over and over, and telling me Server is Invalid, but if I forced dragging each followers to catch up with the leaders it would fix the problem without even restarting anything.
Below is the red error i received
------
Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000088, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_ACDId()
at Zeta.Game.Internals.Actors.DiaObject.Interact()
at AutoFollow.Coroutines.Movement.<MoveToAndInteract>d__13.MoveNext() in c:\Users\yuxin_000\Desktop\Demonbuddy 1.1.2886.443\Plugins\AutoFollow\Coroutines\Movement.cs:line 183
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at AutoFollow.Coroutines.Movement.<FollowThroughPortal>d__35.MoveNext() in c:\Users\yuxin_000\Desktop\Demonbuddy 1.1.2886.443\Plugins\AutoFollow\Coroutines\Movement.cs:line 290
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at AutoFollow.Behaviors.FollowerCombat.<InGameTask>d__8.MoveNext() in c:\Users\yuxin_000\Desktop\Demonbuddy 1.1.2886.443\Plugins\AutoFollow\Behaviors\FollowerCombat.cs:line 119
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Zeta.Bot.ActionRunCoroutine.^jCx57rWX%C#H~;g \\\&QKd7q'.ePud'o!|\[\[yUTyUlL6"8\\xIi.MoveNext()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.**********(Boolean )
at Buddy.Coroutines.Coroutine.******(Boolean )
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.(JLrI1G4@bcm}kP0T\[dXE6Je!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.W"PW\]\\WH9-y)Y0z2}0=Rj_6S$.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.(JLrI1G4@bcm}kP0T\[dXE6Je!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.W"PW\]\\WH9-y)Y0z2}0=Rj_6S$.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.***********()
Below is the red error i received
------
Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000088, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_ACDId()
at Zeta.Game.Internals.Actors.DiaObject.Interact()
at AutoFollow.Coroutines.Movement.<MoveToAndInteract>d__13.MoveNext() in c:\Users\yuxin_000\Desktop\Demonbuddy 1.1.2886.443\Plugins\AutoFollow\Coroutines\Movement.cs:line 183
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at AutoFollow.Coroutines.Movement.<FollowThroughPortal>d__35.MoveNext() in c:\Users\yuxin_000\Desktop\Demonbuddy 1.1.2886.443\Plugins\AutoFollow\Coroutines\Movement.cs:line 290
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at AutoFollow.Behaviors.FollowerCombat.<InGameTask>d__8.MoveNext() in c:\Users\yuxin_000\Desktop\Demonbuddy 1.1.2886.443\Plugins\AutoFollow\Behaviors\FollowerCombat.cs:line 119
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Zeta.Bot.ActionRunCoroutine.^jCx57rWX%C#H~;g \\\&QKd7q'.ePud'o!|\[\[yUTyUlL6"8\\xIi.MoveNext()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.**********(Boolean )
at Buddy.Coroutines.Coroutine.******(Boolean )
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.(JLrI1G4@bcm}kP0T\[dXE6Je!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.W"PW\]\\WH9-y)Y0z2}0=Rj_6S$.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.(JLrI1G4@bcm}kP0T\[dXE6Je!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.W"PW\]\\WH9-y)Y0z2}0=Rj_6S$.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.***********()
Last edited:
razzysnazzy
New Member
- Joined
- Aug 28, 2015
- Messages
- 36
- Reaction score
- 0
Ya sorry it dint work, Guess going to have to wait till the dev sees it, can try pming him think he looks at that more than the forum or at least its ezer for him to find it as he has 3 diff plugins at least that he works on (this, adventurer and trinity).
Thou I will say make sure the ports where forwarded and firewall wasn't blocking them as I know that can be an issue. And make sure it was the local ip given by the VPN not your local network. Would help more but use them all on the same comp myself so don't really got much experience in the matter just knowledge of how simple follow used to kinda work.
Hi there, I've been running 4 accounts in same games for several seasons now, WITHOUT AutoFollow plugin.
Reason I did that, is all 4 can run trinity, and my 3 alts I can setup differently, to drop all whites/blues/legs in town.
Most important reason for this setup, is that all 4 accounts is actually FIGHTING, dealing damage, in combat. In big open maps, they split up and clear T10 rift in under 2 minutes!
And even though they split up, they do still run to pick up legendaries that's far away and 9 out of 10 times find the RG loot etc.
I average over 200 legs/h ! ... but ye, I had a lot of trouble with it, took a loooong-assssss time to setup and work, and often when a rift is opened too fast, one char is stuck in town, but will enter next rift.
Now, my question is, is there any way to solve this? Could AutoFollow solve is? Is there a way to ALSO run Trinity while using AutoFollow?
And also, if I do use Autofollow, can it the chars still split up in open maps, or not possible?
And if I do not use AutoFollow, is there a way to fix chars being stuck in town? Easiest way, is to press Stop and then Start, and then it enters. I could make a macro to do that once every X minutes, and the problem could be solved that way, but it's loosing a bit legs/h then.
Reason I did that, is all 4 can run trinity, and my 3 alts I can setup differently, to drop all whites/blues/legs in town.
Most important reason for this setup, is that all 4 accounts is actually FIGHTING, dealing damage, in combat. In big open maps, they split up and clear T10 rift in under 2 minutes!
And even though they split up, they do still run to pick up legendaries that's far away and 9 out of 10 times find the RG loot etc.
I average over 200 legs/h ! ... but ye, I had a lot of trouble with it, took a loooong-assssss time to setup and work, and often when a rift is opened too fast, one char is stuck in town, but will enter next rift.
Now, my question is, is there any way to solve this? Could AutoFollow solve is? Is there a way to ALSO run Trinity while using AutoFollow?
And also, if I do use Autofollow, can it the chars still split up in open maps, or not possible?
And if I do not use AutoFollow, is there a way to fix chars being stuck in town? Easiest way, is to press Stop and then Start, and then it enters. I could make a macro to do that once every X minutes, and the problem could be solved that way, but it's loosing a bit legs/h then.
razzysnazzy
New Member
- Joined
- Aug 28, 2015
- Messages
- 36
- Reaction score
- 0
First to answer the char getting stuck in town thing. Best you can do is set up YAR with a low inactivity timer to fully reboot the bot if inactive but that will prob cause other issues.
second the entire point on autofollow is not to have them follow but for the bots to act as one team fighting as a team so yes the plugin works with trinity and yes all 4 bots do fight. This is meant for in grifts where if the bots spilt up they lose a ton of time resulting in a lower max grift. EG last season using simplefollow (the outdated old version of auto follow) bots where about to break 170M+ exp an hour.
As for being able to spilt up while using auto follow at this point no its not possible as that its directly opposite of what its meant to be doing. That being said as the plugin is not fully working so the bots don;t stay together perfectly right now it is possible to have them doing what you want. As by running each bot with the rifting profile (not with the followercombat profile), The follower bots will spread out to a degree and fight if one gets stuck out of the rift the auto follower plugin kicks in and moves them into the rift. That being said if they get X distance apart the plugin kicks in and moves them close but if you set the distance to be far apart it should kick in less and only bring them into the rift. Currently max follow distance is 150 so like 2 screens only.
Also another advantage of the auto follow plugin is if a bot dcs or gets kicked for the party for any reason (even if the game randomly closes) between yar and auto follow the bot can start iteself back up and rejoin the game without issue. (this currently dosen't work as Yar is broken but the dev has posted it will be fixed in next version.)
totalschaden
Active Member
- Joined
- Feb 16, 2010
- Messages
- 1,146
- Reaction score
- 1
Cannot get it to work when Clients are not on the same Network, is it even supported ?
Yes, me and a friend of mine got it working over the internet. The 'host' has to put his own IP in autofollow for it to work. And of course the correct port forwarding is required.
Thanks so much man, your the best. Wish I could help you out somehow or return the favour, let me know if u need help for something.
Where do I get this YAR?
So if I setup Auto-follow up ASAP and don't update it, it should work like I wanted? and it doesn't cause other problems, like let's say your main get stuck? then all 4 chars is stuck?
razzysnazzy
New Member
- Joined
- Aug 28, 2015
- Messages
- 36
- Reaction score
- 0
Thanks so much man, your the best. Wish I could help you out somehow or return the favour, let me know if u need help for something.
Where do I get this YAR?
So if I setup Auto-follow up ASAP and don't update it, it should work like I wanted? and it doesn't cause other problems, like let's say your main get stuck? then all 4 chars is stuck?
https://www.thebuddyforum.com/demonbuddy-forum/plugins/223560-plugin-yar-relogger.html
But as I said auto follow is currently not working with yar, Thou xj has said next version will.
If a main gets stuck trinity inactivity timmer after 600 secs will remake the game with or without yar. Thou if using yar with a low inactivty timer the main would also just be fully reset.
As for getting autofollow now and not updating it it might with your trinnity settings just forcing them into the rift if they don't go in on there own but the current version has other bugs such as a delay after entering a rift. you can try and see if it works better the effort taken is small so its worth the time.
Mainly autofollow is a script meant for grifts and keeping the bots as one small unit so what your doing without autofollow will prob be better for normal rifting than set autofollow up for grift (I would just stock up keys till next version thou for grfits if your bots are working that well in rifts.)
im trying to set this up between two computers (main PC and Laptop)
I've tried almost every combination to get this working but they don't communicate.
I've opened the ports on both computers.
if someone could assist via skype that would be fantastic!
I've tried almost every combination to get this working but they don't communicate.
I've opened the ports on both computers.
if someone could assist via skype that would be fantastic!
Same!! I bet someone 50$ that they cant get this to work on my LAN desk top computers!!
Carboncloud
New Member
- Joined
- Jan 16, 2016
- Messages
- 28
- Reaction score
- 0
Can you make this work with the leader status set to busy? I can't see taking busy off ever again. This is the first season I tried the "best bot" for DIII and there is now a 25000 view YouTube video of my account being PK'd so turning off busy is not an option. Thanks in advance if you can get this to work with leader on busy.
I'm using it for 4 toons :
- 2 at home, on same LAN ( 1 leader, 1 follower )
- 2 through internet, ( 2 friends who are botting too ) , following my leader
Just : AMAZING !
I posted this a few month ago :
I'll try to explain how i made it work, i spent some hours before it works.
First : Disable the fucking Windows Firewall : that's why it didn't work for me. And disable the firewall in your antivirus software too.
If you know how to do it, you can create a rule, saying "accept connexion on the simple follow port". Default port is 10920
On the leader char, simple follow option : ip = localhost.
In windows : execute, type CMD, and ipconfig. You will get your local network ip. ( example : 192.168.1.10 ).
Now load a profile.
On the follower, simple follow option : ip = 192.168.1.10 ( in our example ).
Load profile : SimpleFollow.xml.
Start, profit. Follower is in the same house, same local network.
If you want a friend to follow too :
- On the computer of the main char : go here Quelle est mon adresse IP? Outils de l'adresse IP et davantage. Example : 185.12.1.241
This is your internet IP.
- On your friend follower, open simple follow option, enter the IP ( in our example 185.12.1.241 ).
Last, but not least.
The main char must config his routeur to accept connexion on port 10920.
You can find how to do this, google it.
Often, you can access routeur setting, opening internet explorer, and enter the routeur IP adress : 192.168.1.1
You must find NAT, enter the main computer IP ( in our example 192.168.1.10 ), and adding the port 10920.
Yasuko
Member
- Joined
- Oct 28, 2010
- Messages
- 314
- Reaction score
- 6
^this. On most routers it will be under "port forwarding".
1) So I can't use this? Does it work if I don't use AutoFollow?
2) If I use autofollow and 1 char gets stuck (the main char), does that get everyone stuck? And, let's say I use inactivity timer, and they leave after 100 seconds, do ALL 4 chars leave and the main press Start game? And it works again?
3) And, if 1 char gets stuck in town, does it teleport to the main automatically?
CHEERS A LOT, You Answers are REALLY appreciated !!
xzjv
Community Developer
- Joined
- Mar 17, 2014
- Messages
- 1,243
- Reaction score
- 46
1.0.10
TY for your support.
- Tested running on Bounties, Ubers, Key wardens, Greater/Neph rifts and Manual follow.
- Now Supports YAR (should work best with "kickstart" disabled in YAR settings)
- Added LeaderManual.xml profile for having the bots follow you while you play by hand.
- Bots should no longer get separated as much. It effectively goes into a zerg mode when out of range.
- Bots should now follow leader through portal and try their luck with nearby portals if lost.
- Movement has been heavily refactored, now uses a local actor where possible and has faster reactions.
- Added setting for max leader waits for others before starting a profile (will start sooner if everyone is near)
- Improved how the bot waits before starting games and after changing levels to ensure everyone is present.
- Bot should have less memory related exceptions now.
- Improved out of game handling of parties and invites.
- Technical: Removed speed limits on communication, now runs smoothly down to 25ms.
- Technical: Bot now only accesses DB memory in framelock and communication thread reads cached values.
- Technical: Bot now reads names in party lobby out of game to tell if the leader is present.
- Technical: Improved event system, including limits on how fast they can queue up.
- Technical: Changed the way settings are saved to use a new JSON based system.
- Technical: Refactored pretty much everything else + Many other small bug fixes.
- Note: For best results make sure your profiles have stayInParty="true" on LeaveGame tags.
- Note: Completely remove old plugin version before installing.
- Note: folder name has changed in plugins directory to 'zAutoFollow'
TY for your support.